| WIKI | FAQ | Tech FAQ | |
 http://csua.com/feed/ | |
| ||||||
| 11/23 |
| 2002/4/17-18 [Computer/SW/OS/FreeBSD] UID:24466 Activity:high |
4/16 OpenBSD 3.1 is available for preorder:
http://www.openbsd.org/31.html
\_ I'm a linux person who'd like to try out BSD. What are the main
differences between FreeBSD and OpenBSD?
\_ OpenBSD: they put more effort into security and code auditing.
Most of these fixes will make it into the other *BSD's but not
first. FreeBSD: SMP, larger number of packages and a bit
friendlier to admin. Summary: OpenBSD for NAT/firewall, etc and
FreeBSD for servers and workstations. NetBSD for whacky hardware
that doesn't run a real unix. The rest is politics.
\_ Thank you! Finally, an useful answer on the motd...
\_ No problem. Also, my answers are x86 specific. Unlike
some of the others who reply below I have not tried out
the *BSD's on non-x86 hardware. I don't have a PPC or 68k
and I run solaris on my sun boxes.
\_ freebsd is NOT for the workstation. rdesktop doesn't run
vmware doesn't run, their jdk works occasionally.
ask ilyas about ports probs; ask the vaunted csua root
about why scotch is forced to run uniproc. (it's a dual
machine) freebsd claims to
work, but I can write "I fucked yer mom" on a webpage,
regardless of the real truth.
\_ Also OpenBSD is much easier to install than FreeBSD
and runs on a wider range of hardware.
\_ well whatever, only insane geeks own hardware
that freebsd or linux doesn't run on. woo
i can run openbsd on my refrigerator.
\_ FreeBSD doesn't run on Sparc, UltraSparc,
M68K or PowerPC. Contrary to your assertion
many mainstream people have M68K and PowerPC
systems. Sparc and UltraSparc may be rarer,
but not by much for the motd crowd.
While Linux *claims* to run on these platforms,
its performance, compatibility and stability
are quite poor. OpenBSD runs well on Sparc,
M68K and PowerPC. UltraSparc is a little behind,
but for a port started less a year ago it is
very good.
\_ linux runs well on an ultra1. -- writing this from
an ultra1. (p.s. linux doesn't support sparc32
which is why i run openbsd on my sparc32 machines)
\_ put on your asbestos underwear.
\_ I never take 'em off. However, there doesn't seem to be
much flame. Shame, really, because I'm freezing right now...
\_ http://www.cafepress.com/cp/store/store.aspx?storeid=feedle
\_ Okay, fine. Add NetBSD as well.
\_ I hate your pathetic boring life, geek.
\_ Yeah, I'm bored of my life as well, but yermom only
want to do it doggy style.
\_ oh man i'm going to cry now from your rapier wit.
\_ Who's Theo?
\_ Where did Theo come from?
\_ The URL above. The products say:
"Because Theo Is An Asshole"
\_ Well he is an asshole but makes a good unix.
\_ Who is Theo?
\_ notorious ass who started and is main
maintainer of OpenBSD.
\_ He's an asshole but makes a good unix.
\_ No, making good unix requires
working well with others.
\_ Thus, Theo = asshole implies
OpenBSD != good unix. Would you
care to try again?
\_ He works well with others,
provided that they are not
complete morons. The netbsd
fiasco is documented here,
read it for yourself and
you will see that theo's
a**hole reputation is not
deserved:
http://zeus.theos.com/deraadt/coremail.html
\_ people who censor their own posts with
asterisks are assholes.
\_ Fine. They are all wankers.
\_ They're tossers. Wanker. |
| 11/23 |
|
| www.openbsd.org/31.html Secure file transfers are encouraged using the greatly enhanced SFTP subsystem which comes both with an SFTP server and client. A larger part of the website is now available in several languages. Taking advantage of this, the system can have its root partition directly mounted from an auto-detected raid partition. How to install Following this are the instructions which you would have on a piece of paper if you had purchased a CDROM set instead of doing an alternate form of install. The instructions for doing an ftp (or other style of) install are very similar; OpenBSD/i386: Play with your BIOS options to enable booting from a CD. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To make the boot floppy under a Unix OS, use the 19 dd utility. The following is an example usage of 20 dd, where the device could be "floppy", "rfd0c", or "rfd0a". Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. OpenBSD/macppc: Put the CD2 in your CDROM drive and poweron your machine while holding down the C key until the display turns on and shows OpenBSD/macppc boot. OpenBSD/mac68k: Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Run Mkfs to create your filesystems on the A/UX partitions you just made. Finally, you will be ready to configure the BSD/Mac68k Booter with the location of your kernel and boot the system. OpenBSD/mvme68k: You can create a bootable installation tape or boot over the network. The network boot requires a MVME68K BUG version that supports the NIOT and NBO debugger commands. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM. OpenBSD/sparc64: Put the CD3 in your CDROM drive and type boot cdrom. Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. This file contains everything you need except for the kernel sources, which are in a separate archive. This file contains all the kernel sources you need to rebuild kernels. Using these files results in a much faster initial CVS update than you could expect from a fresh checkout of the full OpenBSD source tree. Rather, it is a set of notes meant to kickstart the user on the OpenBSD ports system. However, it is growing very fast and getting more stable. Almost all ports provided with this release should build without problems on most architectures (over 1500 packages build on i386, for instance). The ports/ directory represents a CVS (see the manpage for 25 cvs if you aren't familiar with CVS) checkout of our ports. As with our complete source tree, our ports tree is available via anoncvs. So, in order to keep current with it, you must make the ports/ tree available on a read-write medium and update the tree with a command like: # cd portsdir /; Note that most ports are available as packages through ftp. |
| www.cafepress.com/cp/store/store.aspx?storeid=feedle -> www.cafeshops.com/cp/store.aspx?s=feedle The page you are looking for may have been moved, or deleted. Maybe you'd like to search for the shop you're looking for? US Phone: 1-877-809-1659 Monday-Friday, 8am-5pm PST Or contact 12 Customer Service via email. |
| zeus.theos.com/deraadt/coremail.html XDate: Fri, 21 Apr 1995 01:14:56 -0600 XFrom: Theo de Raadt X Xif that works, please don't commit that; XDate: Fri, 21 Apr 1995 01:14:56 -0600 XFrom: Theo de Raadt X Xif that works, please don't commit that; And once those are X> given, I might as well be given "cvs commit" access. X> X> I am really surprised that you would offer so little after 3 months of X> talking about and around this. X> X XThe only thing _I_ can offer at this point is a private arrangement for the Xsake of finding a practical way of integrating the changes you guys want to Xsee in the -current NetBSD/sparc port. X XPlease consider directing your proposal for cvs access to core@netbsd'; I'm rather annoyed that these things are now being discussed in public X on port-sparc. XSubject: CVS access XDate: Fri, 21 Apr 1995 07:15:19 -0600 XFrom: Theo de Raadt X XI would like to have CVS access once again. I would like to return to Xthe development environment that I once had. Because of the difficulty of maintaining changes Xin multiple places in the tree, I have nearly ceased making any Ximprovements to parts outside of arch/sparc. That will also start to Xchange if I get access once again. XSubject: CVS access XDate: Fri, 21 Apr 1995 07:15:19 -0600 XFrom: Theo de Raadt X XI would like to have CVS access once again. I would like to return to Xthe development environment that I once had. Because of the difficulty of maintaining changes Xin multiple places in the tree, I have nearly ceased making any Ximprovements to parts outside of arch/sparc. That will also start to Xchange if I get access once again. XX-Notice: Duplication and redistribution prohibited without consent of X the author. I would like to return to X> the development environment that I once had. Because of the difficulty of maintaining changes X> in multiple places in the tree, I have nearly ceased making any X> improvements to parts outside of arch/sparc. That will also start to X> change if I get access once again. X XI have no great objection to you having access to the CVS tree. XWhether or not you should be able to freely hack the sparc port is Xreally up to Paul, as it's his "ball" now. Do you think that will be difficult X for you or us to do? That's X what got us to this point to begin with, really. ORG X XIf anyone has a spare/junk Sun vme si scsi card lying around, I would Xlike to have one. I'm a ways along the task of writing an Xinterrupt-driven dma'ing disconnect/reconnect 5380 driver for the Xfollowing scsi's: obio si (sun3-only), vme si (any sun4/sun3), obio sw X(4/100-only). XDate: Sun, 23 Apr 1995 22:41:27 -0600 XFrom: Theo de Raadt X XI heard. X Xsecond: FYI: I resigned from the NetBSD project last monday, effective X last friday so that I could pursue other interests. XDate: Wed, 26 Apr 1995 13:09:54 -0600 XFrom: Theo de Raadt X Xthere hasn't been any progress. EDU XPrecedence: special-delivery XX-Copyright: Copyright 1995, Christopher G. XX-Notice: Duplication and redistribution prohibited without consent of X the author. X XI'm sorry if you didn't like the tone of it, but frankly i wasn't Xparticularly pleased with the tone of _your_ letter, myself. X XThe former _has_ to be decided by 'core', though they seem to be Xrelying on me to do most of the talking (as annoying as that is, to Xme). The latter _has_ to be decided by Paul, as the SPARC port is Xcurrently _his_ baby, and there has been little evidence presented to Xindicate that it someone should be given "complete write access" Xwithout his consent. X XThat being said: X XAs i said before, I have no objection to letting you have an account Xwith CVS tree, _BUT_ in order for this to happen i need to know that Xour relationship is going to be a positive one. Unfortunately, while X'code generated' is important, it _isn't_ the entirety of the matter. X XTo my mind, a "positive working relationship" implies two things in Xaddition to "code": X we (you, and 'core') can communicate well with each other, X that you aren't going to stomp on anybody's toes. X X XI don't want any admissions, or anything like that. X XI _do_ however _need_ to know that you're going to do your best to Xwork with us and to work with the other people involved (in various Xcapacities) with the project. X XOnce i know that, _I_ can strongly advocate that you be given an Xaccount. Since no one else seems to have much feeling about the Xmatter at all, i think that would be enough. XDate: Wed, 26 Apr 1995 16:06:18 -0600 XFrom: Theo de Raadt X Xso what shall i write to core to expedite the process? EDU XPrecedence: special-delivery XX-Copyright: Copyright 1995, Christopher G. XX-Notice: Duplication and redistribution prohibited without consent of X the author. X XI'm sorry if you didn't like the tone of it, but frankly i wasn't Xparticularly pleased with the tone of _your_ letter, myself. X XThe former _has_ to be decided by 'core', though they seem to be Xrelying on me to do most of the talking (as annoying as that is, to Xme). The latter _has_ to be decided by Paul, as the SPARC port is Xcurrently _his_ baby, and there has been little evidence presented to Xindicate that it someone should be given "complete write access" Xwithout his consent. X XThat being said: X XAs i said before, I have no objection to letting you have an account Xwith CVS tree, _BUT_ in order for this to happen i need to know that Xour relationship is going to be a positive one. Unfortunately, while X'code generated' is important, it _isn't_ the entirety of the matter. X XTo my mind, a "positive working relationship" implies two things in Xaddition to "code": X we (you, and 'core') can communicate well with each other, X that you aren't going to stomp on anybody's toes. X X XI don't want any admissions, or anything like that. X XI _do_ however _need_ to know that you're going to do your best to Xwork with us and to work with the other people involved (in various Xcapacities) with the project. X XOnce i know that, _I_ can strongly advocate that you be given an Xaccount. Since no one else seems to have much feeling about the Xmatter at all, i think that would be enough. XDate: Wed, 26 Apr 1995 16:28:09 -0600 XFrom: Theo de Raadt X X> I'm sorry if you didn't like the tone of it, but frankly i wasn't X> particularly pleased with the tone of _your_ letter, myself. X X> The latter _has_ to be decided by Paul, as the SPARC port is X> currently _his_ baby, and there has been little evidence presented to X> indicate that it someone should be given "complete write access" X> without his consent. X X> To my mind, a "positive working relationship" implies two things in X> addition to "code": X> we (you, and 'core') can communicate well with each other, X Xyou and i have communicated; X X> I _do_ however _need_ to know that you're going to do your best to X> work with us and to work with the other people involved (in various X> capacities) with the project. X X> Once i know that, _I_ can strongly advocate that you be given an X> account. Since no one else seems to have much feeling about the X> matter at all, i think that would be enough. XDate: Wed, 26 Apr 1995 16:29:56 -0600 XFrom: Theo de Raadt X Xif you don't go back and re-read it, that's actually better. XDate: Wed, 26 Apr 1995 18:11:13 -0600 XFrom: Theo de Raadt X Xyour last message to me was mangled. EDU XPrecedence: special-delivery XX-Copyright: Copyright 1995, Christopher G. XX-Notice: Duplication and redistribution prohibited without consent of X the author. X X> it really sounded X> like it was treating me as a special case who has previously been a X> real asshole. X XI'm going to disregard the "who has previously been a real asshole" Xclause, because it's pointless. The fact is, we _did_ think that we had to do that, and i Xthink we had reasonable cause to think so. The list wasn't intended to be taken literally, or Xeven completely seriously. X X X> > The latter _has_ to be decided by Paul, as the SPARC port is X> > currently _his_ baby, and there has been little evidence presented to X> > indicate that it someone should be given "complete write access" X> > without his consent. X Xyes, and if he doesn't say anything within a "reasonable... |