try logging on in almost any version of Linux as root with caps lock on. All Linux installs that I've used prior to DSL, have instructed me to make my root user names as all lower case. Others can use upper case. My understanding is that the root is lower case because it becomes the name of the root file and filenames are always lower case.
Quote (stand @ Dec. 23 2005,12:33)
mikshaw: I'm sure that's the BUG!! Just try to login with switched on CAPS LOCK as ROOT.
So what you're saying is you have capslock on, hold the Shift key and type in "root"? If this is the case, i can see how it might be a bug, but...why the heck would you bother to do that in the first place?!?
If you're doing what I originally suspected, which is to have capslock on and type "root" without holding Shift, then it is *not* a bug. It is the way Linux is intended to be.
-- One of the best things i ever did on a computer was breaking the capslock key.noticing a couple of odd things concerning icons. I seldom use them unless testing mydsl packages, so i don't know if this was apparent in earlier versions of DSL....
First, if you do not use "noicons", it seems that a permanent xtdesk pid is being created...at least that's what appears to be happening. If you decide to turn off icons, they will return after running emelfm.
On what i think is a related note, the icon tool does not take effect until manually restarting xtdesk because xtdeskRestart.sh seems to be broken. The error comes from the `pidof xtdesk` test....seems like multiple xtdesk pids are breaking the test. I put it in double quotes and it seems to be working properly now, though there might be a more appropriate fix:
Code Sample
if [ "`pidof xtdesk`" ]; then
I have not been able to reproduce having multiple xtdesk running. Should not happen. Would like to determine why you are experiencing it. I guess I can use pkill but would like it better if I could reproduce it.
The emelfm thing, yep, I keep forgetting about that. Sometimes, I think a little too much integration with a particular fm, but oh well. That's what RC and public beta testing is for. Looks like xtdeskRestart.sh needs to be aware of new .desktop option of noicons.
As usual a good report. Thanks mikshaw.This is the setup in which the trouble appeared:
frugal install on hda4, ext2fs grub options: dsl frugal norestore base vga=791 dma nofirewire nopcmcia
I had mounted and umounted 2 uci extensions prior to noticing the strangeness (python and blender).
Playing around with icontool.lua, and found that i was receiving errors from xtdeskRestart.sh....first an error saying it expected a unary operator, second time saying it expected binary (that was odd enough)...after that i received only messages saying that there were too many arguments. Each time this last error occured was a result of simply opening the tool and pressing "ok", but I had played with various settings several times before finally starting the script from a terminal to see the first 2 errors. So my guess is something happened while i was running icontool which changed the data xtdeskRestart was expecting...perhaps one of the previous tests started a second instance of xtdesk. In any case, the double quotes apparently allowed the multiple PIDs to be read as a single argument? I'm guessing that there should be only one PID for xtdesk at any given time, though....thought it was weird that "killall -9 xtdesk" would not remove all xtdesk PIDs.Next Page...
original here.