On Thursday, October 20, 2011, Brett brett.ma...@gmx.com wrote:
On Fri, 21 Oct 2011 00:28:01 -0400
Ted Unangst t...@tedunangst.com wrote:
On Fri, Oct 21, 2011, Brett wrote:
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
# vnconfig -l
vnd0: not in use
vnd1: not in use
vnd2: not in use
vnd3: not in use
#
vnd's, not vnodes.
Is OpenBSD causing my dyslexia or merely bringing to light a preexisting
condition?
The likely cause of it being busy before is a previous attempt to build the
ramdisks
On Thu, Oct 20, 2011, Brett 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
After prodding from the openbsd community needs to shake thinsg up I
attempted to compile a ramdisk with the patches from
http://marc.info/?l=openbsd-techm=131669525606850w=2. The kernel and
userland built fine with -current from a few days ago, and the patches. But I
have had no luck finding
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
On Fri, Oct 21, 2011, Brett wrote:
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.
Well, it's
On Fri, 21 Oct 2011 00:28:01 -0400
Ted Unangst t...@tedunangst.com wrote:
On Fri, Oct 21, 2011, Brett wrote:
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
7 matches
Mail list logo
