Domain: linuxdevcenter.com
Stories and comments across the archive that link to linuxdevcenter.com.
Comments · 63
-
Please learn how to make links.describing it's development
"its".
Also, Please learn how to make links.<a href="http://www.linuxdevcenter.com/pub/a/linux/2
(without any spaces put there by Slashdot) yields: FlightGear0 03/12/11/flightgear.html">FlightGear</a>
If that's too much typing for you,<URL:http://www.linuxdevcenter.com/pub/a/linux/20
(without any spaces put there by Slashdot) yields: http://www.linuxdevcenter.com/pub/a/linux/2003/120 3/12/11/flightgear.html>/ 11/flightgear.html -
Request for virus writers:
I'm still waiting for a worm that installs Linux on the infected computer.
Propogation:
Scan random IP addresses, use multiple Windows exploits, etc. This part has been done a thousand times before, no need to reinvent the wheel.
Payload:
1. The worm itself
2. Grub for Dos
3. The contents of a network install disk
Behavior:
1. Upon infection, the worm will install Grub for Dos, and copy the contents of the network boot disk into c:\boot, but will not modify the boot.ini file.
2. The worm process will run in the background, and attempt to propogate itself.
3. At a predefined interval, the worm will pop up a window that says: "Your computer has been infected by the so-and-so worm. To install Linux and prevent this from ever happening again, click OK." (This worm should be socially responsible. We don't want to force Linux on the masses, just gently persuade them using Windows lack of security as a tool.)
4. Continue to propogate as long as the user clicks "Cancel".
5. When the user clicks "OK":
5a. ping a mirror list to find the fastest mirror
5b. write a kickstart to the boot directory to use that mirror.
5c. modify the boot.ini file to boot Grub.
5d. Reboot the machine, and it shall be cleansed! -
Request for virus writers:
I'm still waiting for a worm that installs Linux on the infected computer.
Propogation:
Scan random IP addresses, use multiple Windows exploits, etc. This part has been done a thousand times before, no need to reinvent the wheel.
Payload:
1. The worm itself
2. Grub for Dos
3. The contents of a network install disk
Behavior:
1. Upon infection, the worm will install Grub for Dos, and copy the contents of the network boot disk into c:\boot, but will not modify the boot.ini file.
2. The worm process will run in the background, and attempt to propogate itself.
3. At a predefined interval, the worm will pop up a window that says: "Your computer has been infected by the so-and-so worm. To install Linux and prevent this from ever happening again, click OK." (This worm should be socially responsible. We don't want to force Linux on the masses, just gently persuade them using Windows lack of security as a tool.)
4. Continue to propogate as long as the user clicks "Cancel".
5. When the user clicks "OK":
5a. ping a mirror list to find the fastest mirror
5b. write a kickstart to the boot directory to use that mirror.
5c. modify the boot.ini file to boot Grub.
5d. reboot the machine, and it shall be cleansed! -
More comfortable link..
..to a print edition of the quite insightful article.
-
If your company has successfully migrated to Linux
on the desktop, and you have (or can whip up) some documents which will help other companies do the same, then you can win a trip to Novell BrainShare in Spain this year. Novell and O'Reilly are offering a nice little prize.
"Your experience can help guide and inspire others who are considering migrating or who have already embarked on the process. We're looking for entries that describe the benefits realized from a desktop migration, a phased migration plan, or the most practical tips for migrating to Linux. We'll publish the best stories and the top entries have a chance to win some fantastic prizes..." -
Re:Interruptshdparm has to honestly be one of the most undelooked at tools for increasing performance in a Linux system. Everything will get a boost from using hdparm - just remember to update your
/etc/rc* scripts to reinstate your choices on reboot. A good document for hdparm can be found here: -
Re:JDSSort of off topic, but JDS is starting to show up in screenshots of linux machines, even when the main focus of the article isn't JDS.
See Windows Compatibility for the Linux Desktop for an example.
-
All Linux commands
O'Reilly publishing has listing of all Linux commands, at least those that are expected to behave in a conformist way from distro to distro.
-
Re: The point everyone misses
-
Re:Good bit of social engineering
Never heard of a Linux virus?
Granted..it is a LOT more steps to go through to get it to do anything meaningful.
But, could you write a set of instructions that:
runs a keylogger
asks for admin rights and pops up the Admin pw box
Searches through all docs, and finds valid email addresses
Sends itself to those addresses
reports back to home base
and as an after thought, deletes all your /jpg files.
Sure you could.
The tricky part is getting the user to run it. And that's where this one is pretty good. It doesn't do anything that can't be done on another system. It just needs to convince the user that it is something else. -
Re:What about Sylpheed?
I use Sylpheed-claws as well and I must say: it's the stuff.
I used evolution for a while, but it has too many things I don't use (scheduler etc) and it doesn't have enough mail options in my view and a bit slow when you have many messages in a folder.
Then I tried kmail, which is very nice, but due to a bug which seemed to only occur on my ppc based system, it was unable to open my mailbox. I wanted to try something different.
So I tried sylpheed-claws (I think it's something like the developement version of sylpheed). Many options and mailboxes, it reminds me a bit of Eudora on the pc, which is good.
It gets even better with bogofilter (after some configuring)! It blocks 99% of the spam. I wouldn't want to switch to another mail client now.
Here's an article about configuring bogofilter for sylpheed-claws if you like -
Re:Cinelerra
-
You can copy/paste!!
Nice plagarism of Guylhem Aznar's 1/29/04 article at linuxdevcenter!