From: Graham Toal [mailto:[EMAIL PROTECTED] > > You've got a couple of weird things and errors on your page: > > - You say OpenBSD doesn't support multiple consoles: ctrl+alt+f2 > > Yup! Thanks. Linux uses ALT-Fkey which I tried. Didn't try > adding CTRL. :-/ Assumed it didn't have it, and too busy getting > everything else working to go look for it. I've now documented it. > > > - Using the 3.7 ports tree on 3.6 is not recommended. > > The only install disk I have is 3.6. I assume that by doing an > install over the net, I get the 3.7 system - but some trace of 3.6 > seems to have remained because some funny things happened later...
You can't mix versions. If you installed a 3.6 ports tree on 3.7, you made a mistake. Further, you didn't read the documentation which clearly states how to get the proper ports tree. > > - tarring and untarring fake-i386 to install a port is just weird. > > make install should already do that > > It didn't, it gave an error and did a fake install. It appears to > be related to the 3.6/2.7 problem. Other packages installed cleanly. Probably because of a mismatch between the version of the ports tree and the operating system. > > > - Why not install screen from a package like jove? > > I'd rather forget about packages and use ports for everything, but > I thought it was worth mentioning for newbies like myself who spent > hours looking for apt-get and yum and emerge etc etc - i.e coming from > a linux environment... Again, a failure to read the docs. Read the FAQ where it says "OpenBSD is not Linux." Newbie or not - Linux or not - the concepts are the same. What works on one system will not work on another. 'emerge' is a Portage / Gentoo Linux thing. Won't work on other systems unless they are Gentoo based or have Portage ported. If that is true between Linux distros, then it is certainly true between a Linux distro and a BSD flavor. > > > - sh /etc/netstart bridge0 will fire up your new bridge > without rebooting. > > Thanks, didn't know that. Actually I just found out that > "ifconfig bridge0 > create" was the crucial missing step I didn't know. > > > That's all I can think of at the moment. > > Apreciate it, thanks. > > G > PS I'm marking all these comments up in he wiki as I reply. Two more > emails pending from folks who sent similar corrections... Look, everyone can appreciate your effort. It really is good and no one wants to discourage contributions. Really. But the one thing worse than no resources is bad (inaccurate) resources. This is what Linux has plenty of. Lots of poorly done "documentation" from newbies who have a faint idea of what they're talking about, and so produce a document that has so little of a useful lifetime but remains out there indefinately, leading others down the wrong path. (TLDP?) OpenBSD already has good documentation. Most of it is in the manual pages. The majority of the rest is in the FAQs. It is current. It is maintained. And it is general enough that you can glean what you need from it without having to resort to a step-by-step HOWTO if you'll just look at the right information. If I wanted to set up a transparent spamd proxy, I'd read some man pages for spamd things, bridge things, and pf things. A small amount of putting 2 and 2 together and you see how it fits together. Putting out poorly done, uninformed HOWTOs like this do more harm than good. We've already seen it on openbsdsupport.org - I could reference several threads in the archive that have been a result of someone following outdated, vague and uninformed HOWTOs from that site. In fact, stuff that I've contributed falls in this category. I've got docs up there that link to a server that is no longer up, and reference older versions of OpenBSD and do stuff that is no longer supported or else was the wrong way to do it anyway. And the longer its there the worse it will get. I'm certainly not as good of a documentation writer as I must have thought I was then. So while in some ways its a good community resource, in other ways it has a negative effect. There's a reason Nick is handling the FAQ. ;) DS
