Other Help Topics :: boot problem ramdisk



Quote (drio @ Nov. 02 2006,13:45)

Hi.

There's probably nothing wrong with your HDD, I've seen that message before on "functional" systems. Linux also detects 13MB for my config, 3MB isn't much for the kernel.
Furthermore, I think I have posted your solution here: X problems - runlevel 2

Regards,
bkil
bkil:
I tried to follow your instructions althought I don't think I understand what

/grub\ dsl 2

is this one.
Also I don't understand the

su dsl

from what I have seen only sudo su is needed.

Hoever all the other are working up to a point. In order to rm the directories I have to be su (I get permission denied). If I start X as su I get several stuff. But this could be due to the fact that su can't have X in dsl?


If I start X as user dsl everything is working fine :-) :-)

Thanks both bkil and ^thehatsrule^ for your time
Dear drio,

Glad to hear you've got DSL working. :)

About my instructions: well, I have to confess that I made them up from memory, :blush:  you see I don't boot LiveCD's too often, I only needed those commands as a quick hack to make harddrive install work on a PC... Let me try to clarify that post a bit (again from memory)

The first line was supposed to mean that I think it's sufficient for you to simply enter "dsl 2" at the grub boot prompt (you could append other parameters as you will), and as a consequence, the CD will log you into a rather clean root session (no "sudo su" needed for the empty /tmp, /opt recreation).
"su dsl" (or "su - dsl" if you'd like to have a login shell) is needed to change user from root to dsl, to enable you to run startx (it's not needed for installation of course).
After a harddrive install, you probably make both your /opt and /tmp non-volatile, so you don't need these "tricks" later on.
And the superuser can also start X sessions (at least on a hard install), his(her) config files in /root work the same way as any other user's in /home/*. Not that root would need X or anything... :D Anyway, if startx throws errors, you need to either set your home directory, or make sure you use a valid configuration by copying, creating or editing your (hidden) config files and scripts. (Though all worked as expected automagically after a full HD-install over here)

Yours,
bkil

original here.