[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dng
Subject:    Re: [DNG] upcoming usr merge requirements
From:       tito via Dng <dng () lists ! dyne ! org>
Date:       2023-11-29 6:38:42
Message-ID: 20231129073842.27264f80 () devuan
[Download RAW message or body]

On Tue, 28 Nov 2023 18:19:05 -0600
o1bigtenor via Dng <dng@lists.dyne.org> wrote:

> On Tue, Nov 28, 2023 at 12:48 PM Didier Kryn <kryn@in2p3.fr> wrote:
> > 
> > Le 28/11/2023 à 03:43, Steve Litt a écrit :
> > 
> > I'm speaking for Linux, not for the Debian or Devuan packaging...
> > 
> > If you choose to have your /usr on a separate partition mounting on
> > mountpoint /usr, it should be no problem at all because your initramfs
> > will boot off its own OS, and then mount /dev/sda5 /usr, and then
> > pivotroot back to the hard disk, which now has /usr mounted in the
> > correct place. No big deal: It's been done for years: Long before
> > usrmerge.
> > 
> > Now of course if a specific distro's packaging system and installer has
> > a problem with such a setup, you'll need to do some DIY on that distro.
> > But I doubt even Debian is stupid enough to seriously bork this
> > customary technique.
> > 
> > It's exactly that.
> > 
> > My own comment is: it is only if you decide to tweak the boot sequence that you \
> > need to take care. 
> > The boot sequence is nowadays done in two steps:
> > 
> > 1) boot into a first partition which, for distros, is always an initramfs; \
> > perform some mounts and maybe other things; 
> > 2) pivot-root to the final partition and continue the init sequence there.
> > 
> > Note that, if you decide to craft your own first step, the initial partition is \
> > not necessarily an initramfs, provided your kernel is able to mount it, i.e. it \
> > has the drivers built-in, which implies you must build it from source. 
> Hmmmmmmmmmmm - - - - thank you!
> 
> How do I slowly step through my boot sequence to see what's happening?
> 
> (I'm running from SSDs and trying to follow the boot sequence on the
> screen - - -
> I bet I miss at least 70% of it and maybe more even though I read
> very very quickly.)
> 
> TIA
Hi,
you can use:
dmesg 
+ 
bootlogd - record boot messages
The default logfile is /var/log/boot.

Ciao,
Tito
> _______________________________________________
> 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


[prev in list] [next in list] [prev in thread] [next in thread]