You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is support for grub2's 'root=' boot parameter in /sbin/init_full_install but not in /init or /sbin/isoboot.
I have a couple of patches to provide this support.
The attached file: initrd-root.tar.gz
contains the patches as .diff files, 'init_root.diff' and 'iso_root.diff',
and a 'local-initrd.gz' containing the 2 patched files.
This can be tested by adding the 'local-initrd.gz' to a Puppy frugal install directory,
provided the grub2 bootentry supports 'local-initrd.gz', (boot entries generated by FrugalPup do).
You can check that the patched 'init' has been used for a boot, by the first line of /initrd/tmp/bootinit.log.
It should be 'Testing "root=" boot parameter'.
I would hope for more testing other than "It works for me", before I think about commiting the patches to woof-ce.
Since the patches add a new facility,
the primary test is that it doesn't break any existing facility.
Obviously I've tested it in my environment, but there are heaps of facilities in 'init' that I never use.
The text was updated successfully, but these errors were encountered:
There is support for grub2's 'root=' boot parameter in /sbin/init_full_install but not in /init or /sbin/isoboot.
I have a couple of patches to provide this support.
The attached file:
initrd-root.tar.gz
contains the patches as .diff files, 'init_root.diff' and 'iso_root.diff',
and a 'local-initrd.gz' containing the 2 patched files.
This can be tested by adding the 'local-initrd.gz' to a Puppy frugal install directory,
provided the grub2 bootentry supports 'local-initrd.gz', (boot entries generated by FrugalPup do).
You can check that the patched 'init' has been used for a boot, by the first line of /initrd/tmp/bootinit.log.
It should be 'Testing "root=" boot parameter'.
I would hope for more testing other than "It works for me", before I think about commiting the patches to woof-ce.
Since the patches add a new facility,
the primary test is that it doesn't break any existing facility.
Obviously I've tested it in my environment, but there are heaps of facilities in 'init' that I never use.
The text was updated successfully, but these errors were encountered: