[...], then restart networking with 'service network restart.'
I should make this clear -- FreeBSD doesn't require a reboot. A similar dance as above with/etc/rc.network6 (on FreeBSD 4.x) will do all the interface configuration.
It even installs ping6, traceroute6, etc. by default for goodness sakes.
I don't use RedHat, but that is useful to know. Thanks.
If the world switched tomorrow, linux users would probably be the first ones up and running.
Wrong. Linux is nowhere near as IPv6-friendly as the *BSDs. To enable IPv6 in FreeBSD, for example, put 'ipv6_enable="YES"' in/etc/rc.conf and reboot. It'll autoconfig based on router advertisements, etc. You also have the option of enabling it at install time, so you can install over IPv6.
Each FreeBSD CD comes with a bunch prebuilt IPv6-ready apps, like apache, wget, etc -- apps that don't have native IPv6 support. Linux distributions are way behind when it comes to IPv6 adoption.
AEven Microsoft is on the bandwagon here. XP shipped with a "dev release" of their IPv6 code, and service pack 1 upgraded that to a production-ready release. To enable it, type "ipv6 install" at a command prompt, and you're set (no need to reboot!). The new 2003 server release comes with production quality IPv6 code as well.
You have to be a really big ISP to get IPv6 addresses, at least in the Asian-Pacific region. Read section 5.1.1 of the APNIC policy on IPv6 allocation.
Know 200 clients who need/48s in the next two years?
If _YOUR_ mailserver can not get YOUR email out, who's problem is it?
In my case, it's my problem, and my ISP's fault. My ISP doesn't provide reverse DNS. I've heard all sorts of excuses like "no one else has ever asked for it", etc. I've tried several people, on several occasions, and no one's willing to do the work to get me reverse DNS. Hey, it's a telco monopoly.
So I guess you'll never get mail from pretty much anyone in my country...
They probably haven't made the release public because they want the mirrors to catch up. Now that you've told the world about it, the mirror sites have to compete with users trying to download it.
Mono works on FreeBSD-i386. I've been using it off and on for several months.
The only real "catch" is the Windows.Forms libraries (this affects mono on Linux as well). You basically need Wine or something for them. Otherwise, for GUI stuff, you can use gtk#.
I am, yes, assuming that this will turn into a Sun release at some point. Once all the tests patch and it's proven to work in the field, Sun can integrate the patches into its source tree.
I believe this is a precursor to the Sun release because -- as far as I know -- no one else is working on porting Java to FreeBSD.
SO we stil need to bootstrap off of linux's jdk binary?
Yes. Presumably once the JDK works on FreeBSD, Sun will merge in the FreeBSD-specific code, and we'll have a version independent of Linux binaries.
Note that ones this FreeBSD port is complete, you should be a install precompiled JDK binaries. This hasn't been the case in the past because the 1.2/1.3 builds have all been unofficial, and can't be distributed in binary form.
Sure, a quick glance in/usr/lib suggests that most libs have at least two versions
Yes, and if, of those 150 processes you have running, 75 use one version and 75 the other, that's still only two copies of the library in memory.
If you have a system with n processes using anywhere near n/2different libraries, I would like to know more about it. I've never come across anything like that (barring edge cases, like the machine running X in single-user mode).
You're describing a situation that's unlikely to happen.
Think of it this way -- your Unix box probably has a bunch of versioned shlibs that are used by different applications. Does that bother you? Most likely, you never even think of it.
It adds versioning to dlls -- that's all. Multiple programs can use the same version. If a new version of the dll is added (even if it has the same name), the system will direct old applications to the old dll and new ones to the new dll.
I don't see why adding heuristics to a spam throttling device will make it work worse. It should make it work a lot better.
The package I use at the isp I do random consulting for is spamthrottle. It handles the case of multiple connections from a single address (or range of addresses), along with tarpitting. It works really well -- there have been no incidents since I applied the patch, and no (legit) users have called in to complain about the mail server.
I started using it because some customers would mailbomb remote users. Unfortunately the way the ISP's dialup auth stuff works, we really don't know who the users are, so we can't kick them off permanently. It's a combination of no caller-id (we have E1s, not PRIs), and a bad scratch card account scheme by the previous management.
NTT has offeredIPv6 connectivity (both tunnels and native) in Europe and the States for about two years now. I don't know how long they've been operating in Japan (NTT is a Japanese firm). See this site for lots of information.
Maybe not, but that's Islam's fault, with the whole "if it agrees with the Koran it's redundant and if not it's heretical" attitude which caused Omar(?) to burn down the library at Alexandria and has kept them in the stone age ever since.
No one really knows for certain what happened. There's some evidence that the above story isn't correct. See, for example, this link.
And the 'stone age' comment -- are you really that ignorant, or do you just play one on slashdot? Where do you think the knowledge that sparked the European Renaissance came from?
It doesn't work that way. Keep in mind that many of the posts on -questions/-current/etc are from users, not developers. People tend to read -hackers and -current (or -stable, if they're dealing with that branch). They also read specific lists (like -net, or -fs). Someone writing filesystem stuff won't pay much attention to -multimedia. This includes people with commit access and people without commit access. Oh, and -cvs. People with commit access also get to read -developers, which (I just asked) varies from 50-100 messages a day on average (highs of ~ 200, lows in the teens).
Also, you don't need to filter away stuff. This is unix -- don't act so helpless! Use glimpse or kiboze the messages some way to get what you want. Use a threading news/mailreader. Really, it's not a problem.
I can easily imagine a thousand posts a day to that list.
That is incorrect.
Also, if you're working on, say, the sound drivers, there's no reason why you need to read every single message on the framebuffer subsystem (or whatever).
bitkeeper uses SCCS as its underlying layer, sort of similar to how CVS uses RCS for the files. There are (free) SCCS tools available, so you can probably pull your code out of bk if you feel the urge. Also, as I understand it, if the company ever dies, bk goes open source. Not so proprietary now, is it?
bk's a great solution to a problem not really addressed by anyone else. Personally, I hope it doesn't go away.
I don't use it, by the way. I'm thinking of writing a webdav client for a non-Unix operating system, and extending it to support subversion. The bk freebie license prevents me from using bk while working on a competing product.
There's also something called Cons, but it needs perl to work. See this.
I haven't found a good alternative to autoconf yet. There used to be Metaconfig, but I don't know who maintains it any more (or where). It produces configure scripts similar to what you see when you configure perl. This guy uses some unreleased software package for his build systems that tend to work really well -- for C code under Unix.
Come to think of it, if someone ports/writes a build tool in C#, you'd be set.
Slashdot Mirror
[...], then restart networking with 'service network restart.'
I should make this clear -- FreeBSD doesn't require a reboot. A similar dance as above with /etc/rc.network6 (on FreeBSD 4.x) will do all the interface configuration.
It even installs ping6, traceroute6, etc. by default for goodness sakes.
I don't use RedHat, but that is useful to know. Thanks.
If the world switched tomorrow, linux users would probably be the first ones up and running.
Wrong. Linux is nowhere near as IPv6-friendly as the *BSDs. To enable IPv6 in FreeBSD, for example, put 'ipv6_enable="YES"' in /etc/rc.conf and reboot. It'll autoconfig based on router advertisements, etc. You also have the option of enabling it at install time, so you can install over IPv6.
Each FreeBSD CD comes with a bunch prebuilt IPv6-ready apps, like apache, wget, etc -- apps that don't have native IPv6 support. Linux distributions are way behind when it comes to IPv6 adoption.
AEven Microsoft is on the bandwagon here. XP shipped with a "dev release" of their IPv6 code, and service pack 1 upgraded that to a production-ready release. To enable it, type "ipv6 install" at a command prompt, and you're set (no need to reboot!). The new 2003 server release comes with production quality IPv6 code as well.
You have to be a really big ISP to get IPv6 addresses, at least in the Asian-Pacific region. Read section 5.1.1 of the APNIC policy on IPv6 allocation.
Know 200 clients who need /48s in the next two years?
In Pakistan, it's the equivalent of US$0.25/MB, at roughly 56kbps GPRS. That may change once the other GSM provider rolls out its GPRS service.
In my case, it's my problem, and my ISP's fault. My ISP doesn't provide reverse DNS. I've heard all sorts of excuses like "no one else has ever asked for it", etc. I've tried several people, on several occasions, and no one's willing to do the work to get me reverse DNS. Hey, it's a telco monopoly.
So I guess you'll never get mail from pretty much anyone in my country...
They probably haven't made the release public because they want the mirrors to catch up. Now that you've told the world about it, the mirror sites have to compete with users trying to download it.
Mono works on FreeBSD-i386. I've been using it off and on for several months.
The only real "catch" is the Windows.Forms libraries (this affects mono on Linux as well). You basically need Wine or something for them. Otherwise, for GUI stuff, you can use gtk#.
I am, yes, assuming that this will turn into a Sun release at some point. Once all the tests patch and it's proven to work in the field, Sun can integrate the patches into its source tree.
I believe this is a precursor to the Sun release because -- as far as I know -- no one else is working on porting Java to FreeBSD.
SO we stil need to bootstrap off of linux's jdk binary?
Yes. Presumably once the JDK works on FreeBSD, Sun will merge in the FreeBSD-specific code, and we'll have a version independent of Linux binaries.
Note that ones this FreeBSD port is complete, you should be a install precompiled JDK binaries. This hasn't been the case in the past because the 1.2/1.3 builds have all been unofficial, and can't be distributed in binary form.
Why should I bother to use the standard version of foo.dll when I can use my version of foo.dll with a few custom extensions?
Nothing in this scheme prevents you from doing this. In fact, it helps ensure that your foo.dll doesn't clash with the foo.dll used by other apps.
Or just have my own library called foo.dll that has nothing to do with the original foo.dll?
Again, nothing in this scheme prevents you from doing this. I can't figure out why you think this restricts you.
Sure, a quick glance in /usr/lib suggests that most libs have at least two versions
Yes, and if, of those 150 processes you have running, 75 use one version and 75 the other, that's still only two copies of the library in memory.
If you have a system with n processes using anywhere near n/2different libraries, I would like to know more about it. I've never come across anything like that (barring edge cases, like the machine running X in single-user mode).
You're describing a situation that's unlikely to happen.
Think of it this way -- your Unix box probably has a bunch of versioned shlibs that are used by different applications. Does that bother you? Most likely, you never even think of it.
It adds versioning to dlls -- that's all. Multiple programs can use the same version. If a new version of the dll is added (even if it has the same name), the system will direct old applications to the old dll and new ones to the new dll.
See this
I don't see why adding heuristics to a spam throttling device will make it work worse. It should make it work a lot better.
The package I use at the isp I do random consulting for is spamthrottle. It handles the case of multiple connections from a single address (or range of addresses), along with tarpitting. It works really well --
there have been no incidents since I applied the patch, and no (legit) users have called in to complain about the mail server.
I started using it because some customers would mailbomb remote users. Unfortunately the way the ISP's dialup auth stuff works, we really don't know who the users are, so we can't kick them off permanently. It's a combination of no caller-id (we have E1s, not PRIs), and a bad scratch card account scheme by the previous management.
see this thread on journaling filesystems & freebsd.
i'd like to see xfs on freebsd too, but the license...
jfs is one of the oldest journalling filesystems available. it's stable, has been stress-tested, is backed by ibm, etc.
reiserfs and ext3fs are nowhere near as capable. xfs is pretty good, too -- in fact, it's what i use on my debian box.
if so, it'll never end up as part of the base install.
NTT has offeredIPv6 connectivity (both tunnels and native) in Europe and the States for about two years now. I don't know how long they've been operating in Japan (NTT is a Japanese firm). See this site for lots of information.
His point is that there aren't enough 6to4 relays out there.
Maybe not, but that's Islam's fault, with the whole "if it agrees with the Koran it's redundant and if not it's heretical" attitude which caused Omar(?) to burn down the library at Alexandria and has kept them in the stone age ever since.
No one really knows for certain what happened. There's some evidence that the above story isn't correct. See, for example, this link.
And the 'stone age' comment -- are you really that ignorant, or do you just play one on slashdot? Where do you think the knowledge that sparked the European Renaissance came from?
It doesn't work that way. Keep in mind that many of the posts on -questions/-current/etc are from users, not developers.
People tend to read -hackers and -current (or -stable, if they're dealing with that branch). They also read specific lists (like -net, or -fs). Someone writing filesystem stuff won't pay much attention to -multimedia. This includes people with commit access and people without commit access. Oh, and -cvs.
People with commit access also get to read -developers, which (I just asked) varies from 50-100 messages a day on average (highs of ~ 200, lows in the teens).
Also, you don't need to filter away stuff. This is unix -- don't act so helpless! Use glimpse or kiboze the messages some way to get what you want. Use a threading news/mailreader.
Really, it's not a problem.
I can easily imagine a thousand posts a day to that list.
That is incorrect.
Also, if you're working on, say, the sound drivers, there's no reason why you need to read every single message on the framebuffer subsystem (or whatever).
I think you mean "virtual memory", not "virtual machines."
bitkeeper uses SCCS as its underlying layer, sort of similar to how CVS uses RCS for the files. There are (free) SCCS tools available, so you can probably pull your code out of bk if you feel the urge. Also, as I understand it, if the company ever dies, bk goes open source. Not so proprietary now, is it?
bk's a great solution to a problem not really addressed by anyone else. Personally, I hope it doesn't go away.
I don't use it, by the way. I'm thinking of writing a webdav client for a non-Unix operating system, and extending it to support subversion. The bk freebie license prevents me from using bk while working on a competing product.
Some alternatives to ant/make are
There's also something called Cons, but it needs perl to work. See this.
I haven't found a good alternative to autoconf yet. There used to be Metaconfig, but I don't know who maintains it any more (or where). It produces configure scripts similar to what you see when you configure perl. This guy uses some unreleased software package for his build systems that tend to work really well -- for C code under Unix.
Come to think of it, if someone ports/writes a build tool in C#, you'd be set.