On Mon, May 13, 2013 at 10:21:50PM +0000, Thorsten Glaser wrote:
> Ben Hutchings dixit:
>
> >As m68k is not a release architecture, I don't care much what goes
> >in debian/config/m68k (well, it had better not break gencontrol.py).
> >Whatever the m68k porters come up with is fine.
>
> OK, thanks. I’d kinda like to have it somewhat in sync with
> the rest of Debian of course, so people who can do informed
> decisions should do it.
>
> >If there is an initramfs-supporting bootloader for Atari now, you
> >could drop a whole lot of built-in stuff. But let me guess, does
>
> The problem here is that you normally do not have access to
> “where the kernel is” from the booted Linux system, or need
> to go through extra hoops. From my experience in running an
> x86 Debian system, the initrd is regenerated very often and
> system-specific; kernel images are pretty static and share‐
> able as a contrast.
[...]
If you use initramfs-tools configured with MODULES=most, the
initramfs is hardly system-specific.
initramfs-tools itself will put the resume (swap) partition device ID
in there, and mdadm will copy in mdadm.conf. But neither resume from
disk nor booting from md-RAID will work without an initramfs anyway,
so far as I can see.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130513230538.gd31...@decadent.org.uk
