lol they mod him flamebait for talking about FreeBSD on a linux discussion.. I've never seen someone modding Linux flamebait for being refered on a FreeBSD discussion.
I love 5.2.1 on the desktop, avoid it on servers. The only servers I have with 5.2.1 are the ones with dual processors, all others run 4.10-STABLE and have been up for many, many months.
I'll wait and see how 5.3 does. I won't be upgrading my desktop (at least for now) which is running 5.2.1-RELEASE, because I'd need to rebuild pretty much everything -- and we all know how XFree86 and GNOME upgrades tend to be a pain in the ass.
As for the server market, I'm waiting on 5.3 for two months now for a dual xeon, and I'm confident it will do very well; I have one server with 5.3-BETA5 and my gateway at home runs 5.3-BETA3 -- Both without stability/performance issues!
"As all you have noticed the above^ part, will fbsd have the same performance or better? When will this be ready 5.3.X ? Could I get some more accurate information about this? Since I'm planning to use it on my desktop."
You don't want a 5.3.*X* release, as 3-numbered released on FreeBSD are used to address critical bugs. Let's hope it stays 5.3-RELEASE/STABLE, heh.
Has anyone figured out what Microsoft *true* intentions are? I bet there is some legal issue hidden somewhere waiting to be uncovered. But that's just me.
It will work fine since the chroot is implemented at the named binary level. The problem here is the FreeBSD philosophy as I stated in my other post, for example, named.conf should never reside on/var ; But, as said in one of the posts to the mailing list, you can use the -c option to specify an alternative path to named.conf. At least with the port version, the -c option was (I think, almost sure) relative to the chroot path.
I don't know how true the statement in the mailing list was. I say, if it was running fine with the old scheme, it should be kept. If this was going to be implemented, perhaps they should have thought it on an earlier BETA stage. just my 2 cents.
There has been some discussion in the freebsd mailing lists about this change. BIND now resides in/var/named/ and some people are not confortable about this.
The default behaviour now is chrooting named too.
Personally, I like the old way better (/etc/namedb) as/var has a specific usage on FreeBSD, which is not keeping DNS server records. Changing the default from BIND8 to BIND9 will already make some people angry (because of migration issues), let alone changing bind base directory to a directory that won't fit in the freebsd philosophy..
You can read the whole discussion at http://lists.freebsd.org/pipermail/freebsd-current/2004-October/039288.html
Actually, this seems like a real problem as on at least two workstations I've had fdisk insisting the drive geometry was wrong. Specifiying the correct vallues to fdisk didn't help as it insisted with the old values.. But ultimately I could install the OS just fine even with the geometry set wrongly and it reports the partition sizes well.
I saw this movie last week, still can't believe how a country like America allowed Bush to become president.
I never liked the man, but after seeing this documentary ? Damn. Especially shocking was in 9/11 when he was at the elementary school.. and he sat there instead of doing something. I couldn't believe this actually happened, but everything in the movie did make sense.
IMO, the last stages of the movie (focuses on iraqui war) and the testemony of that mother who lost her son are there to cause some revolt on the american people, that really seemed to be his intention.
your ignorance is great, pf is already ported to FreeBSD for quite some time as a kernel loadable module, and it will be integrated with 5.3-RELEASE. Have you copy-pasted a FreeBSD flaming text a year old ?
Fact: BSD's dont have several critical security advisories which could lead to root access EVERY months
Fact: Linux apps running under emulation will sometimes run faster on BSD than on native linux
Fact: Linux community = bunch of script kiddies & pseudo-leet (and as we can see, dozens of trolls) ; BSD Community = Technical guys
Fact: FreeBSD is not dead, 4.11 is still coming, 5.3 is near the release.
Slashdot Mirror
http://www.netbsd.org/
Am I the only one thinking the orange/gray on the logo doesn't look pretty at all with the bluish menus ?
The logo itself is ok, it just doesn't seem to fit with NetBSD's site.
Perhaps the site colours should be changed ?
don't = do not = two words.
lol they mod him flamebait for talking about FreeBSD on a linux discussion.. I've never seen someone modding Linux flamebait for being refered on a FreeBSD discussion.
Oh well.
renice -20 *setiathome pid* will kill pretty much any OS
renice -20 kills pretty much any OS.
I love 5.2.1 on the desktop, avoid it on servers. The only servers I have with 5.2.1 are the ones with dual processors, all others run 4.10-STABLE and have been up for many, many months. I'll wait and see how 5.3 does. I won't be upgrading my desktop (at least for now) which is running 5.2.1-RELEASE, because I'd need to rebuild pretty much everything -- and we all know how XFree86 and GNOME upgrades tend to be a pain in the ass. As for the server market, I'm waiting on 5.3 for two months now for a dual xeon, and I'm confident it will do very well; I have one server with 5.3-BETA5 and my gateway at home runs 5.3-BETA3 -- Both without stability/performance issues!
"As all you have noticed the above^ part, will fbsd have the same performance or better? When will this be ready 5.3.X ? Could I get some more accurate information about this? Since I'm planning to use it on my desktop." You don't want a 5.3.*X* release, as 3-numbered released on FreeBSD are used to address critical bugs. Let's hope it stays 5.3-RELEASE/STABLE, heh.
Has anyone figured out what Microsoft *true* intentions are? I bet there is some legal issue hidden somewhere waiting to be uncovered. But that's just me.
I would have been fired some 6 times then..
It will work fine since the chroot is implemented at the named binary level. The problem here is the FreeBSD philosophy as I stated in my other post, for example, named.conf should never reside on /var ; But, as said in one of the posts to the mailing list, you can use the -c option to specify an alternative path to named.conf. At least with the port version, the -c option was (I think, almost sure) relative to the chroot path.
I don't know how true the statement in the mailing list was. I say, if it was running fine with the old scheme, it should be kept. If this was going to be implemented, perhaps they should have thought it on an earlier BETA stage. just my 2 cents.
The SMP bug is gone, the only left is the data corruption using gvinum.
There has been some discussion in the freebsd mailing lists about this change. BIND now resides in /var/named/ and some people are not confortable about this.
The default behaviour now is chrooting named too.
Personally, I like the old way better (/etc/namedb) as /var has a specific usage on FreeBSD, which is not keeping DNS server records. Changing the default from BIND8 to BIND9 will already make some people angry (because of migration issues), let alone changing bind base directory to a directory that won't fit in the freebsd philosophy..
You can read the whole discussion at http://lists.freebsd.org/pipermail/freebsd-current /2004-October/039288.html
Actually, this seems like a real problem as on at least two workstations I've had fdisk insisting the drive geometry was wrong. Specifiying the correct vallues to fdisk didn't help as it insisted with the old values.. But ultimately I could install the OS just fine even with the geometry set wrongly and it reports the partition sizes well.
I saw this movie last week, still can't believe how a country like America allowed Bush to become president. I never liked the man, but after seeing this documentary ? Damn. Especially shocking was in 9/11 when he was at the elementary school.. and he sat there instead of doing something. I couldn't believe this actually happened, but everything in the movie did make sense. IMO, the last stages of the movie (focuses on iraqui war) and the testemony of that mother who lost her son are there to cause some revolt on the american people, that really seemed to be his intention.
ah, so it begins..
your ignorance is great, pf is already ported to FreeBSD for quite some time as a kernel loadable module, and it will be integrated with 5.3-RELEASE. Have you copy-pasted a FreeBSD flaming text a year old ?
Please.
Fact: BSD's dont have several critical security advisories which could lead to root access EVERY months Fact: Linux apps running under emulation will sometimes run faster on BSD than on native linux Fact: Linux community = bunch of script kiddies & pseudo-leet (and as we can see, dozens of trolls) ; BSD Community = Technical guys Fact: FreeBSD is not dead, 4.11 is still coming, 5.3 is near the release.
... strike back again. Get a life idiots
Wasn't fedora the one promoted as very secure, and was hacked in less than 20 minutes too ? The story was on /. months ago
Connection to database failed Server process fork() failed: Cannot allocate memory Really, you guys are evil. leave the poor server alone!
by stability you mean a new way to get root on linux every month?
are we finally get 'em? :)