Carlo Dapor wrote:
The medium I mount is a hard disk partition.
/dev/ad0s1 is my win98 boot drive, /dev/ad0s2* my FreeBSD world.
It has worked for almost a year, never had a crash or lost a single byte.
I can go back to the kse kernel, and remount Win98, with the instructions
You just
I'm in the process of getting set up for testing KSE too, but I was wondering, how are
you capturing the panic dump? Do you run a
serial console or something to do it?
Carlo Dapor wrote:
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just to confirm this.. if it works there but not with KSE
then we have work to do :-)
I build and run a kernel just before applying the patches, that was able to
mount the partition and 'accepted'
thanks..
I will try duplicate this tomorrow
(today is shaping up to be a bad day)
On Thu, 30 Aug 2001, Carlo Dapor wrote:
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just to confirm this.. if it works there but not with KSE
then we
I can not reproduce this with a memory disk image of an msdos floppy
(I do not have a floppy on that machine)
can you try accessing the floppy without mounting?
e.g. can you try using it as a raw device with TAR or something?
Maybe it's the floppy driver rather than tehe filesystem.
If you can
sometimesm show panic
messages from the last session too.
On Thu, 30 Aug 2001, Jim Bryant wrote:
I'm in the process of getting set up for testing KSE too, but I was wondering, how
are you capturing the panic dump? Do you run a
serial console or something to do it?
Carlo Dapor wrote:
can you
The medium I mount is a hard disk partition.
/dev/ad0s1 is my win98 boot drive, /dev/ad0s2* my FreeBSD world.
It has worked for almost a year, never had a crash or lost a single byte.
I can go back to the kse kernel, and remount Win98, with the instructions
You just posted.
Ciao, derweil,
--
On Wed, 29 Aug 2001, David Wolfskill wrote:
OK; maybe I'm just not cut out to be trying to do this.
The first time I tried the usual approach, my build machine locked up,
hard. (It was running the previous days' -CURRENT -- and I was able to
build today's -CURRENT on a copy of it).
The most recent diffs applied nicely.
The kernel built nicely, as well.
But I could not mount an msdosfs partition, it bombed terribly.
I don't have any ouytput, though, sorry.
Ciao, derweil,
--
Carlo
PS: Only two or three modules did not compile, ncp and smbfs(?) I think
After doing a
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just to confirm this.. if it works there but not with KSE
then we have work to do :-)
On Wed, 29 Aug 2001, Carlo Dapor wrote:
The most recent diffs applied nicely.
The kernel built nicely, as well.
On Wed, Aug 29, 2001 at 03:42:55PM -0700, Julian Elischer wrote:
can you try the same with a matching -current?
I heard that msdosfs is bombing there too.
(just to confirm this.. if it works there but not with KSE
then we have work to do :-)
I'm just tuning into this thread a little late,
the crash I saw was on today's sources I think.
That's why I'm asking for the same revision of the -current
to be used..
My test box has no floppies...
On Wed, 29 Aug 2001, David W. Chapman Jr. wrote:
On Wed, Aug 29, 2001 at 03:42:55PM -0700, Julian Elischer wrote:
can you try the same with
Because we have not patched any non kernel items in the patch
A make world in a source tee with the KSE changes in it's kernel directories
will fail.
You need to do build the kernel outside of the tree you will "make buildworld"
in so that the build tree is untouched. Oherwise it will not
13 matches
Mail list logo
