Re: [DNG] installer woe -- Solved
On Tue, Jun 26, 2018 at 08:38:28AM -0500, d_pridge wrote: > > Original message From: KatolaZ Date: > 6/26/18 8:03 AM (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] > installer woe > On Tue, Jun 26, 2018 at 02:47:17PM +0200, Alessandro Selli wrote: > > [cut] > > > > > > > It will boot the Purism installer from a USB stick if I use the same > > > steps, starting wth the Purism ISO file, of course. > > > > > > So there is something else going on. > > > > If you didn't do it already, try to boot Purism from the same USB stick. > > > > > > guys, according to a previous email it seems it was just a broken usb > stick :) I haven't had that happen to me in years; that's why I didn't suss it out sooner. What clued me in that it was the stick was when I put it into the very USB socket I had used when writing out the ISO, and it didn't even assign a /dev/usb to it. It was as if it wasn't there -- exactly how the new compuer had treated it too. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] installer woe
In the event debootstrap fails, a list of the essential packages would help all those who, in the most extreme case of installation failures, want to manually extract them to an empty partition and do the packages' configuration manually. As far as I remember, Debian requires essential packages to function even if they fail to configure themselves in their installation. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
Original message From: KatolaZ Date: 6/26/18 8:03 AM (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] installer woe On Tue, Jun 26, 2018 at 02:47:17PM +0200, Alessandro Selli wrote: [cut] > > > > It will boot the Purism installer from a USB stick if I use the same > > steps, starting wth the Purism ISO file, of course. > > > > So there is something else going on. > > If you didn't do it already, try to boot Purism from the same USB stick. > > guys, according to a previous email it seems it was just a broken usb stick :) -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux The Chinese versions don't work well for supplying executable code, even though the check sum verifies correctly. Dan.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
On Tue, Jun 26, 2018 at 02:47:17PM +0200, Alessandro Selli wrote: [cut] > > > > It will boot the Purism installer from a USB stick if I use the same > > steps, starting wth the Purism ISO file, of course. > > > > So there is something else going on. > > If you didn't do it already, try to boot Purism from the same USB stick. > > guys, according to a previous email it seems it was just a broken usb stick :) -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
Il giorno Mon, 25 Jun 2018 23:43:04 -0400 Hendrik Boom ha scritto: > On Tue, Jun 26, 2018 at 07:25:48AM +0200, Didier Kryn wrote: >> Le 25/06/2018 à 20:23, Hendrik Boom a écrit : >>>I used dd to copy the installer iso to a USB stck on my old laptop: >>> >>>dd bs=4M if=devuan_ascii_2.0.0_amd64_netinst.iso of=/dev/sdb >>>status=progress && sync >>> >>>Then I moved the USB stick to my new Purism laptop, powered it up, >>>pressed esacpe to get a boot menu, and the USB stick was not recognised >>>as a boot device. >>> >> >Is there something that needs to be done to the ISO before putting it on >>>the USB stick? Or is the dd command wrong? I remember that years ago >>>it had to be modified somehow in order to boot, but I thought that had >>>been fixed long long ago. Something like prefixing it with a >>>recognisable boot record? >>> >>>Sorry for not testing this in the beta days, but I didn't have the new >> >computer yet. >>> >> >> It seems you did it all well. Either your BIOS does not support >> reading an iso9660 filesystem from an USB stick, or you just need to >> allow it to boot from USB (in the BIOS menu). BTW, sync is useless: >> dd is a synchronous connand, AFAIK. > > It will boot the Purism installer from a USB stick if I use the same > steps, starting wth the Purism ISO file, of course. > > So there is something else going on. If you didn't do it already, try to boot Purism from the same USB stick. Alessandro ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Sorry! False alarm (was: Re: installer woe
On Mon, Jun 25, 2018 at 02:23:03PM -0400, Hendrik Boom wrote: > I used dd to copy the installer iso to a USB stck on my old laptop: > > dd bs=4M if=devuan_ascii_2.0.0_amd64_netinst.iso of=/dev/sdb status=progress > && sync > > Then I moved the USB stick to my new Purism laptop, powered it up, > pressed esacpe to get a boot menu, and the USB stick was not recognised > as a boot device. > > Is there something that needs to be done to the ISO before putting it on > the USB stick? Or is the dd command wrong? I remember that years ago > it had to be modified somehow in order to boot, but I thought that had been > fixed long > long ago. Something like prefixing it with a recognisable boot record? > > Sorry for not testing this in the beta days, but I didn't have the new > computer yet. Sorry! False alarm! I just discovered it's a defectuve USB stick that makes intermittent content. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] strategy for missing sysvinit scripts - the tuned case
Le 26/06/2018 à 09:22, Jaromil a écrit : dear dng'ers today I gave a spin to 'tuned' prompted by this article https://www.tecmint.com/tuned-automatic-performance-tuning-of-centos-rhel-servers/ and I quickly realised our package (from Debian) doesn't have any sysvinit script, but only a systemd unit in /lib/systemd/system/tuned.service containing: [Unit] Description=Dynamic System Tuning Daemon After=systemd-sysctl.service network.target dbus.service Requires=dbus.service polkit.service Conflicts=cpupower.service Documentation=man:tuned(8) man:tuned.conf(5) man:tuned-adm(8) [Service] Type=dbus PIDFile=/run/tuned/tuned.pid BusName=com.redhat.tuned ExecStart=/usr/sbin/tuned -l -P [Install] WantedBy=multi-user.target So I start thinking of what strategy we can adopt in order to overcome this limitation. Being a relatively simple CRUD / declarative configuration it may be easy to generate scripts from the information contained in systemd service configurations, or even wrap them runtime with a smaller program executing their commands and called by sysvinit/openrc. Another strategy which IMHO may not be sustainable on the long term is to fork all packages to have such a sysvinit service script in them. I tend to disagree with this approach. After so many years, what are your opinions? Is there a viable and smart way to work around this situation, just like we did with amprolla thanks to Nextime's brilliant intuition? I think on the long term this horrible header of comments describing the rc-scripts dependencies isn't sustainable. This has been a temporary hack (~10 years ?) to provide a hierarchy among these scripts. Better opt for startup systems which offer this functionality natively and/or others which have a hardcoded sequence. I think there are several out there - not counting the devil of course. In no way would it discard sysv-init proper. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] strategy for missing sysvinit scripts - the tuned case
...on Tue, Jun 26, 2018 at 09:22:26AM +0200, Jaromil wrote: > Another strategy which IMHO may not be sustainable on the long term is > to fork all packages to have such a sysvinit service script in them. > I tend to disagree with this approach. Maybe create an additional companion package that just contains the sysvinit/openrc script? Though I have no idea how to declare the dependency without changing the original package. Alex. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
Hi Hendrik, Hendrik Boom writes: > I used dd to copy the installer iso to a USB stck on my old laptop: > > dd bs=4M if=devuan_ascii_2.0.0_amd64_netinst.iso of=/dev/sdb status=progress > && sync Looks fine to me. Apart from the status= bit an using bs=1M, I did the same two days ago and installed an old desktop machine just fine. > Then I moved the USB stick to my new Purism laptop, powered it up, > pressed esacpe to get a boot menu, and the USB stick was not recognised > as a boot device. As Didier mentioned in another reply, you may have to play around with settings in the BIOS. I know I had to. In my case, I had to make the USB stick the first hard disk in the hard disk device list even though none of the other hard disks had any OS on them. The BIOS only ever tried to boot from the first hard disk and if that failed went on to the CD drive. You mentioned that Purism ISOs boot fine for you. Could it be that your BIOS has Trusted Boot or Secure Boot or similar enabled? Guess you oughta ask the Purism people about that (after you check their documentation of course). Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
Le 26/06/2018 à 05:43, Hendrik Boom a écrit : On Tue, Jun 26, 2018 at 07:25:48AM +0200, Didier Kryn wrote: Le 25/06/2018 à 20:23, Hendrik Boom a écrit : I used dd to copy the installer iso to a USB stck on my old laptop: dd bs=4M if=devuan_ascii_2.0.0_amd64_netinst.iso of=/dev/sdb status=progress && sync Then I moved the USB stick to my new Purism laptop, powered it up, pressed esacpe to get a boot menu, and the USB stick was not recognised as a boot device. Is there something that needs to be done to the ISO before putting it on the USB stick? Or is the dd command wrong? I remember that years ago it had to be modified somehow in order to boot, but I thought that had been fixed long long ago. Something like prefixing it with a recognisable boot record? Sorry for not testing this in the beta days, but I didn't have the new computer yet. It seems you did it all well. Either your BIOS does not support reading an iso9660 filesystem from an USB stick, or you just need to allow it to boot from USB (in the BIOS menu). BTW, sync is useless: dd is a synchronous connand, AFAIK. It will boot the Purism installer from a USB stick if I use the same steps, starting wth the Purism ISO file, of course. Not sure what's happening then. Maybe you made a mistake. You could just retry. Since usb sticks with dozens of GB are available now, I'd suggest you copy the full install DVD instead of the netinst. I suggest you this also because this is what I've done with ASCII, therefore I've checked it works. Using the netinst made sense for me when it was an alternative to burning a set of CDs or a DVD; now, with big usb sticks, it is less usefull. Didier PS. What I wrote about dd being synchronous seems to be just wrong, according to the man page. I've never invoked sync after dd, and never had any problem though, I was probably lucky, or maybe the behaviour is special when writing to a raw block device instead of a file. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] strategy for missing sysvinit scripts - the tuned case
On Tue, Jun 26, 2018 at 09:22:26AM +0200, Jaromil wrote: > > Being a relatively simple CRUD / declarative configuration it may be > easy to generate scripts from the information contained in systemd > service configurations, or even wrap them runtime with a smaller > program executing their commands and called by sysvinit/openrc. Debian tried it during GSoC couple years ago: https://github.com/akhilvij/systemd-to-sysvinit-converter Maybe this could be revived and extended. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installer woe
On Tue, Jun 26, 2018 at 07:25:48AM +0200, Didier Kryn wrote: > Le 25/06/2018 à 20:23, Hendrik Boom a écrit : > >I used dd to copy the installer iso to a USB stck on my old laptop: > > > >dd bs=4M if=devuan_ascii_2.0.0_amd64_netinst.iso of=/dev/sdb status=progress > >&& sync > > > >Then I moved the USB stick to my new Purism laptop, powered it up, > >pressed esacpe to get a boot menu, and the USB stick was not recognised > >as a boot device. > > > >Is there something that needs to be done to the ISO before putting it on > >the USB stick? Or is the dd command wrong? I remember that years ago > >it had to be modified somehow in order to boot, but I thought that had been > >fixed long > >long ago. Something like prefixing it with a recognisable boot record? > > > >Sorry for not testing this in the beta days, but I didn't have the new > >computer yet. > > > > It seems you did it all well. Either your BIOS does not support > reading an iso9660 filesystem from an USB stick, or you just need to > allow it to boot from USB (in the BIOS menu). BTW, sync is useless: > dd is a synchronous connand, AFAIK. It will boot the Purism installer from a USB stick if I use the same steps, starting wth the Purism ISO file, of course. So there is something else going on. The Purism hardware uses Coreboot, by the way. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] strategy for missing sysvinit scripts - the tuned case
dear dng'ers today I gave a spin to 'tuned' prompted by this article https://www.tecmint.com/tuned-automatic-performance-tuning-of-centos-rhel-servers/ and I quickly realised our package (from Debian) doesn't have any sysvinit script, but only a systemd unit in /lib/systemd/system/tuned.service containing: [Unit] Description=Dynamic System Tuning Daemon After=systemd-sysctl.service network.target dbus.service Requires=dbus.service polkit.service Conflicts=cpupower.service Documentation=man:tuned(8) man:tuned.conf(5) man:tuned-adm(8) [Service] Type=dbus PIDFile=/run/tuned/tuned.pid BusName=com.redhat.tuned ExecStart=/usr/sbin/tuned -l -P [Install] WantedBy=multi-user.target So I start thinking of what strategy we can adopt in order to overcome this limitation. Being a relatively simple CRUD / declarative configuration it may be easy to generate scripts from the information contained in systemd service configurations, or even wrap them runtime with a smaller program executing their commands and called by sysvinit/openrc. Another strategy which IMHO may not be sustainable on the long term is to fork all packages to have such a sysvinit service script in them. I tend to disagree with this approach. After so many years, what are your opinions? Is there a viable and smart way to work around this situation, just like we did with amprolla thanks to Nextime's brilliant intuition? ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
