Re: grub root=/dev/hd$v$n not root=LABEL=/ why

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > > cramfs images ...
>
> From: Ravi <kravi26 () yahoo ! com>
> From: Jim Bauer <jfbauer () nfr ! com>
> From: Jan Hudec <bulb () ucw ! cz>

Sorry our posts re cramfs images may appear out of
order in the archive of this thread.  The solution we
found was:

Ask `file` to tell us if we have to decompress the
.img before we try to mount it.

Kindly offline someone points out that `tar` has
learned to decompress automagically, maybe `mount ...
-o loop ...` will too, someday.

> From: Jan Hudec <bulb () ucw ! cz> ...
> you speak about a "defconfig", 

Do we have some other jargon established to mean what
I mean by defconfig?  Speaking again now, though
working now only from human memory ...

In 2.5.x I `make defconfig` to create a "defconfig".

In 2.4.x I `make xconfig` and then save and exit
without having changed anything to create a
"defconfig".

I'd `make defconfig` in 2.4.x if I could, but there I
see no defconfig target.  I find this especially
annoying when I am `ssh`ing into a Linux from a
terminal not compatible with the escape sequences that
`make menuconfig` wishes would give me a character
graphic interface.

In 2.4.x I create a Red hat config by creating a
"defconfig" and then copying in Red Hat's .config over
top of mine.  At first I guessed wrong: only thru pain
did I learn to begin by creating a "defconfig".  If I
just copy the .config that doesn't work e.g. no
include/autoconf.h created.

> have you carefuly inspected each and every
> option if you need it or not?

Certainly not.  Being a newbie, as yet I have no idea
what most of the options mean, so as yet I cannot
usefully inspect them.  

> there was no help target

Fetching recently from kernel.org I see `make help`
work only in 2.5.x, not in 2.4.x.

> Out of curiosity ...
> might ... study ... new-kernel-pkg 

Regrettably I suffer from more curiousity than fits
into my twenty-four hour days.

> > $ sudo mount ... -o loop=/dev/loop0
>
> Using -o loop suffices - it will pick the first
> loop device it can.

News to me, thanks.

> easy to use ... original ...
> ... on your own if you don't.

Aye, most software sharply punishes ignorant
creativity.

> From: ...
> are you sure?

I've lost track of specifically who last kindly
suggested further experiments ... but I think I owe
you notice that I've now lost access to the PC I was
borrowing when I launched this thread, so this project
of me learning to boot a Red Hat Linux from a
kernel.org kernel without abandoning the default
root=LABEL=/ option will have to wait for another day.

Pat LaVarre


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux