Re: [DNG] Unix Socket class: how to send arguments to the suid of simple-netaid
Hi,
On 12/9/19 6:49, aitor_czr wrote:
Maybe you are wondering about the reaseon why the server of the socket
should be multithreaded.
Well... Download the following example:
http://gnuinos.org/socket/ip/
The code of the server has been replaced by:
serverSocket( { FILE_DESCRIPTOR, "0", "wlan0" } );
system("sudo ./client");
That is, the information is sent through the file descriptor and
immediatly after the client is run *while*
the server is waiting to be heard in a separate thread.
Just run:
$ ./server
and your network interface (wlan0) will be brung down.
Cheers,
Aitor.
There were some minor error in the example. For example, the name of the
object in the constructor of the server was missing:
serverSocket sender( { FILE_DESCRIPTOR, "0", "wlan0" } );
I fixed them, and now it works:
http://gnuinos.org/socket/ip/
Cheers,
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Can't grub ignore /dev/hdb?
Haven't replaced /dev/hdb yet. Is there some way of getting it ignored in the following scenario? I started aptitude. It told me it hadn't been cleanly shut down last time, and recommended I do dpkg --configure -a before I do anything else. I do that, and the system apparently does some cleanup, generating initrd images, and then starts to update grub. Update-grub stalls on block 51 of device /dev/hdb, trying to do something with it over and over (as presented on the main system console, which is *not* the one I'm trying to run aptitude on) Now evidently /dev/hdb is not working and will need to be replaced. But isn't there some way to tell grub to ignore /dev/hdb? What is it that controls which drives grub tries to work with. It must get this from somewhere. I did not specify or mention /dev/hdb anywhere in my dpkg --configure -a. And there are several other drives I could use to install grub and a boot record. I can even use the grub-install command to do so. So why, oh why, does it pick on /dev/sdb? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can't grub ignore /dev/hdb?
On 2019-09-13 16:24, Hendrik Boom wrote: Haven't replaced /dev/hdb yet. Is there some way of getting it ignored in the following scenario? I started aptitude. It told me it hadn't been cleanly shut down last time, and recommended I do dpkg --configure -a before I do anything else. I do that, and the system apparently does some cleanup, generating initrd images, and then starts to update grub. Update-grub stalls on block 51 of device /dev/hdb, trying to do something with it over and over (as presented on the main system console, which is *not* the one I'm trying to run aptitude on) Now evidently /dev/hdb is not working and will need to be replaced. But isn't there some way to tell grub to ignore /dev/hdb? What is it that controls which drives grub tries to work with. It must get this from somewhere. I did not specify or mention /dev/hdb anywhere in my dpkg --configure -a. And there are several other drives I could use to install grub and a boot record. I can even use the grub-install command to do so. So why, oh why, does it pick on /dev/sdb? -- hendrik Open the case and unplug it? (golinux ducks and runs) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can't grub ignore /dev/hdb?
On 9/13/19 5:43 PM, goli...@devuan.org wrote: On 2019-09-13 16:24, Hendrik Boom wrote: Haven't replaced /dev/hdb yet. Is there some way of getting it ignored in the following scenario? I started aptitude. It told me it hadn't been cleanly shut down last time, and recommended I do dpkg --configure -a before I do anything else. I do that, and the system apparently does some cleanup, generating initrd images, and then starts to update grub. Update-grub stalls on block 51 of device /dev/hdb, trying to do something with it over and over (as presented on the main system console, which is *not* the one I'm trying to run aptitude on) Now evidently /dev/hdb is not working and will need to be replaced. But isn't there some way to tell grub to ignore /dev/hdb? What is it that controls which drives grub tries to work with. It must get this from somewhere. I did not specify or mention /dev/hdb anywhere in my dpkg --configure -a. And there are several other drives I could use to install grub and a boot record. I can even use the grub-install command to do so. So why, oh why, does it pick on /dev/sdb? -- hendrik Open the case and unplug it? (golinux ducks and runs) Golinux beat me to it. update-grub (grub-mkconfig) uses black magic to find all the bootable systems within reach. I read that somewhere in the comments in one of the grub scripts. (Note: It won't find encrypted systems except for the one that's running update-grub.) It... wait... what? hdb? I hope that's a typo. If the disk is dying, make sure you have everything you want off of it before you unplug it. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed
I forgot to mention that after the reboot, after the reboot, in addition to the delay in starting dbus and avahi-daemon and the difficulties to login I cannot access to the GUI, only by console > > From: José Marinho > Sent: Tue Sep 10 21:40:42 CEST 2019 > To: Mark Hindley , devuan developers internal list > , Dng > Subject: Re: [devuan-dev] [DNG] Migrating from Buster to Beowulf - feedback > needed > > > Hi all, > > From a brand new debian server installation on Virtualbox I install desktop > stuff by installing task-xfce-destop metapackage and try your instructions. I > don't know if I miss or misunderstand something. What I got was this: > > After installing devuan-keyring, changing apt sources, updating apt sources, > editing /var/lib/dpkg/status file for removing systemd-sysv of the end of the > line, do an "apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd" > and rebooting the system, when I rebooted I notice that > when the system start after the reboot, it gets stuck on dbus and > avahi-daemon delaying init much more than usual. Besides this, it delays too > a lot when I try to log in the system by console or ssh. When I finally reach > a root console and issue : "apt install --purge policykit-1" I get this > output: > > apt install --purge policykit-1 > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > policykit-1 : Depends: libpolkit-agent-1-0 (= 0.105-25+devuan4) but 0.105-25 > is to be installed >Depends: libpolkit-backend-1-0 (= 0.105-25+devuan4) >Depends: libpolkit-gobject-1-0 (= 0.105-25+devuan4) > E: Unable to correct problems, you have held broken packages. > > I hope this will help > > Jose > > > > > From: Mark Hindley > > Sent: Tue Sep 10 13:59:58 CEST 2019 > > To: devuan developers internal list , Dng > > > > Subject: Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback > > needed > > > > > > I have been further testing ways of migrating buster to beowulf. > > > > With a install of xfce4 and lightdm, the cleanest way I can come up with is: > > > > # Migrate from Debian buster to Devuan beowulf > > > > # Install devuan-keyring > > wget > > http://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2017.10.03_all.deb > > dpkg -i devuan-keyring_2017.10.03_all.deb > > > > # Change APT sources > > cat > /etc/apt/sources.list < > deb http://pkgmaster.devuan.org/merged beowulf main > > deb http://pkgmaster.devuan.org/merged beowulf-security main > > EOF > > > > apt update > > > > # If you have libpam-systemd installed this is an optional and very hackish > > fix > > # for Debian #935304 which is now closed with wontfix. > > # > > # Don't do this if you are at all unsure. > > # > > # 1) Ensure you create a backup! > > # 2) Open /var/lib/dpkg/status with an editor > > # 3) Find libpam-systemd Depends. The line looks like > > # Depends: libc6 (>= 2.28), libpam0g (>= 0.99.7.1), systemd (= > > 241-7~deb10u1), libpam-runtime (>= 1.0.1-6), dbus, systemd-sysv > > # 4) Remove ', systemd-sysv from the end of the line, leaving the rest of > > the line intact > > # 5) Save file > > cp /var/lib/dpkg/status /var/lib/dpkg/status.save > > editor /var/lib/dpkg/status > > > > # Install new init and dbus. > > # Ensure we will have dbus-x11 to provide dbus-session-bus after systemd is > > gone. > > # Remove libnss-systemd to avoid delays on nss lookups after reboot. > > apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd- > > > > reboot > > > > # If you have policykit-1 installed, update it. > > # This will also purge systemd* and install libpam-elogind > > apt install --purge policykit-1 > > > > # The rest of the migration (base-files, eudev, etc) > > # This will also purge sytemd* if not already done. > > apt --purge full-upgrade > > > > # Optionally, if you didn't edit /var/lib/dpkg/status above > > # Reinstall whatever desktop and display manager was removed > > # apt install xfce4 lightdm > > > > # Change ens3 to eth0 in /etc/network/interfaces > > sed s/ens3/eth0/ -i /etc/network/interfaces > > > > reboot > > > > # Remove cruft > > apt autoremove --purge > > > > Done! > > > > The transitional systemd-sysv package I talked about a few days ago to > > smooth > > over #935304 isn't going to work as I had forgotten that sysvinit-core > > conflicts > > with systemd-sysv. > > > > The hack to work around #935304 by editing /var/lib/dpkg/status is not > > pretty at > > all. If you don't
Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed
Hi all, From a brand new debian server installation on Virtualbox I install desktop stuff by installing task-xfce-destop metapackage and try your instructions. I don't know if I miss or misunderstand something. What I got was this: After installing devuan-keyring, changing apt sources, updating apt sources, editing /var/lib/dpkg/status file for removing systemd-sysv of the end of the line, do an "apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd" and rebooting the system, when I rebooted I notice that when the system start after the reboot, it gets stuck on dbus and avahi-daemon delaying init much more than usual. Besides this, it delays too a lot when I try to log in the system by console or ssh. When I finally reach a root console and issue : "apt install --purge policykit-1" I get this output: apt install --purge policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: policykit-1 : Depends: libpolkit-agent-1-0 (= 0.105-25+devuan4) but 0.105-25 is to be installed Depends: libpolkit-backend-1-0 (= 0.105-25+devuan4) Depends: libpolkit-gobject-1-0 (= 0.105-25+devuan4) E: Unable to correct problems, you have held broken packages. I hope this will help Jose > > From: Mark Hindley > Sent: Tue Sep 10 13:59:58 CEST 2019 > To: devuan developers internal list , Dng > > Subject: Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback > needed > > > I have been further testing ways of migrating buster to beowulf. > > With a install of xfce4 and lightdm, the cleanest way I can come up with is: > > # Migrate from Debian buster to Devuan beowulf > > # Install devuan-keyring > wget > http://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2017.10.03_all.deb > dpkg -i devuan-keyring_2017.10.03_all.deb > > # Change APT sources > cat > /etc/apt/sources.list < deb http://pkgmaster.devuan.org/merged beowulf main > deb http://pkgmaster.devuan.org/merged beowulf-security main > EOF > > apt update > > # If you have libpam-systemd installed this is an optional and very hackish > fix > # for Debian #935304 which is now closed with wontfix. > # > # Don't do this if you are at all unsure. > # > # 1) Ensure you create a backup! > # 2) Open /var/lib/dpkg/status with an editor > # 3) Find libpam-systemd Depends. The line looks like > # Depends: libc6 (>= 2.28), libpam0g (>= 0.99.7.1), systemd (= > 241-7~deb10u1), libpam-runtime (>= 1.0.1-6), dbus, systemd-sysv > # 4) Remove ', systemd-sysv from the end of the line, leaving the rest of the > line intact > # 5) Save file > cp /var/lib/dpkg/status /var/lib/dpkg/status.save > editor /var/lib/dpkg/status > > # Install new init and dbus. > # Ensure we will have dbus-x11 to provide dbus-session-bus after systemd is > gone. > # Remove libnss-systemd to avoid delays on nss lookups after reboot. > apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd- > > reboot > > # If you have policykit-1 installed, update it. > # This will also purge systemd* and install libpam-elogind > apt install --purge policykit-1 > > # The rest of the migration (base-files, eudev, etc) > # This will also purge sytemd* if not already done. > apt --purge full-upgrade > > # Optionally, if you didn't edit /var/lib/dpkg/status above > # Reinstall whatever desktop and display manager was removed > # apt install xfce4 lightdm > > # Change ens3 to eth0 in /etc/network/interfaces > sed s/ens3/eth0/ -i /etc/network/interfaces > > reboot > > # Remove cruft > apt autoremove --purge > > Done! > > The transitional systemd-sysv package I talked about a few days ago to smooth > over #935304 isn't going to work as I had forgotten that sysvinit-core > conflicts > with systemd-sysv. > > The hack to work around #935304 by editing /var/lib/dpkg/status is not pretty > at > all. If you don't want it you will have to accept removal of some GUI > components > with libpam-systemd and then reinstall them after libpam-elogind is in place. > > I hope the instructions are reasonably clear. > > Do give feedback. > > Thanks > > Mark > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Sent with https://mailfence.com Secure and private email ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed
For the first point, you are right, the final hyphen makes a big difference and now I am free of the dbus delay and can reach a GUI through Lightdm. But the other issue persists: root@dserver:~# apt install --purge policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: policykit-1 : Depends: libpolkit-agent-1-0 (= 0.105-25+devuan4) but 0.105-25 is to be installed Depends: libpolkit-backend-1-0 (= 0.105-25+devuan4) Depends: libpolkit-gobject-1-0 (= 0.105-25+devuan4) E: Unable to correct problems, you have held broken packages. I'm going to post you the output of some commands with the hope it may help you to understand: root@dserver:~# cat /etc/apt/preferences cat: /etc/apt/preferences: No such file or directory root@dserver:~# ls -l /etc/apt/preferences.d/ total 0 Like I mentioned on my previous post, the system I'm using for this tests is a Virtualbox VM with Debian server installed with a netinstall image and after that I install the metapackage task-xfce-desktop, but I did not change any preference from the stock that comes from Debian root@dserver:~# apt policy policykit-1 policykit-1: Installed: 0.105-25 Candidate: 0.105-25+devuan4 Version table: 0.105-25+devuan4 500 500 http://pkgmaster.devuan.org/merged beowulf/main amd64 Packages *** 0.105-25 100 100 /var/lib/dpkg/status root@dserver:~# apt policy libpolkit-agent-1-0 libpolkit-agent-1-0: Installed: 0.105-25 Candidate: 0.105-25+devuan4 Version table: 0.105-25+devuan4 500 500 http://pkgmaster.devuan.org/merged beowulf/main amd64 Packages *** 0.105-25 100 100 /var/lib/dpkg/status root@dserver:~# apt policy libpolkit-backend-1-0 libpolkit-backend-1-0: Installed: 0.105-25 Candidate: 0.105-25 Version table: *** 0.105-25 500 500 http://pkgmaster.devuan.org/merged beowulf/main amd64 Packages 100 /var/lib/dpkg/status root@dserver:~# apt policy libpolkit-gobject-1-0 libpolkit-gobject-1-0: Installed: 0.105-25 Candidate: 0.105-25 Version table: *** 0.105-25 500 500 http://pkgmaster.devuan.org/merged beowulf/main amd64 Packages 100 /var/lib/dpkg/status If you need more info don't hesitate to ask for it. Thanks José > > From: Mark Hindley > Sent: Tue Sep 10 22:28:06 CEST 2019 > To: José Marinho > Cc: devuan developers internal list , Dng > > Subject: Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback > needed > > > José, > > Hello. Thanks for this. > > On Tue, Sep 10, 2019 at 09:40:42PM +0200, José Marinho wrote: > > Hi all, > > > > >From a brand new debian server installation on Virtualbox I install desktop > > >stuff by installing task-xfce-destop metapackage and try your > > >instructions. I > > >don't know if I miss or misunderstand something. What I got was this: > > > > After installing devuan-keyring, changing apt sources, updating apt sources, > > editing /var/lib/dpkg/status file for removing systemd-sysv of the end of > > the > > line, do an "apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd" > > Could you check that line. It may just be a typo, but should be > > apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd- > > with a hyphen at the end. That cured the dbus delays for me. > > > and rebooting the system, when I rebooted I notice that when the system > > start > > after the reboot, it gets stuck on dbus and avahi-daemon delaying init much > > more than usual. Besides this, it delays too a lot when I try to log in the > > system by console or ssh. When I finally reach a root console and issue : > > "apt > > install --purge policykit-1" I get this output: > > > > apt install --purge policykit-1 > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > policykit-1 : Depends: libpolkit-agent-1-0 (= 0.105-25+devuan4) but > > 0.105-25 is to be installed > >Depends: libpolkit-backend-1-0 (= 0.105-25+devuan4) > >Depends: libpolkit-gobject-1-0 (= 0.105-25+devuan4) > > This is odd as 0.105-25 is the buster version. > > I had tested this from xfce4 install but not the task
Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed
Finally, I managed to get to Beowulf from Buster by doing what is indicated in the text file I send as an attachment. Hope it would be helpful. Jose > > From: Mark Hindley > Sent: Wed Sep 11 12:08:53 CEST 2019 > To: José Marinho > Cc: devuan developers internal list , Dng > > Subject: Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback > needed > > > On Wed, Sep 11, 2019 at 10:41:29AM +0200, José Marinho wrote: > > For the first point, you are right, the final hyphen makes a big difference > > and now I am free of the dbus delay and can reach a GUI through Lightdm. > > Great! > > > But the other issue persists: > > root@dserver:~# apt install --purge policykit-1 > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > policykit-1 : Depends: libpolkit-agent-1-0 (= 0.105-25+devuan4) but > > 0.105-25 is to be installed > >Depends: libpolkit-backend-1-0 (= 0.105-25+devuan4) > >Depends: libpolkit-gobject-1-0 (= 0.105-25+devuan4) > > E: Unable to correct problems, you have held broken packages. > > I think this is a problem in devuan's task-xfce-desktop. > > We are quite behind debian (buster has 3.53, beowulf has 3.48+devuan1.1) and > devuan's version also has a (now) unhelpful dependency on > libpolkit-backend-consolekit-1-0. > > Could you try removing task-xfce-desktop first? > > Thanks. > > Mark -- Sent with https://mailfence.com Secure and private emailroot@dserver:~# wget http://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2017.10.03_all.deb --2019-09-11 17:39:21-- http://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2017.10.03_all.deb Resolving pkgmaster.devuan.org (pkgmaster.devuan.org)... 5.196.38.18 Connecting to pkgmaster.devuan.org (pkgmaster.devuan.org)|5.196.38.18|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 34728 (34K) [application/octet-stream] Saving to: ‘devuan-keyring_2017.10.03_all.deb’ devuan-keyring_2017 100%[===>] 33.91K --.-KB/sin 0.06s 2019-09-11 17:39:37 (607 KB/s) - ‘devuan-keyring_2017.10.03_all.deb’ saved [34728/34728] root@dserver:~# dpkg -i devuan-keyring_2017.10.03_all.deb Selecting previously unselected package devuan-keyring. (Reading database ... 104747 files and directories currently installed.) Preparing to unpack devuan-keyring_2017.10.03_all.deb ... Unpacking devuan-keyring (2017.10.03) ... Setting up devuan-keyring (2017.10.03) ... root@dserver:~# cat > /etc/apt/sources.list < deb http://pkgmaster.devuan.org/merged beowulf main > deb http://pkgmaster.devuan.org/merged beowulf-security main > EOF root@dserver:~# apt update Get:1 http://pkgmaster.devuan.org/merged beowulf InRelease [25.6 kB] Get:2 http://pkgmaster.devuan.org/merged beowulf-security InRelease [25.6 kB] Get:3 http://pkgmaster.devuan.org/merged beowulf/main amd64 Packages [8,046 kB] Get:4 http://pkgmaster.devuan.org/merged beowulf-security/main amd64 Packages [85.5 kB] Fetched 8,183 kB in 31s (262 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 12 packages can be upgraded. Run 'apt list --upgradable' to see them. root@dserver:~# apt list --upgradable Listing... Done base-files/testing 10.3+devuan3.1 amd64 [upgradable from: 10.3+deb10u1] dbus-x11/testing 1.12.16-1+devuan2 amd64 [upgradable from: 1.12.16-1] dbus/testing 1.12.16-1+devuan2 amd64 [upgradable from: 1.12.16-1] desktop-base/testing 1:0.99 all [upgradable from: 10.0.2] gir1.2-polkit-1.0/testing 0.105-25+devuan4 amd64 [upgradable from: 0.105-25] libdbus-1-3/testing 1.12.16-1+devuan2 amd64 [upgradable from: 1.12.16-1] libpolkit-agent-1-0/testing 0.105-25+devuan4 amd64 [upgradable from: 0.105-25] libudev1/testing 1:3.2.7+devuan1.1 amd64 [upgradable from: 241-7~deb10u1] policykit-1/testing 0.105-25+devuan4 amd64 [upgradable from: 0.105-25] sysvinit-utils/testing 2.93-8+devuan1 amd64 [upgradable from: 2.93-8] udev/testing 1:3.2.7+devuan1.1 amd64 [upgradable from: 241-7~deb10u1] upower/testing 1:0.9.23-2+devuan1.3 amd64 [upgradable from: 0.99.10-1] cp /var/lib/dpkg/status /var/lib/dpkg/status.save nano /var/lib/dpkg/status root@dserver:~# apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd- Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: initscripts insserv libdbus-1-3 psmisc startpar sysv-rc Suggested packages:
Re: [DNG] Can't grub ignore /dev/hdb?
On Fri, Sep 13, 2019 at 06:50:05PM -0400, fsmithred via Dng wrote: > On 9/13/19 5:43 PM, goli...@devuan.org wrote: > > On 2019-09-13 16:24, Hendrik Boom wrote: > > > Haven't replaced /dev/hdb yet. > > > Is there some way of getting it ignored in the following scenario? > > > > > > I started aptitude. > > > It told me it hadn't been cleanly shut down last time, and recommended > > > I do > > > dpkg --configure -a > > > before I do anything else. > > > > > > I do that, and the system apparently does some cleanup, generating > > > initrd images, and then starts to update grub. > > > > > > Update-grub stalls on block 51 of device /dev/hdb, trying to do > > > something with it over and over (as presented on the main system > > > console, which is *not* the one I'm trying to run aptitude on) > > > > > > Now evidently /dev/hdb is not working and will need to be replaced. > > > > > > But isn't there some way to tell grub to ignore /dev/hdb? > > > What is it that controls which drives grub tries to work with. > > > It must get this from somewhere. I did not specify or mention /dev/hdb > > > anywhere in my dpkg --configure -a. And there are several other drives > > > I could use to install grub and a boot record. I can even use the > > > grub-install command to do so. So why, oh why, does it pick on > > > /dev/sdb? > > > > > > -- hendrik > > > > > > > > > > Open the case and unplug it? > > > > (golinux ducks and runs) > > > Golinux beat me to it. > > update-grub (grub-mkconfig) uses black magic to find all the bootable > systems within reach. That's useful information. It does suggest that I have to unplug to get update-grub to work. Does that mean if I temporarily have a disk drive plugged in for any temporary readon, it'll be found and get grub boot records installed on it? Sonds ike it. > I read that somewhere in the comments in one of the > grub scripts. (Note: It won't find encrypted systems except for the one > that's running update-grub.) > > It... wait... what? hdb? I hope that's a typo. > > If the disk is dying, make sure you have everything you want off of it > before you unplug it. > > fsmithred > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Can't grub ignore /dev/hdb?
Hendrik Boom wrote on 14/9/19 1:03 pm: > On Fri, Sep 13, 2019 at 06:50:05PM -0400, fsmithred via Dng wrote: >> On 9/13/19 5:43 PM, goli...@devuan.org wrote: >>> On 2019-09-13 16:24, Hendrik Boom wrote: Haven't replaced /dev/hdb yet. Is there some way of getting it ignored in the following scenario? I started aptitude. It told me it hadn't been cleanly shut down last time, and recommended I do dpkg --configure -a before I do anything else. I do that, and the system apparently does some cleanup, generating initrd images, and then starts to update grub. Update-grub stalls on block 51 of device /dev/hdb, trying to do something with it over and over (as presented on the main system console, which is *not* the one I'm trying to run aptitude on) Now evidently /dev/hdb is not working and will need to be replaced. But isn't there some way to tell grub to ignore /dev/hdb? What is it that controls which drives grub tries to work with. It must get this from somewhere. I did not specify or mention /dev/hdb anywhere in my dpkg --configure -a. And there are several other drives I could use to install grub and a boot record. I can even use the grub-install command to do so. So why, oh why, does it pick on /dev/sdb? -- hendrik >>> >>> Open the case and unplug it? >>> >>> (golinux ducks and runs) >> >> >> Golinux beat me to it. >> >> update-grub (grub-mkconfig) uses black magic to find all the bootable >> systems within reach. > > That's useful information. It does suggest that I have to unplug to > get update-grub to work. > > Does that mean if I temporarily have a disk drive plugged in for any > temporary readon, it'll be found and get grub boot records installed on > it? > > Sonds ike it. > That same question apparently came up a while ago at https://unix.stackexchange.com/questions/56004/how-to-stop-update-grub-from-scanning-all-drives In short: do something to /etc/grub.d/30_os-prober (which is a shell script) Ralph. >> ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
