Slashdot Mirror

Telnet has no /join, /msg, etc. You must use RAW irc commands.
PRIVMSG #channel :message
PRIVMSG nickname :message
JOIN #channel
etc.

For anyone else interested in using telnet as an irc client, you might want to check this link out
http://www.daemonnews.org/199907/irchack.html

O'Reilly has a book on PostgreSQL called Pratical PostgreSQL, which was published at the beginning of this year. A bunch of other PostgreSQL books can be found here; Prime Time Freeware has published printed versions of the online documentation (which I did a brief review on the "Use and Administration" portion here.

O'Reilly has a book on PostgreSQL called Pratical PostgreSQL, which was published at the beginning of this year. A bunch of other PostgreSQL books can be found ; Prime Time Freeware has published printed versions of the online documentation (which I did a brief review on the "Use and Administration" portion here.

I've done it with OpenBSD. It's actually quite simple and easy to set up.
One thing I've found helpful was to do it first on a harddrive set only for this (trying to boot it, recompiling and all), and then burning the CD. The first time I tried it, I was making it on top of another intallation and that got me tunning the former installation, which had nothing to do with my intended CD, just to cleanly compile it all.
Take a look at this article and man mfs.

If you don't have the bandwidth to download Darwin and look at it, you could always get a CD version from Daemonnews, that BSD only site.

The current version of Darwin/OS X borrows heavily from FreeBSD 3.2, the next major upgrade to OS X (this summer) will implement changes made to FreeBSD 4.4.

Here's a great look at how Apple bolted BSD and Mach together, since you sounded curious - probably not what you would expect.

OpenBSD has a number of features to do the "transparent" routing which you desire - basically, you can plug in two interfaces and route from one to the other without changing the packets at all. The OpenBSD box basically looks just like a hub or a dumb switch to its peers, eg, it doesn't even have an IP address assigned to either interface, it doesn't decrement ttl, it doesn't do TCP optimizations, etc. As far as I know, this is not possible with Linux and it sounds like this is exactly what you want. See this page for more information.

Back on topic, it is kind of sad that two respected people have left the FreeBSD core team, but things have to evolve and projects need to become somewhat dynamic rather than stay stagnant. Companies cannot survive with the same set of people on their board of directors forever either (though some wish that isn't the case).

As projects get more committers, programmers, and commenters, the harder it is to keep focused and be able to agree on the same thing. I think that Linux has shown some of the same symptoms (disagreements between how kernel patches should be handled, etc.).

Just some of my thoughts... that's all.

Wait, I'm not Jordan Hubbard... Not even the same middle initial. What was I thinking? Uhh, never mind.

The article goes about the tunnel process in a different manner, but it still does not say anything about interoperability with win2k. Could the authors (or someone else) comment on how to get an IPSec replacement for WEP that works with both FreeBSD and Win2k.

I'm aware of this article, but it uses transport mode and is inadequate as a WEP replacement.

Thanks in advance.

-Peter

NetBSD's got a very nice rc (startup) system; as opposed to the monolithic (Open|Free)BSD approach, NetBSD's is a highly modular dependancy based model; no more giving scripts esoteric names like "000.wibble" to try to get it executed before "001.wobble"; just add a dependency in wobble on wibble and the rc system will make sure wibble is executed first.

There's an interesting PDF paper on the design and implimentation, some conciderably more terse and less interesting official documentation and a Daemon News article, and for those uber geeks, the CVS repository where you can compare with the other BSD's.

You'll note FreeBSD -CURRENT is looking at adopting it, while Open sticks with the tried and tested BSD4.4-type setup

Not that PF is bad - you just can't do everything together ;-)

cheers,
Rainer

You will be waiting a long time for .Net to be viable on FreeBSD. It will probably never happen. It's just Microsofts way of dividing the free Unix community, in my opinion.

FreeBSD finally gets Native JDK (December, 2001.) .NET isn't even out yet and MS is targetting BSD. Face it: Microsoft is evil. Sun would love to be evil, if only they had the market share. IBM still thinks that it's evil, but it really isn't anymore. Oracle is still hoping for the day when their DB will dominate the OS market. And Steve Jobs, well, Steve will be wearing his trademark black turtleneck today and dreaming about Apple becoming the One True Computer. All of them are closed-source proprietary companies that would love to Divide the Free Unix Community.

For that matter, Ma Bell would love to control the Free Unix Community. Or aren't you old enough to remember when Murray Hill was the center of the universe?

This release is supposed to be the first one to include out of the box, native support for Java, right ? Does anyone know if they are still on track with that ?

More information about the print magazine can be found here (or http://magazine.daemonnews.org/ for those who are afraid of goatse.cx links). The magazine has turned from every other month to quarterly.

More information about the print magazine can be found here (or http://magazine.daemonnews.org/ for those who are afraid of goatse.cx links). The magazine has turned from every other month to quarterly.

I have it on good authority that Daemon News will be producing FreeBSD 4.5 and giving back to the FreeBSD Foundation. They also have Subscriptions available, so you might want to transfer yours.

Speaking as one of the article writers for this month's issue, I personally don't have the resources nor time to dig into the other BSD operating systems. Also, I focus primarily on FreeBSD since I run FreeBSD on all of my machines that I run and manage (sans my primary work machine, which runs Windows 2000). The only machines that I can install a non-Windows operating system on are usually lower-end machines that don't have a lot of hard drive space (I know hard drive space is cheap, but I'm in debt right now).

Once I'm done with my next two FreeBSD projects for work, then I will try to snag a Mac machine and maybe write an article on Mac OS X 10.1.

If you want to see more general BSD articles or an article on your favorite BSD flavor (be it OpenBSD, NetBSD, Mac OS X 10.x or Darwin), and you have the time to write an article... you are very welcome to submit it to Daemon News. If so, just send a completed article to articles@daemonnews.org

AFAIK, there are different school's of thought on the issue of Journaling Vs "SoftUpdate-like" filesystems.

I could go on and on about this, but theres a perfect comment on this on daemonnews that points to a french article that summerizes the reasons.

http://daily.daemonnews.org/view_story.php3?story_ id=2327

The only thing lacking right now in softupdates is an unattended way of the filesystem coming back up in the case of large data lost. This will be addressed when the background fsck daemon is completed, Softupdates will have all the merits of a journalled FS, plus even more speed ( disputeable ).

As a rather novice Linux user, I've been curious as the differences between it and BSD. Can somebody point to a link that goes into some rather sophisticated detail between the two? (More than "Supports themes, is cool, etc.")

This article might be a good read for you:

http://www.daemonnews.org/199907/d-advocate.html

Check here:Using CVS to manage a website

Evans Data Corporation, a market research company focused on the software development community, is the one that called FreeBSD "A linux distro"
http://daily.daemonnews.org/view_story.php3?story_ id=1748
http://slashdot.org/article.pl?sid=01/03/30/082320 5&mode=thread

My Reply is of the Bad News/Good News form:

Bad News First: Some "Old School" BSD people are not real keen on providing interested students and budding developers with a well defined entry point. The key to learning is directed exploration and you need to point people to a good starting place, not at a sea of code. Getting students to work with Linux is easier,
since the internals guide in addition to the source are available. What you cannot tell students who want to get started is that FreeBSD is well documented,just in C. Sure only seasoned developers will write code for such a system, but if they have other commitments (like feeding themselves and their families) you lose.

Good News: The new school of FreeBSD developer is a bit more aware of this, and documentation is beginning to hit the street, the New Bus documentation is a very good start. FreeBSD needs a system call writers guide (actually Pragmatic of THC had a very good guide but my links to it have died from bit rot).
When is the update to McKusick et al.'s book on 4.4 BSD coming out? I expected a FreeBSD oriented successor to come out this summer.

Quite frankly, that sounds like a very poor design. If you are changing your internal APIs so often and don't have a good abstraction layer in place for basic driver work, then you're shooting yourself in the foot. The internal APIs being in a "constant state of flux" shows that you need to get your heads out of the implementation detail, step back, and do some actual design work first.

As for the kernel API being in a constant state of flux, I believe that the poster didn't mean it that litterally. Sure, some things do change over time, but I find most of the stuff to be very clear and well documented (note, I'm not a FreeBSD kernel hacker/developer). I also find the newbus scheme a very compelling infrastructure for driver development.

OS X has nothing to do with BSD

BSD subscriptions in a nutshell: They send you the DVD or CDs when the latest version is released and bill you instead of having to order it every time there's a new release.

Since it's cheaper to ship 1 DVD as opposed to 10 or so CDs, I can't imagine it getting any more expensive.

BSD subscriptions in a nutshell: They send you the DVD or CDs when the latest version is released and bill you instead of having to order it every time there's a new release.

Since it's cheaper to ship 1 DVD as opposed to 10 or so CDs, I can't imagine it getting any more expensive.

When I got my server at home, I needed something that didn't occupy a lot of space and really didn't need it to be beefy at all. I decided to get a Compaq iPaq desktop, but Compaq only provided Windows 95/98 or Windows NT with it. I got the one with Windows 95, wiped it, and put FreeBSD on it. You can read the little paper on it here.

http://daily.daemonnews.org/view_story.php3?story_ id=1858

Linus Torvalds has been described as a benevolent dictator; the modifications he likes are added. (taken from Daemon News)

One would figure someone like Linus would embrace the OS X concept, or abide by the old saying... "If you don't have anything good to say don't say it at all." or maybe he read articles like this and was offended.

Or maybe its because some authors claim OSX is a threat to Linux users somehow... I dont see how it could be a threat, but maybe he just needed to vent some frustration. I also don't know how he managed to make time to say that since he seems so busy releasing kernels every week

powered by OpenBSD

Linus Torvalds has been described as a benevolent dictator; the modifications he likes are added. (taken from Daemon News)

One would figure someone like Linus would embrace the OS X concept, or abide by the old saying... "If you don't have anything good to say don't say it at all." or maybe he read articles like this and was offended.

Or maybe its because some authors claim OSX is a threat to Linux users somehow... I dont see how it could be a threat, but maybe he just needed to vent some frustration. I also don't know how he managed to make time to say that since he seems so busy releasing kernels every week

powered by OpenBSD

The duke of URL had a graph showing quake running faster on FreeBSD than Linux. way to the Duke and the duke and for the graph. the graph showing its faster

And Walnut Creek had a 1 page glossy claiming 20-30% faster performance.

We now have a Nokia firewall with CheckPoint Firewall 1 and an intrusion detection system in a locked box (thanks to Al Gore for inventing the Internet and lockboxes) that is monitored 24/7 by a security center with a dedicated encrypted connection. The Nokia is a little more than a PC, with extra software. There is quite a bit of OS hardening, management capabilities, etc. in the box itself. Obviously this did set us back a little bit but it doesn't compare to what is at stake for us. We are competing for the same people as the other area banks and if people lose confidence then we are going to be hurting.

It all boils down to what you are protecting. If you are even considering PIX, Checkpoint, etc then maybe you have something worth protecting. If you are only saving a few thousand dollars then you should really reconsider the advantages of support, maintenence, time, etc. and focus on the other areas of security.

It sounds like you are determined to continue with this so I would suggest that you build a second machine with a differeent OS to protect yourself. There's a good article using OpenBSD as transparent bridging firewall. The article suggests using it as a firewall it front of a router but it would work as well as a firewall in front of another firewall. Using different OSs will make it harder to get through both even if they both BSD (Open, Free, Net) or even Linux. I'm looking at using OpenBSD bridge firewalls between all my branch connections and between the network and the modem pool. Using a commercial firewall that is managed gives me the time to lock the rest of the network down and jump on users for doing stupid things. Never underestimate the ability of a user to circumvent your security whenever they get a chance.

All subscribers were emailed a notice of the shipping situation. If you didn't get yours, perhaps you didn't give a valid email address when you ordered? If you want to correct it, mail sales@daemonnews.org with your correct contact information (and a way to correlate it with the info already in the database).

A poster explained it well here: http://daily.daemonnews.org/view_story.php3?story_ id=1485

Yeah, the article said that :)

Today, Network Appliance, Sun, and a few others hide TRAM technology in their core storage products. Network appliance uses TRAM in a different way, though. They hold the NFS rpc requests in memory, not the disk blocks. Their WAFL filesystem is journaled and can come up quick on its own, so it doesn't require the TRAM. They use it to respond to requests quickly, yet still give the client the semantic that the operation is 'safe' or committed to disk. To deal with the journaled filesystem, they use RAID striping.

--Brett

This article was also part of the November Issue of the DaemonNews E-zine. This a link to that article http://www.daemonnews.org/200011/stopspam.html.

Those who do not familiar with Mr. Theo de Raadt's usual action about BSDs should know the following history about the mail filtering.

• not only NetBSD, but also FreeBSD maintain such filtering.
• the reason why the filtering exists is that Mr. de Raadt made threat that he will send mail bomb, and he never retract that. You can confirm this by mailing list archive of FreeBSD or NetBSD.
• NetBSD doesn't maintain a black-hole route to the OpenBSD project networks, but did make a black-hole route to Mr. de Raadt's network. Other OpenBSD developer should not have problem, and there are many developers who have both OpenBSD and NetBSD developers' account. For example, one of NetBSD's core member is a OpenBSD's developer.

This issue is once raised by a OpenBSD developer in DaemonNews forum which has neutral position between FreeBSD, NetBSD and OpenBSD, and its conclusion is that the forum should never have posted the topic. I don't know why Mr. de Raadt mentioned this filtering again in slashdot. Perhaps He'd like to show that he is still ready to post mail bomb to FreeBSD/NetBSD mailing list?

Those who do not familiar with Mr. Theo de Raadt's usual action about BSDs should know the following history about the mail filtering.

• not only NetBSD, but also FreeBSD maintain such filtering.
• the reason why the filtering exists is that Mr. de Raadt made threat that he will send mail bomb, and he never retract that. You can confirm this by mailing list archive of FreeBSD or NetBSD.
• NetBSD doesn't maintain a black-hole route to the OpenBSD project networks, but did make a black-hole route to Mr. de Raadt's network. Other OpenBSD developer should not have problem, and there are many developers who have both OpenBSD and NetBSD developers' account. For example, one of NetBSD's core member is a OpenBSD's developer.

This issue is once raised by a OpenBSD developer in DaemonNews forum which has neutral position between FreeBSD, NetBSD and OpenBSD, and its conclusion is that the forum should never have posted the topic. I don't know why Mr. de Raadt mentioned this filtering again in slashdot. Perhaps He'd like to show that he is still ready to post mail bomb to FreeBSD/NetBSD mailing list?

There was a good article last year from "Daemon News" about how to contribute to the development projects that you benefit from.--jbf

I always keep a single source and ports tree on one machine and NFS export this to all others on the network.

Want to upgrade the entire LAN from 4.1 to RELENG_4 (4-STABLE)? Easy, cvsup the one source tree, buildworld, then on each machine on the lan installworld. You can do the same things with the ports if you want, or you can actually make binary packages from the ports tree (this is how they are done for a release) and share them across the network for each of your thousands of servers to install.

I think everyone agrees that the package management needs to be improved tho'. Daemonnews covered a mail written by Jordan that covers things very well.

http://daily.daemonnew s.o rg/view_story.php3?story_id=1185

It would be great to see the entire distribution become more modular - if parts of the base distribution were added as packages it would be sooo easy to chop and change things for custom installs.

.flip.

There is a possibility that someone might start an English BSD magazine. Go here for a discussion concerning it.

Let's consider another comparison: others have asked ``how many women are on the core team?''.

The answer, both before and after, is ``none''. This isn't discrimination: we currently have no female committers, so it's just not possible. For whatever reason, hacking remains a very predominantly male business.

Obviously it makes sense to select the "politicians" from the group of people that are interested in participating in the project. If no women were interested in participating, it is unsurprising that none were available for selection.

The problem, if it be considered such, does not lie in the selection of the FreeBSD core team, but rather way back when people decide what sorts of things they want to get involved with. Where there weren't any women that put FreeBSD on their lists.

Anyone interested in the way the FreeBSD organization works might want to look at this URL.

Why did they need a new core? Do they have a term of office which expired? Was there a popular uprising and overthrow of the oppressive bourgeoisie?

Greg Lehey's Daemon News article addresses this question.

Check out The Daemon's Advocate for the details. As for the composition of the core team, for those who won't follow the link: - it now has only 9 members(down from 15) - of the old 15, either 7 or 8 ran and only 5 were elected(article says two weren't, 5+2=7, but also said 8 stood for election...go figure) - 5 members of the old core team had a non-English native language where now 1 member has a non-English native language - 7 members of the old team were outside the US where now only two are The elections are held every two years.

There's an interesting article @ Daemonews here: http://www.daemonnews.org/200010 /da dvocate.html. It's a short summary of the history of BSD, the various leadership approaches (NetBSD's + FreeBSD's CORE, Linux's benevolent dictator, OpenBSD's hybrid), and other cool stuff. I recommend it.

Actually the very first steps have been taken to unify all the ports trees. I recall it being listed on Daily Daemonnews and Daemonnews but both sites seem to be down at the moment.

Actually the very first steps have been taken to unify all the ports trees. I recall it being listed on Daily Daemonnews and Daemonnews but both sites seem to be down at the moment.