ClosedBSD 1.0b Released
An unnamed reader submits: "Joshua Bergeron released ClosedBSD 1.0B today. ClosedBSD is a firewall which boots off of a single floppy diskette, and requires no hard drive. It is based off of the FreeBSD kernel, and uses ipfw as it's native ruleset manager. Best of all: it is freely available under the BSD License. ClosedBSD also features an advanced curses based configuration utility for designing and managing firewall rulesets: Screenshots available.
*BSD is DYING, people!
Fist Sport!
"Why did they cancel my favorite Sci-Fi show? I downloaded ALL the episodes!"
Second Post.
Linux Gay Conspiracy v2.0 cumming R.S.N.
"Why did they cancel my favorite Sci-Fi show? I downloaded ALL the episodes!"
Can't even be bothered putting anything filthy and / or deeply offensive to minorities here.
"Why did they cancel my favorite Sci-Fi show? I downloaded ALL the episodes!"
Choice is nice, but do we really need n+1 floppy-based firewalls ? It seems like another beta of $nat_fw_kit comes out every other day, often only differentiated by the user interface and nothing else. Seems to me like these guys should pool together and try to merge the best of everyone's toolset.
-Billco, Fnarg.com
They all taste of shit!
"Why did they cancel my favorite Sci-Fi show? I downloaded ALL the episodes!"
DeadBSD ?
It actually sounds cool...
I've never used/heard of IPFW. How does it compare to IPTables. Do you get the same level of granularity?
*BSD is dying
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *SD accounts for lss than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are quite dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
*BSD is dying
> man picobsd
PICOBSD(8) FreeBSD System Manager's Manual PICOBSD(8)
NAME
picobsd - floppy disk based FreeBSD system
SYNOPSIS
picobsd [options] [floppy-type [site-name]]
DESCRIPTION
picobsd is a script which can be used to produce a minimal implementation
of FreeBSD (historically called PicoBSD) which typically fits on one
floppy disk, or can be downloaded as a single image file from some media
such as CDROM, flash memory, or through etherboot.
blah_foo_and_so_forth and_a_bit_more following_on_fr om_where_we_were_at
Torvalds: The original plan was to try to aim for a nine-month productization
cycle, and part of the reason for that was that I expected the changes for
2.4.x to be much smaller than they ended up being. My original main goal was
to clean up the SMP scalability to four CPUs, and it kind of grew into a major
file-system redesign. That said, everybody knew the nine-month goal was
unrealistic. But it was kind of "if we don't have anything to shoot for, we
certainly won't hit it." I was hoping we could get it down to a year or so.
Four colour screen shots saved as JPEG. That's what GIF/PNG was made for.
The yellow and the light-grey bleed together as the night rages in. The King of the World will not sleep easy tonight.
--Giving to trolls for the benefit of us all
shipng secure sftware on an flayky eror prown meediem iz VARY Gay. Plz konk Urself on da hed a fyu doz tymz.
:)
Thnx!
Why, in heavens name, was this called ClosedBSD, rather than something much more clear and obvious, like, say, "tinyBSD", since it is tiny, as in like PicoBSD, rather than closed, as in ?license? :). Even "BRP" (BSD Router Project) would have been better and less confusing!
I'm sorry but it is months ago since I've used a floppy. And that was to test out PicoBSD. I would be much more happy to see a bootable cd-rom based thingie, which would allow me to put some bigger stuff on it, like sshd, tcpdump, trafshow, ngrep et al. Despite that it is only a firewall, I need these tools to debug stuff.
bash$
PicoBSD has been a part of FreeBSD for a long time....
Doesn't anyone do anything original anymore?
What about both?
A CDROM for the big stuff and a floppy for the config stuff. You can then flip the write protect tab when you get the setup the way you want.
A password could even be set on the floppy which is encrypted with the config file to keep everyone else from looking at the config file on the disk and devising breaks.
That way someone couldn't drop by to copy the disk, go home and analyze your setup and devise breaks on a private setup until it works.
I would like author to submit this project to FreeBSD, in standard FreeBSD distribution, there isn't a TUI utility to setup firwall, I would like to see it in FreeBSD system.
*BSD is so Gay.
look at ISO Linux.
Dan
And secondly, what is this disto do extra what I can't duplicate using PicoBSD? Only a front-end menu?
On their site on the contributions page this guy points to the FreeBSD project and the picoBSD project. I'm glad to see this, give credit where credit is deserved. Nice work on his part, and send some of the money back to the FreeBSD guys so they can keep up the great work they're doing. Props guys...
ahh, the egg in the basket..
from an interview he did with hemos (http://slashdot.org/article.pl?sid=00/12/11/14552 10)
"I must say that I am not a fan of these floppy-based routers. Essentially, you are taking one of the most unreliable pieces of storage known to man, and trying to build security infrastructure on it. That's madness. Just buy a small disk. Perhaps somethings based on a CD plus some other (non-floppy) persistant storage might be sane. But please. Not floppies. Are you mad?
it has merit.
I am all for it!
Here's the link. Looks fairly interesting for comparison to ClosedBSD1.0 I imagine that ClosedBSD1.0 is going to have nicer "interface" as it is specialized. For those of you who are antsy about floppies, you might have to pay for that predilection in more config time.
http://bsdtoday.com/2002/March/Features646.html
hey Tatum you really play some wholesome piano.. howz about some trolling music for the People :O)
--you have been trolled--