Thanks to everyone who responded to my question. A few suggestions got my slow brain moving and here is what I found. Various people suggested I might be missing my index.txt. After some searching, that file seems to be used for http installs and I was doing a cd install, but at least that got me thinking. Another kind soul reminded me that if my install sets were in the root of the cd's filesystem, I would have to tell the install program to look in . instead of the normal place (which was exactly what I was already doing) except some tall blonde dummy (namely me) put the install sets into a folder on the cd instead of the root. Once I told the install where the sets actually resided, it all came up nice and beautiful.
Sorry if I wasted anyone's time.. s > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > stuart van Zee > Sent: Wednesday, May 23, 2007 2:04 PM > To: [EMAIL PROTECTED] Org > Subject: Install CD > > > Hello all, > > This is probably going to be an easy question for > many of you, but it has me stumped, and I can't > seem to find the answer (my google-foo is poor so > a search didn't reveal any wisdom). I admin a > number of OBSD servers and use a separate devel > system to compile patches etc and have been looking > for better ways to do things. A week or so ago, > there was talk on the list about using release(8) > and WOW, that works GREAT (I'm not surprised, just > happy)! So, I figured i would just dump the new > install sets onto a cd so that I could just point > the install at the new sets (and boot off of one > of the new floppy images) but when I get to the > point in the install where I am supposed to pick the > sets that I want the file names are just jumbled up > in there instead of being listed with the nice > checkboxes like they usually are. What did I miss? > > Stuart van Zee > [EMAIL PROTECTED] > > > __________ NOD32 2287 (20070523) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com
