I get the same icon in KDE's konquerer, don't use kde much so its no a biggie and I just type / in the toolbar for root, but you can't even mount it as root which is odd. Would be nice to have and Icon to root to speed up operations but oh well hehhe.

hello i found this problem with unable to read root partition disappears if you use the generic smp kernel...

regards

adrian

Hi mattydee and rworkman, thanks for the comments,


mattydee, that seems to be the whole issue ... it doesn't ... it used to be possible to access the slackware root filesystem (read-only as user) in slack11 through the icon in /media and now in slack12, it isn't .. why not?
Which file do you think needs to be edited to make that partition 'clickable' again?
If it is suddenly impossible to 'click' the slackware partition, then why was it included the /media folder at all ... what would be it's purpose, other than to confuse?

I think that fixing this icon issue so that it has clickable continuity the same as all of the other partitions in /media should remain the main focus of this topic, rather than diverting into other conversations.

rworkman, I was wondering, could this have anything to do with HAL/Udev rules at all? Or, is it possible that it might be a system service that needs to be turned on in /etc/rc.d?

Any suggestions at all?

Regards

Orbit

Hello todders,
That's an interesting point about the kernel.
On my system, uname -r returns;
2.6.21.5-smp

What does your give?

Regards

Orbit

When I try to access the partition where the system is installed it says:
I also can't mount the CD-ROM it displays the same message (in KDE) but when i try to mount it manually it says that the CD-ROM option is not in my FSTAB.

Any idea how to mount the cd-rom?

yes i have the same problem !!!

Why 1 1? 1 1 is only for / partition. For another Linux partitions it should be 1 2.

Mine is exactly the same as yours 2.6.21.5-smp,like i said before i had exactly the same problem with the root hard drive partition i followed the instructions in the directory /boot readme.initrd
to use the generic smp kernel and it solved the mounting problem of the root partition,dont know why as iam not an expert by any means just enjoy tinkering...im also sure that the uname-r command also said i had the 2.6.21.5-smp when i still was using the huge kernel so give it a go anyway...


regards

adrian

Hi Road_Map and Todders, thank you both for your responses.

Road_map: I'll edit the fstab to reflect the Kubuntu partition as 1 2 and see what happens.
Todders : I'll read the readme.initrd file for instructions, and then convert to the generic kernel instead of the huge.

[Unfortunately, I can't do either until Monday next week as I am away, but I will definately post the results (hopefully positive) of both changes on Monday/Tuesday next week].

Thanks again for your help, have a good weekend

Cheers

Orbit

Success!!

Thanks Todders for your suggestion about the kernel/initrd change;
After changing to the vmlinuz-generic-smp-2.6.21.5-smp kernel and generating an initrd.gz (as referenced from /boot/README.initrd), then editing /etc/lilo.conf to reflect these new changes and running lilo -v; the system works a treat!!
(The Slackware partition in now 'Clickable' and is read-only as user, and read-write as root).

I'd like to thank everyone who contributed in this topic, your help has been very much appreciated

Kind Regards

Orbit

Orbit
glad you now have this working,iam only a newbie myself so have a big smile on my face that one of my suggestions worked :-)

regards

todders

Hey,

I'm pretty new to Linux and I'm having the same issues with permissions to mount the root partition. I've edited etc/groups and that seemed to change something (went from the lengthy HAL warning to just 'permission denied'). I then tried to edit etc/fstab, following various instructions from tuxfiles and on this forum. This ruins the automount sequence during boot up and prevents me from reaching login. I've tried booting from my installation disk, using
as recommended at the startup screen. This also freezes somewhere in the process after failing to access certain files that I think are supposed to be in the root.

Anyone have any idea what's happening and what I can do, aside from reinstalling slackware (for the fourth time in as many days)?

The only change I made to my fstab was mount options for my root partition (/dev/sda2 in my case). Before it was 'default'. After it was 'auto,user,rw'.

Hi Todders, gotta admit that it was a mighty fine suggestion though, Thanks again

Hi Sarnok,
Try to boot from a slax (live-on-cd) disc,
then navigate to your hd* partition where slackware is installed, correct the change(s) you made .. save the file(s) ..
reboot slackware .. hopefully smile again!

This is what I do when I make a mistake, and it is a lot less time consuming than re-installing (something I really don't like doing).

If you don't have it, you can get Slax Linux HERE (Right-Click ... Save Link As..)

Hope this helps you.

Cheers

Orbit

Thanks Orbit.

I actually do have a slax disk (I had tried it before I found out about Slackware - I kinda wanted a permanent Linux system more and I was having a few problems with Slax anyway). I don't know why I didn't think of that already, I'll give it a try as soon as I get home.

Now, is there a particular way you're supposed to edit fstab? I didn't see any real specific rules or caveats on the guides I used. I believe that the changes I made there are what has led to these boot problems.

Thx,
Sarnok

I've installed Kaffeine using slapt-get from slack 11 repository and it didn't work, because Pat moved KDE from /opt to /usr and I had to manually move it to the new location.