week old -current system. I'm supping a new
-current right now and will try doing a new "make world" to see
if this helps, but this is the only port I've had any trouble
getting to build.
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e status message, or printed out odd control characters.
It wouldn't even let me switch to a different vty.
If I let it sit for long enough, the login would timeout, and it
went back to normal.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
efore it goes around re-making file systems.
I would hate to see my file system wiped out just because
I have the "FASTCLEAN" environment variable set for some other
application, and didn't intend for "make release" to use it.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED]
seful features are missing from the man page!
Sure! Where are your patches for this? I'll review them
and commit them as soon as you supply them!
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Mon, Sep 13, 1999 at 06:03:19AM -0500, Mike Pritchard wrote:
> > > Speaking of which, are there any plans to actually document vi any time
> > > soon? Lots of useful features are missing from the man page!
> >
> > Sure! Where are your patches for this?
nts correctly, I may have been
doing the same thing.
I've seen this probably 4 or 5 times in the past month, maybe
6 weeks. Anyone have any ideas what is going on?
This is a Compaq AMD K6-2/400 machine. PS/2 style keyboard input
to the motherboard. I'll be glad to supply any further d
xc0222d50 in copystr ()
#11 0xc0dc7209 in ?? ()
#12 0xc0dc5fbd in ?? ()
#13 0xc0224316 in syscall ()
#14 0xc0215b06 in Xint0x80_syscall ()
#15 0x28abf564 in ?? ()
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
core (be sure
> to clear out space from /var/crash if necessary).
>
> Now bring the system up again, and use this for your gdb:
>
> cd /var/crash
> gdb -k /usr/src/sys/compile/YOURCONFIGNAME/kernel.debug vmcore.XX
>
> And do the 'back'
eeBSD Con (or someone gives him connectivity there, since we had
> to pack up the terminal room), there's not going to be any more updates.
After we did some more playing on freefall, it looks more like an NFS
problem. "ls -l /" hangs on nfsrcv, just like cvsupd is doing right no
the dmesg output below.
-Mike
ata-pci0: at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ad0: ATA-5 disk at ata0 as master
ad0: 13029MB (26684784 sectors), 26473 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
Mounting root from u
it seemed to be due to reverse DNS lookups not resolving
correctly (my ISP wasn't always responding to reverse DNS
lookups correctly).
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
t,
oops, it depends on pkg_xxx2, and so on, when in reality that only
reason any of those additional packages were installed were for the
original package.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
't really worry about it.
If we aren't supposed to have "at isa? port ..." stuff in our
config files, then someone should update GENERIC to reflect
that.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
it all again when the
syntax changes?
Something in the loader man pages should be updated to provide info
on the new hints stuff. Having a man page dedicated to describing the
hints stuff probably would also be a good idea to make it easy for people
to figure out how it works.
-Mike
--
Mike Pritchard
I think as long as we can decide how to provide the needed information
in the device specific man pages, this shouldn't be too hard
to actually sit down and do.
Then someone also has to sit down and write hints(4) to back
it all up :-).
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL
latest & greatest to
see how it worked. As you can see, it didn't go very well :-(.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
- End of forwarded message from Mike Pritchard -
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send
ink I've had a bad floppy disk in years and years (plus
I had been up all night beating my head on the desk over the whole
mess).
Thanks to everyone who replied. I'm now typing this message from the
machine that I had to do the re-install on, so all is good.
-Mike
--
Mike Pritchard
[EM
ld prevent word breakage when new keymaps
have been added.
To get around it, I just commented out the file that was causing problems
in the makefile (ua..alt.kbd or something like that), but before that I
had nuked /usr/obj twice, and did fresh checkouts of /usr/src just to be
sure I hadn
18 matches
Mail list logo
