| 1 |
Duncan posted on Mon, 03 Mar 2014 19:43:26 +0000 as excerpted: |
| 2 |
|
| 3 |
> I'm only running an initramfs at all because some kernels ago when I |
| 4 |
> originally setup my (dual-device raid1 mode) btrfs rootfs, the kernel |
| 5 |
> command-line parser couldn't properly parse rootflags=device= , |
| 6 |
> apparently due to splitting at the wrong equal-sign, so the only way I |
| 7 |
> could mount rootfs direct from the kernel commandline was in degraded |
| 8 |
> mode. =:^( I'm not sure if that has been fixed or not, but I have the |
| 9 |
> initramfs setup and working now, so it's not so pressing to find out. |
| 10 |
> Anyway, I expect that someday I'll be able to omit that and go back to a |
| 11 |
> direct (initr*less) kernel commandline root=/rootflags= boot. |
| 12 |
|
| 13 |
FWIW, I tested a couple days ago with a current 3.14-rcX+ git kernel, and |
| 14 |
the kernel commandline parsing issue appears to still be there, so no |
| 15 |
simple way out of the initr* situation for me yet. =:^( |
| 16 |
|
| 17 |
Maybe one of these days I'll go looking into it more intensely, and |
| 18 |
report a kernel bug if necessary. I wonder if there's some other command |
| 19 |
I can double-equal check to see if it parses in the right place, and I've |
| 20 |
not even googled it yet, but that does seem the most likely problem, |
| 21 |
given that a NON-equals-including rootflags (btrfs' degraded option) was |
| 22 |
demonstrated to still work in my earlier testing, so the rootflags option |
| 23 |
is in general working, and btrfs is actually picking up general options |
| 24 |
passed to it that way. |
| 25 |
|
| 26 |
'Cause it'd sure be nice to be able to just dump this initr* business |
| 27 |
again! |
| 28 |
|
| 29 |
(Hmm, just musing, but as a definite non-coder but an otherwise |
| 30 |
reasonably advanced gentooer who never-the-less has kernel bug-reporting |
| 31 |
experience, and who routinely applies patches to other things and |
| 32 |
occasionally to the kernel as well, and who in very limited circumstances |
| 33 |
can actually come up with his own patches... I obviously can't get too |
| 34 |
ambitious about creating my own kernel patches, but I wonder just how |
| 35 |
difficult it might be to patch the kernel btrfs code to use some other |
| 36 |
delimiter in place of the equals in "device="... If I could successfully |
| 37 |
do that just for testing, hopefully conclusively proving my suspicion |
| 38 |
that the double-equals IS the problem, that would certainly make an |
| 39 |
actually practical bug report, while just a suspicion... not so much, |
| 40 |
particularly since I don't have a kernel version where it was known to |
| 41 |
work in the past, thereby making it a known regression, tho various hints |
| 42 |
I've seen in comments found on the net suggest that it must have at some |
| 43 |
point, altho there's also hints that it was some time ago, given the age |
| 44 |
of some of the comments saying it now doesn't work.) |
| 45 |
|
| 46 |
-- |
| 47 |
Duncan - List replies preferred. No HTML msgs. |
| 48 |
"Every nonfree program has a lord, a master -- |
| 49 |
and if you use the program, he is your master." Richard Stallman |
Archives