Upgrading from 4 to 6
With the EOL of FreeBSD 4.X coming close, I'm in the process of upgrading to 6.2. According to http://www.freebsd.org/releases/5.4R/migration-guide.html#UPGRADE Probably the most straightforward approach is that of ``backup everything, reformat, reinstall, and restore user data''. However, things are not that simple, because a system typically has many configured files, other than user data. I'm currently setting up a new 6.2 system on a VMWare host trying to mirror the existing system. After a clean installation of 6.2, I also installed ports and some CPAN modules. I then configured the apache configuration files, the sendmail local host file, the named masters and configuration file, /etc/inetd.conf, /etc/rc.conf, and the imap certificates. Just before the switchoover, I'll also also need to copy the users parts of /etc/passwd* and /etc/group, the mail aliases, the httpd logs, the user mailboxes in /var/mail, and, of course, /home. However, I have an uneasy feeling I may miss copying/adjusting some files. Although I've documented the changes I made to the original system from 2002 onward, the documentation is a 1000-line file and I can't be sure it is 100% complete or that I will spot all required changes. Is there a checklist or a procedure for restoring a 4.X system configuration to a system running 6.X? Am I missing any obvious files or directories I should copy over? Diomidis Spinellis - http://www.spinellis.gr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: groff alternative?
Emanuel Strobl wrote: I'm using NO_CXX in my make.conf to strip down the base system to ~50MB including man pages. The only problem is that groff is missing if I don't build c++, and even if I build groff itself and the needed libstdc++ it costs me about 10MB. If I just skip NO_CXX it's only 500k more, so I moved my patches to /dev/null. Does anybody know any alternative for the groff part to view man pages simply with the man command? It's horrible that the filter needs more space than all the manpages itself! Have you considered preformatting the manual pages on the development system, and copying over the pages into /usr/share/man/cat* of the shrinked-down system? And of course, even if I decide to leave system man pages outside the flash card I still may want to read man pages of installed packages (which is another mountpoint on my installation, so there may be no space limit, depending on the card and additional drives) Again, it appears your shrinked-down system has access to a more powerful machine. You could modify man to run groff on the remote machine. -- Diomidis - dds@ - http://www.spinellis.gr ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sound driver hangs when writing to the system console
For a couple of months I've been trying to crack a puzzling problem. After upgrading from 4.1 to 4.6 (and now to 4.7) my on-board sound card would pause or die after playing for approximately 20 minutes with a message: pcm0:play:0: play interrupt timeout, channel dead I have now managed to isolate the timing dependency: the problem comes from writing to the system console (which a cron job apparently did every 20 minutes). So a command like: cat /usr/share/dict/words /dev/console will immediately break the sound driver with the same message. I have dissabled PnP from the BIOS and locked the card to two different IRQs. I have also dissabled the VGA IRQ and even removed entirely the VGA card (the box works as an appliance), but none of these measures helped. The sound hardware is an on-board WSS-compatible CS4231-based device on an Intel Triton motherboard (Pentium 150MHz) running the latest BIOS update. The box has no local storage booting remotely from another FreeBSD box through Etherboot. I am attaching the output of uname, dmesg, and pciconf. Any ideas or hints on what try would be really appreciated. Diomidis - http://www.dmst.aueb.gr/dds office# uname -a FreeBSD office 4.7-RELEASE-p2 FreeBSD 4.7-RELEASE-p2 #12: Thu Dec 5 23:18:43 EET 2002 dds@spiti:/vol/obj/vol/src/sys/OFFICE i386 office# dmesg Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE-p2 #12: Thu Dec 5 23:18:43 EET 2002 dds@spiti:/vol/obj/vol/src/sys/OFFICE Timecounter i8254 frequency 1193182 Hz CPU: Pentium/P54C (149.69-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 33554432 (32768K bytes) avail memory = 29765632 (29068K bytes) Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 ATA controller port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 orm0: Option ROMs at iomem 0xc8000-0xcbfff,0xcc000-0xc,0xea000-0xebfff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ed0 at port 0x240-0x25f iomem 0xd8000 irq 9 on isa0 ed0: address 00:00:e8:32:81:e8, type NE2000 (16 bit) pcm0: CS4231 at port 0x530-0x537,0x538-0x539,0xf8c-0xf94,0xe0e irq 11 drq 0 flags 0xa111 on isa0 bootpc_init: wired to interface 'ed0' Sending DHCP Discover packet from interface ed0 (00:00:e8:32:81:e8) Received DHCP Offer packet on ed0 from 192.168.136.1 (accepted) (no root path) Sending DHCP Request packet from interface ed0 (00:00:e8:32:81:e8) Received DHCP Ack packet on ed0 from 192.168.136.1 (accepted) (got root path) ed0 at 192.168.136.2 server 192.168.136.1 boot file kernel subnet mask 255.255.255.0 rootfs 192.168.136.1:/ Adjusted interface ed0 Mounting root from nfs: NFS ROOT: 192.168.136.1:/ pcm0:play:0: play interrupt timeout, channel dead office# pciconf -lv chip0@pci0:0:0: class=0x06 card=0x chip=0x12508086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82439HX System Controller (TXC)' class= bridge subclass = HOST-PCI isab0@pci0:7:0: class=0x060100 card=0x chip=0x70008086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 PCI-to-ISA Bridge (Triton II)' class= bridge subclass = PCI-ISA atapci0@pci0:7:1: class=0x010180 card=0x chip=0x70108086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82371SB PIIX3 IDE Interface (Triton II)' class= mass storage subclass = ATA To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Process inexplicably blocks after upgrading to 4.7-RELEASE
After upgrading a diskless client and the respective NFS server from FreeBSD 4.1 to FreeBSD 4.6 (and now 4.7) I have been having trouble with a process on a client blocking for about 15 seconds every 10-20 minutes. The process is an MP3 player (mpg123), so I can not really afford to have it block for that long. The mpg123 process runs on the diskless client, reading data from the server and playing the music locally. Every so often mpg123 stops playing music for about 15 seconds. An strace(1) on the mpg123 process shows it waiting for a write(2) on /dev/dsp to return. If however I break into the kernel debugger on the client and trace the mpg123 stack frame I always find it blocked in the following sequence: sbwait(...) soreceive(...) nfs_send(...) nfs_reply(...) nfs_request(...) nfs_readrpc(...) nfs_getpages(...) vnode_pager_freepage(...) vm_fault(...) trap(...) trap(...) (at that point the stack trace stops due to a page fault while in kernel mode). The problem first manifested itself when the client and server were upgraded from FreeBSD 4.1-RELEASE to 4.6.2-RELEASE-p2. The problem also occurs when the client runs 4.7-RELEASE-p1. On the client side the network and ethernet card are configured as follows: ed0 at port 0x240-0x25f iomem 0xd8000 irq 9 on isa0 ed0: address 00:00:e8:32:81:e8, type NE2000 (16 bit) pcm0: CS4231 at port 0x530-0x537,0x538-0x539,0xf8c-0xf94,0xe0e irq 10 drq 1 flags 0xa110 on isa0 No messages are logged on the client side; on the server I found a few nfsd send error 64 (EHOSTDOWN) messages, but I think these were generated after staying too long in the kernel debugger. I would really appreciate any ideas on how to resolve this problem, or suggestions on how to further attack it. Thanks, Diomidis - http://www.dmst.aueb.gr/dds/ mailto:dds;aueb.gr To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
