On Mon, Sep 18, 2006 at 09:17:33PM -0700, Matthew Dillon wrote:
782MB for the whole repository, 354MB of which is contrib. But most
of contrib is made up of one-offs. We have multiple versions of
sendmail, a few of gcc, a few cvs, and that's pretty much it insofar
as the
Not sure where this issue is coming from I suspect it may be something
that DragonFly-1.6.0-RELEASE doesn't like about VMWare.
I'm developing a few semi-embedded systems built on DragonFlyBSD, I'm
building the systems up in VMWare (Server 1.0.1) and I've noticed
sometimes the DragonFly boot will
On Tue, 19 Sep 2006, Morgan Reed wrote:
Not sure where this issue is coming from I suspect it may be something
that DragonFly-1.6.0-RELEASE doesn't like about VMWare.
I'm developing a few semi-embedded systems built on DragonFlyBSD, I'm
building the systems up in VMWare (Server 1.0.1) and
elevator# burncd -f /dev/acd0c data plan9.iso fixate
next writeable LBA 0
writing from file plan9.iso size 258006 KB
written this track 1120 KB (0%) total 1120 KB
only wrote -1 of 32768 bytes err=16
fixating CD, please wait..
elevator# cdrecord --scanbus
Cdrecord 2.00.3 (--) Copyright (C)
On Tue, September 19, 2006 12:39 pm, Jamie wrote:
In [EMAIL PROTECTED],
Petr Janda [EMAIL PROTECTED] mentions:
elevator# burncd -f /dev/acd0c data plan9.iso fixate
next writeable LBA 0
writing from file plan9.iso size 258006 KB
written this track 1120 KB (0%) total 1120 KB
only wrote -1 of 32768
Matthew Dillon wrote:
Hmm. It sounds ok to me but I do seem to recall that some issues
popped up when FreeBSD did this, so my provisio in importing bsdtar
is that you (Peter) review the FreeBSD mailing lists for bsdtar related
discussions and put together a summary of any issues
Hello,
If i set dumpdev to the slice (bad term?) representing /var, will the
system be able to access /home ? (asking because symlinked /var/crash to
/home/var.crash)
Dumpdev should be set to the swap slice, but maybe that's what you
already have done.
The system will be able to access /home as long as it's mounted
automatically on startup in /etc/fstab and place it where the symlink
/var/crash points to.
Regards,
Jonas Trollvik
On 9/19/06, Gergo Szakal
Gergo Szakal wrote:
Hello,
If i set dumpdev to the slice (bad term?) representing /var, will the
system be able to access /home ? (asking because symlinked /var/crash to
/home/var.crash)
I think you're confusing two things there:
dumpdev is usually set to a swap partition, as in
Jonas Trollvik wrote:
Dumpdev should be set to the swap slice
That's what I misunderstood then (I am tired) and set it to /var. The
crash dump killed my FS, had to reinstall the system, because fsk could
not do anything to it in single user mode as well as running from the
livecd.
Thanks
No worries. Gmail sorts everything out fine for me anyways =)
you could try to restore /var from the livecd in case you dont want to
reinstall the whole system. newfs and cpdup should be able to handle
this for you
Good luck!
//Jonas
On 9/20/06, Gergo Szakal [EMAIL PROTECTED] wrote:
Jonas
ATAPICAM is compiled in the kernel so thats not the problem.
Jamie wrote:
In [EMAIL PROTECTED],
Petr Janda [EMAIL PROTECTED] mentions:
elevator# burncd -f /dev/acd0c data plan9.iso fixate
next writeable LBA 0
writing from file plan9.iso size 258006 KB
written this track 1120 KB (0%) total
On Tue, 19 Sep 2006, Gergo Szakal wrote:
Hello,
If i set dumpdev to the slice (bad term?)...
Yes. The dumpdev is usually set to be the swap
'partition'. The word 'slice' describes one of the
areas of a hard disk which is specified in the DOS
'partition table'. This ambiguity is disgusting,
13 matches
Mail list logo
