I suppose it seemed rude because there wasn't specific mention of a lack of a netgear driver, simply that wireless networking wasn't supported, period. Something about the choice of phrase seemed to imply that such things were beneath FreeBSD. There was no additional information pointing to anyone working on a driver (there are people doing so), not even the gratuitous 'if you need that sort of support, check linux'. Perhaps I'm reading more into it than I should, though. However, given my experiences with the FreeBSD lists in the past, I don't think so:)
I guess I can undertstand that. I learned UNIX on a commercial version that ran on "midrange" hardware, so I sometimes forget it's not all just PC hardware to everyone;)
I can't say that I disagree with you re: the typical response on a FreeBSD mailing list when looking for support, or at least what my experiences have been. I think the most friendly answer I've ever had was from someone else who was trying to solve the same thing (a kernel configuration issue with a built-in SCSI controller on a Compaq server). The more typical answer is more along this interesting one I came across when trying to determine if some POS Netgear USB 802.11b adapter was supported under FreeBSD: "Wireless networking over USB is not supported on FreeBSD." I suppose that's true. A bit rude, though.
With that said, though, I'm interested in using a good OS, not in socializing on mailing lists. So while I'll bemoan the lack of friendliness and general 1337ism that seems to be present, at least in some of the lists, I still prefer FreeBSD to linux because, in my experience and for my needs, it's been a superior product.
damn, you still have $20,000? I've been out of work for 'only' 8 months, and i've got (I think) $11 (as in eleven and no/100). we can tell who was the ant and who was the grasshopper with their earnings. good luck with the move, if you're seriously considering it. i am myself...
Hahaha, I had the same problem when I first bought my iPod. I had to read the damned directions to find out that the "scroll wheel" was what you used to navigate the menus, not the buttons. It was a lot more elegant than I thought it would be, as I too expected the buttons (I had a first-generation iPod) to do that work. Non-nerds to whom I'd shown the device had no problems figuring it out, though. Not one of them needed my help, either. Damned cool people:-|
While I agree that tapes are the best general backup solution, don't count on 10-year shelf life. Not only does changing drive technology contribute to the problem, the actual magnetic tapes, particularly higher density tapes, don't last so long. still, I agree with what you say - it's hard to beat an inexpensive 2nd-hand tape drive, even if you use all new tapes in it (a good idea).
to further drive this completely off-topic, I'd beg about the greatest warrier to ever live. I'd think it'd either have to be William the Bastard, or the man whom he defeated, Harold. Norman bastard... *mumble* *mumble*
the fact you're having problems with RPMs demonstrates more than half your problem - you're using the wrong distro. you should be using debian, or at least using the apt tools on RedHat/SuSE/whatever the fuck distro you're running that's using RPMs. Me, I use windows.
Even if you lose a disk in each mirror, you can still access all your data too.
if you're not a native english speaker, you can be excused for your ignorance. if you are, you're a fucking idiot that needs to go back to grade school.
note the difference: loose:
1. Not fastened, restrained, or contained: loose bricks.
2. Not taut, fixed, or rigid: a loose anchor line; a loose chair leg.
3. Free from confinement or imprisonment; unfettered: criminals loose in the neighborhood; dogs that are loose on the streets.
4. Not tight-fitting or tightly fitted: loose shoes.
5. Not bound, bundled, stapled, or gathered together: loose papers.
6. Not compact or dense in arrangement or structure: loose gravel.
7. Lacking a sense of restraint or responsibility; idle: loose talk.
8. Not formal; relaxed: a loose atmosphere at the club.
9. Lacking conventional moral restraint in sexual behavior.
10. Not literal or exact: a loose translation.
11. Characterized by a free movement of fluids in the body: a loose cough; loose bowels.
lose:
1. To be unsuccessful in retaining possession of; mislay: He's always losing his car keys.
2.
1. To be deprived of (something one has had): lost her art collection in the fire; lost her job.
2. To be left alone or desolate because of the death of: lost his wife.
3. To be unable to keep alive: a doctor who has lost very few patients.
3. To be unable to keep control or allegiance of: lost his temper at the meeting; is losing supporters by changing his mind.
4. To fail to win; fail in: lost the game; lost the court case.
5. To fail to use or take advantage of: Don't lose a chance to improve your position.
6. To fail to hear, see, or understand: We lost the plane in the fog. I lost her when she started speaking about thermodynamics.
7.
1. To let (oneself) become unable to find the way.
2. To remove (oneself), as from everyday reality into a fantasy world.
8. To rid oneself of: lost five pounds.
9. To consume aimlessly; waste: lost a week in idle occupations.
10. To wander from or become ignorant of: lose one's way.
11.
1. To elude or outdistance: lost their pursuers.
2. To be outdistanced by: chased the thieves but lost them.
12. To become slow by (a specified amount of time). Used of a timepiece.
13. To cause or result in the loss of: Failure to reply to the advertisement lost her the job.
14. To cause to be destroyed. Usually used in the passive: Both planes were lost in the crash.
15. To cause to be damned.
MS FrontPage to the rescue! Do you really need to ask? Why else would someone develop such a cavalier attitude about supporting standards, and instead use the excuse of market share, as opposed to technical correctness?
did he connect all those drives to a single port or controller on his mac? I'd agree with you, unless he's just wanting a large filesystem and isn't particularly interested in the overall throughput.
as to being on the front page, do some case mods, add some CCFLs, and some blinking LEDs for each drive, and you should be all set!
The difference in the ROM between Macintosh boards and PC boards is for Open Firmware enumeration. Without that, no operating system that relies on Open Firmware to provide the list of hardware will work. Linux can access a lot of hardware (once it's booted) that isn't normally useable in a Mac ( Promise RAID cards, 3com NICs, etc.), but it won't be available until linux has booted from hardware that Open Firmware supports.
You don't mention how many on-call at once? Is there a primary contact and a secondary contact? At my last job, there was a primary contact, who would receive the initial call. If, within a given time period, there was no response, the secondary person would be called. How about giving the pagers to two people each week - if you've got seven people, you could have time off between the time spent as primary and secondary, or just make everyone do two weeks of on-call (one as the primary contact, one as the secondary), with a large block of free-time before their next on-call bit? *shrugs*
yeah, but both OSes need to know who's reading and writing to the disk at a given point in time. You'd still need some kind of volume manager software, and they're expensive (in comparison to the hardware).
I think the BIOS needs to provide Int13 hooks to the boot device. i've got a pc at work that boots from USB - i'll try to remember to bring my usb Zip drive and see if it'll boot from that. good point about LinuxBIOS!
i think NeXT was a BSD 4.3 hybrid with a Mach microkernel and Objective-C framework. Given that OS X is a BSD hybrid with a Mach microkernel, it seems to me that Apple did stick with NeXT, and modernized it a bit by throwing in stuff from a 4.4-lite compatible BSD (FreeBSD). Since Apple acquired NeXT (or the converse could be said to be true as well), it wouldn't make sense for them to take linux and try to build their new OS from the ground up on that. Besides, remember what linux was like in 1997? Think how much it's changed since then, and how much continual updating Apple would need to do to keep their OS current, in terms of VM and filesystem hooks, etc. I'll give you that they do make stupid decisions, though. Frequently. Sometimes the excuses can be argued to come from fucked-up copyright laws and the need to enforce them or lose intellectual property to the public domain. That doesn't excuse most of their behavior, though. Still in all, I switched to the mac platform when os X came out, and haven't looked back. it's not because of the computers, or their policies, but the OS is superb. I personally would rather run my UNIX on someone's proprietary hardware and be able to acquire and run natively all the software i need to interact with Windows users (most of the world, after all) than run UNIX on a widely available platform, but have to resort to Windows on said platform to do the same from time to time. ymmv. imo, OS X really is a desktop UNIX os. I don't think I'd use it for a server (I'd use BSD or Linux on ia32), but it's a nice environment to work in.
Slashdot Mirror
I'm glad someone appreciated it. Shit, I thought I'd get at least *one* +1; Funny out of that crap. Moderators have no sense of humour....
I suppose it seemed rude because there wasn't specific mention of a lack of a netgear driver, simply that wireless networking wasn't supported, period. Something about the choice of phrase seemed to imply that such things were beneath FreeBSD. :)
There was no additional information pointing to anyone working on a driver (there are people doing so), not even the gratuitous 'if you need that sort of support, check linux'.
Perhaps I'm reading more into it than I should, though. However, given my experiences with the FreeBSD lists in the past, I don't think so
you missed a line...
a littlet eapot.shtml :D
i'm a little teapot
short and stout
here is my handle
here is my spout
when i get all steamed up
hear me shout
tip me over and pour me out
if you need pictures to go along with this:
http://www.enchantedlearning.com/rhymes/Im
Hahahaha, holy shit! Why does that sound so plausible?
I guess I can undertstand that. I learned UNIX on a commercial version that ran on "midrange" hardware, so I sometimes forget it's not all just PC hardware to everyone ;)
I can't say that I disagree with you re: the typical response on a FreeBSD mailing list when looking for support, or at least what my experiences have been. I think the most friendly answer I've ever had was from someone else who was trying to solve the same thing (a kernel configuration issue with a built-in SCSI controller on a Compaq server). The more typical answer is more along this interesting one I came across when trying to determine if some POS Netgear USB 802.11b adapter was supported under FreeBSD:
"Wireless networking over USB is not supported on FreeBSD."
I suppose that's true. A bit rude, though.
With that said, though, I'm interested in using a good OS, not in socializing on mailing lists. So while I'll bemoan the lack of friendliness and general 1337ism that seems to be present, at least in some of the lists, I still prefer FreeBSD to linux because, in my experience and for my needs, it's been a superior product.
damn, you still have $20,000? I've been out of work for 'only' 8 months, and i've got (I think) $11 (as in eleven and no/100).
we can tell who was the ant and who was the grasshopper with their earnings.
good luck with the move, if you're seriously considering it. i am myself...
not quite the last, unfortunately. and i don't have one attached externally, either.
ah, well...
Hahaha, I had the same problem when I first bought my iPod. I had to read the damned directions to find out that the "scroll wheel" was what you used to navigate the menus, not the buttons. It was a lot more elegant than I thought it would be, as I too expected the buttons (I had a first-generation iPod) to do that work. :-|
Non-nerds to whom I'd shown the device had no problems figuring it out, though. Not one of them needed my help, either. Damned cool people
Ouch! you don't have to rub it in - I'm looking for work... :/
While I agree that tapes are the best general backup solution, don't count on 10-year shelf life. Not only does changing drive technology contribute to the problem, the actual magnetic tapes, particularly higher density tapes, don't last so long. still, I agree with what you say - it's hard to beat an inexpensive 2nd-hand tape drive, even if you use all new tapes in it (a good idea).
If you're going to do IDE, don't bother with those 'winraid' cards like promise, et al.
check out these - no drivers required, nothing fancy, and if one disk dies, it automatically switches to the other...
http://www.arcoide.com/index.html
to further drive this completely off-topic, I'd beg about the greatest warrier to ever live. I'd think it'd either have to be William the Bastard, or the man whom he defeated, Harold. Norman bastard... *mumble* *mumble*
maybe he was abbreviating ectoplasmic, for some reason?
*shrugs*
the fact you're having problems with RPMs demonstrates more than half your problem - you're using the wrong distro. you should be using debian, or at least using the apt tools on RedHat/SuSE/whatever the fuck distro you're running that's using RPMs. Me, I use windows.
Even if you lose a disk in each mirror, you can still access all your data too.
if you're not a native english speaker, you can be excused for your ignorance. if you are, you're a fucking idiot that needs to go back to grade school.
note the difference:
loose:
1. Not fastened, restrained, or contained: loose bricks.
2. Not taut, fixed, or rigid: a loose anchor line; a loose chair leg.
3. Free from confinement or imprisonment; unfettered: criminals loose in the neighborhood; dogs that are loose on the streets.
4. Not tight-fitting or tightly fitted: loose shoes.
5. Not bound, bundled, stapled, or gathered together: loose papers.
6. Not compact or dense in arrangement or structure: loose gravel.
7. Lacking a sense of restraint or responsibility; idle: loose talk.
8. Not formal; relaxed: a loose atmosphere at the club.
9. Lacking conventional moral restraint in sexual behavior.
10. Not literal or exact: a loose translation.
11. Characterized by a free movement of fluids in the body: a loose cough; loose bowels.
lose:
1. To be unsuccessful in retaining possession of; mislay: He's always losing his car keys.
2.
1. To be deprived of (something one has had): lost her art collection in the fire; lost her job.
2. To be left alone or desolate because of the death of: lost his wife.
3. To be unable to keep alive: a doctor who has lost very few patients.
3. To be unable to keep control or allegiance of: lost his temper at the meeting; is losing supporters by changing his mind.
4. To fail to win; fail in: lost the game; lost the court case.
5. To fail to use or take advantage of: Don't lose a chance to improve your position.
6. To fail to hear, see, or understand: We lost the plane in the fog. I lost her when she started speaking about thermodynamics.
7.
1. To let (oneself) become unable to find the way.
2. To remove (oneself), as from everyday reality into a fantasy world.
8. To rid oneself of: lost five pounds.
9. To consume aimlessly; waste: lost a week in idle occupations.
10. To wander from or become ignorant of: lose one's way.
11.
1. To elude or outdistance: lost their pursuers.
2. To be outdistanced by: chased the thieves but lost them.
12. To become slow by (a specified amount of time). Used of a timepiece.
13. To cause or result in the loss of: Failure to reply to the advertisement lost her the job.
14. To cause to be destroyed. Usually used in the passive: Both planes were lost in the crash.
15. To cause to be damned.
MS FrontPage to the rescue! Do you really need to ask? Why else would someone develop such a cavalier attitude about supporting standards, and instead use the excuse of market share, as opposed to technical correctness?
as to being on the front page, do some case mods, add some CCFLs, and some blinking LEDs for each drive, and you should be all set!
The difference in the ROM between Macintosh boards and PC boards is for Open Firmware enumeration. Without that, no operating system that relies on Open Firmware to provide the list of hardware will work. Linux can access a lot of hardware (once it's booted) that isn't normally useable in a Mac ( Promise RAID cards, 3com NICs, etc.), but it won't be available until linux has booted from hardware that Open Firmware supports.
You don't mention how many on-call at once? Is there a primary contact and a secondary contact?
At my last job, there was a primary contact, who would receive the initial call. If, within a given time period, there was no response, the secondary person would be called.
How about giving the pagers to two people each week - if you've got seven people, you could have time off between the time spent as primary and secondary, or just make everyone do two weeks of on-call (one as the primary contact, one as the secondary), with a large block of free-time before their next on-call bit?
*shrugs*
damn, i remember playing that game *long* ago. not the particular module you reference, just traveller in general. geez. thanks for the flashback...
doesn't UDB refer to the versions of DB2 that run on Open Systems (aix, solaris, hp-ux, linux) and windows nt derivatives?
yeah, but both OSes need to know who's reading and writing to the disk at a given point in time. You'd still need some kind of volume manager software, and they're expensive (in comparison to the hardware).
I think the BIOS needs to provide Int13 hooks to the boot device. i've got a pc at work that boots from USB - i'll try to remember to bring my usb Zip drive and see if it'll boot from that.
good point about LinuxBIOS!
i think NeXT was a BSD 4.3 hybrid with a Mach microkernel and Objective-C framework. Given that OS X is a BSD hybrid with a Mach microkernel, it seems to me that Apple did stick with NeXT, and modernized it a bit by throwing in stuff from a 4.4-lite compatible BSD (FreeBSD).
Since Apple acquired NeXT (or the converse could be said to be true as well), it wouldn't make sense for them to take linux and try to build their new OS from the ground up on that. Besides, remember what linux was like in 1997? Think how much it's changed since then, and how much continual updating Apple would need to do to keep their OS current, in terms of VM and filesystem hooks, etc.
I'll give you that they do make stupid decisions, though. Frequently. Sometimes the excuses can be argued to come from fucked-up copyright laws and the need to enforce them or lose intellectual property to the public domain. That doesn't excuse most of their behavior, though.
Still in all, I switched to the mac platform when os X came out, and haven't looked back. it's not because of the computers, or their policies, but the OS is superb. I personally would rather run my UNIX on someone's proprietary hardware and be able to acquire and run natively all the software i need to interact with Windows users (most of the world, after all) than run UNIX on a widely available platform, but have to resort to Windows on said platform to do the same from time to time. ymmv. imo, OS X really is a desktop UNIX os. I don't think I'd use it for a server (I'd use BSD or Linux on ia32), but it's a nice environment to work in.