Bug#589118: `rdev` setting ignored
reopen 589118
quit
>From: Ben Hutchings <ben@decadent.org.uk>
> On Thu, 2010-07-15 at 13:48 -0700, Elliott Mitchell wrote:
> > Bzzzt! While the "initrd=" kernel command-line option and `rdev` kernel
> > settings are not completely orthogonal, they are mostly unrelated.
>
> You obviously haven't read the code. I have.
This is in fact true. An unrelated project may cause me to do so.
> > Unlike the kernel command-line, I don't know how the `rdev` (and
> > accompanying) setting is passed along to initial ram disks, but I do know
> > it is (or was).
>
> It isn't.
Reeeaaally? Sorry to be speculating outside my area of firm knowledge,
but I'm noting that the rdev setting was honored all the way through
Debian 3.1/Sarge, which was a 2.4 kernel. Was the rdev setting really
available to initial ramdisks all the way through 2.4, yet lost with 2.6
kernels?
> > I'm unsure whether Debian 4.0/Etch honored the `rdev`
> > setting, but I am pretty certain initial ram disks generated with Debian
> > 3.1/Sage did honor the `rdev` setting unless overridden by the "root="
> > option.
>
> That's nice, but this feature isn't coming back.
That sounds suspiciously like "wontfix", not "done".
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | EHeM@gremlin.m5p.com PGP F6B23DE0 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0
Reply to: