I've been running 5.1-CURRENT for a while and a couple nights ago did
a make world. After a couple hours building, my system was
unusable. Critical binaries like rm, ls, mtree, sh failed,
reporting Exec format error. I can't login, not even single user.
I can no longer even boot single user.
masta [EMAIL PROTECTED] writes:
The easy way is to grab a recent livecd from the jp snapshot service.
[ http://livecd.sourceforge.net/ ]
With the jpsnap livecd I was able to boot, copy all the working
binaries from the cdrom over the corrupt binaries on the local HDD. I
suggest you try the
Barney Wolff [EMAIL PROTECTED] writes:
Re-install/upgrade from a cd. Upgrade should leave your files alone.
Thanks, Barney -- that's what I did and it saved my butt.
A few folks suggested either LiveCD images or fixit functionality.
I was kinda dead in the water and didn't think I could
Some of my systems are 5.1-CURRENT but I still have some older 4.x
boxes. I'd like to upgrade them to the same OS as my 5.1 boxes.
It seems stupid to feed them boot floppies then FTP the OS across the
WAN from freebsd.org or mirrors.
I expect there's a way to build a distribution on my main
I'm trying to do a make buildworld on my system:
FreeBSD PECTOPAH.shenton.org 5.1-CURRENT FreeBSD 5.1-CURRENT #2: Tue
Jul 1 19:48:37 EDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/PECTOPAH i386
And it keeps dying at various points early in the build. It's a
different location each time, some
Chris Shenton [EMAIL PROTECTED] writes:
*** Signal 11
...
Illegal instruction (core dumped)
*** Error code 132
Also seeing
*** Signal 4
if it matters. This sounds way too flakey to be SW.
___
[EMAIL PROTECTED] mailing list
http
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
Well, it seems to be working now, but not necessarily due to this
patch. I lost two of the four drives on my ATA RAID card (RAID-5) so
lost my entire system :-(.
Rebuilt the box from the 5.0-RELEASE floppies/net then
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
When I do the patch, how much of the OS do I need to rebuild, just do
a make install in the .../src/sys/kern dir? Rebuild the OS from
the top dir? Rebuild the kernel?
Don Lewis [EMAIL PROTECTED] writes:
Try the very untested patch below ...
RCS file: /home/ncvs/src/sys/kern/uipc_syscalls.c,v
retrieving revision 1.150
Try the very untested patch below ...
diff -u -r1.150 uipc_syscalls.c
--- uipc_syscalls.c 12 Jun 2003 05:52:09 - 1.150
+++
Don Lewis [EMAIL PROTECTED] writes:
Thanks for doing the testing. I just committed this patch.
Seems fine here too -- many thanks.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
Don Lewis [EMAIL PROTECTED] writes:
I doubt it. I checked in a fix for this problem today so you should get
the fix when you next cvsup.
Yup, many thanks.
Can you break into ddb and do a ps to find out what state all the
processes are in?
I'm a newbie to ddb. Was able to get a ps from a
Oh, FWIW, I did a cvsup and rebuilt the OS and kernel then did a
mergemaster about 30 minutes ago in order to get your fix to my qmail
issue. So I'm running about as CURRENT as possible.
___
[EMAIL PROTECTED] mailing list
Don Lewis [EMAIL PROTECTED] writes:
If you have another machine and a null modem cable you can redirect the
system console of the machine to be debugged to a serial port and run
some comm software on the other machine so that you can capture all the
output from ddb.
OK, I'll give that a
(I don't know if this has any relation to the problems I reported
yesterday with qmail-send consuming 100% cpu after 5.0 to 5.1 upgrade.)
After booting 5.1-CURRENT the system runs fine for a while. Then
later most disk i/o related actions seem to hang. E.g., system works
but when cron kicks off
I've been running qmail for years and like it, installed pretty much
per www.LifeWithQmail.org. My main system was running FreeBSD
5.0-RELEASE and -CURRENT and qmail was fine. When I just upgraded to
5.1-CURRENT a couple days back, the qmail-send process started using
all CPU.
last pid:
I have a DELL 600SC which came with a DELL CERC RAID controller. It's
recognized by FreeBSD-CURRENT as an amr device even though it's got
four ATA disk channels on it instead of the documented SCSI drives for
the PERC controller. I have 4x WD1200JB ATA 120GB disks on it which
have been running
John Wilson [EMAIL PROTECTED] writes:
--- Scott Long [EMAIL PROTECTED] wrote:
[Dell PowerEdge]
What model? There are quite a few PowerEdges out
It's a 600SC - P4 1.8 - Perc3/SC
FWIW, I had absolutely no trouble booting and installing 5.0-R on my
600SC, with the DELL-supplied CERC RAID
Matthew Dillon [EMAIL PROTECTED] writes:
# ls -lR /conf
drwxr-xr-x 5 root wheel 512 Dec 21 10:37 base
drwxr-xr-x 3 root wheel 512 Dec 19 21:56 default
...
/conf/base/etc:
-rw-r--r-- 1 root wheel 18 Dec 19 22:10 diskless_remount
-rw-r--r-- 1 root wheel 6 Dec 19 22:22 md_size
...
Matthew Dillon [EMAIL PROTECTED] writes:
If you do this pxeboot will attempt to load the kernel via TFTP
instead of via NFS. You then put your kernel in /tftpboot right along
side a copy of pxeboot.
This allows you to netboot a different kernel then the one in the
Matthew Dillon [EMAIL PROTECTED] writes:
4.x and -current use the same mechanism, except 4.x uses MFS and
-current uses MD.
4.x uses /etc/diskless[12] while 5.x (by default) uses
/etc/rc.d/(init)?diskless. The latter is works very differently than
the former.
Ignore the
Matthew Dillon [EMAIL PROTECTED] writes:
Make sure your NFS server is exporting to your subnet and that
it is running the necessary services, (portmap, mountd, nfsd -t
-u -n 4).
My boot server is 5.0, so that's the kernel my diskless box gets. My
other boxes are 4.x boxes but
Matthew Dillon [EMAIL PROTECTED] writes:
Are you sure you have done a recent buildworld/installworld? It
sounds like you haven't. In -current kenv is in /bin (i.e.
the source is in /usr/src/bin/kenv on -current) as of the 15th of
this month.
Well, I'll be danged. I
I was running a VIA Mini-ITX diskless box off a 4.7-STABLE box for a
while using a root fs created by the clone_root discussed in the
handbook, then some tweaks. I'm having a heck of a time trying to get
this running under 5.0-RELEASE, now sync'd to 5.0-CURRENT as of
yesterday, then
Chris Shenton [EMAIL PROTECTED] writes:
I've moved the mount -a near the top of rc.d/diskless since it
runs commands which are and not available until /usr is mounted
(e.g., mtree). The NFS mount fails with a message I don't
understand:
[udp] pectopah.shenton.org:/usr: RPCPROG_NFS: RPC
24 matches
Mail list logo
