Re: Two NICs with one IP address each on the same subnet
On Wednesday 10 November 2004 02:57, Sean Peisert wrote: > I have a FreeBSD 5.x box with two NICs that I'd like > to set up on the same subnet. The purpose is to run > separate services on each NIC. I have the box set up > with my rc.conf containing the following lines: > > defaultrouter="..." > hostname="..." > ifconfig_xl0="inet ... netmask 255.255.255.224" > ifconfig_sk0="inet ... netmask 255.255.255.224 mtu > 9000" > > The router and IP addresses are all on the same > subnet, as I previously mentioned. Unfortunately, the > first IP address seems not to work (I can ssh to the > second, but not the first). Is there something > special I need to do to the routing to get this to > work? Anything to the kernel? > > Thanks, > Sean Can you imagine the routing loop? ;) -- Thanks, Josh Paetzel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Keeping Gnome at 2.6
Aloha If I do not wish to update to Gnome 2.8 what should I put in what config file to keep Gnome from trying to upgrade when I do a portupgrade? TIA Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NFS Serving Ext2 Partition
Does FreeBSD not support exporting the ext2 filesystem over NFS? I've tried the following lines one at a time and both / and /mnt worked, but /mnt/oldhome gave a permission denied error on the clients: / 192.168.1.2 192.168.1.3 /mnt 192.168.1.2 192.168.1.3 /mnt/oldhome 192.168.1.2 192.168.1.3 / and /mnt are both on the root partition formatted as UFS2 and /mnt/oldhome is a linux ext3 partition mounted as ext2. The server is running FreeBSD 5.3 and the clients are running FreeBSD 5.3 and Red Hat Linux 9. -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C pgpGluvaIinVF.pgp Description: PGP signature
Re: 5.3-release-i386-disc2.iso will not burn
j&kcooke wrote: I have downloaded both of the 5.3 i386 isos and the miniinstall iso, disc1 and the miniinstall burn an image, disc 2 does not. I downloaded disc2 from two additional ftp sites with the same result. There's probably nothing wrong with the image, I had the same issue with Nero. Check signature with some utility (md5, gpg...) just to be sure than burn with cdrecord (http://www.fokus.gmd.de/research/cc/ glone/employees/joerg.schilling/private/cdrecord.html): cdrecord -help cdrecord -scanbus cdrecord dev=1,1,0 5.3-release-i386-disc2.iso Put the value returned by -scanbus in the dev parameter upthere. I'd still like to know what is the problem with this ISO as I didn't find a Windows utility to handle it sucessfuly. Beside cdrecord :) Regards, Karel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.3 fails to shutdown properly
FreeBSD fails to sync buffers on shutdown and gives up requiring and fsck on reboot everytime. It first syncs vnodes which hit 0 after a short time, then while syncing buffers the count starts at 7 and stays there til it gives up trying to sync them. When I first go into single user mode, then umount all fs by hand I can run reboot and it will shutdown properly. Is there a way to increase the delay on shutdown or some other way to fix this problem? I'm using a clean install of FreeBSD 5.3. -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C pgpK7uOI7msiX.pgp Description: PGP signature
Purpose of FreeBSD 5.3 CDs
I'm trying to figure what all the various cd's for FreeBSD 5.3 are for. The miniinst cd is for installing the freebsd base system, basically everything installed with make installworld. disc1 is miniinst + packages + ports + src + doc? disc2 from past releases was just a rescue disk and a bit smaller than a full cd. Now it's a full sized cd, but still looks like a rescue disk. Is that all it is or does it include more packages, etc. for the install. bootonly is just a boot loader, plus maybe a shell? What it's main purpose? -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C pgpkKgCNp5zbl.pgp Description: PGP signature
gnomevfs2 build failure on 4.10
With gnome_update.sh and portinstall this same error comes up, with no make.conf,. Including after make rmconfig in devel/gnomevfs2 Fresh cvsup of ports, and removing the tarball. FreeBSD fortytwo.zapto.org 4.10-STABLE FreeBSD 4.10-STABLE #0: Sun Aug 15 23:13:02 EDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FORTYTWO i386 cc -DHAVE_CONFIG_H -I. -I. -I../.. -O -pipe -I.. -I../.. -I./imported/neon -I/usr/local/include/libxml2 -I/usr/local/include -D_THREAD_SAFE -DORBIT2=1 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/orbit-2.0 -I/usr/local/include/bonobo-activation-2.0 -I/usr/local/include/libbonobo-2.0 -I/usr/local/include/libxml2 -I/usr/local/include -I/usr/X11R6/include/gconf/2 -I/usr/include @INCLUDE_des@ -I../.. -I../.. -I../../libgnomevfs -I../../libgnomevfs -D_THREAD_SAFE -I/usr/local/include -O -pipe -c ne_request.c -Wp,-MD,.deps/ne_request.TPlo -fPIC -DPIC -o .libs/ne_request.o cc: cannot specify -o with -c or -S and multiple compilations gmake[3]: *** [ne_request.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/gnomevfs2/work/gnome-vfs-2.8.3/imported/neon' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/gnomevfs2/work/gnome-vfs-2.8.3/imported' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gnomevfs2/work/gnome-vfs-2.8.3' gmake: *** [all] Error 2 *** Error code 2 I do a make patch && cd work/gnome-vfs-2.8.3/ && ./configure I get this error (related?) checking libintl.h usability... no checking libintl.h presence... no checking for libintl.h... no checking for ngettext... no checking for ngettext in -lintl... no configure: error: Your Gettext installation doesn't seem to support ngettext to handle translation of plural forms. Please install GNU Gettext with the following installed. # pkg_info |grep gettext gettext-0.13.1_1GNU gettext package p5-gettext-1.03 Message handling functions php4-gettext-4.3.9 The gettext shared extension for php ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3-release-i386-disc2.iso will not burn
Karel Miklav wrote: > j&kcooke wrote: > >>I have downloaded both of the 5.3 i386 isos and the miniinstall iso, >>disc1 and the miniinstall burn an image, disc 2 does not. I downloaded >>disc2 from two additional ftp sites with the same result. > > > There's probably nothing wrong with the image, I had the same issue with > Nero. Check signature with some utility (md5, gpg...) just to be sure > than burn with cdrecord (http://www.fokus.gmd.de/research/cc/ > glone/employees/joerg.schilling/private/cdrecord.html): > > cdrecord -help > cdrecord -scanbus > cdrecord dev=1,1,0 5.3-release-i386-disc2.iso > > Put the value returned by -scanbus in the dev parameter upthere. > > I'd still like to know what is the problem with this ISO as I didn't > find a Windows utility to handle it sucessfuly. Beside cdrecord :) > > Regards, > Karel > I've successfully burned 5.3-RELEASE ISO disks 1, 2 and miniinst using Sonic Record now Version 6. The computer runs XP Pro SP1. No problems. The CDs read fine in a Windows machine, and I've used the miniinst CD to install V5.3. Jay O'Brien ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Do you need to dismount /usr to dump it?
On Tue, 09 Nov 2004 21:21:42 -0800, Matt Staroscik <[EMAIL PROTECTED]> wrote: > > If I boot to single-user mode (reboot, hit space, do boot -s) and dump /usr > to a file, I get read errors on a couple of blocks. > > Running fsck -y (also in single user of course) did not show a problem, but > it did not clear up the errors when I tried the dump again. > > I thought it was safe to dump /usr in single-user mode. Will I need to boot > off a CD or try another trick to get a clean dump of /usr? Or perhaps I am > not using the right fsck options? > > the dump command I used is: > dump 0af /someotherplace/filename.dump /usr > Try running the command: dump -0 -a -f /someplace/filedump /dev/ad0s1g (or whatever your /usr partition uses for /dev) I recall there also being a -L flag for live systems which you may want to try though I think it is only available in 5.x ? ...not to sure. Nelis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Purpose of FreeBSD 5.3 CDs
Loren M. Lang wrote: I'm trying to figure what all the various cd's for FreeBSD 5.3 are for. The miniinst cd is for installing the freebsd base system, basically everything installed with make installworld. disc1 is miniinst + packages + ports + src + doc? disc2 from past releases was just a rescue disk and a bit smaller than a full cd. Now it's a full sized cd, but still looks like a rescue disk. Is that all it is or does it include more packages, etc. for the install. bootonly is just a boot loader, plus maybe a shell? What it's main purpose? Sunday November 7: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=388874+0+current/freebsd-questions -- Jeremy Faulkner <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
