August 2002 Daemon News Ezine Published 102
questionlp writes "The August 2002 Ezine has been published and is packed with articles and columns with topics ranging from behind-the-scenes look at VicFUG 2002, a report on the recent O'Reilly OSCON, one's adventure through Unix starting from Linux to FreeBSD, a HOWTO on backing up FreeBSD with tar and SMBFS, plus a look at some of the most popular web browsers (most of which are available in the BSD Ports collection)."
Re:Here's a little tip (Score:1)
Re:Here's a little tip (Score:2)
I think you've misinterpreted what Slashdot is all about.
The aim of the
This "article" isn't even a real article. It's a newsletter from the BSD camp. Perhaps there is something interesting posted in the issue, but you'd never know it from reading the writeup which just gives a shotgun blast overview of the topics covered.
We don't get updated every time Dr. Dobbs releases a new issue. Why should Ezine be any different?
Re:Here's a little tip (Score:1, Offtopic)
It is obvious what Slashdot ought to post. News for Nerds, Stuff that Matters. It's written right up there at the top of the page.
Let's assume that a news item only has to meet one of those criteria to be worthy of posting. In that case, we can see how Star Wars Ep. 3 trailers would be posted; it is News for Nerds. And we can see how 9/11 coverage would be posted; it is Stuff that Matters. It is difficult to see how a newsletter that people are already subscribed to would fall under either of those categories.
If all it takes to make something Slashdot Frontpage-worthy is an editor's opinion, then maybe you can be satisfied. Take a look at the other stories currently on the front page. They are all easily classifiable under News For Nerds. Then look at this story. It is a piece of crap. Not because the newsletter isn't interesting, but because it isn't news and it doesn't matter.
Re:Here's a little tip (Score:1, Redundant)
Secondly, let's take a look at what "news" is:
news Pronunciation Key (nz, nyz)
pl.n. (used with a sing. verb)
- Information about recent events or happenings, especially as reported by newspapers, periodicals, radio, or television.
- A presentation of such information, as in a newspaper or on a newscast.
- New information of any kind: The requirement was news to him.
So, according to those with the ability to concur what that defination means, this article was news.
Thirdly, like I said earlier, if you don't like it, you can filter it out, or go away.
Re:Here's a little tip (Score:1)
Second point. Unless you think that news about a newsletter counts as news, this wasn't news. News is information about something. This story wasn't about anything.
Third point. Frankly, because of Slashdot editor fanboyism on the part of many
Re:Here's a little tip (Score:1, Troll)
Also, did you not read what NEWS is? It was rather simple, hell, I even posted the definition. Maybe your mother just didn't read that part to you. This post is NEWS about something NEW, which is the NEW issue of the ezine.
I'm hardly a fan of slashdot editors, but it's annoying when linux-infatuated kiddies like yourself whine about anything else being posted and whatnot. If you don't like it, filter out everything but Mandrake news so you can get the info on when the betas come out, so you can be krad and run 0-day OSes.
Re:Here's a little tip (Score:2)
Whoa whoa whoa. There's no need for name calling.
Let's not digress from the main point which is that this article is only news to those people who think it's news that the sun rises every day. If you think it's important that newsletters be announced every time they are published, that's fine. Just keep that crap off the main page.
Re:Here's a little tip (Score:1, Offtopic)
Re:Here's a little tip (Score:2)
If you continue to believe that a newsletter's release, monthly apparently, is newworthy, that's your perogative. I maintain that newsletter publications are not newsworthy, much less front page material.
Reason for decreased popularity of BSD found! (Score:1)
I know this is gonna get me -1 flamebait, but at least I'm honest:
{{{
$ uname -rsm
FreeBSD 4.0-RELEASE i386
}}}
Hmmm, on retrospect, the Linux mags are boring too, and the Windoze ones are even worse.
I recommend everyone to pop over to MP3.com and download Three Dead Trolls in a Baggie's "Every OS Sucks", can you tell I listened to it this morning?
YAWIAR.
Re: (Score:2, Interesting)
Re:Upgrading once a week? Is he serious? (Score:3, Informative)
However, it's so easy to do, I could see people doing it.
Re:Upgrading once a week? Is he serious? (Score:1)
The only thing that stops me doing a build world more often than once a month is that mergemaster takes a little concentration.
Re:Upgrading once a week? Is he serious? (Score:3, Insightful)
>out. He loves FreeBSD and his systems are
>"upgraded once a week (all software)". Is this
>normal pratice? I still have SuSE 6.3 systems
>running.
"Normal practice" varies depending on who you're talking to.
On the networks I administrate, I have a strict policy of "no unjustified upgrades", which usually translates to applying only security patches and relevent bug fixes. It might include new versions of software if, and only if, we're rolling out an enhancement to our services that necessitates it.
Part of the reason for being so restrictive is because we do QA and testing after every upgrade, so all upgrades have an associated cost in admin time. It may seem overly paranoid, but we've caught a lot of subtle issues that would have otherwise effected service to our customers.
Matt
Re:Upgrading once a week? Is he serious? (Score:1)
Yes, effecting service to your customers would be a disaster... You can do better without them ;)
Re:Upgrading once a week? Is he serious? (Score:2)
They pay us to administer their servers. I think we (administrators) do a better job if we keep the server stable and up than we would if we were just their lackeys.
Re:Upgrading once a week? Is he serious? (Score:1)
Re:Upgrading once a week? Is he serious? (Score:2)
It seems to be normal practice on Debian, probably because it's the best way to pick up the security patches.
apt-get update
apt-get upgrade
Re:Upgrading once a week? Is he serious? (Score:1)
Re:Upgrading once a week? Is he serious? (Score:2)
It is for me. Remember though, this is an upgrade to installed ports, not to the whole system. Ports includes everything above the kernel and userland. In Linux terms, it would be everything that isn't installed during a minimal bare-bones install.
Approx once a week I cvsup the ports tree, check for updates to my installed packages, and generally upgrade everything. For this week, it turns out that I can update cups-base, gettext, kdebase, mozilla, netpbm and qt.
Re:Upgrading once a week? Is he serious? (Score:1)
Re:Upgrading once a week? Is he serious? (Score:2, Informative)
*default tag=RELENG_4_6
when you run "cvsup
Most productions systems are safe to update once a week that way. You will eventually need to do a real update.
Re:Upgrading once a week? Is he serious? (Score:1)
Personally I try to keep my entire system upgraded to -STABLE (rather than security-patches-only for -RELEASE or the bleeding edge of -CURRENT), and I manage to download all of the neccesary patches over a dialup modem. :-) Because I have a dialup modem I have to do it frequently though. I've never had any trouble from "cvsuping" yet, and it's so fast that like I said I do it over a 56K connection.
Re:Why BSD isn't spreading (Score:1)
My god I call someone a weenie(which I don't consider a slam), and all of a sudden I am a arrogant 31331ist.
Little touchy eh?
Funny thing is I have no problems with Linux, FreeBSD justs seems to be a better fit for me(especially with my older computers(486's and 586's).
And who modded me as a troll?
Re:Why BSD isn't spreading (Score:1)
True! This hurts more then people think.
Agreed. But there doesn't seem to be any chance to have it change, or maybe an alternative logo being commonly used beside the'devil'.
If there was, the *BSDs would in fact get more installations, even though it may seem hard to believe at first that something like a logo might influence peoples decisions - but it does, sometimes.
Re:Why BSD isn't spreading (Score:2, Insightful)
I've always thought of this as a good thing. The core team makes decisions about the direction of the OS and I've always been happy to accept them and just get on with it. Whereas the last time I installed Linux I got side-tracked with a discussion on the relative merits of the umpteen filesystems Linux supports.
2) BSD users are to the Unix world like how Mac users are towards Window users "Use my superior OS you inferior idiot"
Amusingly I've always found it's Linux are most rabid about OS (and distro) superiority. So this must be a matter of perspective.3) They're obsessed with the opposition, they mention Linux, constantly
I'm not aware that I'm constantly talking about Linux. Yes I will refer to Linux when I describe BSD to someone who doesn't know what unix is. But Linux is seen as "the" free unix not "a" free unix, so one has to make the distinction as people think you're talking about "BSD Linux". Anyhow, what's wrong with talking about Linux? Linux is not as conservative as BSD. So Linux heads out in different direction on a whim. The Linux crowd will learn stuff which the BSD crowd can look at, evaluate, and (if it's worthwhile) mimic. Should the Linux crowd feel the need to not talk about BSD that they are missing out on a choice opportinity to pick up some free R&D.4) The logo is aweful and unsuitable. "Oh boss, I'm just going to install this software with a devil on it.."
The lil' beastie is not awful, he's cute. And classifying the OS based on the mascot? I could say Linux is unsuitable because the mascot is of a bird that can't even fly. But I'd be barking mad if I ever expected somone to believe me.
5) Linux isn't as bad as they try to say it is. If you want quality, get a quality distribution like Slackware and not a hashed together commercial distro.
You see. In a discussion on BSD you're talking distro superiority. Using BSD over Linux is exactly the same sort of decision as using Slackware over RedHat. It Unix, it's free, who cares?Re:offtopic about your response to point 3 (Score:4, Informative)
>Unix clone. FreeBSD is based on Berkeley Unix, and
>is thus, a direct decendant of the original Unix
>source code, not a rewrite. Not that it matters
>much.
It doesn't matter, and it's not really accurate. FreeBSD is based on the 4.4-lite codebase, which is the version that removed the last vestiges of copyrighted USL (Unix Systems Lab) code from the Net/2 codebase released by Berkeley's CSRG (Computer Systems Research Group) as part of a settlement agreement in the lawsuit USL pressed against the BSDI and UCB. So yes, FreeBSD *is* a rewrite.
And even that is somewhat irrelevent, since if you want to be pedantic about the term, UNIX is now a specification and operating systems which are certified to conform to that specification. None of the free Unixes have gone through the certification process, and thus are all "unix-like" and not UNIX.
Matt
(And just as one side note, even if none of the above was true, saying "FreeBSD is THE free Unix" doesn't make sense, since OpenBSD and NetBSD are also derived from the 386BSD codebase, and would therefore qualify under your definition.)
Re:offtopic about your response to point 3 (Score:2)
>grep "UNIX System Lab" *
[snip]
>You were saying...?
And what percentage of the codebase is that? One percent? Even before 4.4lite, it's reported that 90-95% percent of the codebase was rewritten.
Let's say way back when I owned a Packard Bell. Some cool game comes out, so I get a new video card. Then I start running out of space, so I throw in a new hard drive. And then the phone company screws up and doubles voltage, frying my modem, so I replace that. And then I decide I want something faster, so I throw in a new motherboard, processor and memory. Then I want a DVD drive, but there's no room in the case, so I put move the whole thing to a new case.
Am I still running a Packard Bell because I happen to have kept the mouse and sound card from that machine?
If we're going to accept that logic, is Windows XP a BSD since it has Berkeley code in it?
Matt
Re:offtopic about your response to point 3 (Score:1)
It is accurate enough. If memory serves me right, only six files were removed from the codebase as part of a lawsuit settlement.
Re:offtopic about your response to point 3 (Score:2)
>only six files were removed from the codebase as
>part of a lawsuit settlement.
And before that, 90-95% of the code base was rewritten. Which is why I said "the last" of the contested code.
Matt
Re:Why BSD isn't spreading (Score:2)
I know alot of *BSD users use Gentoo for java as well as testing their BSD apps on the linux platform. It seems to me all the good quality distro's are the hardest to use if you have no unix experience. I agree that RedHat and Suse are crap and buggy.
There seems to be a line between ease of use and quality. The only problem is you need to know unix to configure your desktop and highly customize your system under FreeBSD, Gentoo and Slackware. However what I have in return is a highly customized and non buggy system.
I was close to ditching the linux boat and head down to BSD and Windows land but I am glad I finally found a good quality linux distro.
Re:Why BSD isn't spreading (Score:1)
Seriously, BSD doesn't need to be jealous of Linux, we've got Linux binary compatibility mode.
I use both myself (and Cygwin on my one box), but I'd say FreeBSD is my fav. The big thing for me is the install program. I absolutely hate those Bloatware ridden install programs that are becoming de reguleur in the Linux world: I shouldn't need 64 MB of RAM to take an OS off a CD and put it on a hard drive.
Re:Why BSD isn't spreading (Score:1)
I definatly share your sentiments there. I've tried to salvage a few 486's at work thinking, yeah, I'll put linux on it and do something with it (as web server or whatever). Too bad for me, pretty much every distro blows up bacause there is insufficent ram (usually around 32 megs, which is a LOT).
Re:Why BSD isn't spreading (Score:1)
NetBSD, baby. My first home *nix box was a Quadra 700 running NetBSD - I used it for mail, web serving, and playing around with Samba, all on a 230 meg drive and 40 megs of RAM.
I'm playing around with FreeBSD right now, which is a little bloatier, but Net and OpenBSD are like quick little lizards next to the lumbering elephantine bulk of the average linux distro.
--saint
Re:Why BSD isn't spreading (Score:1)
Re:Why BSD isn't spreading (Score:1)
See, I'm in just the opposite situation. My first *nix was NetBSD, and I've been running it and Open on my network for a few years now. I just installed FreeBSD for the first time last week - I picked up a dual Celeron mainboard, and it's the only one of the BSDs with even rudimentary SMP support.
I have nothing against Linux, but there are quite a few things about it that rub me the wrong way.
I think the development differences between BSD and Linux really show. I've tried a lot of different linux distros on a lot of different architectures, and they always feel unpolished and slapped-together. BSDs always feel like a coherent whole.
I actually tried Red Hat and Mandrake on that dual Celeron before I decided on FreeBSD. The linux installs lasted about a day apiece before I got fed up with the OS.
--saint
Re:Why BSD isn't spreading (Score:2)
How to get just throw a patch at the Linux kernel and get Linus to accept it: You don't. You must first prove your qualifications, earn your stripes, keep current on the kernel devel lists, start submitting worthwhile patches, and even then Linus still might reject them.
2) BSD users are to the Unix world like how Mac users are towards Window users "Use my superior OS you inferior idiot"
Throw a NetBSD, OpenBSD and FreeBSD user into a locked closet. Three hours later they may have a few bruises, but they will still be alive. Now throw a Mandrake, Gentoo and Debian user into the same closet. Three hours later two of them will be dead with a severly injured survivor.
3) They're obsessed with the opposition, they mention Linux, constantly
Linux users are also obsessed with the opposition, they mention Windows constantly. It wouldn't surprise me if they spontaneously decided to rename their OS to GNOTWindows. Oh, and all those "*BSD is Dying" posts are evidence of an unhealthy obsession by certain Linux users with reference to competing systems.
4) The logo is aweful and unsuitable. "Oh boss, I'm just going to install this software with a devil on it.."
Oh puh-leaze! Ooh ooh can't install KDE since it has a dragon mascot, and everyone knows the dragon is a metaphor for Satan! Ooh ooh can't install GNOME because it has a gnome's foot as a mascot and everyone knows that gnomes are fairies and fairies are associated with pagan religions!
5) Linux isn't as bad as they try to say it is. If you want quality, get a quality distribution like Slackware and not a hashed together commercial distro.
Certainly Linux is not as bad as "they" say it is. (whoever "they" is referring to). In general, Linux distributions are high quality systems. And Slackware is one of the highest qualities. But there is no law that says only one unix-like system can have quality.
Re:Is BSD dead? (Score:2)
So let's see... OpenBSD and OpenSSH have had a few exploits over the past few weeks. Linux et al have had... um, can somebody count them up for me? I don't have enough free time to do so.
3+ hours and counting... (Score:1)
And still no *BSD Is Dying post. He must have slept in or something. Or maybe they shut off net access at the asylum.
excellent... (Score:2)
While it may be an advertisement, it's a free service and the entire e-zine is based on OSS ... so ... everyone who keeps with the "this is stupid post articles from them" and "BSD is dead" ... chill
First Post!! (Score:1)