RELENG_4 tracks -stable. This is a moving target and isn't always stable or usable. All new developments in the 4.x branch are made here, and all new releases in the 4.x branch are tagged from here.
RELENG_4_X tracks 4.X + security fixes. Security fixes and super-major bug fixes are the only things that get added to this branch. No new features will be added here.
RELENG_4_X_Y_RELEASE will get you 4.X.Y release, the same code as is put on the CDs.
It's not emulation, it's binary compatibility. When a Linux binary is loaded, the kernel loads the Linux system call map and uses that instead of the FreeBSD on. IOW, the binary is running natively, without any emulation layer.
In the early days of FreeBSD 4.x, you could actually run Linux binaries faster on FreeBSD, and in many cases, it would run stabler too. (This is why the CGI in The Matrix was done using Linux apps on FreeBSD servers.)
But, this only works for userland apps. You can't run Linux kernel modules (drivers) inside the FreeBSD kernel.
Yes, they give you the exact co-ordinates. However, they don't tell you how to get to those co-ordinates. That's the challenging part. Maybe it's hidden downtown, on the fifteenth floor of some office building. Maybe it's hidden on the other side of a small mountain range that you have to either climb over, or drive around. Maybe it's hidden deep in some cave. Maybe it's hidden in your backyard... you never know.
It might just be around here. The two public libraries here in town, and the ones in the two neighbouring cities (one smaller the other larger than us) are virtually the same. Haven't been to any of the large (> 1 million people) cities around here to compare to, though.
If only. The library at the local university college has the worst hours of any library I've seen. It's only open 6 hours on weekends and holidays, and it closes between 7 and 9pm during the week. It's horrible.
And they're trying to push for full University status. [shakes head]
The problem with public libraries is that nobody uses them anymore. This means they are losing funding... which leads to fewer new books... which makes it even less relevant and fewer people will use them. The hours are being cut, making it harder for people to use them.
It'd be nice to see a library that didn't open until after noon, and stayed open into the wee hours. Then it would actually be useful for students, those who work, and so on. Being open from 9 until 5 isn't really convenient for anybody.
Strange that you use your whole hand for that manoeuver. My thumb presses CTRL, my index finger (curled under my palm) presses ALT, and my middle finger presses Delete. It's actually quit comfortable, and doesn't require any bending of the hand.
The only client I have installed is Kopete 0.7, and it's been started, stopped, restarted several times over the past week (it's used for work, and only at work). Connects to Yahoo! and MSN without any problems.
Kopete 0.7 never lost connection to the Yahoo! servers, thus they were the first to have this "fix"... as no fix was needed for the client.:)
Got a bunch of warning from Yahoo! and MSN about the protocol being upgraded, yet still have full connectivity to both... without changing anything in the client.
Makes me wonder what the other clients are doing wrong.:D
Not many, but what is your point? He was discussing Type-II / Type-III slots, which is what most laptops come with. Two Type-II slots == 1 Type-III slot. And there are a few Type-III cards out there (the 3COM integrated NIC being one of them).
Why use Type-III when there are so many Type-II cards out there with built-in connectors?
3COM really screwed up when they released their built-in-connector-NIC as a type-III card. It takes up two slots on a laptop... meaning you can't add any other PCMCIA/Cardbus cards, and you can't use it on a laptop that only has 1 Type-II slot.
The Type-II built-in-connector NICs from SMC and Linksys (there are probably others by now) are so much nicer. The connector is external, so you have to put the NIC in the top slot so you can use the bottom slot for something else. No dongles to worry about, not flimsy XJack crap to worry about, and you don't have to get a patch cable with a 90' crimpt in it. It looks/works just like a built-in connector should.
Yep, do that all the time on my SeaNote laptop using a Microsoft Optical USB mouse. Of course, this is on FreeBSD.:)
moused is running so that I have mouse support at the console, and I also have mouse support in XFree86. Can plug/unplug the mouse all I want. Can even use the built-in PS/2 trackpad, regardless of whether the USB mouse is attached or not.
If both the parellel and serial buses run at the same MHz, then yes, the parellel bus will have higher throughput. After all, for every 1 bit that the serial bus pushes through, the parellel bus will push through 8.
However, you can only make a parellel bus go so fast. Once you get beyond a certain MHz, you run into all kinds of syncronisation issues as you try to get all 8 bits to reach the end-point *at the same time*. You end up adding so many checks and ballances that you actually lose throughput.
There are no syncronisation issues on a serial bus. Every bit goes down the same wire, one after the other. If you want to increase the throughput of the bus, just ramp up the MHz of the sending side, make sure the wire can handle it, and ramp up the MHz of the receiver. Done.
The best known parallel buses (SCSI and ATA) are moving to serial buses for just this reason. They can't squeeze out any more throughput on the current parallel buses due to syncronisation issues.
SMS is *extremely* useful for IT people. Instead of getting paged with a weird number that you have to try and decipher, you just configure your servers to send an e-mail to your phone whenever there's a problem. 160 characters is plenty to let you know that something is down or back up.
And it makes for a *much* easier paging system. Just create an e-mail alias on your e-mail server to point to your phone. If anybody needs you, they just send a short e-mail to your phone.
Works beautifuuly, especially since receiving messages is free. Been using this system for just under two years now.:)
Now, to send messages back and forth between two people on cells, I don't really see the appeal for that.
WindRiver doesn't own FreeBSD. They never bought FreeBSD. They bought the trademark and they bought Walnut-Creek CD-ROM's distribution channels for FreeBSD. However, FreeBSD has always been just that... free.
The trademark has since been transfered to The FreeBSD Foundation (or, that was the plan, anyway... not sure if that was completed or not). WindRiver doesn't distribute FreeBSD. In fact, WindRiver has next to no influence on FreeBSD at all.
RELENG_4 tracks -stable. This is a moving target and isn't always stable or usable. All new developments in the 4.x branch are made here, and all new releases in the 4.x branch are tagged from here.
RELENG_4_X tracks 4.X + security fixes. Security fixes and super-major bug fixes are the only things that get added to this branch. No new features will be added here.
RELENG_4_X_Y_RELEASE will get you 4.X.Y release, the same code as is put on the CDs.
It's not emulation, it's binary compatibility. When a Linux binary is loaded, the kernel loads the Linux system call map and uses that instead of the FreeBSD on. IOW, the binary is running natively, without any emulation layer.
In the early days of FreeBSD 4.x, you could actually run Linux binaries faster on FreeBSD, and in many cases, it would run stabler too. (This is why the CGI in The Matrix was done using Linux apps on FreeBSD servers.)
But, this only works for userland apps. You can't run Linux kernel modules (drivers) inside the FreeBSD kernel.
Yes, they give you the exact co-ordinates. However, they don't tell you how to get to those co-ordinates. That's the challenging part. Maybe it's hidden downtown, on the fifteenth floor of some office building. Maybe it's hidden on the other side of a small mountain range that you have to either climb over, or drive around. Maybe it's hidden deep in some cave. Maybe it's hidden in your backyard ... you never know.
Getting to the co-ordinates is where the fun is.
It might just be around here. The two public libraries here in town, and the ones in the two neighbouring cities (one smaller the other larger than us) are virtually the same. Haven't been to any of the large (> 1 million people) cities around here to compare to, though.
If only. The library at the local university college has the worst hours of any library I've seen. It's only open 6 hours on weekends and holidays, and it closes between 7 and 9pm during the week. It's horrible.
And they're trying to push for full University status. [shakes head]
The problem with public libraries is that nobody uses them anymore. This means they are losing funding ... which leads to fewer new books ... which makes it even less relevant and fewer people will use them. The hours are being cut, making it harder for people to use them.
It'd be nice to see a library that didn't open until after noon, and stayed open into the wee hours. Then it would actually be useful for students, those who work, and so on. Being open from 9 until 5 isn't really convenient for anybody.
Must be your distro, then. Our RedHat and Gentoo boxes work with either the left or right CTRL+ALT keys. Same with our FreeBSD and OpenBSD boxes.
Strange that you use your whole hand for that manoeuver. My thumb presses CTRL, my index finger (curled under my palm) presses ALT, and my middle finger presses Delete. It's actually quit comfortable, and doesn't require any bending of the hand.
The only client I have installed is Kopete 0.7, and it's been started, stopped, restarted several times over the past week (it's used for work, and only at work). Connects to Yahoo! and MSN without any problems.
Bizarre, strange, and weird, I guess.
Yeesh! Ye young pups and ye're mangled quotes. Did ye at least watch the thing??
... this is a ping."
"That's not a ping
Heh heh, and the next ink cartridge for that puppy will be about $55. :)
Correction, this is OpenBSD 3.0, which is less than 2 years old.
Kopete 0.7 never lost connection to the Yahoo! servers, thus they were the first to have this "fix" ... as no fix was needed for the client. :)
... without changing anything in the client.
:D
Got a bunch of warning from Yahoo! and MSN about the protocol being upgraded, yet still have full connectivity to both
Makes me wonder what the other clients are doing wrong.
Oh, come on. Be a little more specific, eh? It'll take at least 2 hours, but no more than 3.
Not many, but what is your point? He was discussing Type-II / Type-III slots, which is what most laptops come with. Two Type-II slots == 1 Type-III slot. And there are a few Type-III cards out there (the 3COM integrated NIC being one of them).
Why use Type-III when there are so many Type-II cards out there with built-in connectors?
... meaning you can't add any other PCMCIA/Cardbus cards, and you can't use it on a laptop that only has 1 Type-II slot.
3COM really screwed up when they released their built-in-connector-NIC as a type-III card. It takes up two slots on a laptop
The Type-II built-in-connector NICs from SMC and Linksys (there are probably others by now) are so much nicer. The connector is external, so you have to put the NIC in the top slot so you can use the bottom slot for something else. No dongles to worry about, not flimsy XJack crap to worry about, and you don't have to get a patch cable with a 90' crimpt in it. It looks/works just like a built-in connector should.
Yep, do that all the time on my SeaNote laptop using a Microsoft Optical USB mouse. Of course, this is on FreeBSD. :)
moused is running so that I have mouse support at the console, and I also have mouse support in XFree86. Can plug/unplug the mouse all I want. Can even use the built-in PS/2 trackpad, regardless of whether the USB mouse is attached or not.
If both the parellel and serial buses run at the same MHz, then yes, the parellel bus will have higher throughput. After all, for every 1 bit that the serial bus pushes through, the parellel bus will push through 8.
However, you can only make a parellel bus go so fast. Once you get beyond a certain MHz, you run into all kinds of syncronisation issues as you try to get all 8 bits to reach the end-point *at the same time*. You end up adding so many checks and ballances that you actually lose throughput.
There are no syncronisation issues on a serial bus. Every bit goes down the same wire, one after the other. If you want to increase the throughput of the bus, just ramp up the MHz of the sending side, make sure the wire can handle it, and ramp up the MHz of the receiver. Done.
The best known parallel buses (SCSI and ATA) are moving to serial buses for just this reason. They can't squeeze out any more throughput on the current parallel buses due to syncronisation issues.
SMS is *extremely* useful for IT people. Instead of getting paged with a weird number that you have to try and decipher, you just configure your servers to send an e-mail to your phone whenever there's a problem. 160 characters is plenty to let you know that something is down or back up.
:)
And it makes for a *much* easier paging system. Just create an e-mail alias on your e-mail server to point to your phone. If anybody needs you, they just send a short e-mail to your phone.
Works beautifuuly, especially since receiving messages is free. Been using this system for just under two years now.
Now, to send messages back and forth between two people on cells, I don't really see the appeal for that.
Well, if we're going to go all the way back, Apple's next-gen OS was originally called Pink. :)
Yes, it wasn't until after the NeXT buyout that the name became Rhapsody, but that was still an Apple name, not a NeXT name.
Time to do a little history reading. :) Rhapsody (not capitalised) was Apple's name for their next-generation OS. It had nothing to do with NeXT.
Walnut Creek employed several core members and other committers, as well as providing the main distribution side. I'd hardly consider that "nothing".
Yes.
No. There are the odd port that hasn't been updated to work with 5.x.
Yes.
WindRiver doesn't own FreeBSD. They never bought FreeBSD. They bought the trademark and they bought Walnut-Creek CD-ROM's distribution channels for FreeBSD. However, FreeBSD has always been just that ... free.
... not sure if that was completed or not). WindRiver doesn't distribute FreeBSD. In fact, WindRiver has next to no influence on FreeBSD at all.
The trademark has since been transfered to The FreeBSD Foundation (or, that was the plan, anyway
IBM will never sell a "G5" box, as G5 is an Apple moniker for any Apple box that uses a PPC970 CPU.
IBM has plans to sell Linux workstations using the PPC970 chip. However, they will never be called "G5".