I reboot every over month. Sometimes theres a power outage. Sometimes I upgrade my kernel. Once the FS is journaling, boot times are more than managable.
Also all the dependencies you add to the boot process have to be on the root partition. I had a friend who upgraded bash once and his system wouldn't boot. Apparently he had a symlink from/bin/bash to/usr/local/bin/bash. Works real well provided/usr is mounted.
Makes sense under the current curcumstances. I think if they manage to get the space elevator up that will change the entire economics of the situation. Currently the costs are to just way to high. If the costs drastically drop then... who knows.
I've had this complaint about word processors for a while now. They tie the formating and the content too closely together. It's a symptom of the WYSIWIG mentality. It's excatly the same as hardcoded constants in programs. Once the formating is inplace it's almost imposible to change on a macroscopic level. It also make it harder to ensure that the formatting conventions are consistant.
I haven't fully tried it but I understand "lyx" attempts to to break the WYSIWYG problem in a user friendlyish way. Docbook also helps but seems a bit too program documentation centric.
Anyway once you decide to seperate formatting and content. Using a text editor rather than a word processor is a logical choice. I like vi but any decent editor should work.
As far as I can tell it's a secrecy/reliability trade off. The question I have is "Is the relationship linear?"
Is there some way the election officials can publish a version of the voting data such that:
1. I can comfirm the my vote is correct. 2. I can do my own vote count and confirm the results. 3. It's hard for others to determine my vote. 4. I can compare my copy of the data with other peoples copies and determine that they are the same. 5. No one added votes to the data.
I'm not really up on cryto enough to determine if this is possible. But such a thing would make me feel alot better.
This is th equivalent of saying. If your house gets robbed and you didn't have an alarm system, it's your fault.
The 2 most responsible parties are the hacker/virus writer and Microsoft. And Microsoft only because they advertise as being secure but present so many possible angles of attack.
The only users who should catch any flack for this are those whose primary area of study is computers.
The fact we have all these viruses running around isn't the users fault; it's ours. Email programs shouldn't be this insecure. And, you should be able to buy a secure computer out of the box.
I'm assuming it's ok to bash both Microsoft and Sendmail at the same time. Since qmail exists, we know these bugs don't have to.
Oh BTW an Open source auto update: cat/etc/cron.weekly apt-get update apt-get upgrade --trivial-only EOF
It's probably not a good solution but thats as far as I'd trust automatic updates. Even then there is no gaurantee from anyone that any update won't cripple operations.
Besides, the complaint about MS isn't that they have shitty code. Anyone can have shitty code. The problem with MS is they habitually make design decisions which encourage security issues and other bugs.
I don't know if this applies to you situation but it can't hurt to check the fan. My work Linux machine got in the habit of crashing for a bit. Turned out the CPU fan wasn't working. I haven't have a crash in months now that I've fixed it.
Anyway Linux machines rarely crash in my experience and my top suspect is ussually hardware when it does.
But Unix is an IDE. It was developed by programmers for programmers. I come accros instances every day where a typical IDE just can't keep up. I've always suspected the root of this complaint is that many programmers are too lazy to learn their way around Unix.
Yeah this is pretty much my system.. The only difference being I don't have any anal retentive people so I just leave anything work related in my inbox. List are automatically sent subfolders so they dont cause problems and spam is deleted on sight ussually well before opening. If I need something I either visualy scan for it or use the search feature. When my inbox gets too huge I shift the oldest few months into a local folder.
No Pain all Gain.
Re:There's one good thing about it.
on
Perl 1.0?
·
· Score: 1
Asking people switch editors is probably taken with more disdain than asking them to switch programming languages. By now I know how to use vi/vim better than most people know how to use emacs. Switching would be a real pain in the ass. However, I can switch the editor to use spaces instead.
Personally I find the use of spaces for indentation to be an abomination. Because what invariably happens is somewhere someone uses 3 spaces instead of 4 or something like that. Then one editor will mix spaces and tabs. I used to have macros that would fix indentation for perl. I'm not sure what I would do for Python.
Re:Check out Internet Mail 2000
on
Replacing SMTP?
·
· Score: 1
Assuming this is how IM2000 would work, it seems like one of those ideas thats great for security but not in practicality. Email is high latency. However users want to power up their MUA and get their email now not wait for a bit then get their email. And I happen to agree with them.
Currently it's the servers that have to pay for the delays but it's not a big deal since they're always on. And since the user is downlowding from a local machine they don't experience the delay.
However is the email is retrieved from the sender when the user requests it. It measn that every morning at the same time all your users are going to get on and and screw your connection. Not to mention they'll still complain to me when it's someone else's server which is down.
1. Languages should be complex. Life is complex. Since a large chunk of programming relates to life in some way it's nice to have a language which can handle the nuances easily.
2. I think programming languages should be allowed to evolve for a bit. Write some programs in it befor you lock it down. Invite your friends to use it. Then you'll know what sucks and needs changing. Concurrency will progably find a way to hurt you no matter what. It makes things messy. Expect pain... be suprised when it doens't come.
3. Hierachies are ok but "file" notation should be avoided if you care about portability. Remember, DOS uses '\'; Unix uses '/'; other things use otherthings. Pick something simple an deligate the problem to the compiler.
4. Yeah running it by experienced programmers is probably a good idea. You may want to run it by inexperienced programmers also.
I think you're missing the point. Whats going on here is a conlfict of two moral ideas.
1. People should be able to enjoy the arts.
2. Artist should get compensated for their efforts.
Since the record companies swindle the artists, the second one takes a back seat to the first. And hence we have the p2p networks.
I think it would make more sense if we just mailed the actual artists in question a 20.
As others have pointed out words like "stealing" and "theft" confuse the issue. Especially since theft is derived from "I should be able to use my stuff whenever I want", which you still can since we are getting a copy.
I'm gonna say Linux hands down. Mind you I came from the SCO=evil thought line and this is just a rationalization. Here goes.
1. Linux is low cost which means you can have alot of test systems. Each developer can have a Linux box in his cubicle. Having the ability to play with and test things on your own with out screwing everyone else up is a big benefit.
2. Linux is more wide spread so much of the common software you use probably works better there anyway.
3. Linux isn't going anywhere. Despight SCO's best effort they'll never be able to take control of it. It's already on millions of computera and has thousands of developers. It won. Game Set Match. SCO is an unknown horse on this front.
4. I have yet to see any comercial Unix beat Linux in usability.
Anyway I think the little things are really where Linux will excell over SCO.
In my experience that seems about right. I'm using AxKit with caching shutoff and my own Language module and those are about the results I get. For me its not a big deal since speed isn't that important.
What little I have looked at the speed issue points to 2 things. First caching probably helps alot. Second it may pay to customize the output code. From the few performance tests I've done libxml's output code was the main slow down. Keeping in mind the performance testing was done on C++ code not perl code. It may be possible to write something that walks the DOM and spews the result in a much faster fashion.
While I'm not a master yet there is at least a kernel of truth here. When I first started programming all my code was unstuctured messy and not really all that great. My father said I needed to follow top down design. Now 12+ years later, I still don't design my code, but for some reason it comes out clean and maintainable.
I guess it's the experience base. I'm much more likely to know what my code should look like. And when it starts to get messy, I can figure out how to correct it with a fair amount of ease.
My favorite keyboards are the Keytronic ones. I find the feel compareable to the IBM keyboards. And they don't make that clicky noise. There a few thing I realy like about them.
1. Durability. The one I have at home has survived 6 years of mistreatment and neglect.
2. Keyspacing. Many of the cheaper keybords seem to be slightly smaller and it's really annoying.
3. Feel. The keys don't wobble like a Microsoft keyboard. And the action seems to be excellent.
The main problem, I have with them is that thier website doesn't list any ergonomic keyboards. And I may want to get one of those eventually.
There are other issues in this section: if a company pays employees to contribute to GPL'd software, they might not be able to let the company be the copyright holder, because they do it for money, and the GPL allegedly says you can only do this free of charge. (Is that right?)
No the GPL requires that the code be "Free as in Freedom". Whether people are paid to write it or charge you for a copy is completely irrelivent. What is required is that the source code be available and that it be distributed under the GPL. This way when I get a copy I can distibute it to my friends.
I regret to inform you that I cannot praticipate in this travesty. I will only participate in the merchandising for good movies. Episodes I and II fail to qualify. The tought of you recieving any money for those is too horrible for my participation.
While I realize the GNU/Linux versus Linux issue is a sore topic for many slashdotters, RMS is correct. The kernel is useless without the rest of the software. And having just finished making a Linux From Scratch system, I now know just how correct he is. Most of the software I dowloaded came directy from the GNU ftp site.
Also in light of the SCO lawsuit, he has to make sure that Linux and the GNU software are viewed seperately. If for some strange reason SCO manages to nuke Linux, he can't allow it to nuke the GNU projects as well.
Also assuming for some strange reason SCO manages to get rid of Linux, the GNU project will in all likely hood go on and so will the free software/open source communities. I like "Unix" like operating systems and so do a number of other people. They will continue because we need them to.
For personal aquariums and the like I think this is an awsome idea. I think would be quite entertaining to turn of the lights and have glowing fish in the tank.
And in this case I think the likely hood of an escaped glowing fish having an advantage over natural fish somewhat unlikely. I would think the glow would tend to be a big sign saying "Food Here!"
I tend to take a fairly relaxed view of gentetic engineering. I think our chances of stopping it and our chances of stopping genetically modified species from populating the wild are both slim to none. Therefore the best course of action, I can see, is to figure out how to mitigate the detrimental impact.
I agree whole heartedly. It makrs no sense for Debian to limit what arhitectures it supports. The number of hardware dependant packages should be quite small while the number of developers should be fairy large. Thus the cost for debian to add another achitecture should have a much smaller impact than it would on a commercial distro.
Also in the area of text based insatallers. I see no resaon the text based installer cannot be as easy to use as a graphical one. The standard install for any OS is, prep drive, install base, select and install extras. What purpose do the fancy graphics serve?
The only difference I've seen in installers has been hardware detection. It would be nice if the X server install was a bit smarter. And sometimes soundcards can be freaky.
What I've been wondering about recently is which of the 2 is more important. I'm currently leaning toward the audit trail being more important. I think it's easier to cheat the counting than it is to abuse enough individual voters.
Slashdot Mirror
I reboot every over month. Sometimes theres a power outage. Sometimes I upgrade my kernel. Once the FS is journaling, boot times are more than managable.
/bin/bash to /usr/local/bin/bash. Works real well provided /usr is mounted.
Also all the dependencies you add to the boot process have to be on the root partition. I had a friend who upgraded bash once and his system wouldn't boot. Apparently he had a symlink from
Makes sense under the current curcumstances. I think if they manage to get the space elevator up that will change the entire economics of the situation. Currently the costs are to just way to high. If the costs drastically drop then... who knows.
I've had this complaint about word processors for a while now. They tie the formating and the content too closely together. It's a symptom of the WYSIWIG mentality. It's excatly the same as hardcoded constants in programs. Once the formating is inplace it's almost imposible to change on a macroscopic level. It also make it harder to ensure that the formatting conventions are consistant.
I haven't fully tried it but I understand "lyx" attempts to to break the WYSIWYG problem in a user friendlyish way. Docbook also helps but seems a bit too program documentation centric.
Anyway once you decide to seperate formatting and content. Using a text editor rather than a word processor is a logical choice. I like vi but any decent editor should work.
As far as I can tell it's a secrecy/reliability trade off. The question I have is "Is the relationship linear?"
Is there some way the election officials can publish a version of the voting data such that:
1. I can comfirm the my vote is correct.
2. I can do my own vote count and confirm the results.
3. It's hard for others to determine my vote.
4. I can compare my copy of the data with other peoples copies and determine that they are the same.
5. No one added votes to the data.
I'm not really up on cryto enough to determine if this is possible. But such a thing would make me feel alot better.
This is th equivalent of saying. If your house gets robbed and you didn't have an alarm system, it's your fault.
The 2 most responsible parties are the hacker/virus writer and Microsoft. And Microsoft only because they advertise as being secure but present so many possible angles of attack.
The only users who should catch any flack for this are those whose primary area of study is computers.
The fact we have all these viruses running around isn't the users fault; it's ours. Email programs shouldn't be this insecure. And, you should be able to buy a secure computer out of the box.
I'm assuming it's ok to bash both Microsoft and Sendmail at the same time. Since qmail exists, we know these bugs don't have to.
/etc/cron.weekly
Oh BTW an Open source auto update:
cat
apt-get update
apt-get upgrade --trivial-only
EOF
It's probably not a good solution but thats as far as I'd trust automatic updates. Even then there is no gaurantee from anyone that any update won't cripple operations.
Besides, the complaint about MS isn't that they have shitty code. Anyone can have shitty code. The problem with MS is they habitually make design decisions which encourage security issues and other bugs.
I don't know if this applies to you situation but it can't hurt to check the fan. My work Linux machine got in the habit of crashing for a bit. Turned out the CPU fan wasn't working. I haven't have a crash in months now that I've fixed it.
Anyway Linux machines rarely crash in my experience and my top suspect is ussually hardware when it does.
But Unix is an IDE. It was developed by programmers for programmers. I come accros instances every day where a typical IDE just can't keep up. I've always suspected the root of this complaint is that many programmers are too lazy to learn their way around Unix.
Yeah this is pretty much my system.. The only difference being I don't have any anal retentive people so I just leave anything work related in my inbox. List are automatically sent subfolders so they dont cause problems and spam is deleted on sight ussually well before opening. If I need something I either visualy scan for it or use the search feature. When my inbox gets too huge I shift the oldest few months into a local folder.
No Pain all Gain.
Asking people switch editors is probably taken with more disdain than asking them to switch programming languages. By now I know how to use vi/vim better than most people know how to use emacs. Switching would be a real pain in the ass. However, I can switch the editor to use spaces instead.
Personally I find the use of spaces for indentation to be an abomination. Because what invariably happens is somewhere someone uses 3 spaces instead of 4 or something like that. Then one editor will mix spaces and tabs. I used to have macros that would fix indentation for perl. I'm not sure what I would do for Python.
Assuming this is how IM2000 would work, it seems like one of those ideas thats great for security but not in practicality. Email is high latency. However users want to power up their MUA and get their email now not wait for a bit then get their email. And I happen to agree with them.
Currently it's the servers that have to pay for the delays but it's not a big deal since they're always on. And since the user is downlowding from a local machine they don't experience the delay.
However is the email is retrieved from the sender when the user requests it. It measn that every morning at the same time all your users are going to get on and and screw your connection. Not to mention they'll still complain to me when it's someone else's server which is down.
1. Languages should be complex. Life is complex. Since a large chunk of programming relates to life in some way it's nice to have a language which can handle the nuances easily.
2. I think programming languages should be allowed to evolve for a bit. Write some programs in it befor you lock it down. Invite your friends to use it. Then you'll know what sucks and needs changing. Concurrency will progably find a way to hurt you no matter what. It makes things messy. Expect pain... be suprised when it doens't come.
3. Hierachies are ok but "file" notation should be avoided if you care about portability. Remember, DOS uses '\'; Unix uses '/'; other things use otherthings. Pick something simple an deligate the problem to the compiler.
4. Yeah running it by experienced programmers is probably a good idea. You may want to run it by inexperienced programmers also.
I think you're missing the point. Whats going on here is a conlfict of two moral ideas.
1. People should be able to enjoy the arts.
2. Artist should get compensated for their efforts.
Since the record companies swindle the artists, the second one takes a back seat to the first. And hence we have the p2p networks.
I think it would make more sense if we just mailed the actual artists in question a 20.
As others have pointed out words like "stealing" and "theft" confuse the issue. Especially since theft is derived from "I should be able to use my stuff whenever I want", which you still can since we are getting a copy.
And the majority of the blocks would be on the bottom. So assuming you've built a pyramid or two before, you could really rock and roll for a bit.
I'm gonna say Linux hands down. Mind you I came from the SCO=evil thought line and this is just a rationalization. Here goes.
1. Linux is low cost which means you can have alot of test systems. Each developer can have a Linux box in his cubicle. Having the ability to play with and test things on your own with out screwing everyone else up is a big benefit.
2. Linux is more wide spread so much of the common software you use probably works better there anyway.
3. Linux isn't going anywhere. Despight SCO's best effort they'll never be able to take control of it. It's already on millions of computera and has thousands of developers. It won. Game Set Match. SCO is an unknown horse on this front.
4. I have yet to see any comercial Unix beat Linux in usability.
Anyway I think the little things are really where Linux will excell over SCO.
In my experience that seems about right. I'm using AxKit with caching shutoff and my own Language module and those are about the results I get. For me its not a big deal since speed isn't that important.
What little I have looked at the speed issue points to 2 things. First caching probably helps alot. Second it may pay to customize the output code. From the few performance tests I've done libxml's output code was the main slow down. Keeping in mind the performance testing was done on C++ code not perl code. It may be possible to write something that walks the DOM and spews the result in a much faster fashion.
While I'm not a master yet there is at least a kernel of truth here. When I first started programming all my code was unstuctured messy and not really all that great. My father said I needed to follow top down design. Now 12+ years later, I still don't design my code, but for some reason it comes out clean and maintainable.
I guess it's the experience base. I'm much more likely to know what my code should look like. And when it starts to get messy, I can figure out how to correct it with a fair amount of ease.
I have a friend who removed all the permissions from the ie executable. No one can read write or execute it.
It's not the most elegant solution but it's simple. I don't know if it has any nasty side effects.
My favorite keyboards are the Keytronic ones. I find the feel compareable to the IBM keyboards. And they don't make that clicky noise. There a few thing I realy like about them.
1. Durability. The one I have at home has survived 6 years of mistreatment and neglect.
2. Keyspacing. Many of the cheaper keybords seem to be slightly smaller and it's really annoying.
3. Feel. The keys don't wobble like a Microsoft keyboard. And the action seems to be excellent.
The main problem, I have with them is that thier website doesn't list any ergonomic keyboards. And I may want to get one of those eventually.
There are other issues in this section: if a company pays employees to contribute to GPL'd software, they might not be able to let the company be the copyright holder, because they do it for money, and the GPL allegedly says you can only do this free of charge. (Is that right?)
No the GPL requires that the code be "Free as in Freedom". Whether people are paid to write it or charge you for a copy is completely irrelivent. What is required is that the source code be available and that it be distributed under the GPL. This way when I get a copy I can distibute it to my friends.
I regret to inform you that I cannot praticipate in this travesty. I will only participate in the merchandising for good movies. Episodes I and II fail to qualify. The tought of you recieving any money for those is too horrible for my participation.
While I realize the GNU/Linux versus Linux issue is a sore topic for many slashdotters, RMS is correct. The kernel is useless without the rest of the software. And having just finished making a Linux From Scratch system, I now know just how correct he is. Most of the software I dowloaded came directy from the GNU ftp site.
Also in light of the SCO lawsuit, he has to make sure that Linux and the GNU software are viewed seperately. If for some strange reason SCO manages to nuke Linux, he can't allow it to nuke the GNU projects as well.
Also assuming for some strange reason SCO manages to get rid of Linux, the GNU project will in all likely hood go on and so will the free software/open source communities. I like "Unix" like operating systems and so do a number of other people. They will continue because we need them to.
For personal aquariums and the like I think this is an awsome idea. I think would be quite entertaining to turn of the lights and have glowing fish in the tank.
And in this case I think the likely hood of an escaped glowing fish having an advantage over natural fish somewhat unlikely. I would think the glow would tend to be a big sign saying "Food Here!"
I tend to take a fairly relaxed view of gentetic engineering. I think our chances of stopping it and our chances of stopping genetically modified species from populating the wild are both slim to none. Therefore the best course of action, I can see, is to figure out how to mitigate the detrimental impact.
I agree whole heartedly. It makrs no sense for Debian to limit what arhitectures it supports. The number of hardware dependant packages should be quite small while the number of developers should be fairy large. Thus the cost for debian to add another achitecture should have a much smaller impact than it would on a commercial distro.
Also in the area of text based insatallers. I see no resaon the text based installer cannot be as easy to use as a graphical one. The standard install for any OS is, prep drive, install base, select and install extras. What purpose do the fancy graphics serve?
The only difference I've seen in installers has been hardware detection. It would be nice if the X server install was a bit smarter. And sometimes soundcards can be freaky.
What I've been wondering about recently is which of the 2 is more important. I'm currently leaning toward the audit trail being more important. I think it's easier to cheat the counting than it is to abuse enough individual voters.