[EMAIL PROTECTED] wrote:
Hello!
...Same problem, again (it was already covered some time ago).
When I run the last step in building a release
(see http://www.openbsd.org/faq/faq5.html) , i.e.
# make release
I get a message informing me that /dev/svnd0a is full. This occurs
while make is w
On 11/3/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> # make release
>
> I get a message informing me that /dev/svnd0a is full. This occurs
> while make is working with ramdiskC (exactly as the messages posted
> last July).
> A) Solution is the same as previously suggested (removing a non
> c
Hello!
...Same problem, again (it was already covered some time ago).
When I run the last step in building a release
(see http://www.openbsd.org/faq/faq5.html) , i.e.
# make release
I get a message informing me that /dev/svnd0a is full. This occurs
while make is working with ramdiskC (exact
From: "Nick Holland" <[EMAIL PROTECTED]>
There is an issue with RAMDISKC on -stable, it grew post-release.
Either:
1) Remove a couple non-critical drivers from RAMDISKC
2) Tell the system not to bother building RAMDISKC as part of the
release. You can do this by removing references to ram
Adam Fabian wrote:
> I've tried building an OpenBSD release from the 3.7-stable branch a
> few times in the last few days, on two different i386 machines, and
> both stopped in the same place.
--8<--
> dd if=bsd.gz of=/mnt/bsd bs=512
>
> /mnt: write failed, file system is full
> dd: /mnt/bsd: No
On Mon, Jul 11, 2005 at 01:24:01PM -0400, Jason Crawford wrote:
> from different sources if you so choose. The problem the OP is having
> was caused by one of the stable patches to the 3.7 kernel, making it
> just too big to fit on a floppy, which has been talked about in at
> least one previous th
On 7/11/05, Chris <[EMAIL PROTECTED]> wrote:
> On Mon, 11 Jul 2005, Adam Fabian wrote:
>
> > I've tried building an OpenBSD release from the 3.7-stable branch a
> > few times in the last few days, on two different i386 machines, and
> > both stopped in the same place. I'm following release(8) clo
On Mon, Jul 11, 2005 at 11:48:49AM -0500, Chris wrote:
> On Mon, 11 Jul 2005, Adam Fabian wrote:
>
> >I've tried building an OpenBSD release from the 3.7-stable branch a
> >few times in the last few days, on two different i386 machines, and
> >both stopped in the same place. I'm following release
> Ummm - maybe I don't understand but, how can you make a RELEASE from
> STABLE? Isnt STABLE following the patch branch? And RELEASE is jsut that
> - what's on the CD?
>
> If i'm correct - then you can't do that. If I'm correct, think of it this
> way:
>
> RELEASE = what you buy.
> STABLE = i
On Mon, Jul 11, 2005 at 11:48:49AM -0500, Chris wrote:
> On Mon, 11 Jul 2005, Adam Fabian wrote:
>
> >I've tried building an OpenBSD release from the 3.7-stable branch a
>
> Ummm - maybe I don't understand but, how can you make a RELEASE from
> STABLE? Isnt STABLE following the patch branch? And
On Mon, 11 Jul 2005, Adam Fabian wrote:
I've tried building an OpenBSD release from the 3.7-stable branch a
few times in the last few days, on two different i386 machines, and
both stopped in the same place. I'm following release(8) closely and
not trying to reuse /usr/obj, and dealing with new
I've tried building an OpenBSD release from the 3.7-stable branch a
few times in the last few days, on two different i386 machines, and
both stopped in the same place. I'm following release(8) closely and
not trying to reuse /usr/obj, and dealing with new, clean, complete,
consistent checkouts of
12 matches
Mail list logo
