Puzzling 'ps aux' output
Just noticed that some of the processes running on my system (-current as of Oct 2) seem to report a startup time in UTC rather than local time (see attached). Is this normal behaviour? [(dampurep)~]: uptime 10:54AM up 41 mins, 2 users, load averages: 0.10, 0.05, 0.01 [(dampurep)~]: uname -a FreeBSD bladerunner.alveley.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 2 08:05:22 BST 2000 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLADERUNNER i386 PYD USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root11 80.2 0.0 00 ?? RL 11:13AM 24:44.42 (idle: cpu0) root10 79.1 0.0 00 ?? RL 11:13AM 24:44.13 (idle: cpu1) root19 25.8 0.0 00 ?? ML 11:13AM 27:37.72 (irq9: acpi0) root 471 6.4 0.8 4368 4116 p1 S+ 10:43AM 1:14.20 cvsup -g -L 2 -P m -z /etc/src-supfile root 377 1.0 0.6 3700 2920 ?? S10:20AM 0:12.01 xterm -ls root15 0.0 0.0 00 ?? WL 11:13AM 0:02.01 (irq16: ahc0) root16 0.0 0.0 00 ?? WL 11:13AM 0:00.00 (irq17: pcm0) root17 0.0 0.0 00 ?? WL 11:13AM 0:00.00 (irq14: ata0) root18 0.0 0.0 00 ?? WL 11:13AM 0:00.00 (irq15: ata1) root 2 0.0 0.0 00 ?? DL 11:13AM 0:00.00 (acpi) root20 0.0 0.0 00 ?? WL 11:13AM 0:00.31 (irq1: atkbd0) root21 0.0 0.0 00 ?? WL 11:13AM 0:01.98 (irq12: psm0) root22 0.0 0.0 00 ?? WL 11:13AM 0:00.00 (irq6: fdc0) root23 0.0 0.0 00 ?? WL 11:13AM 0:00.00 (irq7: ppc0) root24 0.0 0.0 00 ?? WL 11:13AM 0:10.02 (irq0: clk) root25 0.0 0.0 00 ?? WL 11:13AM 0:09.46 (irq8: rtc) root 3 0.0 0.0 00 ?? DL 11:13AM 0:00.01 (pagedaemon) root 4 0.0 0.0 00 ?? DL 11:13AM 0:00.00 (vmdaemon) root 5 0.0 0.0 00 ?? DL 11:13AM 0:00.05 (bufdaemon) root 6 0.0 0.0 00 ?? DL 11:13AM 0:01.04 (syncer) root52 0.0 50.6 262532 262500 ?? ILs 11:13AM 0:02.82 mfs /dev/da1s1b /tmp (mount_mfs) root74 0.0 0.0 208 92 ?? Is 11:13AM 0:00.00 adjkerntz -i root 129 0.0 0.1 952 624 ?? Is 10:13AM 0:00.07 syslogd -s daemon 133 0.0 0.1 952 512 ?? Is 10:13AM 0:00.00 /usr/sbin/portmap root 153 0.0 0.2 1076 800 ?? Is 10:13AM 0:00.02 inetd -wW root 155 0.0 0.2 1000 780 ?? Ss 10:13AM 0:00.02 cron root 158 0.0 0.1 960 664 ?? Is 10:13AM 0:00.00 /usr/sbin/lpd root 161 0.0 0.3 1584 1372 ?? Ss 10:13AM 0:00.03 sendmail: accepting connections (sendmail) root 165 0.0 0.3 2156 1376 ?? Is 10:13AM 0:00.65 /usr/sbin/sshd root 213 0.0 0.3 1920 1588 ?? Ss 10:13AM 0:00.19 /usr/local/sbin/httpd pgsql 244 0.0 0.1 724 528 con- I10:13AM 0:00.00 /bin/sh /usr/local/pgsql/bin/pg_ctl -w start pgsql 245 0.0 0.3 4144 1712 con- I10:13AM 0:00.03 /usr/local/pgsql/bin/postmaster -i -o -F (postgres) nobody 253 0.0 0.3 1980 1668 ?? I10:13AM 0:00.01 /usr/local/sbin/httpd nobody 254 0.0 0.3 1980 1668 ?? I10:13AM 0:00.01 /usr/local/sbin/httpd nobody 255 0.0 0.3 1980 1668 ?? I10:13AM 0:00.01 /usr/local/sbin/httpd nobody 256 0.0 0.3 1980 1668 ?? I10:13AM 0:00.01 /usr/local/sbin/httpd nobody 257 0.0 0.3 1980 1668 ?? I10:13AM 0:00.01 /usr/local/sbin/httpd root 267 0.0 0.3 2892 1460 ?? Is 10:13AM 0:00.06 /usr/X11R6/bin/xdm root 272 0.9 23.6 122912 122372 ?? Ss 10:13AM 0:46.49 /usr/X11R6/bin/X -auth /usr/X11R6/lib/X11/xdm/authdir/authfiles/A:0-SXC267 (XF root 273 0.0 0.1 960 648 v0 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv0 root 274 0.0 0.1 960 652 v1 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv1 root 275 0.0 0.1 960 652 v2 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv2 root 276 0.0 0.1 960 652 v3 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv3 root 277 0.0 0.1 960 652 v4 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv4 root 278 0.0 0.1 960 652 v5 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv5 root 279 0.0 0.1 960 652 v6 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv6 root 280 0.0 0.1 960 652 v7 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv7 root 281 0.0 0.1 960 652 v8 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv8 root 282 0.0 0.1 960 652 v9 Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyv9 root 283 0.0 0.1 960 652 va Is+ 10:13AM 0:00.01 /usr/libexec/getty Pc ttyva root 284 0.0 0.4 3016 2320 ?? Is 10:13AM 0:00.09 /usr/X11R6/bin/xdm dampurep 297 0.0 0.8 5032 4304 ?? Ss 10:14AM 0:03.50
Re: nsswitch meets current
Makoto MATSUSHITA wrote: tanimura You still need host.conf to run old binaries (including Netscape) tanimura linked against libc.so.3 and earlier. I prefer to warn 'host.conf is tanimura for compatibility with old libc.' Is there any chance that compat1x, compat2*, compat3x includes /etc/host.conf for backward compatibility ? Users who install FreeBSD to fresh PC will meet unpredictable behavior if users run Navigator... This might be true for the FreeBSD binary, but does not seem to be for the BSDI one -- I suppressed /etc/host.conf and have yet to encounter a problem... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[Fwd: Problems with new PCI bus space implementation?]
Forwarded for completeness, since the message I sent yesterday didn't draw any attention... "Dampure, Pierre Y." wrote: Doug, Prior to yesterday, my last world / kernel rebuild was on August 25th. Since yesterday, any attempt at generating a kernel results in an image that: 1. Does not recognise my on-board fxp. 2. Does not recognise my PCI Adaptec 2940UW plus maybe some other things, but it's a bit difficult to track everything on a scrolling screen and I do not have a second PC I could use as a serial console. Because all my disks are SCSI, it is obviously a bit difficult to dig much further but, as mentioned in a previous message to -current, a pnpscan -v does detect a SCSI adapter. The problem exists whether I use an SMP kernel or not. The board is an Intel OR840 (Kitty Hawk) and the attached should described pretty much everything better than I could (of course, the dmesg and mptable outputs were generated with my previous kernel) Could you please let me know what to try in order to help tracking down the problem? Best Regards, PYD # # BLADERUNNER -- Custom kernel configuration, host bladerunner.alveley.org # machine i386 ident BLADERUNNER maxusers32 makeoptions CONF_CFLAGS=-fno-builtin options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options BLKDEV_IOSIZE=8192 options PQ_NORMALCACHE options ROOTDEVNAME=\"ufs:da1s1a\" options RANDOMDEV #hints "BLADERUNNER.hints" # # SMP OPTIONS: options SMP options APIC_IO options NCPU=2 options NBUS=4 options NAPIC=1 options NINTR=43 # # CPU OPTIONS cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK # # COMPATIBILITY OPTIONS options COMPAT_43 options COMPAT_LINUX options SYSVSHM options SYSVSEM options SYSVMSG # # DEBUGGING OPTIONS options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG # # NETWORKING OPTIONS options INET device ether device loop1 device bpf device disc # # FILESYSTEM OPTIONS options FFS options MFS options PROCFS options FFS_ROOT options SOFTUPDATES options FFS_EXTATTR options QUOTA # # POSIX P1003.1B options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # # CLOCK OPTIONS options HZ=100 options CLK_CALIBRATION_LOOP options CLK_USE_TSC_CALIBRATION # # SCSI DEVICES device scbus device da device sa device cd device pass device pt # # MISCELLANEOUS DEVICES AND OPTIONS options MSGBUF_SIZE=40960 device pty device gzip device vn device snp # # HARDWARE DEVICE CONFIGURATION options AUTO_EOI_1 options AUTO_EOI_2 options VESA options MAXCONS=12 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=cp850 options SC_DISABLE_DDBKEY options SC_DISABLE_REBOOT options SC_PIXEL_MODE options ATA_ENABLE_ATAPI_DMA options AHC_ALLOW_MEMIO options PPC_PROBE_CHIPSET device isa device atkbdc 1 device atkbd device psm device vga device splash device sc 1 device npx device ata device atadisk device atapicd device fdc device sio device pci device ahc device fxp device ppc device ppbus device lpt device ppi device pps device pcm device
Adaptec 2940UW not probed any further?
I CVSup'd this morning around 05:00 BST, then make -DCLOBBER world / mergemaster / sh MAKEDEV all / buildkernel / installkernel. My Adaptec 2940UW is no longer probed at boot time. /boot/device.hints contains the proper entries and a pnpscan -v detects a SCSI controller. Attached are my current kernel configuration file and the corresponding hints, which have been copied to /boot/device.hints. I'm a bit at loss here and could really do with some help... Many thanks, PYD # # BLADERUNNER -- Custom kernel configuration, host bladerunner.alveley.org # machine i386 ident BLADERUNNER maxusers32 makeoptions CONF_CFLAGS=-fno-builtin options MAXDSIZ="(256*1024*1024)" options DFLDSIZ="(256*1024*1024)" options BLKDEV_IOSIZE=8192 options PQ_NORMALCACHE options ROOTDEVNAME=\"ufs:da1s1a\" options RANDOMDEV #hints "BLADERUNNER.hints" # # SMP OPTIONS: options SMP options APIC_IO options NCPU=2 options NBUS=4 options NAPIC=1 options NINTR=43 # # CPU OPTIONS cpu I686_CPU options CPU_FASTER_5X86_FPU options NO_F00F_HACK # # COMPATIBILITY OPTIONS options COMPAT_43 options COMPAT_LINUX options SYSVSHM options SYSVSEM options SYSVMSG # # DEBUGGING OPTIONS options UCONSOLE options USERCONFIG options VISUAL_USERCONFIG # # NETWORKING OPTIONS options INET device ether device loop1 device bpf device disc # # FILESYSTEM OPTIONS options FFS options MFS options PROCFS options FFS_ROOT options SOFTUPDATES options FFS_EXTATTR options QUOTA # # POSIX P1003.1B options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # # CLOCK OPTIONS options HZ=100 options CLK_CALIBRATION_LOOP options CLK_USE_TSC_CALIBRATION # # SCSI DEVICES device scbus device da device sa device cd device pass device pt # # MISCELLANEOUS DEVICES AND OPTIONS options MSGBUF_SIZE=40960 device pty device gzip device vn device snp # # HARDWARE DEVICE CONFIGURATION options AUTO_EOI_1 options AUTO_EOI_2 options VESA options MAXCONS=12 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=cp850 options SC_DISABLE_DDBKEY options SC_DISABLE_REBOOT options SC_PIXEL_MODE options ATA_ENABLE_ATAPI_DMA options AHC_ALLOW_MEMIO options PPC_PROBE_CHIPSET device isa device atkbdc 1 device atkbd device psm device vga device splash device sc 1 device npx device ata device atadisk device atapicd device fdc device sio device pci device ahc device fxp device ppc device ppbus device lpt device ppi device pps device pcm device sbc device midi device seq hint.scbus.0.at="ahc0" hint.scbus.0.bus="0" hint.da.0.at="scbus0" hint.da.0.target="0" hint.da.0.unit="0" hint.da.1.at="scbus0" hint.da.1.target="1" hint.da.1.unit="0" hint.da.2.at="scbus0" hint.da.2.target="2" hint.da.2.unit="0" hint.da.3.at="scbus0" hint.da.3.target="3" hint.da.3.unit="0" hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" hint.atkbd.0.at="atkbdc" hint.atkbd.0.irq="1" hint.psm.0.at="atkbdc" hint.psm.0.irq="12" hint.vga.0.at="isa" hint.sc.0.at="isa" hint.npx.0.at="nexus" hint.npx.0.port="0x0F0" hint.npx.0.flags="0x0" hint.npx.0.irq="13" hint.ata.0.at="isa" hint.ata.0.port="0x1f0" hint.ata.0.irq="14" hint.ata.1.at="isa" hint.ata.1.port="0x170" hint.ata.1.irq="15" hint.fdc.0.at="isa" hint.fdc.0.port="0x3F0" hint.fdc.0.irq="6" hint.fdc.0.drq="2" hint.fd.0.at="fdc0" hint.fd.0.drive="0" hint.sio.0.at="isa" hint.sio.0.port="0x3F8"
Re: World breakage from exit-sys_exit change?
Mike Meyer wrote: Ok, I give up. It seems that the world change from exit to sys_exit broke the world build, but I can't figure out where. I've fixed every occurence of SYS_exit in the source tree (this one seems to be src/lib/csu/i386/crt0.c, but there were some in gdb as well), and removed /usr/obj - and I still get the following error from buildworld: I think this might be due to the fact that, for some reason, the build is still using the old syscall.h (the one that references SYS_exit rather than SYS_sys_exit -- ie. the installed one rather than the newly generated one). The funny thing here is I would have expected a make -DCLOBBER to take care of that... Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Stephan van Beerschoten wrote: And what is the word on thise IOERROR's given by my kernel when its init'ing its usb stack. uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port 1 power on failed, IOERROR uhub0: port 2 power on failed, IOERROR Funny you should mention that :-) I asked the same question to N. Hibma a while ago (I get the same problem on my Intel OR840), but so far haven't had an answer. Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mtree -L problems in ports
Thomas Stromberg wrote: It's probably been fixed by now, but what I did when I first had the mtree problem was set NO_MTREE in /usr/ports/Mk/bsd.port.mk - Not sure of the side affects though (anyone care to enligtnen me?) Im sure there is a more elegant solution, I was just looking for a quicky. It is not fixed. Th current version of /usr/ports/Mk/bsd.ports.mk still has an OS version test to determine whether to use the -L flag -- committed by Satoshi Asami after the initial "no -L, now -L" move. The move was later backed out, but not this change. The whole issue of mtree behaviour has been discussed ad nauseam on cvs-all. Up until a concensus is reached, it's most probably easier to locally override MTREE_ARGS. Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weird top output
With a recently (10:00 BST) cvsup'd and built world / kernel: last pid: 288; load averages: 0.05, 0.04, 0.01up 0+00:03:27 15:53:02 32 processes: 1 running, 31 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 282M Active, 17M Inact, 20M Wired, 108K Cache, 20M Buf, 181M Free Swap: 3072M Total, 3072M Free PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 288 dampurep 46 0 1876K 1184K CPU0 1 0:00 0.87% 0.44% top 238 root 2 0 171M 170M select 1 0:05 0.00% 0.00% XFree86 35 root 10 0 256M 256M mfsidl 1 0:01 0.00% 0.00% mount_mfs 254 dampurep 2 0 3780K 2916K select 0 0:01 0.00% 0.00% wmaker 137 root 2 0 2140K 1408K select 0 0:00 0.00% 0.00% sshd 265 dampurep 10 0 2312K 1456K nanslp 0 0:00 0.00% 0.00% wmCalClock 220 mysql 2 0 10928K 9952K poll 0 0:00 0.00% 0.00% mysqld 285 dampurep 2 0 3668K 2988K select 0 0:00 0.00% 0.00% xterm 266 dampurep 10 0 2052K 1244K nanslp 1 0:00 0.00% 0.00% wmmixer 222 root 18 0 2864K 1468K pause 0 0:00 0.00% 0.00% xdm 239 root 10 0 2988K 2304K wait 0 0:00 0.00% 0.00% xdm 101 root 2 0 916K 656K select 1 0:00 0.00% 0.00% syslogd 270 dampurep 2 0 3128K 2412K select 0 0:00 0.00% 0.00% xconsole 286 dampurep 10 0 1092K 944K wait 0 0:00 0.00% 0.00% bash 125 root 2 0 1040K 784K select 0 0:00 0.00% 0.00% inetd 205 root 10 0 628K 460K wait 0 0:00 0.00% 0.00% sh I'm somewhat surprised by the resident size of XFree86-4 and mfs... from memory, the resident size of mfs was around 30Mb up until today (no recollection as to what it was fro XFree86-4, though). FWIW, this is just after a reboot. PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/lib/libc/net getaddrinfo.c
Jun-ichiro itojun Hagino wrote: itojun 2000/07/04 22:07:23 PDT Modified files: lib/libc/net getaddrinfo.c Log: sync with kame. - better return code. from enami@netbsd - do not use "class" as variable name. C++ guy had trouble with it. Revision ChangesPath 1.12 +50 -29src/lib/libc/net/getaddrinfo.c To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe cvs-all" in the body of the message Hmmm. Something definitely looks strange, 'cause since this morning if I do: telnet localhost (or telnet to ANY host, either in my host file or in DNS) I get: localhost: no address associated with name whereas a 'ping localhost' works perfectly fine (and so does a telnet 127.0.0.1) Any clues? PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/lib/libc/gen Makefile.inc
Alexander Langer wrote: alex2000/07/02 14:45:16 PDT Modified files: lib/libc/gen Makefile.inc Log: Add strunvisx.3 MLINK. Revision ChangesPath 1.65 +2 -2 src/lib/libc/gen/Makefile.inc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe cvs-all" in the body of the message This breaks installworld, as the following diff: +MLINKS+=unvis.3 strunvis.3 strunvisx.3 should have been: +MLINKS+=unvis.3 strunvis.3 unvis.3 strunvisx.3 PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Boot Oddities
"Dampure, Pierre Y." wrote: Apologies if this ought to be in -questions rather than -current, but since I first noticed the problem on 5.0-2621-CURRENT... The above snapshot was installed on a brand new system (OR840, 2x733EB, 512MB RDRAM, 1xAHA2940UW, 4x9.1Gb Barracuda). The disk organisation is as follows: da0:one NTFS partition (W2K), FreeBSD multiboot MBR installed da1:fully dedicated, FreeBSD, has the root partition (da1s1a) da2:fully dedicated, FreeBSD da3:fully dedicated, FreeBSD Since this is a recent snapshot, I assume it defaults to use loader(8). When the system boots, I get the usual F1/F5 choice, as follows: F1 ?? F5 Drive 1 Default: F5 Selecting F5 (or letting the timer run to completion) leads to the following: Disk error 0x1 (lba=0xe0040) No /boot/loader FreeBSD/i386 BOOT Default: 1:da(1,a)/kernel boot: then proceeding to load /kernel, rather than /boot/loader (which is why I posted about problems with nlist (aka top/vmstat/systat) a few days ago). If I hit a key early enough, I get: FreeBSD/i386 BOOT Default: 1:da(1,a)/boot/loader boot: Hitting RETURN then leads to: Disk error 0x1 (lba=0xe0040) No /boot/loader after which I need to enter 1:da(1,a)/kernel to proceed. Needless to say, /boot/loader IS on da1s1a (with its usual assortment of .rc and .conf in required places), which is why I am a bit surprised. Can anyone shed a light on the above? I now know how to get around the nlist issue, but this is not the recommended method... Configuration files available upon request. Best Regards, PYD FWIW, I DID have a look at the archives before posting... the only thread that looks remotely related is: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=3392426+3394340+/usr/local/www/db/text/1999/freebsd-current/19990509.freebsd-current but this is in the case of IDE drives, not SCSI... CAM reports my drives as having a (255H 63S/T 1106C) geometry, so even with a 512Mb root partition I am still under the 1023 cylinders limit (if even applicable to SCSI devices). Best Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl ...
"George W. Dinolt" wrote: I have found that the following small diff to /usr/src/Makefile.inc1 allows the buildworld to proceed: It breaks further down the line when building /usr/src/gnu/usr.bin/perl/perl, with the following message: lib/auto/DynaLoader/DynaLoader.a(DynaLoader.o): In function `SaveError': DynaLoader.o(.text+0x1e2): undefined reference to `Perl_vmess' This is with PERL_THREADED=true. PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Boot Oddities
Apologies if this ought to be in -questions rather than -current, but since I first noticed the problem on 5.0-2621-CURRENT... The above snapshot was installed on a brand new system (OR840, 2x733EB, 512MB RDRAM, 1xAHA2940UW, 4x9.1Gb Barracuda). The disk organisation is as follows: da0:one NTFS partition (W2K), FreeBSD multiboot MBR installed da1:fully dedicated, FreeBSD, has the root partition (da1s1a) da2:fully dedicated, FreeBSD da3:fully dedicated, FreeBSD Since this is a recent snapshot, I assume it defaults to use loader(8). When the system boots, I get the usual F1/F5 choice, as follows: F1 ?? F5 Drive 1 Default: F5 Selecting F5 (or letting the timer run to completion) leads to the following: Disk error 0x1 (lba=0xe0040) No /boot/loader FreeBSD/i386 BOOT Default: 1:da(1,a)/kernel boot: then proceeding to load /kernel, rather than /boot/loader (which is why I posted about problems with nlist (aka top/vmstat/systat) a few days ago). If I hit a key early enough, I get: FreeBSD/i386 BOOT Default: 1:da(1,a)/boot/loader boot: Hitting RETURN then leads to: Disk error 0x1 (lba=0xe0040) No /boot/loader after which I need to enter 1:da(1,a)/kernel to proceed. Needless to say, /boot/loader IS on da1s1a (with its usual assortment of .rc and .conf in required places), which is why I am a bit surprised. Can anyone shed a light on the above? I now know how to get around the nlist issue, but this is not the recommended method... Configuration files available upon request. Best Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with nlist on -current?
Bernd Luevelsmeyer wrote: Dampure, Pierre Y. wrote: I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB RDRAM) and had problems with top / systat / vmstat all failing after reporting problems with nlist: [...] At a guess, you don't use /boot/loader? The loader seems to be no longer optional, see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=17422 This problem has been discussed several times in the "questions" mailing list, and R. Ermilov kindly mailed 2 patches: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1186602+1196206+/usr/local/www/db/text/2000/freebsd-questions/2409.freebsd-questions (While I'm at it, may I suggest that the patches be committed? I'm using them for more than a month now on 4.0-Stable, and they work just fine.) My system has 4 SCSI disks, W2K on disk 0, FreeBSD on 1, 2 and 3 (FreeBSD Multiboot installed on disk 0; disks 1, 2 and 3 all in dedicated mode). At boot time, boo2 throws out a 'No /boot/loader' messages, then proceeds to load the kernel normally. So... I guess indeed I do not use /boot/loader, though not of my own will. Thanks for the pointers! PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Problems with nlist on -current?
I installed 5.0-2621-CURRENT on a new system (OR840, 2x733EB, 512MB RDRAM) and had problems with top / systat / vmstat all failing after reporting problems with nlist: When using top: top: nlist failed When using systat: systat: nlist: can't find following symbols: _ccpu _fscale When using vmstat: vmstat: undefined symbols: _kmemstatistics _bucket _zlist Later CVsup did not cure the issue. The problems happen regardless of the kernel used (original GENERIC, recompiled GENERIC, custom UP or custom MP) Any clues? PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Vendor import of Perl 5.6
Apologies if this has already been reported, but `make world` is currently failing when trying to generate Config.pm for the newly imported Perl 5.6 (failure at line 20 of configpm) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
