SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
well ok, i was kinda happily using slack when one day it didn't want to boot from lilo cause it said that my partition wasn't mounted as read-write and i should press ENTER to mount it read-write and when i press enter it chokes when it tries to load some syslog daemon so i'm forced to force reboot. then i try to boot from my slack boot disk and then type "mount root=/dev/hda1 rw" and it then doesn't want to mount it rw. ok, it boots rw, but it promts me to accept the ro change or something like that. the first few times i could then just use slack normally, but now, i can't login to my user account because gnome gives me some failure because home/dukey/.Xauthority is kinda corrupt, so now i'm just clueless what's up
Sounds like a strange problem but I would suggest logging into Runlevel 3 as root and chown -R your entire /home directory. Sometimes I've had ownership change on me and I couldn't get access to .Xauthority either. That's what fixed it for me.
k, now i'm logged in as root and in my user home dir is a ".xsession-errors" file
Code:
stderr is not a tty - where are you?
** (gnome-session:2203): WARNING **: Unable to lock ICE authority file: /home/dukey/.ICEauthority
strange....now it's ICEauthority and not Xauthoritx...wtf? and what is no actually wrong with this file?
edit: lol wtf, it really worked, so now i can start x without any errors as my user login. but i still have the prob that the partition doesn't want to boot directly from lilo
Last edited by AgentDukey; 11-19-2004 at 03:38 PM.
To edit lilo go to /etc/lilo.conf and edit it by hand with your favorite editor, to run lilo just type lilo or /sbin/lilo from a command prompt and that will ensure that what you edited is recognized by lilo when you reboot.
i made the new liloconfig, but it still gives me this error at startup:
Code:
Remounting root device with read-write enabled.
EXT2-fs: Unrecognized mount option umask
mount: / not mounted already, or bad option
Attempt to remount root device as read-write failed! This is going to
cause serious problems.
If you're using the UMSDOS filesystem, you **MUST** mount the root partition
read-write! You can make sure the root filesystem is getting mounted
read-write with the 'rw' flag to Loadlin:
loadlin vmlinuz root=/dev/hda1 rw (replace /dev/hda1 with your root device)
Normal bootdisks can be made to mount a system read-write with the rdec command:
rdev -R /dev/fd0 0
You can also get into your system by using a boot disk with a command like this
on the LILO prompt line: (change the root partition name as needed)
LILO: mount root=/dev/hda1 rw
Please press ENTER to continue, then reboot and use one of the above methods to
get into your machine and start looking for the problem.
Is your /etc/fstab file screwy? Why don't you post that or change it if it's not normal. Actually, you should convert to Reiser or Ext3 but assuming you don't want the hassle, make sure your fstab file looks like this for that partition:
/dev/hda1 / ext2 defaults 1 1
I really don't know for sure at what point your system will read the fstab file but that umask part made me think of this.
Let me know what you've got.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.