Post #180,897
10/25/04 2:20:58 PM
|
Note to self re: winbind
1. apt-get remove winbind
2. clean up PAM
3. reboot
Doing that in the wrong order can lead to headaches. Like not being able to login.
*bonk*
|
Post #180,925
10/25/04 4:23:15 PM
|
BWAHAHA...
Umm hey, if you knew what you were doing in the first place... you'd still be able to login anyway.
-- [link|mailto:greg@gregfolkert.net|greg], [link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
|
Post #180,935
10/25/04 5:37:58 PM
|
Ran across a funny Debian thread
...one developer [link|http://lists.debian.org/debian-testing/1999/01/msg00059.html|suggesting]: I think we should change the default LILO config to prompt the
user (so they don't have to hit shift to get a LILO prompt)
and then time out in a reasonable value, say 7 seconds.
This can be done by adding:
prompt
timeout=70
to the default /etc/lilo.conf. Is the boot floppies package the right
place for this? Making the user hit shift for a LILO prompt is oogy. I agree; it's oogy. :)
The Sig: "Despite the seemingly endless necessity for doing
so, it's actually not possible to reverse-engineer intended invariants
from staring at thousands of lines of code (not in C, and not in
Python code either)." Tim Peters on python-dev
|
Post #180,936
10/25/04 5:42:55 PM
|
Dude. LILO is oogy.
It needs to die.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Home]
|
Post #180,951
10/25/04 8:14:08 PM
|
Should have mentioned previous post was a :-P
I have seen some *REALLY* hilarious threads lately in Debian Boot and Debian-Devel about the freeze. Recently Joey Hess responding to someone blathering: I see you can't distinguish your own writing and someone else's, because you've mistakenly started to attack yourself. Heck, you don't even understand your complaint, I surely don't, therefore I must object. I'll see if I can did it up. -- [link|mailto:greg@gregfolkert.net|greg], [link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwetheyNo matter how much Microsoft supporters whine about how Linux and other operating systems have just as many bugs as their operating systems do, the bottom line is that the serious, gut-wrenching problems happen on Windows, not on Linux, not on Mac OS. -- [link|http://www.eweek.com/article2/0,1759,1622086,00.asp|source]Here is an example: [link|http://www.greymagic.com/security/advisories/gm001-ie/|Executing arbitrary commands without Active Scripting or ActiveX when using Windows]
|
Post #180,960
10/25/04 8:54:18 PM
|
Oh nighted men who know not elegance
-drl
|
Post #180,927
10/25/04 4:26:18 PM
|
Similar
Recompile kernel without devfs AND THEN
Fail to remove devfs daemon AND THEN
Reboot AND THEN
Repeatedly hit face on keyboard.
Now who would do such a silly thing? I can‘t possibly imagine.
Peter
[link|http://www.debian.org|Shill For Hire]
[link|http://www.kuro5hin.org|There is no K5 Cabal]
[link|http://guildenstern.dyndns.org|Home]
|
