[blfs-support] /dev/null // udev -- Re: Kde cannot start !!!!! solved !!!!!
zarniwhoop at ntlworld.com
Sat Sep 21 17:55:38 PDT 2013
On Sun, Sep 22, 2013 at 12:36:50AM +0100, akhiezer wrote:
> > Date: Sat, 21 Sep 2013 12:02:11 -0700 (PDT)
> > From: Sirsendu Roy <xairoy at yahoo.com>
> > To: BLFS Support List <blfs-support at linuxfromscratch.org>
> > Subject: Re: [blfs-support] Kde cannot start !!!!! solved !!!!!
> > Hi akhzier,
> > Thanks for the reply. At last I have my KDE login again.
> > The problem was:
> > 1. Now I boot when when udev starts and populates /dev node, the /dev/null cannot get the permission that requires, i.e. 666, no idea suddenlz why it happens !!!!!
> > 2. suddenly /usr/X11/bin/Xorg losts its sticky bit. I reverted the change.
> > Now in my ~/bashrc file I needed to add :
> > sudo chmod 666 /dev/null.
> It's probably prudent to fix that /dev/null issue system-wide, rather than just
> via one of your login environments. You _could_ put the chmod command into a
> system startup file under /etc/rc* : but in your case it's probably less hacky
> if you try to correct it via udev.
> I don't use udev (& instead just use static device files), so the following may
> be better addressed by someone on-list who does use it.
> For the command:
> grep -r null /etc/udev /lib/udev/[a-ce-z]*
> , do you get any lines like:
> /lib/udev/rules.d/50-udev-default.rules:KERNEL=="null|zero|full|random|urandom", MODE="0666"
> /etc/udev/rules.d/40-fix-permissions-rules:SUBSYSTEM=="mem", KERNEL=="null|zero|full|random|urandom", MODE="0666"
> ? If not, then you might want to create something like
> '/etc/udev/rules.d/40-fix-permissions-rules' ( 0644 root root ) with the contents
> as shown in the above example grep output.
On a (eudev) 7.4 I see that /lib/udev/rules.d/50-udev-default.rules
line : if Roy doesn't have it then I suggest he needs to think about
what he has been doing, to work out why it got trashed.
das eine Mal als Tragödie, dieses Mal als Farce
More information about the blfs-support