| 1 |
Anyone who boots directly to X'doze without first going through a safe |
| 2 |
console login is a raging mad lunatic who needs his head examined. This |
| 3 |
is linux we are talking about. It's crap. It always has been crap, and |
| 4 |
it always will be crap. Never ever ever trust it. I leave my computer on |
| 5 |
continuously because booting it is such a risk. Every single time I load |
| 6 |
X'doze and find that my keyboard and mouse are working I ghasp with |
| 7 |
surprise. The linux developers, or the penguins as I like to call them |
| 8 |
are so smug on the sublime superiority of the open source approach that |
| 9 |
they never bother to design essential things such as fail-safe design, |
| 10 |
fallback drivers, stable apis so that it doesn't just die if it's not |
| 11 |
compiled against this specific point release. ... You know, the kind of |
| 12 |
things that any competent programmer would think about. =| |
| 13 |
|
| 14 |
|
| 15 |
Bertram Scharpf wrote: |
| 16 |
> Hi, |
| 17 |
> |
| 18 |
> since an emerge-update-world on my notebook the keyboard |
| 19 |
> does no longer respond in X. This is extremely annoying |
| 20 |
> because when I have xdm in rc-update, X is started right at |
| 21 |
> boot. I have no chance to get back to the console using |
| 22 |
> Ctrl-Alt-F1, and the device in unusable. |
| 23 |
> |
| 24 |
> Yet, this is only a problem of the boot process. At home, |
| 25 |
> when I ssh into the system, I can do an |
| 26 |
> |
| 27 |
> # /etc/init.d/xdm restart |
| 28 |
> |
| 29 |
> and from that point on the keyboard works. It is even |
| 30 |
> possible to disable xdm in rc-update and start it after the |
| 31 |
> boot process has completed. I solved the problem temporarily |
| 32 |
> this way, but the problem probably is a bug and should be |
| 33 |
> reported. |
| 34 |
> |
| 35 |
> So I have a closer look. When I diff "Xorg.0.log" and |
| 36 |
> "Xorg.0.log.old" (after removing the time stamps) I find one |
| 37 |
> line that doesn't appear in the log of the working X. |
| 38 |
> |
| 39 |
> (EE) kbd: Keyboard0: failed to set us as foreground pgrp (Inappropriate ioctl for device) |
| 40 |
> |
| 41 |
> What does this mean? I estimate that "us" is the personal |
| 42 |
> pronoun and not a keyboard layout, and that the server tries |
| 43 |
> to do some chgrp on some /dev/*. I have no clue what to try |
| 44 |
> next. |
| 45 |
> |
| 46 |
> Thanks in advance. |
| 47 |
> |
| 48 |
|
| 49 |
-- |
| 50 |
IQ is a measure of how stupid you feel. |
| 51 |
|
| 52 |
Powers are not rights. |
Archives