FreeBSD 10.x comes with unbound instead of bind, however this change is likely not done in the 9.x series because it would be a large change that would go against POLA (the principle of least astonishment). FreeBSD tries to keep binary compatibility and a consistent base system throughout a Release-Branch.
This basically means 9.x and lower will stick with BIND whereas from 10.x onward the base system will come with unbound instead. Also i seem to recall there are efforts underway to replace the basesystem sendmail as well.
What amazes me the most is how practically everybody looks at this from the "when it crashes" point of view, when to me personally the biggest advantage to all of this is that one can actually have 40+ tabs open and having the system need Only swap in the Current Tab instead of every single tab all at once after an extended period of browser inactivity (likely causing the system to swap out the currently single browser process).
I know people will say RAM is cheap and all that... but still why should the system worry about swapping back in all 40+ open tabs when i am really only interested in the currently active one. Let it worry about swapping in another when i want it.
It keeps amazing me over and over again how "Open Source Development" and "Free Standards" somehow miraculously always seem to transform into "Linux"...
Let's not conveniently forget this test was completely UniProcessor, which is precicely where FreeBSD added additional overhead by its efforts to move away from the GIANT Kernel Lock (which NetBSD-2.0 still uses enitrely).
I would definately like to see these same tests performed on SMP-hardware and see if the NetBSD results are Still this much better than FreeBSD's.
Looks about right... except for the plugin location, i would personally use FreeBSD's nice/usr/X11R6/lib/browser_plugins/ directory to make the symlink in... that way if you have multiple browsers.. they can all pick up the plugin in the same location.
at least this works if you have both mozilla & firefox, and very likely will also work with the gazillion of GNOME-browsers like epiphany, galeon and whatever....
I guess the only reason i can think of not to use PHP on Apache-2... is if you absolutely HAVE to use a threaded version of Apache-2.
THe apache-2 (Worker MPM) itself is rock solid and definately seems to boost performance of ones http-server compared to traditional apache-1.3.
I am not exactly sure about a prefork-MPM vs apache-1.3 comparison.
The biggest problem with PHP on any threaded Apache-2 (i am not sure if this holds true for the 1.3 series as well)... is the fact that PHP keeps continuously crashing your httpd-processes.
Switching to the prefork MPM makes everything rock-solid again... but looses the benefits the threaded-MPMs offer.
If PHP could actually solve their problems with running in a threaded Apache-2... i would jump right on it:)
Again.. i never experimented with a threaded apache-1.3 (not even sure if that's possible)... but for Apache-2 with the current state of PHP.. it's not recommended...
The reason it's highly recommended to Upgrade all ports depending on the gettext-libraries (libintl), is because apparently the gettext-0.12.1 port installs libintl.so.5 instead of libintl.so.4 which came with the previous gettext-0.11.5 port.
in other words... a Version Bumb in the shared library... which Could result in a lot of future package dependencies being fucked up if you don't upgrade your old gettext installation and recompile those ports that depend on it... to use the new shared library version.
What it's exactly doing on Slashdot though.... i leave that to the original poster.
Re:Portage is a *BSD ports killer
on
Gentoo Linux 1.2
·
· Score: 1
And yes... that was SARCASM
Re:Portage is a *BSD ports killer
on
Gentoo Linux 1.2
·
· Score: 1
> It is everything that FreeBSD should have been but isn't.
is that this is the First Official CD Release of FreeBSD by the DaemonNews Crew. FreeBSD by itself has been available on CD for as long as i can remember.... (at least back to the 2.2.x days).
In that case You simply let the system make a "snapshot" of your dirty filesystem. Mount the filesystem... and simply let FSCK do the cleanup in the background... FreeBSD-5.0-CURRENT already has this functionality WORKING for (if i recall correctly) several months by now.... so don't be surprised if this starts to creep up into e.g. NetBSD/OpenBSD as well.
I honestly think it's not nearly as narrow minded as it might seem... and this it's actually a rather acceptable question... After all.. (at least) Perl, Java, and PHP are ALL available under a Windows platform as well as a UNIX platform. If he finds Windows to so much better.. I am actually wondering why he switches to Linux to do development .
So, set "console" to "insecure" in "/etc/ttys" to force root to authtenticate him/herself even when booting to single user mode using the boot -s command at the boot loader.
If i recall correctly there have been postings on the FreeBSD maillinglist requesting people to test a new updated "linux_base" port that is based on a recent redhat-7.
I assume that when the port has received "enough" testing and reported issues are addressed... marcel (port maintainer of linux_base) will surely replce the current linux_base port with this updated version....
Ok... Maybe they should have said Mozilla on LINUX requires GLIBC-2.1... I For Sure do NOT want to have to install that beast on my FreeBSD or NetBSD systems e.g. That would be just outright Gross.
> Seriously though guys, what is the need for this program to exsist other than to cause new problems and incompatibilites?
Ever considered the possibility (i know it must sound rediculous) that there actually ARE people out there that do NOT use Wintendo(TM) as their Operating System... and who DO want to have a decent browser that DOES support todays W3C standards like CSS2 etc.
Slashdot Mirror
FreeBSD 10.x comes with unbound instead of bind, however this change is likely not done in the 9.x series because it would be a large change that would go against POLA (the principle of least astonishment). FreeBSD tries to keep binary compatibility and a consistent base system throughout a Release-Branch.
This basically means 9.x and lower will stick with BIND whereas from 10.x onward the base system will come with unbound instead. Also i seem to recall there are efforts underway to replace the basesystem sendmail as well.
What amazes me the most is how practically everybody looks at this from the "when it crashes" point of view, when to me personally the biggest advantage to all of this is that one can actually have 40+ tabs open and having the system need Only swap in the Current Tab instead of every single tab all at once after an extended period of browser inactivity (likely causing the system to swap out the currently single browser process).
I know people will say RAM is cheap and all that ... but still why should the system worry about swapping back in all 40+ open tabs when i am really only interested in the currently active one. Let it worry about swapping in another when i want it.
It keeps amazing me over and over again how "Open Source Development" and "Free Standards" somehow miraculously always seem to transform into "Linux" ...
All the world's NOT a Linux Box.
While we're at it ... may i suggest in that case to just rename Linux to "Red Herring" ?
Sorry .. Can't Reproduct Still ...
FreeBSD/amd64 7.0-CURRENT firefox-1.0.6
it's availabe in x11-wm/enlightenment-devel
Let's not conveniently forget this test was completely UniProcessor, which is precicely where FreeBSD added additional overhead by its efforts to move away from the GIANT Kernel Lock (which NetBSD-2.0 still uses enitrely).
I would definately like to see these same tests performed on SMP-hardware and see if the NetBSD results are Still this much better than FreeBSD's.
Looks about right ... except for the plugin location, i would personally use FreeBSD's nice /usr/X11R6/lib/browser_plugins/ directory to make the symlink in ... that way if you have multiple browsers .. they can all pick up the plugin in the same location.
....
at least this works if you have both mozilla & firefox, and very likely will also work with the gazillion of GNOME-browsers like epiphany, galeon and whatever
I guess the only reason i can think of not to use PHP on Apache-2 ... is if you absolutely HAVE to use a threaded version of Apache-2.
... is the fact that PHP keeps continuously crashing your httpd-processes.
... but looses the benefits the threaded-MPMs offer.
... i would jump right on it :)
.. i never experimented with a threaded apache-1.3 (not even sure if that's possible) ... but for Apache-2 with the current state of PHP .. it's not recommended ...
THe apache-2 (Worker MPM) itself is rock solid and definately seems to boost performance of ones http-server compared to traditional apache-1.3.
I am not exactly sure about a prefork-MPM vs apache-1.3 comparison.
The biggest problem with PHP on any threaded Apache-2 (i am not sure if this holds true for the 1.3 series as well)
Switching to the prefork MPM makes everything rock-solid again
If PHP could actually solve their problems with running in a threaded Apache-2
Again
If your sole qualification for an IRC client is their quit-messages ....
If people are looking for a nice alternative client for mIRC for their Win32 systems i would highly suggest you give HydraIRC a try.
The reason it's highly recommended to Upgrade all ports depending on the gettext-libraries (libintl), is because apparently the gettext-0.12.1 port installs libintl.so.5 instead of libintl.so.4 which came with the previous gettext-0.11.5 port.
... a Version Bumb in the shared library ... which Could result in a lot of future package dependencies being fucked up if you don't upgrade your old gettext installation and recompile those ports that depend on it ... to use the new shared library version.
.... i leave that to the original poster.
in other words
What it's exactly doing on Slashdot though
And yes ... that was SARCASM
> It is everything that FreeBSD should have been but isn't.
You mean it uses the FreeBSD kernel too ?
I understand your reasoning ... though the example is (often) kinda a moot point.
Since when do we allow remote users to open the DISPLAY ?
It's news for the exact same reason that the release of Linux-development kernel gazillion-and-one is slashdot Frontpage News.
is that this is the First Official CD Release of FreeBSD by the DaemonNews Crew. FreeBSD by itself has been available on CD for as long as i can remember .... (at least back to the 2.2.x days).
In that case You simply let the system make a "snapshot" of your dirty filesystem. Mount the filesystem ... and simply let FSCK do the cleanup in the background ... FreeBSD-5.0-CURRENT already has this functionality WORKING for (if i recall correctly) several months by now .... so don't be surprised if this starts to creep up into e.g. NetBSD/OpenBSD as well.
I honestly think it's not nearly as narrow minded as it might seem ... and this it's actually a rather acceptable question ... After all .. (at least) Perl, Java, and PHP are ALL available under a Windows platform as well as a UNIX platform. If he finds Windows to so much better .. I am actually wondering why he switches to Linux to do development .
Oops ... I said "ttyv0" where i meant "console"
So, set "console" to "insecure" in "/etc/ttys" to force root to authtenticate him/herself even when booting to single user mode using the boot -s command at the boot loader.
I Know it's a troll i am responding to ... but for those interested in how to avoid the here mentioned boot -s "security flaw" ....
/etc/ttys set ttyv0 to insecure
in
that will require root to STILL authtenticate him/herself EVEN when booting to Single User mode.
If i recall correctly there have been postings on the FreeBSD maillinglist requesting people to test a new updated "linux_base" port that is based on a recent redhat-7.
... marcel (port maintainer of linux_base) will surely replce the current linux_base port with this updated version ....
I assume that when the port has received "enough" testing and reported issues are addressed
Apparently SlashDot can't handle posts that provide NetBSD-Changelogs ... because of their stupid (doesn't work anyway) Lameness Filter.
It won't allow me to post the contents of the CHANGES-1.5.1 file that contains the changes from 1.5.2 compared to the 1.5.1 Release.
Ok ... Maybe they should have said Mozilla on LINUX requires GLIBC-2.1 ... I For Sure do NOT want to have to install that beast on my FreeBSD or NetBSD systems e.g. That would be just outright Gross.
> Seriously though guys, what is the need for this program to exsist other than to cause new problems and incompatibilites?
... and who DO want to have a decent browser that DOES support todays W3C standards like CSS2 etc.
Ever considered the possibility (i know it must sound rediculous) that there actually ARE people out there that do NOT use Wintendo(TM) as their Operating System