December 2003 - cypherpunks-legacy

Perl 5.00401, gcc 2.7.2.3 ..
by Andreas Brusinsky 17 Dec '03

17 Dec '03

It was told in the mailinglists that with the integration of the gnu utillities into the source tree it is easy to keep up with changes of their utillities. So what is the reason to stay on little elder versions of perl and gcc? Shouldn't gcc 2.7.2.3 and perl 5.00401 be within the source tree? Why are they not? Does the source tree really depend on the 'old' perl? I got somehow the impression that gcc is a special adapted version so I could understand that this is not integrated but perl? Or am I utterly wrong because perl is a kind of compiler and gcc is a kind of compiler so they dont need to be chaged becaus they work and may be more fixed than real gcc/perl and utillities that demand perl5.00401 can just be twiddled to use OpenBSD/perl .. Thanks for comments. Bye Brusi by E-Mail: ab2(a)inf.tu-dresden.de Tel.-priv: 0351-8499347 (Germany/Dresden) \____

1 0

Checklist, expanded
by Marshall Midden 17 Dec '03

17 Dec '03

NOTE: if upgrading or restoring files, it appears that some group numbers have been changed. ----------------------------------------------------------------------------- New installation checklist, after install and multi-user boot. (Instructions for correcting not given.) 1) Login on console as "root". 2) Check the system date. Type "date". If necessary, set the system date, and/or change the symbolic link to get the correct Time Zone. 3) Put a password on root. Run "passwd". 4) Check hostname. Type "hostname". (man "hostname" if need to change, and you also need to edit /etc/myname.) 5) Verify network interfaces configured correctly. a) "ifconfig -a". Correct by editing /etc/hostname.{INTERFACE} and via "ifconfig" if you do not with to reboot. Loopback interface will look something like: lo0: flags=8009<UP,LOOPBACK,MULTICAST> inet 127.0.0.1 netmask 0xff000000 An ethernet interface something like: le0: flags=9863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,LINK0,MULTICAST> inet 192.168.4.52 netmask 0xffffff00 broadcast 192.168.4.255 [Will someone else fill in the ppp and slip interfaces.] b) You may wish to turn off multicast routing in /etc/netstart by commenting out (place a # sign at start of line) the line: # route add -net 224.0.0.0 -interface $hostname c) Check for routing. ("netstat -r -n") It will look something like: Routing tables Internet: Destination Gateway Flags Refs Use Mtu Interface default 192.168.4.254 UGS 0 11098028 - le0 127 127.0.0.1 UGRS 0 0 - lo0 127.0.0.1 127.0.0.1 UH 3 24 - lo0 192.168.4 link#1 UC 0 0 - le0 192.168.4.52 8:0:20:73:b8:4a UHL 1 6707 - le0 192.168.4.254 0:60:3e:99:67:ea UHL 1 0 - le0 Fix via editing /etc/mygate, and using "route delete" and "route add" if you do not wish to reboot. d) If using the Bind Name Server (DNS), check /etc/resolv.conf. It might look something like: domain nts.umn.edu nameserver 128.101.101.101 nameserver 134.84.84.84 search nts.umn.edu. umn.edu. If using a caching name server add the line "nameserver 127.0.0.1" first. (Of course, you need to change "named_flags" in /etc/rc.conf and add the named.boot file in the appropriate place. Same holds true if this is the name server for you domain. Also make sure "named" is running. [Otherwise there are long waits while timeouts happen.]) e) If using "NIS" (old yellow pages), check "domainname" and edit /etc/defaultdomain to correct. [Will someone else fill in more here. I refuse to use this package.] 6) Check disks correct. a) cat /etc/fstab b) df Edit "/etc/fstab" and "umount" and "mount" as necessary. (See man pages.) c) You may want to do NFS partitions later, but you may do them now. d) If you are using concatenated disks, edit /etc/ccd.conf and use "ccdconfig -U" and "ccdconfig -C" till you have it correct. ("umount" and "mount" and edit /etc/fstab as needed.) e) Go into the "amd" directory if using this package. [Will someone else fill in more here. I do not use this package.] 7) The system should be usable now, but you may with to do more customizing, adding of users, etc. Many sections may be skipped if you are not using that package (for example kerberos!). My suggestions are to go into /etc ("cd /etc") and: a) Edit motd to make lawyers comfortable and make sure that no mention of the word "Welcome" appears. (Some U.S. lawyers have stated that the word "Welcome" is an invitation to come on in.) b) Add users. There is a "adduser" script. You can use "vipw", and edit "/etc/group" if you desire. Make sure to put people in "/etc/group", under the "wheel" group if they need root access (non-kerberos). Something like: wheel:*:0:root,m4 c) Check for any local changes needed in /etc/rc.conf, /etc/netstart, /etc/rc.local, rc.securelevel.. Turning on something like the Network Time Protocol in /etc/rc.local and /etc/rc.securelevel requires: A) Making sure the package is installed. (see http://www.openbsd.org under "Ports: a Nice Way to Get Third-Party Software). B) Uncommenting the lines in rc.local (delete the # signs). if [ -f /usr/local/etc/httpd/httpd ]; then echo -n ' httpd'; /usr/local/etc/httpd/httpd fi C) Uncommenting the lines in rc.securelevel (delete the # signs). if [ -x /usr/local/sbin/xntpd ]; then /usr/local/sbin/tickadj -Aq echo -n ' xntpd'; /usr/local/sbin/xntpd fi d) Edit /etc/printcap and /etc/hosts.lpd to get printers set up. e) You might want to tighten up security by editing: fbtab Set security for X -- when you install X ... . inetd.conf Turn off extra stuff, add that which is really needed. f) Go into /etc/kerberosIV and configure kerberos. Remember to get a srvab. g) Edit /etc/aliases. Set postmaster, etc. Run newaliases after changes. h) If this is a bootp server, edit /etc/bootptab. You will have to turn it on in /etc/inetd.conf, or run "bootpd" in stand-a-lone mode. i) If this is an NFS server A) make sure /etc/rc.conf has "nfs_server=YES". B) Edit /etc/exports and get correct. It is probably easier to reboot than get the daemons running, manually, but you can get the order correct by looking at /etc/netstart. j) Edit /etc/rbootd.config if needed for remote booting (ethernet MAC address to IP tranlation). k) Look at and possibly edit the /etc/daily, /etc/weekly, and /etc/monthly scripts. Your site specific things should go in /etc/daily.local, /etc/weekly.local, and /etc/monthly.local. l) Look at the other files in /etc and edit as needed. (Do not edit files ending in ".db" -- like aliases.db, pwd.db, spwd.db, nor localtime, nor rmt, nor any directories.) 8) Check what is running via crontab "crontab -l". Do you need anything else? Do you wish to change things? For example: 30 1 * * * /bin/sh /etc/daily 2>&1 > /var/log/daily.out 30 3 * * 6 /bin/sh /etc/weekly 2>&1 > /var/log/weekly.out 30 5 1 * * /bin/sh /etc/monthly 2>&1 > /var/log/monthly.out 9) After the first nights security run, change ownerships and permissions on things. Best bet is to have permissions as in the security list (the first of the two listed permissions, and the first group number of the two). Use "chmod" and "chgrp" as needed. 10) Install packages to make the system more useful. A) Install your own. Easiest way is to copy source and compile it. B) Copy vendor binaries and install them. You will need to install any shared libraries, etc. (hint: "man -k compat") C) Install any of a large number of Third-Party Software that is available in source form. (See http://www.openbsd.org under "Ports: a Nice Way to Get Third-Party Software). You may have "fun" installing due to various compiling errors. Don't get discouraged easily! Sometimes checking the mailing lists for past problems that people have encountered will result in a fix posted.

1 0

Discount Full-Service Travel
by globaladventures＠alluwant.com 17 Dec '03

17 Dec '03

Good Morning, We were given your name as someone who enjoys (or must) travel. Global Adventures Travel Service is a full service, wholesale and retail travel agency. Combining high-tech and high-touch to deliver an unparalleled level of customer service. We have divisions specializing in Domestic and International Leisure Tours, Cruises, Business, Corporate, Singles, Seniors, and Last Minute Adventures. Our prices are always low and service always high... For a few current .specials. (as of 10/06/97), please hit reply and put the word "SPECIALS." in the subject line and push send for an automated response. For a personal response, press reply, do not change subject, and just ask.... we will be glad to help! Thank You for your time... The Crew at Global Adventures Travel Service /////////////////////////////////////////////////////////////////////////////////////////// If you would like to be taken off our mailing list....please hit reply and type the word 'remove' in the subject field and you will be omitted from Global Adventures future mailings.... ///////////////////////////////////////////////////////////////////////////////////////////

1 0

Where are another cypherpunk
by Nobuki Nakatuji 17 Dec '03

17 Dec '03

Where are another cypherpunk mailinglist ? ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

2 1

Information Security Policies
by scannmann＠nevwest.com 17 Dec '03

17 Dec '03

Security Policies To Go! Don't re-invent the wheel. Get the most comprehensive source of information security policies available. Information Security Policies Made Easy (version 6) is a collection of 840 already-written policies in book and CD-ROM. ISPME is the fastest and most expedient way to write new and /or revise existing information security policies. Use your favorite word processing package and cut and paste from these ready-to-go policies, justification statements, and other supporting materials. Generate a complete policy statement in five minutes or less. It Includes extensive instructions which provide practical advice about the policy development process. Applicable to organizations throughout the world, the book/CD-ROM provides policies covering a broad range of topics including: Internet, intranets, firewalls, network security, contingency planning, computer viruses, electronic payment systems, web surfing activity monitoring, Java, macroviruses, data classification, push information distribution, software development, intellectual property rights, password management, and much more. The latest version also includes ten skeleton policies which are ready-to-go complete policy statements. These skeleton policies can be used as is or expand them with other policies from the book. ISPME provides everything needed to write standards and communicate them in a clear, concise manner. Check out our web site for further details -- www.baselinesoft.com or contact us via e-mail info(a)baselinesoft.com or call us today (800) 829-9955 (USA & Canada) (415) 332-7763. Here are what people are saying about ISPME: "It saved me thousands of hours and thousands of dollars." -- J. P., Capital Blue Cross "An excellent source for policies on new technologies. Great to have it on CD." -- B. S. F., CISSP, The Vanguard Group "Excellent reference, I would recommend this book to all policy writers." -- R. M., Atlantic Lottery Corporation. "Wood has hit a home run with this one!" -- B. A., Rekam Graphics

1 0

consensus on pgp? can we consolidate for action?
by Attila T. Hun 17 Dec '03

17 Dec '03

-----BEGIN PGP SIGNED MESSAGE----- two of the things I was trying to do in my rant "GET WITH IT" on the issues may not have been clear: 1. as Tim says, let's make sure the OpenPGP standard (which in itself I did not address) is for PGP by itself, none of the peripheral issues or means of implementing GAK/CAK/CMR or the rest of the faloderol. now, if PGP, under market pressure wishes to allow hooks for each of the sins from the necessary to the unpardonable GAK --that is a business decision. 2. as far as the proposed SNMP "enforcer" --that is also a business consideration. however, the more PGP is willing to listen to some of our voices of reason[1], the more likely PGP is going to be in the rather enviable position which at least permits companies to make a choice. [1] by and large, despite the polarity of the arguments, this issue with PGP has been one of our memorably sane and polite debates with so many threads I may need to establish a separate text retrievable database! and it involves one of our most emotional issues: privacy. the second point is critical to our interests as well as for PGP's stand in the industry as a whole. if the SNMP enforcer product is carefully designed, it can not only provide warnings for each level of security but even more importantly, it does not necessarily need to provide GAK functionally in the standard product: browsers use plugins --so why not security level plugins for the "Bad Daddy" SNMP enforcer? essentially, the SNMP is a network connected, ie- communication system, supervisor to one or more "clients" scattered anywhere in the network which recognizes Bad Daddy. some of the PGP control functions are basic, but the rest should go on plugin, each relating to a different level of sin, forgivable to abominable. likewise, the local PGP crypto engine should be built around plugins. in this manner, anyone concerned with privacy can easily check for the presence of the dirty little black boxes, or hopefully PGP will display a panel of "features" (if you can ever call invasion of absolute privacy that). plugins today are a nobrainer. personally, I would not be willing to endorse a system which gives the SNMP Bad Daddy the ability to retrieve my secret keys and PGP should permit holding my secret keys on a flop of some type -in other words specify a separate location for the secring which we can not do now unless we move the rest of PGP environment (at least as far as I have read). however, if I am stupid enough to put them in a network accessible position for the superuser to scarf -- that's my problem. for use on network machines, I have a c program which is effectively a one time pad to make the ring accessible for as short a time as possible. I was writing a c code supervisor which took care of this task rather neatly with an out of place checksum passwd for the pad keys but have been sidetracked. I think we have all pretty much agreed on the necessity of separate signature, communication, and storage keys; Adam Back convinced me rather quickly (I was using only a separate storage key). there is less agreement on the effectiveness of GAKing the communications key since some form of DH session keys could be deployed and mail is transient; eg: GAK only serves the Fed in this case, which, of course, is what they want. I have not seen any further discussion on my suggestion to create a sendmail type daemon which implements DH between mail clients. this, of course, is on the presumption that DH is a wrapper for an already encrypted packet, I also agree with Adam's design on isolating the recovery aspect from possible GAK outreach. although I will cop a plea to sometimes in the back and forth Adam was grasping for something which was never going to be there <g> bottom line: I think the consensus has already formed that PGP is not going to be the pristine voice crying in the wilderness we all hoped to hear; now the issue is, how can we shape the product to have a) the most flexibility, realizing full well there will be brain dead organizations who will insist on ordering GAK; and b) have the fewest potholes unknowingly enabling some level of pseudoGAK, etc.] again, that means focusing the pressure on PGP to keep the basic crypto engine pristine, and do the dirty work in Bad Daddy --and use "visible" plugins. I can only presume PGP 5.5 is a fair ways down the pipe to delivery, complete with its Big Daddy SNMP enforcer; this will make it all the harder to influence changes as PGP, Inc. appears to have grown enough in size to contain too many non-caring v/v real privacy (I have nothing to hide type ignorance), and even more disappointing, not only technically ignorant, but distrustful of technology bureaucrats that arrive with corporate growth -focused on a) closing off the design cycle; b) stifling the debate over methods; c) shipping product (oh, hell, we can listen to their complaints and make changes later...); and, d) recover the vulture capital investors money. if the foregoing is true, I hope PRZ has the good sense to take a walk, selling his stock (to do otherwise would be complicit in the deception of PGP's reputation capital). regardless of the above, if we as a group, with reasonable consensus, are willing to make an assault on the powers that be at PGP, Inc. including whatever relevant public publicity to heat the fire, there may be action. hell, if we could afford it (or Tim feels _real_ generous <g>), buy a NYTimes page and all of us sign the "selling out our the constitution" with cute little graphics of children being tortured for their keys. another point to consider: if a majority of cypherpunks as a group are willing to "endorse" the pgp product, that may be an issue worth discussing with pgp. the only problem may be the level of the outside managers and bean counters which hold down the front offices, totally ignorant of anything but feeelthy money; or, more probable, some cp subset who have been the primary contributors historically on these issues, and I think most of us know who the primary thinkers are on this issue are. obviously we must be fully informed and our opinions assessed --even with divergences. in the end, I would like to think decisions could be settled by consensus, rather than Supreme Court style. <g> if we (and I say this as: "who's this we...").... despite the cynical contempt with which the mass media often displays to our attitudes, even resorting to name calling, reputation capital is not necessarily gained from main line press popularity, and certainly not from government "popularity" in this issue [particularly cogent to those of us "fortunate" to have received the IRS spam]. FWIW of course, I may be presumptuous PGP would even want to hear from us, let alone have any form of "Cypherpunks Inside" (yuk) label on the box! particularly with the round robin multi-teaming of the sleepless Jon Callas. this has been an attila rant... attila, out, one more time.... and: it aint over 'til the fat lady sings, vahalla burning! "attila" sig: 1024/C20B6905/23D0 FA7F 6A8F 6066 BCAF AE56 98C0 D7B0 -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: latin1 Comment: No safety this side of the grave. Never was; never will be iQCVAwUBNEXXkb04kQrCC2kFAQHD1wQAiAMt4qP+GX0SXpF9XSuWbJc38tBWFD+U ErAn5iAhrWkzl1/HpkmxDb8qUS9fh1fTsUjTihTOCSU8RwvtkBuzkhMm02MXxxyK eJndaYgdpt+pluGYfrDIj9Vd3QDQVlJ0gf+o+CQ+pwQUJxYjmI/oELb0jBDnOwek EUl1MAszW90= =EulT -----END PGP SIGNATURE-----

4 5

kernal timezone options
by Matthew E. Patton 17 Dec '03

17 Dec '03

I'm not having much luck figuring out what values exist for the TIMEZONE and DST kernel options. The default is 0 and 0 which puts my machine off by about 4 hours. The installation routine put in the proper link to US/Eastern or on another box EST5EDT. This apparently is insufficient to get the date command to behave. Incorrect time obviously impacts the entire system. My bios clock is right on. So where are the integers defined that correspond to the various zoneinfo files? This is definately man page material. thanks for the continuing assistance. ps, I figure -1 or -4 is the correct value for DST

2 1

Checklist
by Daniel Colpi 17 Dec '03

17 Dec '03

Greetings and Salutations, A few days ago, I asked for help in making a step by step list on how to "copy" OpenBSD from one computer to another. Well I got a few answers, but many people wanted me to post this list when I was done. So this is it, a mindless checklist of everything I did to "convert a DEC 3100 to the Dark Side" If you can think of something I have missed, please throw me an e-mail. Thanks Daniel Colpi colpi(a)purdue.edu ====================================================================== So, you want another OpenBSD computer hu? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (assuming same disk setup, target is disk #0, and source is disk #1) (also assuming rrz0a -> / ; rrz0c -> swap rrz0d -> /usr ; rrz0e ->/usr/target ) (Note: I am on a /bio backbone, this isn't going to be the same for you) (Note: /bio/scratch3 is a temp space that I can write to) ___Save Files ___dump root to scratch (just in case) -->% dump -0f /bio/scratch3/dump /dev/rrz0a ___/etc/passwd --> % mv /etc/passwd /bio/scratch3/passwd.target ___/etc/crontab ___any self created scripts you made to run with crontab ___/etc/fstab ___/usr/local/etc/mk-exports ___/etc/export.hosts ___/etc/export.fs.[n] (if you have a drive that is set up the way you want for target machine, you might want to save it to a file to save you some time) (Note: you might want to do this on a machine that is already converted) ___save your partition list -->% disklabel -r /dev/rrz1a >> temp_part % mv temp_part /bio/scratch3 ___Shut down target ___Connect source drive ___Make sure drives are jumpered not to conflict (target=>0 ; source=>1) ___Plug in and power up ___Make sure clock is right time (some old computers lose some time) ___Make sure you see both drives (ie drive 1 & drive 0) ___Run disklabel (I had drouble labeling the disk, but this worked) -->% disklabel -r /dev/rrz1a >> temp % disklabel -B -R /dev/rrz0a temp % disklabel -e /dev/rrz0a ___ / = _______________ ___ swap = ____________ ___ /usr = ____________ / ______________ (target / source) (remove src if desired) ___ /usr/target = _______________ (if you have a "cookie-cut" version you can just:) -->% disklabel -B -R /dev/rrz0a /bio/scratch3/temp_part ___Run newfs -->% newfs /dev/rrz0[ad] ___Transfer files --->% mount /dev/rz0a /mnt % cd /mnt % df -k . (make sure enough room) % df -k / % dump 0f - /dev/rrz1a | restore -rf - % rm restoresystable (if you don't do this you'll be sorry) % cd / % umount /mnt % mount /dev/rz0d /mnt ---+ % cd /mnt | % df -k . | Repeate this % dump 0f - /dev/rrz1d | restore -if - | section if restore > add [all dir's you want to keep] | needed restore > extract | on restore > set owner/mode for /./? [yn] n | other restore > quit | partitions (Note: it will say "DUMP not completed" if you | did not restore everything. This is not a bad | thing, ignore it) | % rm restoresystable (might not be there) | % cd / | % umount /mnt ---+ ___Configure (BE CAREFUL to configure /mnt/etc NOT /etc !!!!) ___mount /usr --->% mount /dev/rz0d /mnt ___remove /mnt/etc/npt.drift ___make dir /mnt/usr/preserve ___replace all scripts made to be run by crontab ___move /bio/scratch3/mk-exports /mnt/usr/local/etc/mk-exports ___umount /mnt ___mount / --->% mount /dev/rz0a /mnt ___replace rest of scripts to be used by crontab ___move /bio/scratch3/export.hosts /mnt/etc/export.hosts ___move /bio/scratch3/export.fs.[n] /mnt/etc/export.fs.[n] ___hostname ___/mnt/etc/hostname.le1 ___/mnt/etc/exports (or run /usr/local/etc/mk-exports) ___/mnt/etc/hosts (change IP number too) ___/mnt/etc/myname ___/mnt/etc/rc (maybe not if (flavor == vanilla)) ___/mnt/etc/mygate ___/mnt/etc/passwd ___/usr/local/bin/tcsh (OpenBSD doesn't come with tcsh) ___reconfigure passwd file (for correct format) __ % mv /bio/scratch3/passwd.target /mnt/etc/passwd.orig same / % nawk -F: ' { print $1 FS $2 FS $3 FS $4 "::0:0:" $5 FS \ line \__ $6 FS $7 } ' /mnt/etc/passwd.orig >> /mnt/etc/passwd % pwd_mkdb -c /mnt/etc/passwd % pwd_mkdb -d /mnt/etc/ /mnt/etc/passwd % pwd_mkdb -d /mnt/etc/ -p /mnt/etc/passwd % chmod 600 /mnt/passwd.orig ___do you want permissive /mnt/root/.rhosts (bilbo root ; gimli root) ___how about cooperative /mnt/etc/ttys (%s/network/network secure) ___if your source machine boots off disk 1 and target boots off disk 0, you need to make sure the correct kernal is at /mnt/bsd ___umount /mnt ___Power down ___Remove source drive ___Correct jumpers if nessary ___Power up ___Before starting OpenBSD at Boot Ram type: >> printenv >> setenv bootpath rz(0,0,0)/bsd ___Boot off of target disk ___restore user file system --->% cd /usr/target % rsh bilbo ls /usr/amanda/\* __ (now in order) same / % rsh bilbo cat /usr/amanda/target.date.[0->(n-1)] \ line \__ < /dev/null | resore -rf - (now when done with above loop (IN ORDER!!!!!)) % rm restoresystable ___recreate crontab --->% crontab -e ___Checks ___ping source machine (to make sure not same IP addresses) ___run ntpq -p ___finger @localhost ___finger @target ___cd into /bio/scratch3/ ___run date ___telnet to target from another machine ___ftp one file from another machine ___cd to /bio/target from another machine ___Go home early Nessary Tools: =============== Screwdrivers (if internal drives) Postit-notes (for keeping drives straight) One hell of a lot of coffee

1 0

Re: Encyrption Program
by semprini＠theschool.com 17 Dec '03

17 Dec '03

This is in response to the several posts regarding the assumed weakness in the program I wrote: While it is true that PRNG's are not very good, because of the inherent lattice structure, I believe I found a way around that problem. To work around the lattice problem, I used a systm of cubic arrays. The program first creates sixteen cubic arrays, and fills them one space at a time with random characters. When the stream of characters to be XORed with the plaintext is generated, it picks a random cube and a random location with that cube. The resulting "random" character is then XORed with the appropriate character of the plaintext. If someone can prove to me that this method is stupid or easily breakable, I would actually be happy. So, those of you bent on proving that I'm wrong, I heartily encourage you to do so. As I mentioned before, you can download both the compiled version *and* the source at "http://www.brigadoon.com/~semprini/3dmx". If you are having trouble reaching that site, e-mail me and I will send you a copy via e-mail. Thank you for your interest and criticisms. They have been helpful. --Dylan

4 3

Re: Documentation
by Charlie Root 17 Dec '03

17 Dec '03

> >In the coming weekend, I'll be updating the newuser FAQ > >(for things like PPP and 2.2). I'm sure a post-install checklist would be > >a welcome addition. > > > >B U T . . . . > > > >Not everyone runs things like Kerberos or DNS. Keep in mind that many > >people use OpenBSD for many things and in many environs. The OpenBSD setup > >on my firewall at the office is much different than the Sparc, Alpha, and > >P5/133 I run it on at home. The setup on my router machine at home is also > >much different than the other machines in my house. There are ways people > >have setup OpenBSD on embeded systems to do things like manage the > >fuel/air mix ratio on their Corvettes (OK, one person I know of planned > >that, but couldn't get the financing for the car...) I hope that draws the > >picture. > > > >As for the verification after install, that is sort of "auto-manditory"-- > >if a filesystem isn't mounted right, /etc/fstab has to be checked out. If > >the network doesn't work, the network files must be examined to "make it > >go." As oopposed to attacking this as a checklist, how about it is > >attacked as "If networking doesn't work, check hostname.(interface)"-- but > >there is more to that then just files in /etc (boot -c in order to > >reconfigure hardware addresses) > > As a user of OpenBSD, and having tried to manage projects with it for > implementation of added features for customers...I could not agree with > the above position. > > You see, if you are ALREADY familiar with OpenBSD then you will most likely > know exactly what to do when installing and seting up a system. New User's > Notes / Installation Checklist's will most likely be ignored by you. > > However, if you are brand new to the system, then an Installation / Setup > Checklist (a good one) will prove to be essential. Wouldn't it be great if > just about every post to these groups from a new user was one like "..hey! > This OpenBSD thingy works great! The installation was a snap!.." or something > like that. We all know that hardly happens now...but, it could..... > > I, for one, believe strongly that a good 'Overview', 'Setup Notes' and 'Installation > Checklist' must somehow find it's way into the distribution. It is also clear > that the machine / arch specific differences will require unique versions > for each. I completly agree with you. Just anoze topic that i can add is installation procedure,especially disk partitoning. It's a very dungerous/important procedure but it's description ins INSTALL.i386 is a bit too short and need examples(espcially). Something like - "Imagine we have disk with such and such patitions and now we want to install OpenBSD here & there so we should... It would'be _very_ helpfull. BTW, does anybody work on installation software ? Something like in FreeBSD/RedHat ? Alexey Pialkin

1 0