Ted Unangst wrote: > vnconfig -v -c vnd0 mr.fs > vnconfig: VNDIOCSET: Device busy > *** Error code 1 > > Stop in /usr/src/distrib/macppc/ramdisk (line 77 of > /usr/src/distrib/macppc/ramd > isk/Makefile). > > Is there some more recent instructions floating around I could try?
Did you read the error message? Are you using vnd0? ---- On Thu, 20 Oct 2011 10:32:53 -0500 Amit Kulkarni <[email protected]> wrote: > > I attempted to compile a ramdisk with the patches from > > http://marc.info/?l=openbsd-tech&m=131669525606850&w=2. The kernel and > > userland built fine with -current from a few days ago, and the patches. But > > I have had no luck finding working instructions on building a ramdisk. Most > > seemed to be intermixed with instructions on building an install CD (to > > test the ramdisk, I was just going to boot into it, then install the sets > > from a recent snapshot CD). > > > > This site: > > http://www.seattlecentral.edu/cgi-bin/cgiwrap/dmartin/moin.cgi/OpenBSD says > > to make crunchgen from /usr/src/distrib/crunch but that directory does not > > exist in my source code. > > crunchgen is now part of base. so you just follow the rest. I built it > using the exact same instructions (seattlecentral) in September a > month ago or so ago. Grab current sources because there was a > something which nigel@ pointed in bsd.rd generation and its fixed in > current as of 2 days ago. > > HTH ---- Hi, Following Amit's suggestion I updated my source tree (mine was more like 3-4 days old) and now it builds, once I manually enter " # export DESTDIR=/ " (Note it will not compile until I set a destdir, I'm not sure if that is supposed to be the behaviour). I booted into a shell using the generated bsd.rd and it worked on G4 macppc (sorry, should have mentioned the architecture in the earlier port). Will try it on an install later today. As others have reported, the ramdisk is less than half the size of the regular one. Ted Unangst asked if I was using vnd0 (which shows in the error message). As far as I know I am not, it does not show up in the boot dmesg and I did not configure it myself. I assumed this was something used in the ramdisk compiling process. Thanks, Brett.
