On a more serious note, a similar question was asked some time ago, however on a much larger scale. Some of the suggestions posted in the comments might be relevant to your case.
I suppose the users would have to inform the cableco when they change the device, as (assuming the cableco has set things up properly) cannot change the MAC address and expect to get an IP address automagically. Of course, this doesn't apply if PPPoE is being used.
Given that MAC addresses are given out to companies in blocks, one would simply have to scan for those that belong to known broadband routers. What happens with those that use PCs as NAT boxes, though, is a different matter.
Almost, but not quite. According to Sox's manpage:
CD-R files are used in mastering music Compact Disks. The file format is, as you might expect, raw stereo raw unsigned samples at 44khz. But, there's some blocking/padding oddity in the format, so it needs its own handler.
So it could never really catch fire? Guess ESR needs to update this entry.
The MC6800 microprocessor was the first for which an HCF opcode became widely known. This instruction caused the processor to toggle a subset of the bus lines as rapidly as it could; in some configurations this could actually cause lines to burn up.
Many have stated here already: don't rely on those so-called "résumé writers". I wholeheartedly agree with this, since there is no one way of writing a résumé that works for everyone. However, there are some things to know about résumés that do apply to all.
One of the things that I remember from my tech writing class is the way most people tend to read a résumé. Imagine that you draw two diagonal lines on your average letter- or A4-sized piece of paper from each corner to the opposite corner, thus dividing the page into four triangles. Of these, the topmost triangle is always the one to be read first; if the HR droid has not found anything interesting from a quick scan of this small area, chances are your résumé will be chucked into the bin. Of course, this doesn't mean that you must cram your entire résumé into that top 1/4 of the page, but it is best if you try to place the most relevant information within that space.
Following that, I've found that the following order of items is preferred by HR people:
Name, address, contact info;
Objective;
Skills, in descending order of relevance to the intended job position;
Previous work/experience, in reverse chronological order;
IIRC, on MFM controllers you could jump to the low-level formatting utility by entering the following at DEBUG's dash prompt:
g=c800:8
I'm not sure if SCSI controllers ever had this feature, since most of them have a config utility that's accessible after POST when the BIOS is initialising the controller.
The 0 F mark was chosen because at the time it was the lowest temperature achievable by artificial means (some sort of salt was used, although I can't recall what the chemical's name is). The intention was to reduce the use of negative values in the reporting of weather conditions. Other significant values, like 72 (the average temp on a nice day in some places), 96 (normal body temp), and 228 (boiling point of water) were chosen in a somewhat arbitrary manner; whether the fact that these numbers are evenly divisible by 12 had to do something with it or not is unknown. Later on, revisions to the scale were made, so that body temperature is now 98.6.
... as soon as one of us finds out and submits it to Slashdot, everyone knows.
Ahh, yes...
We are the SlashBorg. Your marketing secrets will be linked from an article in our website for the knowledge of all. Prepare to be Slashdotted. Resistance is futile.
Re:MP 1900+ same as XP 1900+
on
Athlon MP Reviewed
·
· Score: 2, Informative
There are some additional, albeit minor, differences between the MP and XP; IIRC, the MP's hardware data prefetch is optimised for SMP configurations. You can put any Athlon on a 760MP(x) board (even a Duron), but the MP will be a bit faster because of this. However, beyond this, yes, they're pretty much identical.
You don't have to lose the address book feature if your IMAP client can use LDAP. I have used both Netscape, Pine, and OS X Mail.app as IMAP/LDAP clients with Exchange, and haven't lost any e-mail functionality (other than the viruses, that is). You don't get to access the Calendar, Contacts, Tasks, Journal, or Notes that way, though, but that's obvious.
I recently installed 3.0 to replace a 2.8 that I was using as a firewall. At first I didn't want to upgrade due to ipf and ipnat having been removed (ipnat in particular is quite powerful given its simplicity). Fortunately, pf is quite easy to set up, and I managed to do the switch in the course of one work day (most of it spent installing the OS). I noticed the following gotchas, though:
with frag/short is gone. if you have it in your rules, you'll have to remove it. I think scrub does the same, though (but correct me if I'm wrong);
NAT is not quite the same NAT. pf only supports many-to-one at the moment, and the outside address *must* be the machine's external address. If you've used ipchains, you'll recognise this is the same as masquerading.
pflogd doesn't log to syslog. Instead, it dumps logged packets to a binary file, which you then examine with tcpdump.
However, those are minor issues, mind. In the end, I'm quite pleased with the changes. It "feels" much more stable, for one. And the installer couldn't be any simpler: it sets up your disklabels, formats the partitions, configures your network connections, and downloads the OS, and you only need one floppy for that.
Your analogy is, unfortunately, incomplete. Let's review:
If you hired private security guards for your house, and the FBI showed up with a warrant to search the place, would you expect them to turn away the FBI?
In such a case, the following is expected to happen:
FBI spooks obtain search warrant from court;
Spooks knock at your door;
Guards step out and meet spooks;
Spooks show the search warrant to guards;
Guards inform you of the presence of spooks with a search warrant, and (presumably) let them through.
Now, in the case of Magic Lantern, the following *might* happen:
FBI spooks obtain a (possibly fake) lead;
Spooks infect your computer with Magic Lantern, and poke around it as they wish;
You're not informed of what's going on.
So, what's missing here? Simply enough, the agents did not have the consent of the court to infect your computer, and you've been deprived of the knowledge of what occured. This is the major issue here. I wouldn't want them poking inside my computers as much as the next guy, but if they're going to, I'd like to know when they're doing it, and they better have that bloody warrant in hand.
I give it a month before someone figures out how its doing the LAN networking and gets an VPN/IP tunneling server set up so you can do real internet play with Halo
How hard would it be to get OpenBSD to do bridging over an IPSec tunnel? *hint, hint*
That's what I thought would be the case, but didn't want to throw any guesses. I haven't seen it as standard equipment on new computers, though. Meanwhile, it is known that Apple's next Power Macs will come with *both* USB 2.0 and 1394b.
Go to your preferences page, and choose your timezone. To me, your post appears as having been posted at 7:16pm, and I'm in EST. Everything else in this and other articles seems right, too.
Slashdot Mirror
Could you imagine a Beowulf cluster of Tivos?
On a more serious note, a similar question was asked some time ago, however on a much larger scale. Some of the suggestions posted in the comments might be relevant to your case.
I suppose the users would have to inform the cableco when they change the device, as (assuming the cableco has set things up properly) cannot change the MAC address and expect to get an IP address automagically. Of course, this doesn't apply if PPPoE is being used.
Given that MAC addresses are given out to companies in blocks, one would simply have to scan for those that belong to known broadband routers. What happens with those that use PCs as NAT boxes, though, is a different matter.
Almost, but not quite. According to Sox's manpage:
So it could never really catch fire? Guess ESR needs to update this entry.
Perhaps you ought to watch Playing God. It's like watching another episode of the X-Files, but with Mulder getting high.
Many have stated here already: don't rely on those so-called "résumé writers". I wholeheartedly agree with this, since there is no one way of writing a résumé that works for everyone. However, there are some things to know about résumés that do apply to all.
One of the things that I remember from my tech writing class is the way most people tend to read a résumé. Imagine that you draw two diagonal lines on your average letter- or A4-sized piece of paper from each corner to the opposite corner, thus dividing the page into four triangles. Of these, the topmost triangle is always the one to be read first; if the HR droid has not found anything interesting from a quick scan of this small area, chances are your résumé will be chucked into the bin. Of course, this doesn't mean that you must cram your entire résumé into that top 1/4 of the page, but it is best if you try to place the most relevant information within that space.
Following that, I've found that the following order of items is preferred by HR people:
HTH.
IIRC, on MFM controllers you could jump to the low-level formatting utility by entering the following at DEBUG's dash prompt:
I'm not sure if SCSI controllers ever had this feature, since most of them have a config utility that's accessible after POST when the BIOS is initialising the controller.
I'd be more afraid if Meept's great...grandchild were to post on Slashdot in 3003. Think about it...
The 0 F mark was chosen because at the time it was the lowest temperature achievable by artificial means (some sort of salt was used, although I can't recall what the chemical's name is). The intention was to reduce the use of negative values in the reporting of weather conditions. Other significant values, like 72 (the average temp on a nice day in some places), 96 (normal body temp), and 228 (boiling point of water) were chosen in a somewhat arbitrary manner; whether the fact that these numbers are evenly divisible by 12 had to do something with it or not is unknown. Later on, revisions to the scale were made, so that body temperature is now 98.6.
Ahh, yes...
We are the SlashBorg. Your marketing secrets will be linked from an article in our website for the knowledge of all. Prepare to be Slashdotted. Resistance is futile.
There are some additional, albeit minor, differences between the MP and XP; IIRC, the MP's hardware data prefetch is optimised for SMP configurations. You can put any Athlon on a 760MP(x) board (even a Duron), but the MP will be a bit faster because of this. However, beyond this, yes, they're pretty much identical.
This reminds me of the various hacks done on the Green Building at MIT, my favourite being the VU metre.
You don't have to lose the address book feature if your IMAP client can use LDAP. I have used both Netscape, Pine, and OS X Mail.app as IMAP/LDAP clients with Exchange, and haven't lost any e-mail functionality (other than the viruses, that is). You don't get to access the Calendar, Contacts, Tasks, Journal, or Notes that way, though, but that's obvious.
I recently installed 3.0 to replace a 2.8 that I was using as a firewall. At first I didn't want to upgrade due to ipf and ipnat having been removed (ipnat in particular is quite powerful given its simplicity). Fortunately, pf is quite easy to set up, and I managed to do the switch in the course of one work day (most of it spent installing the OS). I noticed the following gotchas, though:
However, those are minor issues, mind. In the end, I'm quite pleased with the changes. It "feels" much more stable, for one. And the installer couldn't be any simpler: it sets up your disklabels, formats the partitions, configures your network connections, and downloads the OS, and you only need one floppy for that.
Your analogy is, unfortunately, incomplete. Let's review:
In such a case, the following is expected to happen:
Now, in the case of Magic Lantern, the following *might* happen:
So, what's missing here? Simply enough, the agents did not have the consent of the court to infect your computer, and you've been deprived of the knowledge of what occured. This is the major issue here. I wouldn't want them poking inside my computers as much as the next guy, but if they're going to, I'd like to know when they're doing it, and they better have that bloody warrant in hand.
I guess that'd be the first smokable that can also be used as a patch.
Well, it could be.
How hard would it be to get OpenBSD to do bridging over an IPSec tunnel? *hint, hint*
Quite trivial, mind you, but wouldn't it be confused with this Cyclone?
That's what I thought would be the case, but didn't want to throw any guesses. I haven't seen it as standard equipment on new computers, though. Meanwhile, it is known that Apple's next Power Macs will come with *both* USB 2.0 and 1394b.
Given that USB 2.0 isn't widespread yet (is it even available anywhere right now?), you forgot:
And that's only for the second revision. It is expected to reach 1600 and 3200 Mbps in the following versions.
It gets better:
Coincidence? Hhmmm...
Redneck: Globalizashun
Elmer Fudd: Gwobawization
Swedish Chef: Glubeleezeshun
1337: g|0b4|1s4710n
The Dialectizer doesn't have 1337 yet, though.
You let a private corporation operate the Space Shuttle, and some dork will find yet another very tall building to crash it into...
Go to your preferences page, and choose your timezone. To me, your post appears as having been posted at 7:16pm, and I'm in EST. Everything else in this and other articles seems right, too.