Are you sure you want your name on products you don't control? The headlines: "Today, thousands of Martin CPUs were racalled after a problem was discovered. Apparently, someone forgot to upload the whole floating-point division table..." --------
Genius dies of the same blow that destroys liberty.
I always tell people "get 100Mbps ethernet now, because you won't want to have to replace it later," but does anyone listen? No.... --------
Genius dies of the same blow that destroys liberty.
...that someone thinks they can shove down our throats. You'd think they'd have learned from the Java experience that people do not want to be tied to a single programming language. Of course, they don't know what an OS or what Open Source is either.
The new Amiga made the smart move of pushing an assembly-level language, so people could use compilers for their preferred language. The new Amiga also didn't cloud their position on "open source".
I hope we see more things like the new Amiga and less like this. --------
Genius dies of the same blow that destroys liberty.
The reason there is almost no documentation for people like you is because it's assumed that you will want to get a little deeper into the system and learn the CLI (command-line interface). This is probably what you want to do. Besides, unless you have a new machine, KDE/GNOME will be too slow for you (and even if you have a new box, it's still nice to have the extra speed).
Here's a quick list of useful commands:
ps afx -- lists all processes
ps afx | less -- lists all processes, page-by-page
programname --help -- gives you help on programname
man programname -- gives you the manual page (more help) for programname
info programname -- gives you the texinfo page (sometimes even more help) for programname
shutdown -h now (as root) -- shuts down Linux
./programname -- runs programname which is located in the current directory
dselect -- the Add/Remove Programs equivalent (learn the keyboard controls first; only applicable to the Debian distribution)
killall netscape -- if netscape hangs
killall -KILL netscape -- if the above didn't work
uparrow -- previous commands you've typed
su [username] -- switch userid to username, or root if username is omitted
pico -w filename -- edit filename
nano -w filename -- some distributions use this one instead
Some packages you'll want to have a look at sometime:
licq -- an ICQ client
Window Maker -- a much faster window manager than KDE/GNOME
vi / vim -- a really powerful editor; really useful once you learn the keyboard controls
emacs -- an editor, and a programming language, and a calculator, and a web browser, and a MIDI player, and a window manager, and an operating system, and the kitchen sink, and the BATHROOM sink.
Sorry, I have to cut this list short. Other duties are calling. Slashdotters: please fill in what I have missed!
--------
Genius dies of the same blow that destroys liberty.
On Debian, the package manager is "dselect". Once you learn the keyboard controls (not hard) it's easy. --------
Genius dies of the same blow that destroys liberty.
Your posts are hard to read. I suggest you start using less abbreviations and more grammar. --------
Genius dies of the same blow that destroys liberty.
There's only one way you can make a difference: Write GOOD free software, and lots of it.
BUT, spend 4 times more time PLANNING your code than you spend writing it. Be a perfectionist -- shoddy code will get us nowhere. Write every function so it's PERFECT before you continue on to the next function. Do more engineering and less aimless coding.
Make your code as simple, secure, efficient, and well-organized as you possibly can. Take pieces of other people's code of equal license. And most of all: don't be afraid to recode!
So let's get off our sorry asses and get organised!
I've written enough. Time to get back to work. I have a distribution to rebuild. --------
Genius dies of the same blow that destroys liberty.
It should be against international law to complain about your taxes until you've lived in Canada. --------
Genius dies of the same blow that destroys liberty.
Your point is undoubtedly true for half of the programmers that hade IDEs, but there's another side to it: Not every programmer has dual infMHz system with infMB of RAM.
I find that using IDEs would be easier if they weren't so slow and bloated. It's much quicker to use vi in textmode than to start X and some GNOME/KDE debugger, and then wait for the GUI each time you want to do something.
I usually have 2 terminals open: one for editing with vi, and the other for running the program. I also tend to set up my makefile so I can issue a "make run" to recompile and execute my code. --------
Okay, I get #1, but how can you hold someone responsible for PUBLIC PROPERTY? When people release something into the public domain, how can they be held responsible for something they no longer control? --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
The GPL only restricts your freedom to restrict others' freedom. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Could you explain to me the difference between the BSD license and the public domain, and why people tend to use the former, rather than the latter? --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Alright, I give that to you. But my point (which you seem to have missed) was that it's typical disciplinary action for violating security policy. Nothing new here. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
It looks like simple security policy enforcement to me.
Think about it: they ran a public server from an internal network that has access to sensitive information. This is very bad, security-wise. What would happen if somebody outside rooted their box? Depending on the information that could be accessed, people could die because some morons were running some IRC server.
This wouldn't be the first organization that's fired employees for breaking the security policy. This story fills me with nausea. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
IPv4 addresses can also be traced to you, albeit with *slightly* more difficulty.
NAT and dynamic IP addresses are the two most troublesome systems on the internet. They're the reason we have all these klugy client-server protocols (instant messengers and the DynDNS come to mind) that would be better replaced by true peer-to-peer protocols (like SMTP, DNS, internet phone, etc).
If you're worried about anonymity, have a look at the Freenet project, rather than hindering the much-needed adoption of IPv6.
Some benefits of IPv6 off the top of my head:
Users get a block of addresses, rather than a single address to split/NAT/etc (Remember: dynIP != security)
Autoconfiguration (plug your new 'net appliance into you home network, and away you go)
Zillions of addresses (good for organization and allowing your appliances to be connected)
Better routing
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
There's nothing really different about the military-grade signal, except the sequence is significantly longer (repeats every 3 days, IIRC), and there are 2 frequencies (for compensation of atmospheric interference).
AFAIK, it's not signed or anything. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Nope, EEPROM isn't secure enough. You need DRAM, and you need to shuffle the key around to avoid electron migration.
Then just have it so if it's tampered with, the power is cut. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Isn't the DUL a little too drastic? After all, I used to run my own mailserver (exim) on my dialup line for outgoing traffic.
Or are there that many spams getting blocked by the DUL that can't also be blocked by the RSS/RBL. --------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Slashdot Mirror
Are you sure you want your name on products you don't control? The headlines: "Today, thousands of Martin CPUs were racalled after a problem was discovered. Apparently, someone forgot to upload the whole floating-point division table..."
--------
Genius dies of the same blow that destroys liberty.
I always tell people "get 100Mbps ethernet now, because you won't want to have to replace it later," but does anyone listen? No....
--------
Genius dies of the same blow that destroys liberty.
...that someone thinks they can shove down our throats. You'd think they'd have learned from the Java experience that people do not want to be tied to a single programming language. Of course, they don't know what an OS or what Open Source is either.
The new Amiga made the smart move of pushing an assembly-level language, so people could use compilers for their preferred language. The new Amiga also didn't cloud their position on "open source".
I hope we see more things like the new Amiga and less like this.
--------
Genius dies of the same blow that destroys liberty.
True, but the way I wrote it doesn't cloud what I'm trying to say.
--------
Genius dies of the same blow that destroys liberty.
The reason there is almost no documentation for people like you is because it's assumed that you will want to get a little deeper into the system and learn the CLI (command-line interface). This is probably what you want to do. Besides, unless you have a new machine, KDE/GNOME will be too slow for you (and even if you have a new box, it's still nice to have the extra speed).
Here's a quick list of useful commands:
Some packages you'll want to have a look at sometime:
Sorry, I have to cut this list short. Other duties are calling. Slashdotters: please fill in what I have missed!
--------
Genius dies of the same blow that destroys liberty.
On Debian, the package manager is "dselect". Once you learn the keyboard controls (not hard) it's easy.
--------
Genius dies of the same blow that destroys liberty.
> > BSD is a mess from a security viewpoint
;)
> Compared to what OS?
Why, Windows 95, of course!
--------
Genius dies of the same blow that destroys liberty.
Your posts are hard to read. I suggest you start using less abbreviations and more grammar.
--------
Genius dies of the same blow that destroys liberty.
This is free software we're talking about. Not every FS programmer has an IT manager with unlimited funds.
--------
There's only one way you can make a difference: Write GOOD free software, and lots of it.
BUT, spend 4 times more time PLANNING your code than you spend writing it. Be a perfectionist -- shoddy code will get us nowhere. Write every function so it's PERFECT before you continue on to the next function. Do more engineering and less aimless coding.
Make your code as simple, secure, efficient, and well-organized as you possibly can. Take pieces of other people's code of equal license. And most of all: don't be afraid to recode!
So let's get off our sorry asses and get organised!
I've written enough. Time to get back to work. I have a distribution to rebuild.
--------
Genius dies of the same blow that destroys liberty.
It should be against international law to complain about your taxes until you've lived in Canada.
--------
Genius dies of the same blow that destroys liberty.
Sadly, not here in the US or Canada. "Everything" is already here, so "nobody" cares.
--------
Genius dies of the same blow that destroys liberty.
Slashdotters are probably more intelligent on
average than the general populace</I>
<P>Yeah... sure...
--------
Genius dies of the same blow that destroys liberty.
... and you know the state of the world in 10 years.
--------
Genius dies of the same blow that destroys liberty.
Your point is undoubtedly true for half of the programmers that hade IDEs, but there's another side to it: Not every programmer has dual infMHz system with infMB of RAM.
I find that using IDEs would be easier if they weren't so slow and bloated. It's much quicker to use vi in textmode than to start X and some GNOME/KDE debugger, and then wait for the GUI each time you want to do something.
I usually have 2 terminals open: one for editing with vi, and the other for running the program. I also tend to set up my makefile so I can issue a "make run" to recompile and execute my code.
--------
Okay, I get #1, but how can you hold someone responsible for PUBLIC PROPERTY? When people release something into the public domain, how can they be held responsible for something they no longer control?
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
The GPL only restricts your freedom to restrict others' freedom.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Could you explain to me the difference between the BSD license and the public domain, and why people tend to use the former, rather than the latter?
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Alright, I give that to you. But my point (which you seem to have missed) was that it's typical disciplinary action for violating security policy. Nothing new here.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
It looks like simple security policy enforcement to me.
Think about it: they ran a public server from an internal network that has access to sensitive information. This is very bad, security-wise. What would happen if somebody outside rooted their box? Depending on the information that could be accessed, people could die because some morons were running some IRC server.
This wouldn't be the first organization that's fired employees for breaking the security policy. This story fills me with nausea.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
IPv4 addresses can also be traced to you, albeit with *slightly* more difficulty.
NAT and dynamic IP addresses are the two most troublesome systems on the internet. They're the reason we have all these klugy client-server protocols (instant messengers and the DynDNS come to mind) that would be better replaced by true peer-to-peer protocols (like SMTP, DNS, internet phone, etc).
If you're worried about anonymity, have a look at the Freenet project, rather than hindering the much-needed adoption of IPv6.
Some benefits of IPv6 off the top of my head:
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
There's nothing really different about the military-grade signal, except the sequence is significantly longer (repeats every 3 days, IIRC), and there are 2 frequencies (for compensation of atmospheric interference).
AFAIK, it's not signed or anything.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Nope, EEPROM isn't secure enough. You need DRAM, and you need to shuffle the key around to avoid electron migration.
Then just have it so if it's tampered with, the power is cut.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Oh, and the alternative is?
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.
Isn't the DUL a little too drastic? After all, I used to run my own mailserver (exim) on my dialup line for outgoing traffic.
Or are there that many spams getting blocked by the DUL that can't also be blocked by the RSS/RBL.
--------
Life is a race condition: your success or failure depends on whether you get the work done on time.