Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #255507
| From | davenull@tuxfamily.org |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable |
| Date | 2023-03-02 16:20 +0100 |
| Message-ID | <G4SSR-9zXV-1@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <G4NzP-9w9K-3@gated-at.bofh.it> <G4Qo1-9yiL-3@gated-at.bofh.it> <G4QxH-9ymn-1@gated-at.bofh.it> <G4QR3-9yJb-5@gated-at.bofh.it> <G4R0K-9yMY-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2023-03-02 14:19, Greg Wooledge wrote:
> On Thu, Mar 02, 2023 at 02:01:57PM +0100, davenull@tuxfamily.org wrote:
>
>> > > > akb@akira:~$ LC_ALL=C aptitude why ifupdown
>> > > > p netscript-2.4 Provides ifupdown
>> > > > p netscript-2.4 Depends bridge-utils (>= 0.9.3)
>> > > > p bridge-utils Suggests ifupdown
>> > > > akb@akira:~$ LC_ALL=C aptitude why netscript-2.4
>> > > > p netscript-2.4 Provides ifupdown
>
>> dpkg -l netscript-2.4 or even dpkg -l | grep netscript
>>
>> Don't return anything… Not sure why "aptitude why ifupdown" mentions
>> netscript-2.4 at all
>
> Oh, that's reassuring. And also confusing.
>
> Man, I really wish the aptitude(8) man page would explain how to read
> the output of "why". What does the "p" mean? Purged? There's nothing
> in the man page that explains the symbols in the first 3 columns, as
> far as I can find.
I wonder if aptitude just uses the dpkg-query abbreviations,
so "purged" seems a reasonable guess. But yeah, it would be
much more helpful if aptitude(8) man was not that ambiguous
about those abbreviations
>
> I have *no* idea how to interpret this:
>
> unicorn:~$ aptitude why ifupdown
> p netscript-2.4 Provides ifupdown
> p netscript-2.4 Depends bridge-utils (>= 0.9.3)
> p bridge-utils Suggests ifupdown
> unicorn:~$ dpkg -l ifupdown | tail -n1
> ii ifupdown 0.8.36 amd64 high level tools to
> configure network interfaces
>
> Maybe "aptitude why" simply can't handle packages that are part of
> the base system ("Essential", or priority "required" or "important"),
> or which have been manually installed and aren't part of a
> dependency...?
>
> unicorn:~$ aptitude why bash
> i bash-builtins Depends bash (= 5.1-2+deb11u1)
> unicorn:~$ aptitude why dpkg
> i google-chrome-stable PreDepends dpkg (>= 1.14.0)
> unicorn:~$ aptitude why abcde
> Manually installed, current version 2.9.3-1, priority optional
> No dependencies require to install abcde
>
> OK, I guess it handles manually installed packages. But not base
> system packages... at least not in a way one would expect.
>
> In any case, ifupdown is an "important" package, and should be present
> on almost all Debian systems, regardless of what "aptitude why" says
> about it.
>
> unicorn:~$ dpkg -s ifupdown | grep Prio
> Priority: important
Good to know. I'd except it to be installed by default by the way.
Looking again at files in /etc/network, there are
drwxr-xr-x 2 root root 4096 2 déc. 2021 if-post-down.d
drwxr-xr-x 2 root root 4096 2 déc. 2021 if-pre-up.d
The laptop was installed on the 2nd December 2021, so the files existed
from day one,
But if-down.d and if-up.d content was updated later.
Must by the reason why someone (don't remember their name) on this
thread suggested I have installed
ifupdown a few months laters.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-22 18:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Roberto C. Sánchez <roberto@debian.org> - 2023-02-22 18:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Christoph Brinkhaus <c.brinkhaus@t-online.de> - 2023-02-22 18:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Reco <recoverym4n@enotuniq.net> - 2023-02-23 18:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-22 19:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-22 22:10 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 10:50 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-23 11:00 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-24 06:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-24 06:50 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-24 10:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-02-24 10:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-24 11:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable tomas@tuxteam.de - 2023-02-24 11:50 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-27 15:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-27 15:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-02-24 13:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-25 01:30 +0100
Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-02 11:50 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available Tim Woodall <debianuser@woodall.me.uk> - 2023-03-03 04:10 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-03 06:30 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available Tim Woodall <debianuser@woodall.me.uk> - 2023-03-03 07:40 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-03 16:10 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 16:20 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-06 13:40 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-07 05:10 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 17:20 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-10 02:00 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-06 13:20 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-07 05:10 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 17:00 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available Max Nikulin <manikulin@gmail.com> - 2023-03-07 16:30 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-07 18:00 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-10 02:00 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-10 09:50 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 06:30 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available davenull@tuxfamily.org - 2023-03-03 18:10 +0100
Re: Forcing dhclient to not ignore tun0 interface when it's available David Wright <deblis@lionunicorn.co.uk> - 2023-03-04 18:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Cindy Sue Causey <butterflybytes@gmail.com> - 2023-02-23 02:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable conover@panix.com (John Conover) - 2023-02-23 03:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-23 11:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Jeremy Ardley <jeremy@ardley.org> - 2023-02-23 11:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-02-28 05:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-02-28 16:10 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Tixy <tixy@yxit.co.uk> - 2023-02-28 17:00 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-02 00:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 10:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-03-02 13:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 13:50 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 14:10 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Greg Wooledge <greg@wooledge.org> - 2023-03-02 14:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable davenull@tuxfamily.org - 2023-03-02 16:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David <bouncingcats@gmail.com> - 2023-03-02 16:40 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David <bouncingcats@gmail.com> - 2023-03-02 16:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable Curt <curty@free.fr> - 2023-03-02 18:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-02 19:20 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable <tomas@tuxteam.de> - 2023-03-02 20:30 +0100
Re: Debugging what is deleting/recreating /etc/resolv.conf with wrong configuration, on debian stable David Wright <deblis@lionunicorn.co.uk> - 2023-03-03 06:20 +0100
csiph-web