| 1 |
On Sep 2, 2013 5:21 AM, "Walter Dnes" <waltdnes@××××××××.org> wrote: |
| 2 |
> |
| 3 |
> On Sun, Sep 01, 2013 at 09:49:23AM +0200, Joerg Schilling wrote |
| 4 |
> > Walter Dnes <waltdnes@××××××××.org> wrote: |
| 5 |
> > |
| 6 |
> > > You can get away with most stuff as modules; ***BUT NOT THE ROOT |
| 7 |
> > > FILESYSTEM***. Think about it for a minute. Gentoo reads modules off |
| 8 |
> > > the disk. If the code for the root filesystem is a module, Gentoo |
| 9 |
would |
| 10 |
> > > have to read the module off the disk to enable it to read the module |
| 11 |
off |
| 12 |
> > > the disk... OOPS. This is a classic "chicken and egg" situation. |
| 13 |
> > |
| 14 |
> > On Solaris no problem with loadable modules - everything is |
| 15 |
> > dynamically loaded. ***YOU NEED A GRUB THAT UNDERSTANDS ZFS AND THAT |
| 16 |
> > GIVES A ZFS INTERFACE TO THE KERNEL TO USE BEFORE ZFS WAS LOADED***. |
| 17 |
|
| 18 |
I'm confused as to what this means. Grub reads a filesystem, loads a kernel |
| 19 |
with options, and may give it an initrd. What happens from then on is none |
| 20 |
of grub's business. The filesystem it reads from and the one the kernel |
| 21 |
uses may be completely unrelated - this is why we have /boot filesystems. |
| 22 |
|
| 23 |
At what point does grub "present a zfs interface for the kernel to use"? |
Archives