Re: portsnap failing
On Monday 27 February 2006 23:46, Donald J. O'Neill wrote: That file you were missing, lives in /var/db/portsnap/files/ , did you look there to see if it was there or not? No it's not there. The point is, portsnap should be fetching it but isn't. Did you do anything to the setup of portsnap? Did you somehow, happen to install portsnap from the ports system? No definitely not. One of the reasons I like FreeBSD 6 is because portsnap is in the base system. A dumb question I know, but it's got to be asked. did you make any changes to /etc/portsnap.conf? Nope- stock file. Just what portsnap files did you delete? The whole of /var/db/portsnap (well actually I just moved them, and put them back when the download from scratch failed). How did you use portsnap, any options when you ran it? portsnap fetch, plain and simple Just a funny thought: do you have defaultrouter=some IP address in /etc/rc.conf. No, I'm using DCHP. But the (low level) network is not an issue- the server is otherwise fully functional. One final thought, did portsnap ever work for you? *Possibly* not. On the test machine I installed, then definitely not - it failed first time. However, the other server I used ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing ... maybe more serious issue with RAID?
Meh... I tried deleting the portsnap files again and it worked :-S Took a long time when it got to 97% of the snapshot but it worked this time. Bloody computers... Still I have yet to see whether it'll work later when I (or cron) run portsnap to fetch the patches. Ashley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Saturday 25 February 2006 03:07, Donald J. O'Neill wrote: Why are you deleting the portsnap files. That's a 39 MB file that you have to download everytime you do that. The idea is to just download the patches necessary to update the ports tree after 'portsnap fetch', 'portsnap install' has been run once. After that, all you need to do is run 'portsnap fetch update', you'll get plenty of action from that. I think by now you're going to have to remove the ports tree and start over. Why not do it an easier way. I deleted the portsnap files because the incremental update didn't work, so I wanted to know if it would work from scratch. I'm not in a habit of deleting them every time I update the ports tree! For some reason though, neither works now, although they fail in (apparently) different ways. Ashley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Friday 24 February 2006 22:56, Colin Percival wrote:
Go on, humour me and run that bad boy with -x!
sh -x /usr/sbin/portsnap fetch
Even better, throw in the --debug flag as well:
sh -x /usr/sbin/portsnap --debug fetch
I've had a quick look through and it's obviously failing because it's missing
a file but I can't work out why it isn't getting it. When I run portsnap
fetch with no portsnap files it only gets to 97% complete. What's really
strange is how it fails on two amd64 machines but succeeds on two i386
machines. I thought there was absolutely no difference.
I'd be extremely grateful for any help on this one... it's a right bind not
being able to fetch updates.
Ashley
+ export
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/administrator/bin
+ get_params fetch
+ init_params
+ KEYPRINT=
+ EXTRACTPATH=
+ WORKDIR=
+ PORTSDIR=
+ CONFFILE=
+ COMMAND=
+ COMMANDS=
+ QUIETREDIR=
+ QUIETFLAG=
+ STATSREDIR=
+ XARGST=
+ NDEBUG=
+ DDSTATS=
+ INDEXONLY=
+ SERVERNAME=
+ parse_cmdline fetch
+ [ 1 -gt 0 ]
+ COMMANDS= fetch
+ shift
+ [ 0 -gt 0 ]
+ [ -z fetch ]
+ sanity_conffile
+ [ ! -z ]
+ default_conffile
+ [ -z ]
+ CONFFILE=/etc/portsnap.conf
+ parse_conffile
+ [ -r /etc/portsnap.conf ]
+ eval _=$KEYPRINT
+ _=
+ [ -z ]
+ grep ^KEYPRINT= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ eval _=$WORKDIR
+ _=
+ [ -z ]
+ tail -1
+ grep ^WORKDIR= /etc/portsnap.conf
+ cut -f 2- -d =
+ eval WORKDIR=
+ WORKDIR=
+ eval _=$PORTSDIR
+ _=
+ [ -z ]
+ grep ^PORTSDIR= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval PORTSDIR=
+ PORTSDIR=
+ eval _=$SERVERNAME
+ _=
+ [ -z ]
+ grep ^SERVERNAME= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval SERVERNAME=portsnap.FreeBSD.org
+ SERVERNAME=portsnap.FreeBSD.org
+ default_params
+ _QUIETREDIR=/dev/null
+ _QUIETFLAG=-q
+ _STATSREDIR=/dev/stdout
+ _WORKDIR=/var/db/portsnap
+ _PORTSDIR=/usr/ports
+ _NDEBUG=-n
+ eval _=$QUIETREDIR
+ _=
+ eval __=$_QUIETREDIR
+ __=/dev/null
+ [ -z ]
+ eval QUIETREDIR=/dev/null
+ QUIETREDIR=/dev/null
+ eval _=$QUIETFLAG
+ _=
+ eval __=$_QUIETFLAG
+ __=-q
+ [ -z ]
+ eval QUIETFLAG=-q
+ QUIETFLAG=-q
+ eval _=$STATSREDIR
+ _=
+ eval __=$_STATSREDIR
+ __=/dev/stdout
+ [ -z ]
+ eval STATSREDIR=/dev/stdout
+ STATSREDIR=/dev/stdout
+ eval _=$WORKDIR
+ _=
+ eval __=$_WORKDIR
+ __=/var/db/portsnap
+ [ -z ]
+ eval WORKDIR=/var/db/portsnap
+ WORKDIR=/var/db/portsnap
+ eval _=$PORTSDIR
+ _=
+ eval __=$_PORTSDIR
+ __=/usr/ports
+ [ -z ]
+ eval PORTSDIR=/usr/ports
+ PORTSDIR=/usr/ports
+ eval _=$NDEBUG
+ _=
+ eval __=$_NDEBUG
+ __=-n
+ [ -z ]
+ eval NDEBUG=-n
+ NDEBUG=-n
+ cmd_fetch
+ [ ! -t 0 ]
+ fetch_check_params
+ uname -r
+ export HTTP_USER_AGENT=portsnap (fetch, 6.0-RELEASE)
+ _SERVERNAME_z=SERVERNAME must be given via command line or configuration file.
+ _KEYPRINT_z=Key must be given via -k option or configuration file.
+ _KEYPRINT_bad=Invalid key fingerprint:
+ _WORKDIR_bad=Directory does not exist or is not writable:
+ [ -z portsnap.FreeBSD.org ]
+ [ -z 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 ]
+ echo 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ grep -qE ^[0-9a-f]{64}$
+ [ -d /var/db/portsnap -a -w /var/db/portsnap ]
+ cd /var/db/portsnap
+ BSPATCH=/usr/bin/bspatch
+ SHA256=/sbin/sha256
+ PHTTPGET=/usr/libexec/phttpget
+ fetch_run
+ fetch_pick_server
+ echo -n Looking up portsnap.FreeBSD.org mirrors...
Looking up portsnap.FreeBSD.org mirrors...+ host -t srv
_http._tcp.portsnap.FreeBSD.org
+ grep -E ^_http._tcp.portsnap.FreeBSD.org has SRV record
+ cut -f 5,6,8 -d
+ wc -l
+ [ 2 -eq 0 ]
+ cut -f 1 -d serverlist
+ sort -n
+ head -1
+ SRV_PRIORITY=1
+ SRV_WSUM=0
+ read X
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_WSUM=10
+ read X
+ echo 1 10 portsnap1.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_WSUM=20
+ read X
+ [ 20 -eq 0 ]
+ SRV_W_ADD=0
+ jot -r 1 1 20
+ SRV_RND=6
+ read X
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_W=10
+ [ 6 -le 10 ]
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 3 -d
+ SERVERNAME=portsnap2.freebsd.org.
+ break
+ echo using portsnap2.freebsd.org.
using portsnap2.freebsd.org.
+ fetch_key
+ [ -r pub.ssl ]
+ /sbin/sha256 -q pub.ssl
+ [ 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 =
9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 ]
+ return
+ [ -d files -a -r tag -a -r INDEX -a -r tINDEX ]
+ fetch_update
+ rm -f patchlist diff OLD NEW filelist INDEX.new
+ cut -f 2 -d |
+ OLDSNAPSHOTDATE=1139992217
+ cut -f 3 -d |
+
OLDSNAPSHOTHASH=4c82c29ee7d6bc4a9085cd948c9c2f08fe81b1305b52e4211ab28100cce125a1
+ fetch_tag latest
+ rm -f snapshot.ssl tag.new
+ echo -n Fetching snapshot tag...
Fetching snapshot tag... + fetch -q
Re: portsnap failing
On Friday 24 February 2006 22:56, Colin Percival wrote:
Go on, humour me and run that bad boy with -x!
sh -x /usr/sbin/portsnap fetch
Even better, throw in the --debug flag as well:
sh -x /usr/sbin/portsnap --debug fetch
I've had a quick look through and it's obviously failing because it's missing
a file but I can't work out why it isn't getting it. When I run portsnap
fetch with no portsnap files it only gets to 97% complete. What's really
strange is how it fails on two amd64 machines but succeeds on two i386
machines. I thought there was absolutely no difference.
I'd be extremely grateful for any help on this one... it's a right bind not
being able to fetch updates.
Ashley
+ export
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/home/administrator/bin
+ get_params fetch
+ init_params
+ KEYPRINT=
+ EXTRACTPATH=
+ WORKDIR=
+ PORTSDIR=
+ CONFFILE=
+ COMMAND=
+ COMMANDS=
+ QUIETREDIR=
+ QUIETFLAG=
+ STATSREDIR=
+ XARGST=
+ NDEBUG=
+ DDSTATS=
+ INDEXONLY=
+ SERVERNAME=
+ parse_cmdline fetch
+ [ 1 -gt 0 ]
+ COMMANDS= fetch
+ shift
+ [ 0 -gt 0 ]
+ [ -z fetch ]
+ sanity_conffile
+ [ ! -z ]
+ default_conffile
+ [ -z ]
+ CONFFILE=/etc/portsnap.conf
+ parse_conffile
+ [ -r /etc/portsnap.conf ]
+ eval _=$KEYPRINT
+ _=
+ [ -z ]
+ grep ^KEYPRINT= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ eval _=$WORKDIR
+ _=
+ [ -z ]
+ tail -1
+ grep ^WORKDIR= /etc/portsnap.conf
+ cut -f 2- -d =
+ eval WORKDIR=
+ WORKDIR=
+ eval _=$PORTSDIR
+ _=
+ [ -z ]
+ grep ^PORTSDIR= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval PORTSDIR=
+ PORTSDIR=
+ eval _=$SERVERNAME
+ _=
+ [ -z ]
+ grep ^SERVERNAME= /etc/portsnap.conf
+ cut -f 2- -d =
+ tail -1
+ eval SERVERNAME=portsnap.FreeBSD.org
+ SERVERNAME=portsnap.FreeBSD.org
+ default_params
+ _QUIETREDIR=/dev/null
+ _QUIETFLAG=-q
+ _STATSREDIR=/dev/stdout
+ _WORKDIR=/var/db/portsnap
+ _PORTSDIR=/usr/ports
+ _NDEBUG=-n
+ eval _=$QUIETREDIR
+ _=
+ eval __=$_QUIETREDIR
+ __=/dev/null
+ [ -z ]
+ eval QUIETREDIR=/dev/null
+ QUIETREDIR=/dev/null
+ eval _=$QUIETFLAG
+ _=
+ eval __=$_QUIETFLAG
+ __=-q
+ [ -z ]
+ eval QUIETFLAG=-q
+ QUIETFLAG=-q
+ eval _=$STATSREDIR
+ _=
+ eval __=$_STATSREDIR
+ __=/dev/stdout
+ [ -z ]
+ eval STATSREDIR=/dev/stdout
+ STATSREDIR=/dev/stdout
+ eval _=$WORKDIR
+ _=
+ eval __=$_WORKDIR
+ __=/var/db/portsnap
+ [ -z ]
+ eval WORKDIR=/var/db/portsnap
+ WORKDIR=/var/db/portsnap
+ eval _=$PORTSDIR
+ _=
+ eval __=$_PORTSDIR
+ __=/usr/ports
+ [ -z ]
+ eval PORTSDIR=/usr/ports
+ PORTSDIR=/usr/ports
+ eval _=$NDEBUG
+ _=
+ eval __=$_NDEBUG
+ __=-n
+ [ -z ]
+ eval NDEBUG=-n
+ NDEBUG=-n
+ cmd_fetch
+ [ ! -t 0 ]
+ fetch_check_params
+ uname -r
+ export HTTP_USER_AGENT=portsnap (fetch, 6.0-RELEASE)
+ _SERVERNAME_z=SERVERNAME must be given via command line or configuration file.
+ _KEYPRINT_z=Key must be given via -k option or configuration file.
+ _KEYPRINT_bad=Invalid key fingerprint:
+ _WORKDIR_bad=Directory does not exist or is not writable:
+ [ -z portsnap.FreeBSD.org ]
+ [ -z 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 ]
+ echo 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330
+ grep -qE ^[0-9a-f]{64}$
+ [ -d /var/db/portsnap -a -w /var/db/portsnap ]
+ cd /var/db/portsnap
+ BSPATCH=/usr/bin/bspatch
+ SHA256=/sbin/sha256
+ PHTTPGET=/usr/libexec/phttpget
+ fetch_run
+ fetch_pick_server
+ echo -n Looking up portsnap.FreeBSD.org mirrors...
Looking up portsnap.FreeBSD.org mirrors...+ host -t srv
_http._tcp.portsnap.FreeBSD.org
+ grep -E ^_http._tcp.portsnap.FreeBSD.org has SRV record
+ cut -f 5,6,8 -d
+ wc -l
+ [ 2 -eq 0 ]
+ cut -f 1 -d serverlist
+ sort -n
+ head -1
+ SRV_PRIORITY=1
+ SRV_WSUM=0
+ read X
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_WSUM=10
+ read X
+ echo 1 10 portsnap1.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_WSUM=20
+ read X
+ [ 20 -eq 0 ]
+ SRV_W_ADD=0
+ jot -r 1 1 20
+ SRV_RND=6
+ read X
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 2 -d
+ SRV_W=10
+ SRV_W=10
+ [ 6 -le 10 ]
+ echo 1 10 portsnap2.freebsd.org.
+ cut -f 3 -d
+ SERVERNAME=portsnap2.freebsd.org.
+ break
+ echo using portsnap2.freebsd.org.
using portsnap2.freebsd.org.
+ fetch_key
+ [ -r pub.ssl ]
+ /sbin/sha256 -q pub.ssl
+ [ 9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 =
9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 ]
+ return
+ [ -d files -a -r tag -a -r INDEX -a -r tINDEX ]
+ fetch_update
+ rm -f patchlist diff OLD NEW filelist INDEX.new
+ cut -f 2 -d |
+ OLDSNAPSHOTDATE=1139992217
+ cut -f 3 -d |
+
OLDSNAPSHOTHASH=4c82c29ee7d6bc4a9085cd948c9c2f08fe81b1305b52e4211ab28100cce125a1
+ fetch_tag latest
+ rm -f snapshot.ssl tag.new
+ echo -n Fetching snapshot tag...
Fetching snapshot tag... + fetch -q
Re: portsnap failing
On Monday 27 February 2006 11:00, Ashley Moran wrote: the same things four times Does anyone else suffer from a spam-happy Kontact? :D My messages go into the outbox but don't leave it until KMail has fired off at least 500 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Monday 27 February 2006 03:19, Ashley Moran wrote: On Saturday 25 February 2006 03:07, Donald J. O'Neill wrote: Why are you deleting the portsnap files. That's a 39 MB file that you have to download everytime you do that. The idea is to just download the patches necessary to update the ports tree after 'portsnap fetch', 'portsnap install' has been run once. After that, all you need to do is run 'portsnap fetch update', you'll get plenty of action from that. I think by now you're going to have to remove the ports tree and start over. Why not do it an easier way. I deleted the portsnap files because the incremental update didn't work, so I wanted to know if it would work from scratch. I'm not in a habit of deleting them every time I update the ports tree! For some reason though, neither works now, although they fail in (apparently) different ways. Ashley That file you were missing, lives in /var/db/portsnap/files/ , did you look there to see if it was there or not? Did you do anything to the setup of portsnap? Did you somehow, happen to install portsnap from the ports system? A dumb question I know, but it's got to be asked. did you make any changes to /etc/portsnap.conf? Just what portsnap files did you delete? How did you use portsnap, any options when you ran it? Just a funny thought: do you have defaultrouter=some IP address in /etc/rc.conf. One final thought, did portsnap ever work for you? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On 23/2/06 11:33, Ashley Moran [EMAIL PROTECTED] wrote: I'm trying to update my ports tree on a 6.0-RELEASE/amd64 machine. I get this error: Updating from Wed Feb 15 08:30:17 GMT 2006 to Thu Feb 23 10:20:03 GMT 2006. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... /usr/sbin/portsnap: cannot open f1777c019669546744ef448c17531bdd125884253a6bf4b73f6e77001d7a0b12.gz: No such file or directory If I delete the portsnap files and try to fetch a new snapshot, I get this error instead: Fetching snapshot generated at Thu Feb 23 03:09:19 GMT 2006: f4b0454e7bce8a4decdb9190e22b8325a966e92005df5f 97% of 39 MB 118 kBps 00m08s fetch: transfer timed out Neither of my i386 boxes have this problem. Does anyone know where the issue lies? Go on, humour me and run that bad boy with -x! sh -x /usr/sbin/portsnap fetch Ceri -- That must be wonderful! I don't understand it at all. -- Moliere ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
Ceri Davies wrote: On 23/2/06 11:33, Ashley Moran [EMAIL PROTECTED] wrote: Updating from Wed Feb 15 08:30:17 GMT 2006 to Thu Feb 23 10:20:03 GMT 2006. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... /usr/sbin/portsnap: cannot open f1777c019669546744ef448c17531bdd125884253a6bf4b73f6e77001d7a0b12.gz: No such file or directory Go on, humour me and run that bad boy with -x! sh -x /usr/sbin/portsnap fetch Even better, throw in the --debug flag as well: sh -x /usr/sbin/portsnap --debug fetch Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsnap failing
On Thursday 23 February 2006 05:33, Ashley Moran wrote: I'm trying to update my ports tree on a 6.0-RELEASE/amd64 machine. I get this error: Updating from Wed Feb 15 08:30:17 GMT 2006 to Thu Feb 23 10:20:03 GMT 2006. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... /usr/sbin/portsnap: cannot open f1777c019669546744ef448c17531bdd125884253a6bf4b73f6e77001d7a0b12.gz: No such file or directory If I delete the portsnap files and try to fetch a new snapshot, I get this error instead: Fetching snapshot generated at Thu Feb 23 03:09:19 GMT 2006: f4b0454e7bce8a4decdb9190e22b8325a966e92005df5f 97% of 39 MB 118 kBps 00m08s fetch: transfer timed out Neither of my i386 boxes have this problem. Does anyone know where the issue lies? Ashley Why are you deleting the portsnap files. That's a 39 MB file that you have to download everytime you do that. The idea is to just download the patches necessary to update the ports tree after 'portsnap fetch', 'portsnap install' has been run once. After that, all you need to do is run 'portsnap fetch update', you'll get plenty of action from that. I think by now you're going to have to remove the ports tree and start over. Why not do it an easier way. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: portsnap failing
I'm trying to update my ports tree on a 6.0-RELEASE/amd64 machine. I get this error: Updating from Wed Feb 15 08:30:17 GMT 2006 to Thu Feb 23 10:20:03 GMT 2006. Fetching 3 metadata patches.. done. Applying metadata patches... done. Fetching 3 metadata files... /usr/sbin/portsnap: cannot open f1777c019669546744ef448c17531bdd125884253a6bf4b73f6e77001d7a0b12.gz: No such file or directory If I delete the portsnap files and try to fetch a new snapshot, I get this error instead: Fetching snapshot generated at Thu Feb 23 03:09:19 GMT 2006: f4b0454e7bce8a4decdb9190e22b8325a966e92005df5f 97% of 39 MB 118 kBps 00m08s fetch: transfer timed out Neither of my i386 boxes have this problem. Does anyone know where the issue lies? Ashley I don't think ports have anything to do with branches, although some ports may not have an amd64-compatible to use. The make.conf tells what CPU to make for. I *may* be all wet though and would be happy to be corrected. I have no problem with portsnap - using FBSD-6.0 with builtin portsnap. Jack _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
