Plus, I imagine the ZIP compression algorhythm has some interesting mathemetics to it.
He didn't invent the algorithms though... I believe the version 1.x algorithms (squeeze or squish or something starting with squ:) was LZW, and the current 2.x deflate algorithm is pretty much LZ77.
Exactly, if you could get a slotA/slotB coverter (just as Intel slot1/Slot2 converters already exist) you could have a dual SMP Athlon system running on a 21264 Alpha board, right now.
Eh, I don't think an Athlon would be happy trying to run AlphaBIOS or SRM firmware. While maybe the processors would fit on the board, it's not gonna actually do anything. You need a x86-style BIOS...
WHEN are they going to come out with the dual processor MOBO"s for the Athlon... thats going to be freaking awesome.
Dunno, but that's what I'm holding out for... the last Wintel system I bought was a Pentium 100 back in 1995, so I guess it's about time to get a new machine (although I did get a nice 430HX motherboard for the P100, and have since upgraded the CPU to a K6-2 450).
Speaking of EV6, an Alpha EV6 would be nice too:) I've already got an Alpha EV56 though, so I'm not in a hurry to get another Alpha...
I've come to love OpenBSD and have *tremendous* respect for the development team (IPF on OpenBSD rocks!).
Isn't IPF (assuming that stands for IP Filter) written by a third party not associated with OpenBSD? Certainly, IPF on OpenBSD does rock, but so does IPF on FreeBSD, IPF on NetBSD, etc...
Looks more like a SourceSafe ID string to me (so you can tell which version of the source code this DLL was compiled from). Have you tried running either the ident or what commands on just about any Unix system?
linux ~> uname -a Linux linux 2.0.36 #3 Fri Dec 17 00:10:51 CST 1999 i686 unknown linux ~> ident/bin/su /bin/su: $Id: su.c,v 1.9 1998/01/29 23:22:44 marekm Exp $ $Id: getdef.c,v 1.10 1998/04/02 21:51:42 marekm Exp $ $Id: port.c,v 1.3 1997/12/07 23:26:54 marekm Exp $ $Id: pwauth.c,v 1.6 1998/01/29 23:22:30 marekm Exp $ etc...
Does this mean/bin/su on that Linux machine (I think it's Redhat, but I don't actually know) has a backdoor? No.
I believe the L+R/L-R is known as "joint stereo" (which is probably the most common format for stereo MP3s). MPEG does support discrete stereo though, with L and R being encoded separately.
I'm afraid you are the one that is mistaken. bitrate refers to the uncompressed stream of audio, and has nothing at all to do with the amount of compression.
Actually, you're the one that is mistaken. So there.:-P
Well, I'm probably biased since I'm a NetBSD user and have contributed some code to NetBSD, but I don't think there's that much difference in security between NetBSD and OpenBSD. NetBSD folks read the OpenBSD commit logs (and vice versa), so if OpenBSD makes any security fixes, NetBSD'll pull 'em in too. I'd say if NetBSD is working for you, stick with it. That said, I think if you switched to OpenBSD, you'd like it just fine too (assuming you like NetBSD:)... the two are really quite similar.
Also, perhaps you already know this, but ipfilter in NetBSD is the same ipfilter that's in OpenBSD... it's not like you'd be getting anything different if you switched (not sure why you think it's not that good either; seems great to me:)
I'm using a 386/33 with 8MB of RAM, cheap NE2000 compatible, and a 4 port 16650 card running NAT and routing for two ISDN connections (to separate places) (the other 2 ports are mostly unused... occasional modem dialin). It was also routing my wireless network (Aviator2.4), but then I upgraded the other end to Windoze 2000 and now NetBSD's driver doesn't want to talk to the Windows driver:( So I got a NT 4 box handling the wireless now... Anyways, the 386 has been doing NAT/routing for a few years and it works great:)
Which one is used less? I think I'll go with the one that is used less, that way there is less support, and I won't have to listen to all the newbie complaints of "how do I do this?"
Definitely NetBSD/pc532:) Good luck finding a machine to run it on; less than 200 boards were made.
and now NetBSD folks get all pissy when OpenBSD people integrate their code. Get a clue. You should be happy that people use your code in accordance with the license you release it under.
Well, I'm certainly not pissy that OpenBSD has integrated my code (although it is a bit annoying that they credit Allen Briggs, when he wrote none of the code. I mean the first line of the thing even says it's copyright David Huang... Allen was the NetBSD/mac68k portmaster, and certainly answered a lot of my questions and was very helpful in general though.)
Anyways, I think it's great that people are using my code, and I haven't seen any other NetBSD folks complain that OpenBSD is taking NetBSD code. I do see some grumbling when OpenBSD takes NetBSD code and makes out like it's some new feature of theirs, but that's human nature. They're not against OpenBSD taking the code, they just want some credit for it. NetBSD folks don't like Theo for a reason... while I've never met him in person, based on email conversations with him and watching him on the NetBSD mailing lists (before he was banned), he's rude and quite abrasive. To be fair, some NetBSD folks can be too, but Theo seems like that all the time:)
Sounds like you've got a case of anti-American bigotry. What does the statement have to do with America? It means what it says--if you're anywhere on this planet where it's still night time when you see the message, and you're close enough to one of the poles to see aurorae, go out and look. Duh.
By the way, I'm pretty sure that Linux on PalmOS PDAs came out before NetBSD/hpcmips, so even your claim that "the code for booting Linux on a PDA form factor is taken from NetBSD" is suspect. It's only the code for booting Linux on a MIPS-based WinCE PDA that was taken from NetBSD.
Linux and PDA's - The code for booting up Linux on a PDA form factor is taken from NetBSD. (so the BSD ideal of code reuse everywhere is upheld again
You're probably referring to running Linux on WinCE machines (pbsdboot). I'm not talking about that; I'm talking about PDAs that run Linux as shipped. E.g. the Yopy.
Commerical Applications - www.netbsd.org/gallery/software.html Also note that NetBSD can run Linux binaries due to the compatibility layer, so the BSD's have access to not only Linux binaries, but SCO, Solaris, and even Windows binaries (via WINE)
Yes, I know that... I was talking about native NetBSD commercial applications. There are many more commercial Linux apps.
So, as far as facts go, thanks for playing. When you take off the pro-linux rose colored glasses you will see that what you said is not backed up by facts.
Actually, they are backed up by facts. Linux PDA exists? Yes. NetBSD PDA exists? No. More commercial Linux software than commercial NetBSD software? Yes. And what pro-Linux rose-colored glasses? I don't like Linux, and I don't use it. I'm a NetBSD user and occasional developer (see the copyright line of this file? That's me.)
As for mine being a 'cheap ripoff', mine was a tasteless parody of a tasteless post. Scatalogical humor of someone using scatological humor. Humor via goring the sacred cow that is/.
Not much of a parody... not particularly tasteless either. well-done parodies involve some creativity. Running the original through sed to change a few names around does not make a good parody.
So rather than wasting time slamming other opensource projects, wouldn't the rising tide for OpenSource work better when ALL boats get floated?
When did I slam any open source projects? NetBSD is the best OS for me, but I know it's not perfect. I know its shortcomings. Even NetBSD's core developers recognize that NetBSD is just not gonna have a lot of apps compared to Linux and FreeBSD, and that NetBSD should make it's emulation good enough to run Linux and FreeBSD apps (and the emulation's not perfect yet; for example, I can't run the Linux version of the Pervasive.SQL 2000 database server).
(And if you didn't consider this funny, then why was the 1st one funny?)
Because the first one was original; yours is just a cheap ripoff of it. Also because the first one is an exaggeration of the truth, while yours has very little truth to it (Linux has a couple of commercial applications; NetBSD has what? Zero? [Okay, I think there is at least one, maybe two] I bought AcceleratedX back when they had a NetBSD version, then they dropped it. While both Linux and NetBSD run on PDAs, there are/will be PDAs that come from the manufacturer running Linux [Yopy]. NetBSD? None.)
Besides, NetBSD really is l33t:)
Re:The definition of slashdotted...
on
Quickielanche
·
· Score: 1
The "Uses for an Altoid tin" site has a link to a guy who put a webserver on a PIC microcontroller, including a real TCP/IP stack (not just a plain serial link with a terminal server handling the TCP/IP, as the Atari 800 webserver is). Much cooler, IMO:)
JLG is the one who OPENED UP the Mac: the Mac II was his baby, with its 6 NuBus slots and expandable nature: this was the blueprint for all subsequent Macs.
That's "open" as in "expandable," not "open" as in "technical details available." Sure, there's some info available in Designing Cards and Drivers and Macintosh Family Overview (or whatever those books are called), but it's not enough info to write an OS with. The NetBSD/mac68k (née MacBSD) folks had to do a lot of work to figure out how the hardware worked (and still do, actually... anyone wanna tell me how the PSC works in the 660av/840av?:) DMA SCSI and sound support would be nifty:)
they added new primitive types and storage classes, like "vector", rather than bother to do loop vectorization in a compatible way.
Did they do it the same way as the MacOS compilers? When the G4 Powermacs first came out, I took a quick look at some sample Altivec code on Apple's developer website, and thought the way they handled the vectors was pretty nasty looking... like to initialize a vector variable, you did something like vector v = (vector)(0x50147242, 0x72353233, 0xbedac0ed, 0x3aa10dab);
Wasn't exactly like that, but the gist of it was that it looked like a cast of a list of constants separated by the comma operator. Eew:)
Anyone remember the Radius Pivot monitors, back in what, the late '80s? They were Mac monitors that you could rotate between landscape and portrait mode. When you rotated the screen, MacOS would know and resize the desktop and everything; pretty slick:) Portrait was good for fitting a DTP page on the screen... I don't remember what resolution those things ran at, maybe 624x832? Perhaps 768x1024...
Linux runs on more, and a much wider range of, CPUs. NetBSD artificially inflates their numbers by counting every architecture separately, while Linux lumps all ports to Motorola 68k processors as the m68k port, for example, instead of as separate Mac, Atari, etc. ports like NetBSD.
The numbers aren't artificially inflated; I can't run MacLinux on an Amiga, just as I can't run NetBSD/mac68k on an Amiga. And quantity isn't the only measure of which OS "owns" multi-platform. I think NetBSD's integration of all of its ports into a single source tree counts for a lot, as does having a clean split between arch-dependent code and arch-independent code so that, e.g., most of the drivers are shared between all the arches. Someone wrote a driver for sound cards using ForteMedia FM801 chip on his x86 machine. I added the driver to my Alpha's kernel config file, compiled a kernel, and had the sound card working perfectly, with no changes to the source code. I wouldn't be surprised if the same driver would work in a PowerMac or Ultrasparc (perhaps there may be some endian issues the author overlooked, but those would be very minor things to fix).
Similarly, the S/390 Linux port is one Linux port but would be four NetBSD ports, assuming NetBSD ever gets around to supporting S/390 (the Linux port runs on the bare metal or as a virtual session under any of the three OSes available for S/390).
I dunno about that... isn't the idea of the S/390 that the virtual machine looks identical to the bare metal? If there aren't really major differences in OS's view of the hardware, I'd think that NetBSD would put it all in one port. After all, although they were originally separate, NetBSD even managed to combine the sun3 and sun3x ports (I think the sun3x machines looked more like the sun4 SPARCs, except they had a 68k processor).
Slashdot Mirror
He didn't invent the algorithms though... I believe the version 1.x algorithms (squeeze or squish or something starting with squ :) was LZW, and the current 2.x deflate algorithm is pretty much LZ77.
Eh, I don't think an Athlon would be happy trying to run AlphaBIOS or SRM firmware. While maybe the processors would fit on the board, it's not gonna actually do anything. You need a x86-style BIOS...
Dunno, but that's what I'm holding out for... the last Wintel system I bought was a Pentium 100 back in 1995, so I guess it's about time to get a new machine (although I did get a nice 430HX motherboard for the P100, and have since upgraded the CPU to a K6-2 450).
Speaking of EV6, an Alpha EV6 would be nice too :) I've already got an Alpha EV56 though, so I'm not in a hurry to get another Alpha...
Isn't IPF (assuming that stands for IP Filter) written by a third party not associated with OpenBSD? Certainly, IPF on OpenBSD does rock, but so does IPF on FreeBSD, IPF on NetBSD, etc...
linux ~> uname -a /bin/su
/bin/su:
Linux linux 2.0.36 #3 Fri Dec 17 00:10:51 CST 1999 i686 unknown
linux ~> ident
$Id: su.c,v 1.9 1998/01/29 23:22:44 marekm Exp $
$Id: getdef.c,v 1.10 1998/04/02 21:51:42 marekm Exp $
$Id: port.c,v 1.3 1997/12/07 23:26:54 marekm Exp $
$Id: pwauth.c,v 1.6 1998/01/29 23:22:30 marekm Exp $
etc...
Does this mean /bin/su on that Linux machine (I think it's Redhat, but I don't actually know) has a backdoor? No.
Oh, okay... when you said "followed by the can of coke," I thought you meant the contents of the can, not the can itself :)
I believe the L+R/L-R is known as "joint stereo" (which is probably the most common format for stereo MP3s). MPEG does support discrete stereo though, with L and R being encoded separately.
Actually, you're the one that is mistaken. So there. :-P
Didn't that make the Coke go flat?
Also, perhaps you already know this, but ipfilter in NetBSD is the same ipfilter that's in OpenBSD... it's not like you'd be getting anything different if you switched (not sure why you think it's not that good either; seems great to me :)
I'm using a 386/33 with 8MB of RAM, cheap NE2000 compatible, and a 4 port 16650 card running NAT and routing for two ISDN connections (to separate places) (the other 2 ports are mostly unused... occasional modem dialin). It was also routing my wireless network (Aviator2.4), but then I upgraded the other end to Windoze 2000 and now NetBSD's driver doesn't want to talk to the Windows driver :( So I got a NT 4 box handling the wireless now... Anyways, the 386 has been doing NAT/routing for a few years and it works great :)
Definitely NetBSD/pc532 :) Good luck finding a machine to run it on; less than 200 boards were made.
Well, I'm certainly not pissy that OpenBSD has integrated my code (although it is a bit annoying that they credit Allen Briggs, when he wrote none of the code. I mean the first line of the thing even says it's copyright David Huang... Allen was the NetBSD/mac68k portmaster, and certainly answered a lot of my questions and was very helpful in general though.)
Anyways, I think it's great that people are using my code, and I haven't seen any other NetBSD folks complain that OpenBSD is taking NetBSD code. I do see some grumbling when OpenBSD takes NetBSD code and makes out like it's some new feature of theirs, but that's human nature. They're not against OpenBSD taking the code, they just want some credit for it. NetBSD folks don't like Theo for a reason... while I've never met him in person, based on email conversations with him and watching him on the NetBSD mailing lists (before he was banned), he's rude and quite abrasive. To be fair, some NetBSD folks can be too, but Theo seems like that all the time :)
Sounds like you've got a case of anti-American bigotry. What does the statement have to do with America? It means what it says--if you're anywhere on this planet where it's still night time when you see the message, and you're close enough to one of the poles to see aurorae, go out and look. Duh.
By the way, I'm pretty sure that Linux on PalmOS PDAs came out before NetBSD/hpcmips, so even your claim that "the code for booting Linux on a PDA form factor is taken from NetBSD" is suspect. It's only the code for booting Linux on a MIPS-based WinCE PDA that was taken from NetBSD.
You're probably referring to running Linux on WinCE machines (pbsdboot). I'm not talking about that; I'm talking about PDAs that run Linux as shipped. E.g. the Yopy.
Commerical Applications - www.netbsd.org/gallery/software.html Also note that NetBSD can run Linux binaries due to the compatibility layer, so the BSD's have access to not only Linux binaries, but SCO, Solaris, and even Windows binaries (via WINE)
Yes, I know that... I was talking about native NetBSD commercial applications. There are many more commercial Linux apps.
So, as far as facts go, thanks for playing. When you take off the pro-linux rose colored glasses you will see that what you said is not backed up by facts.
Actually, they are backed up by facts. Linux PDA exists? Yes. NetBSD PDA exists? No. More commercial Linux software than commercial NetBSD software? Yes. And what pro-Linux rose-colored glasses? I don't like Linux, and I don't use it. I'm a NetBSD user and occasional developer (see the copyright line of this file? That's me.)
As for mine being a 'cheap ripoff', mine was a tasteless parody of a tasteless post. Scatalogical humor of someone using scatological humor. Humor via goring the sacred cow that is /.
Not much of a parody... not particularly tasteless either. well-done parodies involve some creativity. Running the original through sed to change a few names around does not make a good parody.
So rather than wasting time slamming other opensource projects, wouldn't the rising tide for OpenSource work better when ALL boats get floated?
When did I slam any open source projects? NetBSD is the best OS for me, but I know it's not perfect. I know its shortcomings. Even NetBSD's core developers recognize that NetBSD is just not gonna have a lot of apps compared to Linux and FreeBSD, and that NetBSD should make it's emulation good enough to run Linux and FreeBSD apps (and the emulation's not perfect yet; for example, I can't run the Linux version of the Pervasive.SQL 2000 database server).
Because the first one was original; yours is just a cheap ripoff of it. Also because the first one is an exaggeration of the truth, while yours has very little truth to it (Linux has a couple of commercial applications; NetBSD has what? Zero? [Okay, I think there is at least one, maybe two] I bought AcceleratedX back when they had a NetBSD version, then they dropped it. While both Linux and NetBSD run on PDAs, there are/will be PDAs that come from the manufacturer running Linux [Yopy]. NetBSD? None.)
Besides, NetBSD really is l33t :)
The "Uses for an Altoid tin" site has a link to a guy who put a webserver on a PIC microcontroller, including a real TCP/IP stack (not just a plain serial link with a terminal server handling the TCP/IP, as the Atari 800 webserver is). Much cooler, IMO :)
Gay lions, perhaps? (roaar :)
That's "open" as in "expandable," not "open" as in "technical details available." Sure, there's some info available in Designing Cards and Drivers and Macintosh Family Overview (or whatever those books are called), but it's not enough info to write an OS with. The NetBSD/mac68k (née MacBSD) folks had to do a lot of work to figure out how the hardware worked (and still do, actually... anyone wanna tell me how the PSC works in the 660av/840av? :) DMA SCSI and sound support would be nifty :)
Yeah, the Daemon's definitely cuter, but I think this little fellow takes the cuteness prize :)
Did they do it the same way as the MacOS compilers? When the G4 Powermacs first came out, I took a quick look at some sample Altivec code on Apple's developer website, and thought the way they handled the vectors was pretty nasty looking... like to initialize a vector variable, you did something like vector v = (vector)(0x50147242, 0x72353233, 0xbedac0ed, 0x3aa10dab);
Wasn't exactly like that, but the gist of it was that it looked like a cast of a list of constants separated by the comma operator. Eew :)
Anyone remember the Radius Pivot monitors, back in what, the late '80s? They were Mac monitors that you could rotate between landscape and portrait mode. When you rotated the screen, MacOS would know and resize the desktop and everything; pretty slick :) Portrait was good for fitting a DTP page on the screen... I don't remember what resolution those things ran at, maybe 624x832? Perhaps 768x1024...
The numbers aren't artificially inflated; I can't run MacLinux on an Amiga, just as I can't run NetBSD/mac68k on an Amiga. And quantity isn't the only measure of which OS "owns" multi-platform. I think NetBSD's integration of all of its ports into a single source tree counts for a lot, as does having a clean split between arch-dependent code and arch-independent code so that, e.g., most of the drivers are shared between all the arches. Someone wrote a driver for sound cards using ForteMedia FM801 chip on his x86 machine. I added the driver to my Alpha's kernel config file, compiled a kernel, and had the sound card working perfectly, with no changes to the source code. I wouldn't be surprised if the same driver would work in a PowerMac or Ultrasparc (perhaps there may be some endian issues the author overlooked, but those would be very minor things to fix).
Similarly, the S/390 Linux port is one Linux port but would be four NetBSD ports, assuming NetBSD ever gets around to supporting S/390 (the Linux port runs on the bare metal or as a virtual session under any of the three OSes available for S/390).
I dunno about that... isn't the idea of the S/390 that the virtual machine looks identical to the bare metal? If there aren't really major differences in OS's view of the hardware, I'd think that NetBSD would put it all in one port. After all, although they were originally separate, NetBSD even managed to combine the sun3 and sun3x ports (I think the sun3x machines looked more like the sun4 SPARCs, except they had a 68k processor).
Actually, I'd say that NetBSD owns multi-platform. No clue about SMP, other than NetBSD definitely doesn't own it ;)
I think a more common translation is "no contest."