Hi!
> > To some degree, /initrd was supposed to do things like that, and in
> > theory, it still could. However, realistically, 99% of any /initrd is more
> > about the distribution than the kernel, so right now we have to count
> > /initrd as a distribution thing, not a kernel thing.
>
> ... and if we're truly going to be pouring more and more complexity
> into initrd (such as userspace swsusp), then (a) we probably should
> make it more of a kernel-specific thing, and not a distro-specific
Actually, distros started to do swsusp-resume-from-initrd long before
uswsusp -- because of scsi modules. So that complexity exists
already...
Anyway somehow simplifying/kernelizing initrd would be nice. Right now
I'm using read-only ext2 as poor-mans initrd (because it is easier to
set up that way).
Pavel
--
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
