I'd love to put my Linux box at home on a serial console, but I just haven't been inspired to run the cable I need to do it. If I could just drop the other end of these little radios on whatever machine I want to access to console, that would be great.
Has anyone gotten serial consoles working over the radio?
Would you pay $100 for a 4GB Solid State Drive that is up to 6x faster than a WD Raptor?
---------------
No, especially considering that's just $100 for the card itself - you still have to populate it with the RAM, which will run you $400 using slow RAM, DDR2100, give or take whatever the deal of the week is.
I believe that developers comprehend code just like a computer, one line at a time. We store things in memory (short-term memory) and "run" them through our minds, simulating what the computer might do. Of course, our human syntax checkers can sometime don't catch, but the logic is there.
------------------
I think you're completely off here. Computers have no concept of the end state of a code snippet. Humans work exactly the opposite of computers in most cases: we visualize the final desired state, and begin building the code to reach that state, one line at a time.
Object-orientedness is a way to do what you suggest - write large codebases without requiring the build-one-line-at-a-time approach - but somewhere in there, the code that lets you do in one object method what you would have had to do in 100 lines, is written in 100 lines - you just don't see it publically. RAD tools aid in this goal, too, giving prebuilt frameworks so that you don't have to start with the egg, you can start with a chicken and just cook it. But at some time, someone wrote those hundreds of lines.
Until computing reaches a new paradigm, we're stuck with the step-by-step code that we have to write now. Maybe when we get to quantum computing or something where the code doesn't break down to "If A then B else C", we'll have to break into a new method of programming, but until then, it's line by line for us.
Named pipes are...well..."named" FIFO structures on the filesystem whose contents reside in memory. Check this article for some more information.
If he were using just a pipe, he'd be doing something like....
mplayer blah blah | lame foo blargh
That's not what he's suggesting here - he's suggesting using a named pipe as a temporary repository for your data stream, which is a bad idea, both for the strain on your memory, and the lack of integrity should your computer burp.
Give mplayer the option to output the raw audio to a file which is a named pipe.
Ouch, I wish all my computers had a couple of gigs of memory. Named pipes are OK for data volumes up to a couple of hundred meg that you're going to use immediately or throw away, but if you're taking raw audio and saving it, those are potentially huge amounts of data, and if you're using a named pipe, there are data integrity issues should something happen like your cat walk across the keyboard or you lose power (like, your data goes away).
The concept is sound, but dump it to a file, your computer will thank you in the end and you won't be pissed off when you lose that last Radio BBC broadcast of Dr Who that you've been needing.
Re:I'm waiting for missing track #17 - Silent nigh
on
Automatic Christmas Music
·
· Score: 4, Informative
Garcia said:
Brian, perhaps 17 - Silent night should just be a blank MP3 that goes on for 2:34. I think that one would be the most popular.
In a truly large user environment, where there are 2000+ users, everyone doesn't have administrative access to their workstation. The admin assistants have their apps pre-installed, the call center people have theirs, all based off of a standard base install. No way could the IT department of a company that size manage to install by hand 2000+ workstations.
When you aren't allowed to install software on your computer, it's amazing how simple tech calls are...
User: Yes, I can't install this program my cousin Jeb sent me, can you come install it for me?
ITHelp: No.
U: But I don't have admin acce...
I: No. Installing non-approved software is against company policy.
Ticket closed, all done.
When only the techs have access to their computers, and the techs have to fix their own problems or face reformatting and reinstallation of the base image, there's relatively few problems with people actually installing their own software on their own workstations.
U: OK.
Read the article. They're not limiting how many weeks/months/years you can keep Adult Swim - Episode 342, Princess Zelda Gets Naked. These regularions are explicitly targeted at PPV shows.
PPV television is the only rental outlet where the rentee has no ability to limit the time you have access to the media. Movie stores bill you per time period, places like Netflix bill you per month, services like MovieBeam cycle the movies on and off as they desire.
Only with PPV television does the renter determine how long they want to "rent" the show for. It's a technological loophole in the whole rental concept, and if the PVR companies can figure out a way to close it up, they should.
Besides, most PVRs have the ability to dump digital media to something else - tape, DVD-R, whatever. Just like you used to do, if you want to keep the show, move it off onto permanent storage.
Well, here's your problem....
on
Portable Storage?
·
· Score: 2, Insightful
I wasn't too pleased with the quality of the barebones models I found at Fry's.
A wise man whose name escapes me once said you can have two of the following three:
Cheap
Fast
Good
This isn't a backup drive or something for occassional use you're talking about, you're talking about your data. Get over the barebones models and spend the money on something with a decent shockproof enclosure, a carrying case, and all the other features that make it actually "portable"
I looked through some of the answers here, and as near as I can tell, you've got a bunch of home hobbyists telling you how to back up your home computers. Perhaps all your needs entail is a computer with an external IDE drive array and 4-10 200G SATA drives in it. But from your initial post, it's not clear what you need your offline storage _for_.
First of all, you mention that you generate and use 1G of data a month. What happens at the end of that month? Does all of the data become useless? Is some of it carried through? Is it useful for historical processing for some time after it's not "live" any more? The disposition of that offline data is important; you can't determine how you can most effectively back up your data until you know what you need to do with that data once it's backed up.
Since no one cares about backing up old data that they never use any more, I'm going to assume you need this data in some form in the future. I'm also assuming that your data ages out completely every month.
Realistically, you have two options: Large redundant disk arrays, or tape. Various factors give credence to one or the other.
First of all, get off of the SATA hacks, and realize you're going to need to go to SCSI, whether you end up with disk or tape. You're backing up data, you're going ot want it to be reliably written out, and SCSI is the de facto standard for backup architecture. Yes, you pay more for it, but there's a reason for it: the SCSI equipment I manage at work fails a fraction of the percentage of time that the various IDE/ATA systems fail. While SATA is marketed as a consumer technology, it will never meet the rigors of being a reliable backup methodology.
Media Cost: Tape wins over disk here. LTO tape is running, at a quick check, for about $75 retail for 200/100G tapes. Even assuming only reasonable compression, you're looking at 150G for $75 bucks. And that is single-cart pricing; tape pricing quickly drops if you're ordering in bulk (typically in packs of 10, then at the 3-packs level, then more, check with your preferred media vendor)
Hardware Cost: Disk wins, but it's a double-edged sword - every disk you own has electrical and mechanical failure chances. The more disks you have, the more likely you are to lose one of them. The more you're storing on disk, the more you open yourself to a catastrophic failure of those disks themselves. High-end fast tape drives and libraries are expensive, but they just _work_. You plug them in, load your preferred tape management software (hell, run mtx for that matter), and start backing stuff up. No formatting, settings up arrays, hot-swap schedules, anything like that. But you pay through the nose for it - expect to spend into the $10K range for a large-scale tape storage solution that you could match (in short-term storage duration) for a couple of thousand dollars for a disk-based solution.
Hosting Space: Try to store 10TB of disk, and you'll need an air conditioner in that room just to cool down the disk cabinet and controllers. 10TB of tape just sits there though; you can store 4TB of tape online in a small 3U (about 6 inches) tape library - that's 24 tapes, and such libraries typically also support two drives. Go to 5-6U, and you can get 4 drives and over 50 tapes. If those were 200GB LTO tapes, you'd be looking at up to 10TB of storage available online, or easily offline and off-siteable. In addition, tape is easily expandable. Need more storage space? Buy another tape. No new hardware needed, no power concerns, just drop it in the drive or library and go.
Speed: Disk definitely has an edge. Set up an decent SCSI RAID5 array (real hardware raid across multiple disks on separate physical controllers, not this playtime software 0+1 homebrew IDE raid crap) and watch your write speeds triple. If you need to back up that 1 TB overnight, you don't have much of a choice but to go to disk in some form. But again, you pay a price for it. The speed you save in the
I'm oging to guess no, there's no console version of an aplpication which graphically represents the state of your network traffic. Hence the reason you need to install 40MB of GNOME libraries:)
Next time, in promulgating your esoteric cogitations, or articulating your superficial sentimentalities and amicable, philosophical or psychological observations, beware of platitudinous ponderosity. Let your conversational communications possess a clarified conciseness, a compacted comprehensibleness, coalescent consistency, and a concatenated cogency. Eschew all conglomerations of flatulent garrulity, jejune babblement, and asinine affectations.
Let your extemporaneous descantings and unpremeditated expatiations have intelligibility and veracious vivacity, without rodomontade or thrasonical bombast. Sedulously avoid all polysyllabic profundity, pompous prolixity, psittaceous vacuity ventriloquial verbosity, and vaniloquent vapidity. Shun double-entendres, prurient jocosity, and pestiferous profanity, obscurant or apparent!!
So? So were most cablemodems until recently. VoIP is a new technology to the consumer market, it will take a while for one or two standards to settle, and when they do, just like most things like DVD formats and Cable modem protocols and such, firmware gets upgraded and no one cares. Besides, so their proprietary, what di you want to do, take your hardware and move to some other linux-native VoIP provider? Wait...there aren't any.
Skype is using a proprietary protocol that no VoIP carriers/providers will be using.
You said this already, but so? Who cares what protocol you speak from your headset unit to the 'Net, once it gets to the 'Net it's IP. When it gets to the phone system, it's converted to proprietary digital forms that Sprint or AT&T use, and when it reaches another VoIP carrier, it might convert to another protocol. It doesn't matter though, the frmat is meaningless to the data.
Let me laugh, it just happens that Skype is only able to do audio, so all your upload can be devoted to audio.
Duh. That's why it's Voice over IP. There are no pictures in Voice. If you want videoconferencing, use another service. But if you want good audio quality, use a service that utilizes all of your available bandwidth for audio (go figure, a specialized service works better than a general one).
Do you think Google.com is virtual hosted with dozens of other sites? No, I'm sure it's got it's own IP address dedicated to it alone.
I'm sure it does, but you also have to have the docs in the "blah.foo.com" DocumentRoot as the server's main DocumentRoot. I am assuming that this is not the case. For big sites like Google, their servers might be set up that way,t hey might not. If not, you're screwed using IPs to get to webservers.
You just have to associate the IP with the hostname in your '/etc/hosts' file, and virtual hosts will work even without any DNS servers in the world running.
Right, but that's not what the original post said - it said you'd just have to use the IP address instead of the name. If you're remapping hostnames to IP addresses in your hosts file, you're not just using IP addresses. Virtual Hosts can work without DNS, but you still need that name-to-IP mapping for them to work, whether you do it through DNS or through a hostfile.
Unless the server that lives at IPaddress W.X.Y.Z only hosts 1 server, and that server has it's documents in the server root folder. Most webservers any more use virtual name services to map HTTP requests to the right "web server" and set of documents.
My personal server runs 7 domains with 12 or 13 sites. Some have real docroot folders, some use the default "you aren't looking in the right place" set of docs. But using an IP address to access a web site probably won't work in these days of many servers per machine.
If you create a fan that doesn't need water and guarantees performance of a water cooler, I think it'd be a hit.
It would also be impossible. The only way this would happen would be to use immense volumes of supercooled air. Liquids are a much better conductor of thermal energy; even inefficient liquid cooling systems are more efficient then air-based ones.
your firewall rules should allow your email client to make connections to your mail server ONLY
You assume a network of one - one computer running one firewall.
I have just one computer attached to my Internet-facing network: the Linux box that serves as a NAT/firewall proxy. That is all it does - the PC's inside, all running Windows, know nothing about how to get out to the network, and they have 192.168 private addresses, so nothing inside me network knows how to speak to the net in general.
Your firewall shouldn't have to be able to filter out requests per application, your email client should be smart enough to not render HTML in previews in the first place:)
The problem is, in many places, people still pay per quantity of bandwidth or time online. Saying "filter it at the client" doesn't do anything to stop the spam from being sent to the user, and still requires the user to retreive and parse the message before deciding it's spam and filing it in the circular bin.
No, client-side spam filtering should be the last line of defense against spam. Spam should be killed off before it ever reaches a mailbox, final or intermediate, by the servers that handle the mail.
Wouldn't it be hard to drink very much that way? I mean, even if it's a walnut shell, that's what, half an ounce at a time, at the best, if you hollow it out?
Being unable to send e-mail from the application of my choice would not make for any of my repeat business at said cafe
-------
Being able to prevent spammers from dumping piles of spam out to the world will allow said cafe to stay open, since having their network conenction terminated for spamming wouldn't be of use to anyone.
If you really need to be able to use a local client, they could set it up so that you are given access on a per-MAC, per-person basis. I go in, show my ID, show my MAC address, they enable the firewall for me. Someone else can't use my card, and I can't use someone else's card, and then if something goes wrong, they can say "Sven did it, here's his address and the MAC accress of teh card he was using". Local law enforcement gets a detailed search warrant for a network device identified by MAC address XXX in the possession of Sven, or the equivalent in your local municipality, and another spammer goes to jail.
I would guess that you are a minority of the userbase, and that most people have access to webmail on their remote servers. Inconvenience? Yeah, but not as inconvenient as cafes closing down because they aren't blocking spammers.
Slashdot Mirror
I'd love to put my Linux box at home on a serial console, but I just haven't been inspired to run the cable I need to do it. If I could just drop the other end of these little radios on whatever machine I want to access to console, that would be great.
Has anyone gotten serial consoles working over the radio?
No, especially considering that's just $100 for the card itself - you still have to populate it with the RAM, which will run you $400 using slow RAM, DDR2100, give or take whatever the deal of the week is.
I think you're completely off here. Computers have no concept of the end state of a code snippet. Humans work exactly the opposite of computers in most cases: we visualize the final desired state, and begin building the code to reach that state, one line at a time.
Object-orientedness is a way to do what you suggest - write large codebases without requiring the build-one-line-at-a-time approach - but somewhere in there, the code that lets you do in one object method what you would have had to do in 100 lines, is written in 100 lines - you just don't see it publically. RAD tools aid in this goal, too, giving prebuilt frameworks so that you don't have to start with the egg, you can start with a chicken and just cook it. But at some time, someone wrote those hundreds of lines.
Until computing reaches a new paradigm, we're stuck with the step-by-step code that we have to write now. Maybe when we get to quantum computing or something where the code doesn't break down to "If A then B else C", we'll have to break into a new method of programming, but until then, it's line by line for us.
Wouldn't that be "Shark"?
Named pipes are not |'s.
Named pipes are...well..."named" FIFO structures on the filesystem whose contents reside in memory. Check this article for some more information.
If he were using just a pipe, he'd be doing something like....
That's not what he's suggesting here - he's suggesting using a named pipe as a temporary repository for your data stream, which is a bad idea, both for the strain on your memory, and the lack of integrity should your computer burp.
Ouch, I wish all my computers had a couple of gigs of memory. Named pipes are OK for data volumes up to a couple of hundred meg that you're going to use immediately or throw away, but if you're taking raw audio and saving it, those are potentially huge amounts of data, and if you're using a named pipe, there are data integrity issues should something happen like your cat walk across the keyboard or you lose power (like, your data goes away).
The concept is sound, but dump it to a file, your computer will thank you in the end and you won't be pissed off when you lose that last Radio BBC broadcast of Dr Who that you've been needing.
It would also be a Copyright Infringement of John Cage's most famous work :)
Isn't this tough to do if your computer isn't booting any more?
Nor does the Christmas season last for 4 months
In a truly large user environment, where there are 2000+ users, everyone doesn't have administrative access to their workstation. The admin assistants have their apps pre-installed, the call center people have theirs, all based off of a standard base install. No way could the IT department of a company that size manage to install by hand 2000+ workstations.
When you aren't allowed to install software on your computer, it's amazing how simple tech calls are...
User: Yes, I can't install this program my cousin Jeb sent me, can you come install it for me?
ITHelp: No.
U: But I don't have admin acce...
I: No. Installing non-approved software is against company policy.
Ticket closed, all done.
When only the techs have access to their computers, and the techs have to fix their own problems or face reformatting and reinstallation of the base image, there's relatively few problems with people actually installing their own software on their own workstations. U: OK.
Read the article. They're not limiting how many weeks/months/years you can keep Adult Swim - Episode 342, Princess Zelda Gets Naked . These regularions are explicitly targeted at PPV shows.
PPV television is the only rental outlet where the rentee has no ability to limit the time you have access to the media. Movie stores bill you per time period, places like Netflix bill you per month, services like MovieBeam cycle the movies on and off as they desire.
Only with PPV television does the renter determine how long they want to "rent" the show for. It's a technological loophole in the whole rental concept, and if the PVR companies can figure out a way to close it up, they should.
Besides, most PVRs have the ability to dump digital media to something else - tape, DVD-R, whatever. Just like you used to do, if you want to keep the show, move it off onto permanent storage.
- Cheap
- Fast
- Good
This isn't a backup drive or something for occassional use you're talking about, you're talking about your data. Get over the barebones models and spend the money on something with a decent shockproof enclosure, a carrying case, and all the other features that make it actually "portable"I looked through some of the answers here, and as near as I can tell, you've got a bunch of home hobbyists telling you how to back up your home computers. Perhaps all your needs entail is a computer with an external IDE drive array and 4-10 200G SATA drives in it. But from your initial post, it's not clear what you need your offline storage _for_.
First of all, you mention that you generate and use 1G of data a month. What happens at the end of that month? Does all of the data become useless? Is some of it carried through? Is it useful for historical processing for some time after it's not "live" any more? The disposition of that offline data is important; you can't determine how you can most effectively back up your data until you know what you need to do with that data once it's backed up.
Since no one cares about backing up old data that they never use any more, I'm going to assume you need this data in some form in the future. I'm also assuming that your data ages out completely every month.
Realistically, you have two options: Large redundant disk arrays, or tape. Various factors give credence to one or the other.
First of all, get off of the SATA hacks, and realize you're going to need to go to SCSI, whether you end up with disk or tape. You're backing up data, you're going ot want it to be reliably written out, and SCSI is the de facto standard for backup architecture. Yes, you pay more for it, but there's a reason for it: the SCSI equipment I manage at work fails a fraction of the percentage of time that the various IDE/ATA systems fail. While SATA is marketed as a consumer technology, it will never meet the rigors of being a reliable backup methodology.
I'm oging to guess no, there's no console version of an aplpication which graphically represents the state of your network traffic. Hence the reason you need to install 40MB of GNOME libraries :)
Next time, in promulgating your esoteric cogitations, or articulating your superficial sentimentalities and amicable, philosophical or psychological observations, beware of platitudinous ponderosity. Let your conversational communications possess a clarified conciseness, a compacted comprehensibleness, coalescent consistency, and a concatenated cogency. Eschew all conglomerations of flatulent garrulity, jejune babblement, and asinine affectations.
Let your extemporaneous descantings and unpremeditated expatiations have intelligibility and veracious vivacity, without rodomontade or thrasonical bombast. Sedulously avoid all polysyllabic profundity, pompous prolixity, psittaceous vacuity ventriloquial verbosity, and vaniloquent vapidity. Shun double-entendres, prurient jocosity, and pestiferous profanity, obscurant or apparent!!
From Don't Use Big Words...
Gives a whole new meaning to "pop-up" doesn't it?
Unless the server that lives at IPaddress W.X.Y.Z only hosts 1 server, and that server has it's documents in the server root folder. Most webservers any more use virtual name services to map HTTP requests to the right "web server" and set of documents.
My personal server runs 7 domains with 12 or 13 sites. Some have real docroot folders, some use the default "you aren't looking in the right place" set of docs. But using an IP address to access a web site probably won't work in these days of many servers per machine.
You assume a network of one - one computer running one firewall.
I have just one computer attached to my Internet-facing network: the Linux box that serves as a NAT/firewall proxy. That is all it does - the PC's inside, all running Windows, know nothing about how to get out to the network, and they have 192.168 private addresses, so nothing inside me network knows how to speak to the net in general.
Your firewall shouldn't have to be able to filter out requests per application, your email client should be smart enough to not render HTML in previews in the first place :)
The problem is, in many places, people still pay per quantity of bandwidth or time online. Saying "filter it at the client" doesn't do anything to stop the spam from being sent to the user, and still requires the user to retreive and parse the message before deciding it's spam and filing it in the circular bin.
No, client-side spam filtering should be the last line of defense against spam. Spam should be killed off before it ever reaches a mailbox, final or intermediate, by the servers that handle the mail.
I get these nifty little metal boxes, about half an inch thick.
In the famous words of one of the SNL skits, "You can put your weed in there"
Wouldn't it be hard to drink very much that way? I mean, even if it's a walnut shell, that's what, half an ounce at a time, at the best, if you hollow it out?
Being able to prevent spammers from dumping piles of spam out to the world will allow said cafe to stay open, since having their network conenction terminated for spamming wouldn't be of use to anyone.
If you really need to be able to use a local client, they could set it up so that you are given access on a per-MAC, per-person basis. I go in, show my ID, show my MAC address, they enable the firewall for me. Someone else can't use my card, and I can't use someone else's card, and then if something goes wrong, they can say "Sven did it, here's his address and the MAC accress of teh card he was using". Local law enforcement gets a detailed search warrant for a network device identified by MAC address XXX in the possession of Sven, or the equivalent in your local municipality, and another spammer goes to jail.
I would guess that you are a minority of the userbase, and that most people have access to webmail on their remote servers. Inconvenience? Yeah, but not as inconvenient as cafes closing down because they aren't blocking spammers.