Obviously after the voter verifies that their vote is printed correctly on the card it is dropped in a standard ballot box. This way you can use the printouts to do a manual recount, which is about the only reliable way to detect tampering with the machines.
Heck, if you make it so the voters can visually inspect the printout and verify that it says the same thing they punched in on the machine, then you don't even have to trust the machine. All you have to do is randomly recount a portion of the precints using the paper ballots and compare them to the machine tallies.
It doesn't scale well. The population of Canada is about an order of magitude smaller than the population of the US. The Election officials and staffers in the US are already overworked as it is, even with the votes counted electronically. That system is also extremely labor intensive, which is why the US started switching to mechanical voting years ago.
The warning is to prevent companies from accidentally getting GPL code in something they plan to modify and release for profit. The FreeBSD kernel in the screenshot will be contaminated by GPL and it's viral properties, which means it cannot be used without abiding by the terms of the GPL.
FreeBSD does have lots of GPL code in the (optional) userland tools, although the system tools (cp, mount, etc...) are BSD licensed. This allows you to use FreeBSD on a desktop PC (with Gnome) or in a router. Companies like FreeBSD because they can modifiy the code in interesting ways and sell it without having to give away the farm.
Believe it or not, significant portions of the FreeBSD Kernel and userland come from companies donating the code back to the community, despite the lack of legal requirement that they do so.
Does the BIOS do some sort of emulation that makes the parallel port device look like a regular ATA device (I've seen Dells do this with floppy drives)? If not, your chances of finding support are vastly deminished. The only parallel port mass storage device supported is the AIC-7110 SCSI controller built into various Iomega products.
Java JVMs are a port, like most software on FreeBSD. Java is a little unusual in that the port cannot fetch the source tarballs directly due to licensing restricitons, so when you cd to/usr/ports/java/jdk13 and do a "make install" it will tell you what page to go to in order to download the sources and patches.
The ports tree actually contains several different JVMs for you to choose from, including Sun JDK1.1 to JDK1.4, Blackdown JDK 1.2 to 1.4 (and JRE 1.1) -- but it runs under the linuxulator, the Linux Sun JDKs for 1.2 to 1.4, and the Diablo JDK 1.3 kit. Java is not included in the base operating system because the FreeBSD core team wants to keep the core size as small and efficent as possible.
I've used those toughbooks, and I was not impressed. The case is probably plenty tough (I never tested this part) but the rest of the machine is a pretty mediocre laptop. It just wasn't as polished as most of the other (HP, Dell, Apple) laptops I've used. Just my US$0.02.
When posting on dodgy servers, I've taken to sticking the entire contents of my message in the cut buffer before posting, so if the site barfs and the back button doesn't work correctly I can still post the message. That's saved me a couple of times when the weblog coders decided to PRAGMA: NOCACHE their input fields for some reason.
These -HACKs books are for Series 1, which is pretty stable these days. Currently it's a fair bit harder to hack the Series 2 because there are more legal implications (especially with the DMCA) and Tivo has gotten smarter about keeping people out of their box. It's kinda sad actually, the hacker community kept Tivo alive and running during the formative years, and now they're doing everything they can to lock them out. It's like the Tivo guys have started listening to the big Media guys.
That doesn't help the damn internal websites at work that don't work with Mozilla. Besides, it's not like my GF just choose her bank becaues it was closest or something, that was the one she chose because it was the best in several important areas for her. Unfortunatly you can't test their internal webpages until AFTER you sign up.
I've also run into problems with surprisingly high profile sites, like buy.com. This is a problem since I run FreeBSD and have to pull out Netscape 4 to get it working, or sometimes even just wait until I get to a windows machine at work.
You guys must not be using the same web that I am. While I can still use Mozilla for most of my web browsing, there is still that 5% of websites that don't work. It is almost always a javascript issue, and almost aways listed as an "advocacy bug" in bugzilla. This drives me nuts. I can tell you right now that BBandT bank is not going to fix their website anytime soon. Wouldn't it have made more sense to implement those few "broken" features and pop up a warning about them being depricated/contact the webmaster? Once most sites stop using them, THEN you can remove them from the browser. My GF gave up on Mozilla because it just didn't work for her online banking and a few other sites she frequents. Yes, I told the webmasters about the problem, but most of the time they're just using some out-of-the-box web services suite and have no idea of how to fix it. In a couple of instances the original company is out of business (oh those.coms ) but they figure: why fix it, it works with everything here?
IMHO, advocacy bugs are one of the leading causes of "screw it, I'm switching back to IE".
2) Proper preservation must be taken in the original form. 35mm films should be transcribed to 35mm so they can be watched in original form in the future. I think nitrate must be sacrificed (even though they say it has a different glow on projeciton) and acetate used instead, but the importance of original media in film archiving is not to be understated.
Why is this? It seems to me that by not updating the medium, you run the risk of not being able to play your preserved media because all of the players have decayed with age and lack of spare parts. What if the original medium was magnetic tape? Would it be wrong to copy it over to a modern HDD or optical solution? Do we really care if the tint/contrast/dynamic range is slightly different (usually more stable) on the preserved copy? Mandating that all preservation must keep the same medium seems like an unreasonable request when you're dealing with tons (literally) of 35mm and prints, doubly so if you have aging technologies like microfilm and microfiche or other things that may (or already have) become obsolete in the near future.
Pshaw, I remember having to choose between the 20 and 40MB HDD (back when $1/meg was some holy grail) and thinking at the time that I was getting into the whole mass storage thing late. I'd gotten so used to the C64 DD Floppies that 20 or 40MB seemed unreasonably large. It took me less than a year to fill that 40MB HDD.
Well, when I was up in Canada, those $2 coins (which have the face of the Queen on the front) were called "moonies" because they had the Queen on the head and a "bear" tail. I guess that hasn't spread too far, but I thought it was cute. I fully agree that "Loonie" is a much better name than "Sakajawea" or even "gold dollar".
This isn't a new question either. When MS originally announced that they were going to integrate the web browser with the OS, people said they were crazy because browsers were huge bloated buggy pieces of software that ground lesser machines to a halt whenever they were started. Other people pointed out that a software project as large as web browser is virtually impossible to completely secure (witness sendmail), and would be a source of security troubles for MS (of course this was Win95/Win98 days, so people laughed about how the browser wasn't going to make it any _less_ secure than it already was). Thus far the only saving grace is that IE doesn't (on purpose) provide any IP services, which makes it somewhat harder to remotely exploit than sendmail.
So how do we get application developers to start using this facility? I'd rather like to be able to copy a range of cells or an arbitrary graph out of a gnumeric sheet and paste it into koffice? It's very annoying that the only thing most programs will stick in the cut buffer is unformatted text. Heck, in MS Office, when I paste text into a word document, it even gives me the option of keeping the existing formatting, or reformatting it with the current text settings.
People suggesting that you export the document and import it are nuts. That's a huge amount of effort, especially considering how spreadsheets and the like frequently have multiple charts and all sorts of stuff most people don't want in their documents.
Don't you think that's a little disingenuous? When I'm writing reports, I frequently switch out to Excel to generate a chart which I then copy and paste into the Word document. Sometimes I'll copy over the cells instead, or I'll grab a drawing off of the Gimp. The copy and paste is very useful in these cases.
I wish X was just a _little_ bit smarter with the copy and paste support and included a mimetype tag with the data in the cut buffer. That way your program could examine the mimetype to figure out how to handle the data. It would even be possible to transition by just adding a new function that specifies the mimetype in the cut buffer functions, if not specified (old application) assume text/plain. The X consortium moves soo slow though that I doubt I'll see anything like that anytime soon.
Slashdot Mirror
Obviously after the voter verifies that their vote is printed correctly on the card it is dropped in a standard ballot box. This way you can use the printouts to do a manual recount, which is about the only reliable way to detect tampering with the machines.
Heck, if you make it so the voters can visually inspect the printout and verify that it says the same thing they punched in on the machine, then you don't even have to trust the machine. All you have to do is randomly recount a portion of the precints using the paper ballots and compare them to the machine tallies.
It doesn't scale well. The population of Canada is about an order of magitude smaller than the population of the US. The Election officials and staffers in the US are already overworked as it is, even with the votes counted electronically. That system is also extremely labor intensive, which is why the US started switching to mechanical voting years ago.
Maybe the computer should just compare the heights of the candidates and choose whichever is taller? Seems to work for most people.
The warning is to prevent companies from accidentally getting GPL code in something they plan to modify and release for profit. The FreeBSD kernel in the screenshot will be contaminated by GPL and it's viral properties, which means it cannot be used without abiding by the terms of the GPL.
FreeBSD does have lots of GPL code in the (optional) userland tools, although the system tools (cp, mount, etc...) are BSD licensed. This allows you to use FreeBSD on a desktop PC (with Gnome) or in a router. Companies like FreeBSD because they can modifiy the code in interesting ways and sell it without having to give away the farm.
Believe it or not, significant portions of the FreeBSD Kernel and userland come from companies donating the code back to the community, despite the lack of legal requirement that they do so.
Does the BIOS do some sort of emulation that makes the parallel port device look like a regular ATA device (I've seen Dells do this with floppy drives)? If not, your chances of finding support are vastly deminished. The only parallel port mass storage device supported is the AIC-7110 SCSI controller built into various Iomega products.
Java JVMs are a port, like most software on FreeBSD. Java is a little unusual in that the port cannot fetch the source tarballs directly due to licensing restricitons, so when you cd to /usr/ports/java/jdk13 and do a "make install" it will tell you what page to go to in order to download the sources and patches.
The ports tree actually contains several different JVMs for you to choose from, including Sun JDK1.1 to JDK1.4, Blackdown JDK 1.2 to 1.4 (and JRE 1.1) -- but it runs under the linuxulator, the Linux Sun JDKs for 1.2 to 1.4, and the Diablo JDK 1.3 kit. Java is not included in the base operating system because the FreeBSD core team wants to keep the core size as small and efficent as possible.
I've used those toughbooks, and I was not impressed. The case is probably plenty tough (I never tested this part) but the rest of the machine is a pretty mediocre laptop. It just wasn't as polished as most of the other (HP, Dell, Apple) laptops I've used. Just my US$0.02.
When posting on dodgy servers, I've taken to sticking the entire contents of my message in the cut buffer before posting, so if the site barfs and the back button doesn't work correctly I can still post the message. That's saved me a couple of times when the weblog coders decided to PRAGMA: NOCACHE their input fields for some reason.
Plus, how the heck are they going to handle the song translations in the dub?
If you want to get technical then: Copyright Laws. The MPAA/RIAA rules are only enforacable through the Copyright Law framework.
These -HACKs books are for Series 1, which is pretty stable these days. Currently it's a fair bit harder to hack the Series 2 because there are more legal implications (especially with the DMCA) and Tivo has gotten smarter about keeping people out of their box. It's kinda sad actually, the hacker community kept Tivo alive and running during the formative years, and now they're doing everything they can to lock them out. It's like the Tivo guys have started listening to the big Media guys.
700W?!?! Is it just me or does that sound _way_ too high? Every 17" CRT I've ever looked at is in the 100W range.
That doesn't help the damn internal websites at work that don't work with Mozilla. Besides, it's not like my GF just choose her bank becaues it was closest or something, that was the one she chose because it was the best in several important areas for her. Unfortunatly you can't test their internal webpages until AFTER you sign up.
I've also run into problems with surprisingly high profile sites, like buy.com. This is a problem since I run FreeBSD and have to pull out Netscape 4 to get it working, or sometimes even just wait until I get to a windows machine at work.
You guys must not be using the same web that I am. While I can still use Mozilla for most of my web browsing, there is still that 5% of websites that don't work. It is almost always a javascript issue, and almost aways listed as an "advocacy bug" in bugzilla. This drives me nuts. I can tell you right now that BBandT bank is not going to fix their website anytime soon. Wouldn't it have made more sense to implement those few "broken" features and pop up a warning about them being depricated/contact the webmaster? Once most sites stop using them, THEN you can remove them from the browser. My GF gave up on Mozilla because it just didn't work for her online banking and a few other sites she frequents. Yes, I told the webmasters about the problem, but most of the time they're just using some out-of-the-box web services suite and have no idea of how to fix it. In a couple of instances the original company is out of business (oh those .coms ) but they figure: why fix it, it works with everything here?
IMHO, advocacy bugs are one of the leading causes of "screw it, I'm switching back to IE".
Pshaw, I remember having to choose between the 20 and 40MB HDD (back when $1/meg was some holy grail) and thinking at the time that I was getting into the whole mass storage thing late. I'd gotten so used to the C64 DD Floppies that 20 or 40MB seemed unreasonably large. It took me less than a year to fill that 40MB HDD.
Sideshow Bob: There might be a slight ringing in your ears. Fortunatly you will be nowhere near them.
Well, when I was up in Canada, those $2 coins (which have the face of the Queen on the front) were called "moonies" because they had the Queen on the head and a "bear" tail. I guess that hasn't spread too far, but I thought it was cute. I fully agree that "Loonie" is a much better name than "Sakajawea" or even "gold dollar".
This isn't a new question either. When MS originally announced that they were going to integrate the web browser with the OS, people said they were crazy because browsers were huge bloated buggy pieces of software that ground lesser machines to a halt whenever they were started. Other people pointed out that a software project as large as web browser is virtually impossible to completely secure (witness sendmail), and would be a source of security troubles for MS (of course this was Win95/Win98 days, so people laughed about how the browser wasn't going to make it any _less_ secure than it already was). Thus far the only saving grace is that IE doesn't (on purpose) provide any IP services, which makes it somewhat harder to remotely exploit than sendmail.
So how do we get application developers to start using this facility? I'd rather like to be able to copy a range of cells or an arbitrary graph out of a gnumeric sheet and paste it into koffice? It's very annoying that the only thing most programs will stick in the cut buffer is unformatted text. Heck, in MS Office, when I paste text into a word document, it even gives me the option of keeping the existing formatting, or reformatting it with the current text settings.
People suggesting that you export the document and import it are nuts. That's a huge amount of effort, especially considering how spreadsheets and the like frequently have multiple charts and all sorts of stuff most people don't want in their documents.
Don't you think that's a little disingenuous? When I'm writing reports, I frequently switch out to Excel to generate a chart which I then copy and paste into the Word document. Sometimes I'll copy over the cells instead, or I'll grab a drawing off of the Gimp. The copy and paste is very useful in these cases.
I wish X was just a _little_ bit smarter with the copy and paste support and included a mimetype tag with the data in the cut buffer. That way your program could examine the mimetype to figure out how to handle the data. It would even be possible to transition by just adding a new function that specifies the mimetype in the cut buffer functions, if not specified (old application) assume text/plain. The X consortium moves soo slow though that I doubt I'll see anything like that anytime soon.