Re: Copying kernel and OS
It should work fine. You need to preserve mod and access times as well as flags and permissions. If you are going to do this on a repeated basis, I'd look into something like cvsup or rsync, maybe even mirror, to keep the slow machines directory structures in sync rather than a cp -Rp. Paul. Jack Raats wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. *** Is it also possible to scp both directories to the slow machine? JAck - Original Message - From: Stephen Montgomery-Smith [EMAIL PROTECTED] To: Jack Raats [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org; FreeBSD Stable freebsd-stable@freebsd.org Sent: Wednesday, December 07, 2005 10:29 PM Subject: Re: Copying kernel and OS Jack Raats wrote: I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. Jack I do something like this. I build on the fast machine, and then use NFS to allow the slow machine to access /usr/src and /usr/obj. I have found that it is important to preserve the names of the directories, so that they are also called /usr/src and /usr/obj on the slow machine. Then I just do mergemaster, make installworld, make installkernel (in the appropriate order) on the slow machine, and it works like a charm. The entries in fstab are like this: hub2:/usr/obj/usr/objnfs rw,bg,noauto0 0 hub2:/usr/src/usr/srcnfs rw,bg,noauto0 0 where hub2 is the name of the fast machine. In /etc/exports on hub2 I have something like this /usr -maproot=root -alldirs -network 10.0.0.0 -mask 255.255.255.0 (here 10.0.0.0 is the IP addresses of my LAN) and in /etc/rc.conf on hub2 I have some lines like nfs_server_enable=YES rpcbind_enable=YES Then on the slow machine I simply type mount /usr/src mount /usr/obj -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make own freebsd distro
Way back in the, I'd have to guess, 2.2.8 days. I made my own distro on CD, for my multiple desktops. It was a boot floppy (I think I had the CD boot) and a script to partition, newfs, etc. the disk, and then do a restore from the dumps I made of the template machine. Then the script went through setting the hostname, and such, in the file that was replaced by rc.conf. /etc/sysconfig maybe? It was a long time ago. It wasn't particularly fast, but it worked. iv gan wrote: Try man sysinstall. You can easily script the sysinstall and create an install.cfg and personalize the installation including packages, config files, users to add, etc. It is a bit tricky but it is enough powerfll for your needs I think so. So first try a mfsroot file. Then mount it on your machine mdconfig -a -t vnode -u 0 -f /path/to/mfsroot mount /dev/md0 /mnt/mfs In /mnt/mfs then you have to create install.cfg there is an example of that file somewhere on your disk, don't remember anymore. Then put back the mfsroot in /your/disk/to/burn/boot/ Then mkisofs it and cdrecord it etc. And that's all. Another solution is to set up a installation server. This is also covered by sysinstall. A nice howto is situated at http://www.tnpi.biz/computing/freebsd/pxe-netboot.shtml. What else. If you really need to put in on a cd you can probably use an emulator like qemu to see if things work before burn etc.. good luck Ivo On 8/25/05, Damon Blom [EMAIL PROTECTED] wrote: Hi I have a current-freebsd 7.0 amd64 system on my Presario 3000. Is there any way I can make a freebsd distro cd (disk 1 and disk2 ) of my system so I can easily put it on other presarios or easily reinstall it back on my notebook after disk crash? Thank's Damon ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
HP Proliant DL320
I just got a Proliant DL320 put on my desk to configure for a tcpdump monitoring project. The cooling fans run at full speed and as loud as can be. I see that there is hpapm or cpqhealth programs for Windows, and looks like Red Hat and Suse, that will watch the temperature and turn down the fans to needed levels. Is there anything to control these things for FreeBSD? I installed 5-4 from DVD and will be updating via source today. Man, it's fast compared to the old stuff I'm used to. Paul. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
serial console
I'm trying to get a HP Vectra up without keyboard or monitor with Serial A as the console. I looked in the Handbook and FAQ, all it talks about is for an install. The worst part is, I have 1 machine running this way (Intel motherboard) and I remember I tested doing that on an identical Vectra. The intel box is running 4.11-Stable (I haven't got around to upgrading yet, weekends are tight). The Vectra is 5.4-Stable (cvsuped yesterday). What I've tried (loader.conf) doesn't seem to work. Thanks, Paul. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unable to mount secondary hard disks now
I'm not entirely sure, but it sure looks like da1s4c to me. Why is one drive da0c and the other da1s1c? How did you set them up? Shea Frederick wrote: Im running FreeBSD 5.3, its an almost fresh install. Its been running for about 7 days now. I have an internal IDE drive that the OS runs from, then I have two external firewire drives (da0, da1) that are only used as Samba shares. This morning i found that one of the firewire drives are no longer mounted (da1), this might have happened when I uninstalled Samba 2.x and installed 3.x yesterday, then rebooted. but im not sure, because i didnt check to see if the drive was still mounted after the reboot. So i figured i would just mount it again (even though da1 in the fstab) FileServer# mount /dev/da1s1c /mnt/jabba mount: /dev/da1s1c on /mnt/jabba: incorrect super block So now im not realy sure what to do, this drive was working perfectly before the reboot. someone told me to run fsck on the drive, but that gives me the following error. FileServer# fsck /dev/da1s1c ** /dev/da1s1c Cannot find file system superblock /dev/da1s1c: NOT LABELED AS A BSD FILE SYSTEM (unused) here is what fdisk returns... FileServer# fdisk /dev/da1s1c *** Working on device /dev/da1s1c *** parameters extracted from in-core disklabel are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 5 (24 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 Here are the relevant lines from my fstab... /dev/da0c /mnt/yoda ufs rw 2 2 /dev/da1s1c /mnt/jabba ufs rw 2 2 Thanks in advance -Shea -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum trouble on 5.3-Stable
I upgraded to 5.3 on one system a while ago. And when it boots up vinum panics the system on startup with this message: panic: unmount: dangling vnode I found that if I boot in single user mode and mount / to make it rw, then start vinum, everything is fine. I just patched the kernel for the sendfile bug so this has come up again. Is this an order of execution problem? Do I change when vinum is started? What the solution. I'm happy (apart from this) with 5.x and plan to upgrade my main server to 5.x. Now that I got a good handle (I think on bind 9). Thanks, Paul. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
