FreeBSD XP^H^H 4.5 available now 362
The_Rift was one of many who wrote in with this news: "The official mail has gone out to the FreeBSD-announce mailing list announcing the availability of Freebsd 4.5. Check your local mirrors for the ISOs.". The release notes have all the details, but take it from me -- this one is worth it just for the TCP/IP performance improvements by Matt Dillon and others. Kudos to Murray, Bruce, and the rest of the release engineering team.
freebsd is good (Score:1, Informative)
I like the fact that it is coherent and most of all, the stability missing from most linux distribution is amazing.
Good job!
Cool topic (Score:1)
Why call it XP? (Score:1, Interesting)
Re:Why call it XP? (Score:2, Informative)
Regards
Re:Why call it XP? (Score:2, Insightful)
XP stand for experimental.
as in Microsoft Windows eXPerimental.
You....don't get out much, do you?
Rule number 1: If you need to explain the joke, especially in this crowd, it's probably not nearly as funny as you think it is.
Rule number 2: If you feel the need to send us the same joke again, at least make it original!
bad example:
XP stands for unknown(as in X) Piracy.
Re:Why call it XP? (Score:3, Insightful)
It's a nice idea but since MS-DOS you've only been allowed to make one primary partition, and after that you're forced to put in an extended partition and logical drives. Most operating systems need to be installed on a primary, so your best bet would be using the operating system in question to set up the partition table. Last I checked even XP won't let you add more than one primary partition, but I could be wrong.
I've had the same problem with Intel Solaris. Bleh.
Logical partitions fictional (Score:2)
Yes, logical partitions are fictitional. So are all partitions. They're just conventions on how to share sections of the disk. Come to think of it -- files are fictitional, so are jpegs. etc.
Or did you just mean to suggest that the name logical partition is somehow less valid than logical drive.
Regardless of how problematic you view this system to be, it is the normal way of slicing the disk up into more than four chunks that can be shared among many operating systems on the x86 platform. You don't have to like it, but you'd think FreeBSD -- which is native to x86 -- would support it.
This is a very lame joke. (Score:2, Funny)
FreeBDSM... Sure, they'd all be perferts, but hell... a user's a user.
Lame joke, I know. but I warned you.
Re:This is a very lame joke. (Score:2, Funny)
Re:This is a very lame joke. (Score:2, Funny)
Not to mention (re)booting, powering down, and hot-mounting USB toys ..
Re:This is a very lame joke. (Score:1)
Do OS X, Apple or Mac ring a bell?
/max
Speaking of Etch-a-Sketchs (Score:2, Funny)
Well as a joke, I borrowed an etch-a-sketch and in the middle of a meeting. I pulled it out of my briefcase with the straightest face I could put on. Ignoring everyone, I started scribbling with it and the meeting just fell apart from there. The person speaking tried to ignore it and contine but the laughter from the rest was overwhelming.
Well, we already have Midori Linux (Score:2)
Geeks? Perverts? Who'da thought!?!
-Mark
Where's the DVD (Score:1)
Oh well, I guess I'll just erase some Corel Linux CD-RW's.
Someone tell me how to install this over a network, please.
Re:Where's the DVD (Score:1)
Re:Where's the DVD (Score:5, Informative)
The FreeBSD folks have already done this, in very plain language [freebsd.org].
For myself, I'm doing a cvsup now as I write this. Make world gonna start to cooking tomorrow night. I'm probably about 2 weeks behind the release as I try to update fairly regularly with the latest stuff.
The really good part about this is that all that stuff that's been held back for release is now gonna start flowing back into the ports tree and src directories. Yummy!
Re:Where's the DVD (Score:3, Informative)
you need two floppies
kern.flp and mfsroot.flp
boot with them and choose a few menu items and it's off
all detailed at the freeBSD homepages of course
Check you local mirrors for the ISOs? (Score:3, Insightful)
and waste a lot of bandwidth in the process. cvsup is your friend [freebsd.org].
Re:Check you local mirrors for the ISOs? (Score:1)
install (Score:2)
I generally install from the three disks (there's an optional fixit.flp with lots of programs on it) by choosing an absolute minimal configuration, installing the cvsup package, then "make update" in
hawk
Cute topic... (Score:1)
If it weren't for the uptime on my server, (64 days...upgraded the mobo again), I'd be working on this one right now!
syncookies? only now? (Score:2, Troll)
Re:syncookies? only now? (Score:2)
In my experience the IPF and PF firewall configurations are the most simple, flexible and powerful to use, and can be found on freebsd and openbsd and probably the others.
Re:syncookies? only now? (Score:3, Interesting)
I'm not sure how you went from syncookies to OpenBSD, but you did mention stateful inspection, so flame on!
Stateful Inspection(tm), stateful inspection, and TCP flag checks are not all the same thing. The INSPECT engine included in FireWall-1 is a dynamically-programmable state machine, capable of semi-complicated connection state tracking over a variety of connection-oriented (e.g. TCP) and connectionless (e.g. UDP) protocols. INSPECT is, in some form or another, patented. IPFILTER 's keep state clause (and IPFW's dynamic rules using the keep-state clause and the check state rule) also tracks connection state, but only for ICMP, UDP, and TCP, and it can only be changed by re-compiling the appropriate C code.
Here's the rant part: SIMPLY CHECKING TCP FLAGS IS NOT STATEFUL INSPECTION!! It's sometimes called stateless inspection and it means that a decision to pass or block a packet is decided on the characteristics of that packet alone. Allowing J. Random TCP packet to go through the firewall with a cursory check of the headers means I can do FIN or ACK scans through your firewall, and if you've got it set up to only log connection attempts, the scans won't even be logged. Suck!
As for stop denial of service attacks (aside: I hope to God I'm not the only person who has to figure out whether a person means the operating system or the network attack every time he sees those three letters), the only way to do that is to implement proper ingress AND egress filters on the gateway firewall or router. Needless to say, this is complicated, so most people don't bother.
Only you can prevent forest fires and improperly configured firewalls.
Re:syncookies? only now? (Score:2)
SIMPLY CHECKING TCP FLAGS IS NOT STATEFUL INSPECTION!! It's sometimes called stateless inspection and it means that a decision to pass or block a packet is decided on the characteristics of that packet alone.
Well, based on what you just said.. I still am ok. My rules basically states, only allow the packet into the state if it a) meets the port/proto requirements, b) meets the TCP Flags (S/SA). You seem to know what your talking about , so I am asking.. wouldn't that block a FIN/ACK scan through the firewall, being that the state wouldn't be established unless you met the criteria?
Cheers
Re:syncookies? only now? (Score:2, Informative)
The rule you describe (only allow S/SA and keep state) would indeed block a FIN or ACK scan.
For example, I have the following IPFILTER rule installed on my firewall:
This allows the initial SYN packet in, and tracks state from there on out. The next packet it allows through the firewall must be a SYNACK, and the packets following that must be ACKs, RSTs, or FINs. Once it sees the terminating FIN or RST, it removes the connection from the dynamic state. If it doesn't complete the handshake (SYN, SYNACK, ACK), the dynamic rule times out pretty quickly. If it does complete the handshake, I think the default timeout is on the order of a few days.Sorry about the flame bit. It's just that so many people mis-understand stateful firewall rules that I try to explain it to avoid people getting confused.
Re:syncookies? only now? (Score:3, Interesting)
I didn't quite know what syncookies were. I just knew I didn't want them anymore after that. If it was an option in FreeBSD at that time, I would have laughed at the option, and subsequently turned it off. After other issues in 2.0.28 (was Linus drunk?), I tried FreeBSD by suggestion of my brother. Been pretty happy since.
I'm sure the issues I had have been long fixed in the Linux tree, and should be in the new FreeBSD implementation, I hope.
I'd check the CVS commits on the Linux kernel to give more precise info of the syncookies, but I can't seem to find them linked from http://www.linux.org/
Re:syncookies? only now? (Score:5, Informative)
Now FreeBSD implements both commonly accepted solutions; I haven't looked at the code enough to say for certain, but I'd assume that syn cookies would be used in order to avoid connection loss only during *very* high packet rates (10^5+ SYN packets/second) since the syn cache works fine up to those levels.
FreeBSD 5 (Score:2)
> Well, what the hell do expect from an obsolete,
> ancient code base which is developed in a
> closed fashion?
Linus and friends approves patches to the kernel, does that make it's development model closed?
Having the core team approve commits to the base OS is no different to any other open source project, and just serves to keep the base system as high quality as possible.
As for old, since when has maturity been a bad thing for Unix?
> (Yeah, it "supports" SMP. As in, when one CPU
> is running, the other is locked idle. And vice-
> versa.
FreeBSD's current SMP support scales poorly because the kernel is based around a "Giant" lock, which prevents multiple CPU's from entering most of the kernel at the same time. However, except on systems where the kernel itself is heavily loaded, and/or on systems with lots of CPU's (4 or more), it's not a major problem.
FreeBSD 5, due out at the end of the year, will have Giant mostly removed, as well as things like kernel preemption and advanced userland threading. It'll scale as well as if not better than Linux.
It'll also have a new startup system based on NetBSD's (have a look at it, it's pretty cool - http://www.freebsd.org/cgi/cvsweb.cgi/basesrc/etc
FreeBSD 4.x STABLE branch. (Score:4, Funny)
It was kinda annoying that the FreeBSD guys obsoleted 3.X so quickly, they had only really just fixed the glaring issues with the ATA driver corruption problem and other important issues (that affected my use of FreeBSD 3.4 for fileserving) and then they went and obsoleted it.
If 4.X stays as the most current tree in STABLE for another year, hell, another 2 years, I for one will be happy. I dont see the 1-year cycle for major number increments as much really other than ticking over the most siginificant version-numbers. Stuff that gets MFC'd from CURRENT is usually good enough for STABLE, Look at Linus, he dosent feel a need to tick over the major version numbers for Linux. I'd stay with FreeBSD 4.x if it goes all the way to (say) 4.7 or 4.8.
Re:FreeBSD 4.x STABLE branch. (Score:3, Informative)
Linus and vers. numbers (Score:5, Funny)
2.x aout
3.x elf
4.x cam
5.x new smp
Linux - 2.4 - the kernel of pain
What will 2.5 be? The kernel of torment?
Then 2.7 The kernel of icy death?
3.0 The Kernel of eternal buring flesh?
@.8 could just be the kernel of itchy rash.
Re:FreeBSD 4.x STABLE branch. (Score:2)
Time to give it a try? (Score:3, Interesting)
Is it worthwhile for me to try FreeBSD now? I've already installed Win 95/98/2000, RedHat, Slackware,Suse,Debian & BeOS before and I still have an unfinished Linux from scratch install lurking around, but until now only Debian, Slack & Win 2000 stayed on long enough to make real use of them. ATM I'm running Debian w/KDE2.2 and I'm really happy with it, but hey, I still have a free 2Gig partition.
Can I run all apps/libs (or equivalents of the same quality) I use regularly now on FreeBSD? That would be KDE2.2, XMMS, OpenGL on GeForce2, MSN client, \LaTeX{}, Java1.2 a.o. Would It really bring me some extra performance/stability?
The whole FreeBSD approach does appeal to me, so I'm definitely interested in trying, but only if it has a real chance becoming my primary LILO partion
Linux is a better tinker-toy (Score:3, Insightful)
I had a freebsd box sitting my in closet for about 18 months, until I got bored with it and install openbsd. BUT, I don't really do any xwindows stuff on it.. basically web serving, outgoing email gatway, nat, proxy, and the place where I build my Python programs and scripts.
I guess to summarize my experience, *BSD is not a workstation supliment, but more a compliment. It will sit there and do it's job without much headache. Thats good enough for me
Re:Linux is a better tinker-toy (Score:3, Informative)
I have to respectfully disagree. There's nothing that Linux can do that FreeBSD can't. So why is there this perception that Linux is suitable for a workstation but FreeBSD isn't?
KDE, GNOME, Xmms, StarOffice, Java, Mozilla, Wine, etc., etc. I'm using FreeBSD as my desktop at home and my workstation at work. I couldn't be happier.
Re:Time to give it a try? (Score:2, Interesting)
The list archives are here. [debian.org]
Re:Time to give it a try? (Score:3, Informative)
I know KDE2.2, XMMMS, and the MSN client will run fine. I also know most source-code apps will compile in general. Also, FreeBSD does have Linux binary compatibility (to an extent). However, if you don't thrash your machine much, you will probably prefer Linux.
In short, put some time into learning about it and FreeBSD really is a fantastic OS. I would recommend it to tech-savvy people anyday. And it's constantly getting better (not dying
--jquirke
Re:Time to give it a try? (Score:4, Informative)
KDE2.2: yes
XMMS: yes
OpenGL: yes
GeForce2: yes, but not hardware accelerated. Fortunately, it is being worked on: http://nvidia.netexplorer.org/news.html
MSN client: ?, there are Jabber clients for instant messenging with MSN.
LaTeX: yes
Java: in a few days. It is standard with FreeBSD (they paid the licenses fees). It is v1.3.
Extra performance/stability: yes (SMP is lacking)/yes
I believe LILO can handle FreeBSD.
Re:Time to give it a try? (Score:2)
SMP is not lacking, at least for x86.
>I believe LILO can handle FreeBSD.
yes, and FreeBSD's loader can handle linux partitions.
hawk
Re:Time to give it a try? (Score:2)
> SMP is not lacking, at least for x86.
He was asking about extra performance of FreeBSD over Linux. I wanted him to know that SMP is not quite up to par. As he did not mention SMP, I believe he will see very nice performance. I just didn't want others to assume SMP was stellar. When 5.0 comes out, I will have to consider getting me an SMP box.
> > I believe LILO can handle FreeBSD.
> yes, and FreeBSD's loader can handle linux partitions.
Well, he did ask if LILO worked with FreeBSD. Personally, I use FreeBSD's loader.
Agree with your flamebait (Score:2)
I'm not sure how much of
Re:Time to give it a try? (Score:3, Informative)
I'd recommend giving a few hundred megs to a partition for FreeBSD. Since you're using your computer as a workstation, you won't see that much of a difference. It's not noticeably faster or more stable.
KDE, et. al. are just Unix programs. They work fine on BSD. The real difference is how you install it. Wait until you give the /usr/ports tree a try. The coolest way ever to install software.
*BSD is somewhat different from the Linuxes, especially RedHat. My last experience with RH was back at 6.2, but I got frustrated with its habit of tossing thing hither and thither all over the filesystem, and after my RH server was comprimised (buggy wu-ftp), I switched all my machines to Free and OpenBSD.
I, personally, prefer the BSD way of configuration, and I've been very happy since.
Re:Time to give it a try? (Score:2)
Re:Time to give it a try? (Score:2)
That's an ignorant myth. A most there are (_literally_) a *few* more apps because of commercial software companies that sell closed source applications.
Thankfully, FreeBSD can run these as well under it's Linux ABI compatibility.
Re:Time to give it a try? (Score:3, Informative)
Re:Time to give it a try? (Score:3)
Yes, yes, no, yes, yes, sorta. Most apps for linux compile for freebsd out of the box, and if they don't, you just type 'linux bash' at a shell and install a redhat rpm. nVidia is never going to release a driver for freebsd, closed or otherwise (don't start with OSX, it's not even close to the same thing at that level), or sufficient specs to write one. There's native Java now, but I doubt they'll port a retrograde version -- it should be backward compatible anyway.
The whole FreeBSD approach does appeal to me, so I'm definitely interested in trying, but only if it has a real chance becoming my primary LILO partion
We may yet see the death of LILO and it won't be too soon. FreeBSD's bootloader is comparable to GRUB and then some. It'll load Linux just fine as well.
Re:Time to give it a try? (Score:2)
Re:Time to give it a try? (Score:2)
Re:Time to give it a try? (Score:2)
And now you ask if LaTeX! of all things is on FreeBSD? Dude, TeX (and friends) are OLDER than Linux! So is the X Window System!
The answer to your question "is it worthwile to try FreeBSD now?" can be found by asking YOURSELF that question. Is it worthwile? Would you gain anything? Not just in performance or stability, but would you maybe learn anything in the process? Would you maybe even find that you just 'like it' better and switch completely? Is spending the time learning another OS (course, it's still Unix so as long as you don't go into it with preconceptions it'll be easy) worth any rewards you may gain?
This goes for anything, and not just FreeBSD, and not just Operating Systems and computers.
Tis better to have loved and lost than never to have loved at all.
FreeBSD Ports (Score:4, Interesting)
> a steaming pile of horse crap. It offers little
> or no flexibility in regards to how packages
> are built,
Most ports include all the options you need as make defines. If you need more, you can copy the makefile and edit it to your hearts content, and maybe type "send-pr" and submit a patch. Or you can just compile from bog standard source and have the rest of the ports tree use it because they look for libs, binaries and executables, not packages.
> and has a nasty habit of installing
> unecassary dependencies.
Such as? It's certainly nowhere near as bad as Debian, where the entire packages system is so complex and interdependent that it needs to go through years of testing before a release is concidered stable.
> For an example, try compiling PostgreSQL on a
> non-XFree FreeBSD machine from the ports tree.
> Notice how it insists on installing XFree86.
It used to want TK, which would want the XFree libs. That's no longer the case.
> You can't pass it any configure script options > like --without-xfree or ---don't build-
> retarded-gui.
For most people flags like -DWITHOUT_X11 etc are good enough. Otherwise scratch your itch and send-pr.
> Even with RPMs I can do that. In the end, you
> usually just wind up downloading the tarball
> and compiling it yourself, which seems to
> defeat the purpouse of a Ports/ Package
> Managment system entierly.
Making your own ports is trivial, pr's usually get resolved in a couple of days, and installing from source interacts with the ports system far better than any RPM/DEB system I've seen.
Frankly it sounds like you haven't tried it in a while. Sure, it's nowhere near perfect, but what is? Certainly not a binary package system with fragile dep issues and completely unaudited sources.
Re:FreeBSD Ports (Score:2)
Sounds more like he never really tried it in the first place. Being able to customize Ports behavior has been a feature for nearly as long as the system has existed.
He just never bothered to learn it. There's no harm there of course, but then he's not allowed to bitch and moan afterwards.
Re:FreeBSD Ports (Score:2)
Wait, or what if I could just type a 5 line gcc command?
I heard there's this low-level ASSembly thing-a-ma-jig so you wouldn't even have to do that.
What I _really_ wish for is a microscopic magnet so I could just twiddle the bits on the disk myself. That would rawk!.
You're so smart, I think you're really onto something here.
In other words, your sarcasm has not gone unnoticed. Of course you can customize software at compile time when building something manually. That, however, wasn't what the parent of my comment was talking about. They thought Ports were unflexible when the opposite is true.
Native JAVA (Score:5, Informative)
now no fucking about with linux emulated Java
maybe now I can get java in Konqueror to work
and I know it's not new but maybe you linux heads might've missed it.
FreeBSD now has a third party script that will auto-update any ports you've installed.
cvs update to the lates ports list and run portupgrade -ra and ALL of your port instaleld software will be updated to the latest version and dependencies resolved and reset (and a tool pkgdb will do some pre upgrade checks)
It's great. I'm going on about it because I'm so impressed with it.
FreeBSD rocks
Re:Native JAVA (Score:3, Insightful)
Native threading is in alpha and I'm currently working on the HotSpot compiler.
Re:Native JAVA (Score:2, Informative)
With this native JAVA, does it mean we don't need linux-jdk anymore? Should I cvsup and reinstall my port?
Re:Native JAVA (Score:5, Informative)
Having to deal with Linux emulated Java does suck. It doesn't integrate well with desktop apps that are compiled to run native on FreeBSD, like Konqueror or Mozilla. It's out of date, thus impacting stand alone apps like JEdit and server side apps as well. It'll be nice to see that Linux emulated Java yanked from the port tree. This is NOT about whether Linux is good or bad.
The "third-party" script being referred to is an implementation of even greater automation with installing and updating apps. The two key commands involved are "portupgrade" and "portinstall". For you Debian kinda folks this should look awful familiar...
portinstall gnome
portupgrade gimp
Essentially, an even smarter handling of apps building up from the infrastructure of the ports tree rather than trying to replace it. It works smooooooth too. apt-get, eat your heart out
Coupled with cvsup for keeping things all up to the minute, FreeBSD does rock!
Re:Native JAVA (Score:2, Informative)
I've had two in two days that patently aren't
must've pissed someone off
I don't care though, I'm in the 45-50 cap zone anyway.
Sure Debian might have the upgrading problem sorted out
(but actually I doubt it's as good tbh but that's pure speculation)
but the other distro's don't.
The java thing is annoying for me as I've got a project waiting for a java applet and I can't get konq to use java.
For me FreeBSD brings me consistency and ease of use. Linux has the light but so what, strength to your Penguin. I moved from slackware to FreeBSD (sadly via NT 3.5-4!). I tried Debian but didn't get along with it. My real OS of choice is plan9 but I won't go on.
cvsup! (Score:1)
Or save some bandwidth and point cvsup to the RELENG_4_5 branch on your local cvsup mirror.
Something the release notes don't mention: Could someone please clue me in on the state of native Java on FreeBSD? There was an announcement in late December but I haven't heard from it since then. Having to install the Linux JDK to build a FreeBSD JDK can't be the last word.
Re:cvsup! (Score:1)
I just wish I could get it to work. I tried to follow the instructions in the handbook, It was clearly written by someone who knew a lot about how it worked, but, at least for me, the entire message did not come across. I guess if you already into it, the manual is pretty clear.
Re:cvsup! (Score:1)
Native JDK (Score:2, Informative)
http://www.freebsd.org/releases/4.5R/relnotes-i
2.3.2 Ports/Packages Collection
Due to delays in the certification process, native JDK support for FreeBSD will be released shortly after 4.5-RELEASE. An announcement will be made on the FreeBSD Web site, as well as the FreeBSD announcements mailing list , when the distribution is available.
Insulting title (Score:1, Flamebait)
4.4 installer (Score:1, Interesting)
about distribution problems but.... frankly the installer on 4.4 was buggy to say the least.
I hope they've fixed it for 4.5. It was the only thing that cast a cloud on the 4.4 release.
Re:4.4 installer (Score:2)
It's not so much buggy as it is non-intuitive. Unlike the Linux installers I've seen, it doesn't provide a good step by step wizard for what things you do next. I guess you could call that buggy, but it's not like it doesn't work.
Robert Watson recently commented on this in an interview on OS News [osnews.com]. There's apparently work being done now to get a more straight forward, and quite possibly pertier, installer up and ready for FreeBSD 5.0.
It's actually a great interview, worthy of it's own thread.
Re:4.4 installer (Score:2)
Should I triy it? (Score:3, Insightful)
I heard a lots of good things about FreeBSD, but how big are the differences to Linux (installation)?
X
Re:Should I triy it? (Score:3, Informative)
What are the differences? Well that depends. What specific Linux distro are you comparing it to? All the Linux distros are different, so you can't really compare it to Linux as a whole, because that's just the kernel. Some distros don't even use glibc.
Installation is similar to Slackware and Debian. You won't get a fancy GUI that routinely misdetects your video card. It's very straight forward, sensible, and chock full of help.
Administration is uses sysinstall, which happens to lead a double life as the installer. No need to learn two programs when one will do. Similar to YaST in that regard. But you can also edit everything by hand in vi, and sysinstall won't undo you changes. You won't have a SysV style init scripts, but BSD (duh!) style scripts instead. I prefer the latter as it's easier to learn and understand. Everything in the base system is configured in one file, rc.conf. Apache, Sendmail, etc., still have their own configuration files though.
Installing software is similar to Debian and Gentoo. There are precompiled packages available, but the standard way is to use ports, which automatically fetches source, builds and installs. Using the cvsup and portupgrade utilities, keeping your system up to date is simplicity.
The GNU utilities aren't standard, so if you learned Unix the GNU way you may be thrown for a loop now and then. But if you learned Unix the Unix way, then you'll feel right at home. sh and tcsh are the standard shells, but just install bash if that's what you want. I prefer bash at the command prompt, but I write my scripts for plain vanilla sh.
Mirror site speed... no complaints! (Score:3, Informative)
Not all of the sites have the full set of files (yet), I had to hunt around a bit to find the '4.5-install.iso [freebsd.org]'.
Don't trust my math on transfer speeds?
(Yes, that transfer went via a proxy firewall)Damnit.. (Score:3, Funny)
I was about the finish the second ISO (96%)
and I had 3-5% on each of the third and fourth ISO's
and then they release 4.5... damnit...
*deletes 1+ gb of data, and begins again*
And this is all at a top of 15KB/s. And I can assure you it never got that high.
Re:Damnit.. (Score:3, Informative)
install ISO and then get anything else you need
once the system is up.
better yet . . . (Score:2)
hawk
Robert Watson's interview about the release (Score:5, Informative)
sounds like 5.0 should be incredible.
What about the new JDK (Score:3, Interesting)
Re:What about the new JDK (Score:3, Informative)
For now, you have to download the source from Sun, apply patches, and build it.
Already running it... (Score:2)
Whaddaya know, it booted up as "4.5-STABLE" instead of "4.4-STABLE". Talk about pleasant surprises... I guess if I read my email before rebooting I would have known.
improvements by Matt Dillon (Score:2)
Is there an Understanding Ports HOWTO? (Score:2)
I have FreeBSD 4.3 on a little x86 pizzabox that will eventually become my firewall and Web server. I'd like to upgrade to 4.5. Everyone I meet says, "just run cvsup and recompile the world."
Er, uh... Well, first of all, cvsup doesn't appear to be installed by default (why the heck not if it's so integral to keeping the system up to date?). Second, "recompiling the world" seems like a fairly drastic and space-hungry step, particularly since I installed binary packages in the first place (and presuming that actual recompilation is involved). And third, all the docs I could find on FreeBSD.org are rather thin (and even way out of date) on this process.
Is there a HOWTO or a step-by-step tutorial for FreeBSD newbies to become conversant with cvsup, the ports tree, and upgrading packages?
Schwab
Re:Is there an Understanding Ports HOWTO? (Score:2, Informative)
Next, here's my cvsup script (which I have run via cron every Thursday):
su-2.05# more `which cvsupLatest`
#!/bin/sh
sed -e 's/CHANGE_THIS/cvsup9/g'
rm
#rm -rf
sed -e 's/CHANGE_THIS/cvsup9/g'
rm
Running this will update the sources and ports in one go. Finally, I usually use the following to do the whole build world mess in one quick script (change REDRACER to the name of your kernel configuration file):
su-2.05# more `which makeworld`
#!/usr/local/bin/bash
(cd
Unfortunately, I've only given you a fish, not taught you how to fish, but it really just takes a little poking around to figure out what you need to do. Look at the handbook [freebsd.org], especially chapter 9. Rebuilding world and kernel is less space-hungry than you might think, it seems to take more time than anything. Another good source of advice is the newsgroup comp.unix.bsd.freebsd.misc
Re:Is there an Understanding Ports HOWTO? (Score:2)
'make world' sounds scarier than it is, mostly for mythical religious reasons. It's not space hungry at all really. A full
The fact that you installed binary packages is not relevant to building the world. FreeBSD is not a package based system (ala RPM, Deb, etc) and thus no portion of the OS itself is installed via a Package. 'make world' refers to rebuilding FreeBSD, not any 3rd party packages you installed so you wouldn't have to worry about them.
Freebsd.org/handbook is anything but thin on the process, and it's most CERTAINLY not out of date as it was updated to 4.4-RELEASE and 5.0-CURRENT for the recent 2nd Edition hardcopy publication (www.freebsdmall.com) handbook/makeworld.html has full step-by-step directions.
If you want to understand ports, the best source aside from the Handbook is 'man ports'. There's a man page for nearly everything in FreeBSD. You'd be surprised. Since Packages are just pre-compiled ports, they fall under the realm of the 'portupgrade' and pkg_* utilities. This is academic of course because there's no need to rebuild your packages after a make world unless you just happen to want newer versions of those packages (should new ones be available.)
"BSD is dying" is dying! (Score:2)
Yet another crippling bombshell hit the beleaguered Slashdot community when recently IDC confirmed that "*BSD is dying" trolls account for less than a fraction of 1 percent of all posters. Coming on the heels of the latest Netcraft survey which plainly states that "*BSD is dying" trolls have lost more market share, this news serves to reinforce what we've known all along.
You don't need to be a Kreskin to predict their future. The hand writing is on the wall: "*BSD is dying" trolls face a bleak future. In fact there won't be any future at all for them because "*BSD is dying" trolls are dying. Things are looking very bad.
All major surveys show that "*BSD is dying" trolls have steadily declined in market share. They are very sick and their long term survival prospects are very dim. If they are to survive at all it will be among the "hot grits" dabblers. "*BSD is dying" trolling continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, it is dead.
Fact: "*BSD is dying" trolling is dead
Re:Where is the "BSD is dying" clown? (Score:1, Troll)
Not to fear I suppose, the clown and the bitcher will be around eventually. Death, taxes, and trolls.
Re:Where is the "BSD is dying" clown? (Score:2)
Re:Firewall? (Score:3, Interesting)
Re:Firewall? (Score:3, Informative)
Part of 'secure by default' is that the base install omits a lot of fluff- this makes for quicker installs, and a smaller footprint.
One nice option for a firewall, there are plenty of cheap 64MB 'IDE FLASH ATA' devices showing up on Ebay, etc. These look like a laptop drive, work with any IDE controller, have no moving parts.Compared to FreeBSD, there are drawbacks, the most glaring being the lack of SMP support.
Also, OpenBSD's installation process can be intimidating the first few times through. Where Free makes it easy, Open makes you think about disk partitioning and other low-level issues.
Re:Firewall? (Score:3, Interesting)
Without sounding like an elitist, (which I am clearly or qualified to be), though the instalation was a bit awkward, it was direct and forward. After getting it installed, it was VERY easy to setup the configuration. All you really have to do is follow the instructions on the website. I had a machine setup in 2 hours (downloads and all w/floppy based install), after never touching the distro before thats not bad. Within 3 hours (and another helpful howto) I had the box hardened. Before the end of a long working day I had a VERY impressive set of rules setup to block various types of traffic, I understdood the difference between a stateless and statefull firewall and most importantly I understand why all the rules in my PF config where there.
I just find it nice knowing that there OBSD crew is working overtime to help me sleep better at night. At this stage in my career, if I am using and deploying open source solutions.. my judgment and credibility is on the line. I can't blame it on Scott or Bill if something goes wrong.
Cheers
Re:Firewall? (Score:2)
Re:I disagree with the installation remark (Score:2)
One thing I really like about the Solaris 8 installer is they've gone back to the pure command line, no more 'Press F1 to continue`.
Not only is a command line a lot faster at low baud rates than a full-screen TUI, but the scrollback history is of infinite value to figure out where you went wrong when things start to go all wahoonie-shaped.
Good experience with ISDN/FreeBSD (Score:5, Informative)
ISDN support under FreeBSD is very convenient. It uses the isdn4bsd [freebsd-support.de] system, which is integrated into recent versions of FreeBSD. In my opinion, it's superior to Linux, partly because configuration is easier and partly because ituses user-mode ppp [awfulhak.org] by default instead of kernel-based systems which are usually more difficult to configure and maintain. You have to see if your ISDN card is supported. Most passive cards are. Check the ISDN section [freebsd.org] of the FreeBSD handbook [slashdot.org].
Re:Firewall? (Score:3, Interesting)
A Pentium 120 with 48 MB RAM and a total 62 MB installation. 3 legged bastion host, making NAT for 130 WEB and ICQ maniac clients, protecting the DMZ with a heavy loaded Web server inside (2 requests per second). Making stateful inspection for the DMZ.
The only part expensive is the ethernet cards used in this box. Intel Pro100S, 51$ +VAT each (here in Turkiye).
ISDN support for {Free|Net|Open}BSD is really sophisticated. It's hard to experience problems.
Regards...
Re:Here's the text before it got slashdotted... (Score:2)
Move along unfunny troll, move along.
Re:Building a better BSD (Score:3, Informative)
leading to new metamoderation categories . . . (Score:2)
At least there we get to have a little fun with it (find the Seebach/Crispin flamewar at dejanews [search for "popcorn" in title]), but not here.
Coldn't we add "funny" to fair and unfair for meta-moderation categories?
While we're add it, let's add "-1, twit" as a moderation option, as well as "-1, just plain wrong" . . .
hawk
Re:leading to new metamoderation categories . . . (Score:2)
in that case . . .
Still, though, I've seen other moderations that were funny.
hawk
Re:Building a better BSD (Score:5, Informative)
It's a pretty damn good troll, though. Well crafted and subtle.
Re:Recommended hardware for a new FreeBSD box? (Score:2)
hawk
Re:Recommended hardware for a new FreeBSD box? (Score:2)
There's a hardware compatibility list in the ISO. HARDWARE.TXT in the root directory gives it to you. Or: Here's the link. [freebsd.org]
Recently, they've started producing an HTML version of HARDWARE.TXT as well. Look for HARDWARE.HTM on the ISO.
Re:Anyone know... (Score:2)
Re:What I would like to see in freeBSD… (Score:2)
Boots as fast as Linux and faster than Windows.
2. Ease of use
It's as easy to use as any Unix. Get over it.
3. Better setup interface (auto probe of PC hardware, setup hardware, if no drivers for hardware install modem or NIC and download drivers via cvsup and complete setup using xserver)
I don't know what you're talking about here. The GENERIC kernel, which is the one installed has support for all network cards already. A modem is just a serial device and doesn't need 'drivers'. All your typical PC hardware is also supported in GENERIC. That's why it's called 'GENERIC'.
4. One standard/exclusive window manager
This isn't a FreeBSD issue but a Unix/X one. It's the same situation on Linux.
5. One tool for window manager configuration.
If you mean to choose between wm's then this would seem to conflict with #4. If you mean to configure options for which ever wm you use, this already exists. GNOME and KDE (which are desktop environments more than window managers. GNOME runs on top of WindowMaker, Blackbox, Enlightenment, etc....), WindowMaker, etc all have their own window manager config tools.
And, like #4, this isn't a FreeBSD issue. Talk to your local window manager development team. Or hell, do it yourself.
6. One tool for driver/software tracking and installation/removals.
CVS baby (at least for the first part.) FreeBSD isn't a package based system so with the exception of 3rd party software (via Packages or the Ports Collection) What You See Is What You Get. You add and remove drivers by either recompiling your kernel or removing kernel modules that you've added. (In fact, build a very slim kernel and you can do nearly all via modules.)
As for 3rd party Packages that you've installed (Installed Ports essentially become registered Packages. In fact Packages are themselves made from Ports via 'make package' in
7. One tool for system administration
Several such tools exist. Myself, I like vi(m).
Re:What I would like to see in freeBSD… (Score:2)
#1. Sure, instant boot would be great.
#2. FreeBSD is as easy a Unix as any. This is not a biased or narrow view. I know full well that Unix isn't terribly user-friendly. I don't have to put a disclaimer in every single comment to cover my ass just so I don't offend ACs such as yourself.
#3. The question itself indicated an unfamiliarity with FreeBSD's support for hardware. Since no setup for specific hardware is actually required for installs. The context of the question implied this. This type of question often comes up when users do new installs because of the visual Kernel Config (boot -c followed by 'visual' at the config prompt will get you back into it on a running system) which would LOGICally fit within this context. The inexperienced new user is often confused by this screen and proceeds to deactivate every device they think they don't need. In fact, this screen can be skipped completely. The 'conflicts' indicated at the top are not real but only those that _could_ exist if you actually _had_ every device that was listed. If you skip it (I always do), the kernel automatically probes for everything (which I believe is what was asked for?). That (like I originally said) is what GENERIC is for. There's no chance that there'd be 'no drivers for hardware' because they already exist. Removing items from this 'setup interface' is actually the opposite of #3's request.
Of course LOGIC is not perfect. I could just have misunderstood #3, but that's only human, and not not a symptom of narrow visions or fanatiscism.
#4 and #5. Too obvious.
#6 also demonstrates some misunderstandings on the part of the poster. My answer is factual.
#7. There _ARE_ several such applications. There was a company with one at BSDCon 2000 but it's name escapes me. I suppose I could go out of my way and look it up (or find the sample CD I got) but then, so could you.
Of course, I don't know that it was you, but the tone of your response would indicate that it was. That, or you're just another fanatic with a narrow vision who sees evil and conspiracy where none exist. You have erred.
If I actually read comments on many Linux stories and saw an equally misinformed comment I would respond in kind in much the same way I did this one. My goal was only to inform the uninformed, nothing more. You should learn to relax.