Re: Page fault, GEOM problem??
I'm coming in very late here, and only have some hearsay. But, a friend of mine has built a new hobby machine, with twin 160G drives on a 3Ware 8006, working as a stripe. He had a bunch of problems with stability of the drives until I gave him a couple of tiny (half size) jumpers, that he put on the drive. Smooth sailing since them. If needed, I can find what the jumpers did. But looking through the controllers doco should give you a clue. Johan Ström wrote: On 23 jan 2006, at 09.53, Michael S. Eubanks wrote: On Mon, 2006-01-23 at 06:43 +0100, Johan Ström wrote: Wish I could be of more help. :) Have you tried to toggle the sysctl dma flags? I've seen similar posts in the past with read timeouts caused from dma being enabled. # sysctl -a | grep dma ... hw.ata.ata_dma: 1 <=== Try turning this one off (1 ==> 0). hw.ata.atapi_dma: 1 ... Disabling DMA, wouldnt that give me pretty bad performance? -Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Paul Root "Few people know what to do when hula girls attack." - Sam, age 8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GDM problem
Two of us just went through it, last week. A number of tweaks gets you going again, but the real answer is to set: VTAllocation=true in /usr/X11R6/etc/gdm/gdm.conf You may want to set the Virtual Terminal you want as well. I turn off 5-8 to tty, and have mine come on VT5. I never use the four as it is. Paul. Justin Smith wrote: After upgrading to STABLE a few days ago, several odd problems developed: 1. cups did not start automatically. It turned out the CUPS script was being given the parameter 'faststart' rather than 'start' 2. GDM started but in an odd mode that didn't detect any keyboard input (so I couldn't log in). The mouse continued to work. When I started in nongraphical mode and manually started GDM as root, it worked normally. Any suggestions? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Paul Root "Few people know what to do when hula girls attack." - Sam, age 8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gdm problem with kernel as of 2005-01-04
I'm in at work and turned off gdm in my rc.conf and rebooted. The keyboard works fine! Then manually starting gdm and it still works. That's great. I think that something happened in the rc files that makes it start earlier and that's conflicting with something that freezes the keyboard. Richard Kuhns wrote: I just finished a buildworld/buildkernel/mergemaster on my Dell Inspiron 9300. Upon rebooting, I noticed that gdm seemed to start earlier in the boot process than it used to. When the login screen appeared, the mouse seemed to work fine, but nothing I typed appeared. Attempting to use C-A-F1 to switch to vty0 just beeped. C-A-Del worked to reboot the laptop. I booted single user, commented out gdm_enable="YES" in /etc/rc.conf, and rebooted -- everything was fine. I put the gdm_enable back and ran /usr/X11R6/etc/rc.d/gdm.sh start -- gdm started, fully functional. I rebooted again -- gdm ignored the keyboard. After several reboots, I've found that gdm seems to work fine as long as I don't have 'gdm_enable="YES"' in /etc/rc.conf when the machine boots. I've just finished upgrading gdm (using portmanager); still the same problem. If anyone has suggestions/wants me to try anything, just say so. Thanks! - Rich -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
keyboard failing on Dell laptop with 6.0-Stable this week.
I have an old Dell Inspiron 5000 (800MHz, 512M RAM), that I've been running 6.0 since it was released. It was running great with -Stable cvsupped around Dec 18th or so. Tuesday, I saw that a problem with NFS locking was fixed, and I was having an nfs/amd problem on a desktop Vectra, so I cvsupped both machines and did a buildworld, etc. The Vectra had no problem. I'm not sure if the NFS issue is solved, I haven't had opportunity to be on that machine this week. Anyway, after coming up in full user mode, the keyboard is locked up on the Dell. I searched the archives and it seems that 5.4-S has some problems in this regard and that devd is the culprit. I commented out the 8-10 lines in devd.conf that have ukbd0 in them. But that didn't help at all. I tried turning off devd, big mistake, the network didn't come up then. Makes sense. I tried coming up without DBUS, as that was the last thing I'd done before the holiday's on the machine. No help. I have a usb keyboard at home, but this machine is at work, and I forgot it over night. Anybody have any other ideas. Oh, I had a custom kernel, also tried the GENERIC kernel and the old kernel. I re-cvsupped on Wednesday and built again. Thanks, Paul. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nfs server timeout
I have a HP Vectra running FreeBSD acesfbsd 6.0-STABLE FreeBSD 6.0-STABLE #0: Fri Dec 9 14:44:30 CST 2005 that has trouble with nfs mounts (amd home directory) from a Solaris 8 box. It started life as 4.x went through a lot of 5.x all with no problems. However, since upgrading to 6.0, occasionally, it will get the dreaded "nfs server not responding" message. That will last for a few minutes and then come back. The server is fine, all the Solaris clients have no trouble at the time. The ethernet interface is clean. 100Meg full. Any thoughts? Thanks, Paul. -- ______ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 Stable" 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tunnels through a NAT device
I sent this out Saturday from home, but it doesn't look like it went out... Original Message Message-ID: <[EMAIL PROTECTED]> Date: Sat, 19 Nov 2005 17:52:18 -0600 From: Paul Root <[EMAIL PROTECTED]> User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: freebsd-stable Subject: tunnels through a NAT device Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I'm trying to setup and encrypted tunnel between 2 FreeBSD machines. Yesterday, I did get the tunnel up between two machines on the same network, and got it encrypted. Pretty easy following the handbook. Now, I have a machine at home behind a DSL modem (Actiontec) that NATs everything. I've made the machine the DMZ host for the Actiontec, which basically passes all ports not otherwise directed to the machine. The machines are both Sparcs. I'm using aliases for routing. Internet machine: hme0: flags=8843 mtu 1500 options=b inet A.B.C.D netmask 0xffe0 broadcast A.B.C.Z inet6 fe80::a00:20ff:fec0:3fe1%hme0 prefixlen 64 scopeid 0x1 inet 192.168.99.1 netmask 0x broadcast 192.168.99.1 ether 08:00:20:c0:3f:e1 media: Ethernet autoselect (10baseT/UTP) status: active gif0: flags=8051 mtu 1280 tunnel inet A.B.C.D --> E.F.G.H inet6 fe80::a00:20ff:fec0:3fe1%gif0 prefixlen 64 scopeid 0x3 inet 192.168.99.1 --> 192.168.90.250 netmask 0x home NATed machine: hme0: flags=8843 mtu 1500 options=b inet6 fe80::a00:20ff:fec0:5061%hme0 prefixlen 64 scopeid 0x1 inet 192.168.0.250 netmask 0xff00 broadcast 192.168.0.255 inet 192.168.90.250 netmask 0x broadcast 192.168.90.250 ether 08:00:20:c0:50:61 media: Ethernet autoselect (100baseTX) status: active gif0: flags=8051 mtu 1280 tunnel inet E.F.G.H --> A.B.C.D inet6 fe80::a00:20ff:fec0:5061%gif0 prefixlen 64 scopeid 0x3 inet 192.168.90.250 --> 192.168.99.1 netmask 0x Now this works, exactly like this, on two machines that are not NATed. E.F.G.H is the address of the dsl modem on the outside. I've tried setting the home machine's gif0 interface to both E.F.G.H and 192.168.0.250 going to A.B.C.D. Obviously, the internet machine has to point to E.F.G.H. Should I set the alias of hme0 on the home machine to E.F.G.H? Is there a way to do this? -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
Things are running better now. I moved it to a dedicated DSL line in my lab, and it's chugging along. I see an occasional g_vfs_done message fly across. Error 16 on a read. Something like g_vfs_done: acd0[READ(offset=81920, length=2048) Error = 16 Opps, I crashed the machine. When I moved it, I unplugged the USB DVD-RW and I had mounted one of the dist discs on there. When I did a umount it paniced. My bad. acd0 would be the internal DVD drive. It seems that problem with my network was indeed the Cisco ASA box we're beta testing. We have the CSC module installed which is a stand alone linux box running trend for virus, intrusion, etc. And there is a bug in the ftp inspection. Hangs things up. Ok, since I think the network is solved, I'll take this opportunity to restart portmanager on the network. Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thursday 10 November 2005 09:42, Paul T. Root wrote: I moved the machine to a DSL line here, and am running portmanager. It seems to be working. We're going to investigate issues with this beta Cisco ASA machine. I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first "portmanager -v". If any problems arise I am more than happy to work with you in solving them quickly. -Mike Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Wednesday 09 November 2005 18:26, Paul Root wrote: Michael C. Shultz wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** port and install or restart gnome-upgrade.sh I'm now assuming that since all gnome has been wiped off the disk, that the thing to do is build/install the port directly. Starting that up, I seem to be having the same downloading difficulties. As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. Interesting. The web page said specifically don't do portupgrade. I didn't say portupgrade, it is sysutils/portmanager My main problem is it's having trouble downloading, I think. I'm not sure why. We found problems on our Pix (actually the new ASA firewall) and the port the machine is on. We were getting half duplex, but those are all fixed now. Curiously, command line ftp never has a problem downloading, it's fetch (I think it's using fetch), that can't seem to download. While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed [EMAIL PROTECTED] from the return address as it is a dupe of [EMAIL PROTECTED] ___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrading 5.4 -> 6.0 without reinstalling. safe ?
How is this different from a fresh install? Except for a very limited amount in config files, which would be easier to save and restore. And home directories. Again, save and restore. Pete French wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** You don't have to remove the ports prior to upgrading. Just recompile them later. Why would I want to do that though ? It gives me no advantages, and some serious disadvantages (especially if I am doing this on a 'live' system). Much easier to delete everything prior to the upgrade, and then I know that the machine is just the base system, and that none of my users are running apache, or pine, or exim or whatever - because I deleted them :-). Standard practice for me, even when going from one minor release to the next... -pcf. ___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gnome-upgrade.sh
This script is one of the most frustrating things ever written. I made a fresh install (from CD) of 6.0R. In the install I added gnome2, sudo, and bash. That's it. Gnome came up fine. bash is great, sudo works. Now, since gnome 2.12 is out, I want to upgrade to that. Seems resonable. http://www.freebsd.org/gnome tells us not to use portupgrade to upgrade gnome2. The upgrades get out of order. Ok fine, use gnome-upgrade.sh. And keep trying it says. I've run it better than a dozen times, now. It's still trying. All day, I turn and look at it periodically, resolve whatever problem it seems to be having and start it up again. 1 time it said that it was successful! Woo Hoo! Wait, 2 times, it just finished... However it lies. What it's done is removed gnome completely. The problem seems to lie in that downloads fail and so I get a bunch of files in /usr/ports/distfiles that are not valid. Using good old ftp, I grab the file needed and either build the port and install or restart gnome-upgrade.sh I'm now assuming that since all gnome has been wiped off the disk, that the thing to do is build/install the port directly. Starting that up, I seem to be having the same downloading difficulties. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrading 5.4 -> 6.0 without reinstalling. safe ?
Oliver Fromme wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** Pete French <[EMAIL PROTECTED]> wrote: > usually when I upgrade across major versions of BSD I wipe the whole > machine and re--install from scratch. But I understand that the move > to 6.0 from 5.4 is nowhere near such a big leap. > > So I was wondering hether I could just do this from source without any > ill effects, as if I was upgrading 5.4->5.5. That's exactly what I did. I installed a new machine from a 5.4-Release DVD-ROM, then updated to RELENG_5, and then went to RELENG_6 from there. The only special thing I had to do was to manually rm -rf /usr/obj, otherwise the build- world broke. Oh yeah, I did rm -r the object tree, I forgot about that. It was kind of a reflex thing when it failed. Of course you should do take the usual precautions, i.e. have a reliable backup, read UPDATING, don't forget to run mergemaster etc. Best regards Oliver -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: upgrading 5.4 -> 6.0 without reinstalling. safe ?
I did this on a Sun Ultra5 system last night. I forgot (as I usually do) mergemaster -p. But everything worked fine. The -p usually just catches missing users and such that could cause install problems. Claus Guttesen wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** usually when I upgrade across major versions of BSD I wipe the whole machine and re--install from scratch. But I understand that the move to 6.0 from 5.4 is nowhere near such a big leap. So I was wondering hether I could just do this from source without any ill effects, as if I was upgrading 5.4->5.5. I have nnever tried this before though, and was wondering if there are any major pitfalls (i.e. is it actually a really bad idea?) The easiest would be to 1. cvsup to RELENG_6 (or RELENG_6_0) 2. cd /usr/src 3. make buildworld 4. make buildkernel 5. make installkernel 6. mergemaster -p 7. reboot into single-usermode and verify your new kernel works 8. mount -a 9. make installworld 10. mergemaster 11. reboot All described in /usr/src/Makefile (and the handbook). You may need to reinstall some apps, but most should work with compat5x in place. regards Claus ___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
Jan Grant wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thu, 27 Oct 2005, Paul T. Root wrote: man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. I also found: [[[ STANDARDS The inet_ntop() and inet_pton() functions conform to X/Open Networking Services Issue 5.2 (``XNS5.2''). Note that inet_pton() does not accept 1-, 2-, or 3-part dotted addresses; all four parts must be specified and are interpreted only as decimal values. This is a narrower input set than that accepted by inet_aton(). ]]] on that same man page :-) Sure but the hosts(5) man page says that it follows inet_addr(3) spec. Sorry, I neglected to put that little leap in. Cheers, jan PS. I only raised the issue in case anyone else was bitten by it (which is why a PR might be handy). Having "fixed" /etc/hosts, I don't think this is worth wasting more energy on. Yeah, you're right there. -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Resolver doesn't like 1.2.3.04 in /etc/hosts
man inet_addr and you'll find: All numbers supplied as ``parts'' in a `.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; otherwise, the number is interpreted as decimal). So a leading zero means hex. Stop trying to make it look pretty. Standards are a good thing and need to be followed. Jan Grant wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. ***-*** On Thu, 27 Oct 2005, Mark Andrews wrote: On 2005-10-26, Mark Andrews wrote: Leading zeros are ambigious. Some platforms treat them as octal others treat them as decimal. There is nothing ambiguous about the example provided. (Perhaps it wasn't a good example, but it's always a bug if '04' is not correctly decoded, regardless of the numeric base in use.) You want a ambigious example? 192.168.222.012 It amazed me that no RFC ever appears to have standardised this format (although it is alluded to in passing as being decimal in various other places). Eg, 1035 has: [[[ The RDATA section of an A line in a master file is an Internet address expressed as four decimal numbers separated by dots without any imbedded spaces (e.g., "10.2.0.52" or "192.0.5.6"). ]]] (although that's DNS zone file format, not /etc/hosts.) It's much easier to just reject octal and hexadecimal than to work out when and when not it is ambigious. It is also better to demand all 4 octets. It also generates less support complaints. I'm happy to reject octal and hex too! Anyway, count this as one (minor) support gripe :-) Thanks for your time, jan -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Advice sought on upgrading from 4.11-R to 5.4...
I went via cvsup and a source tree, straight to 5.4 stable from 4.10 stable. Brad Knowles wrote: Folks, I've seen the migration guide at <http://www.freebsd.org/releases/5.4R/migration-guide.html>, and the thread at <http://lists.freebsd.org/pipermail/freebsd-stable/2005-September/018151.html>, but I was wondering about the specific sequence of the upgrade process. In particular, I'm wondering if I should go from RELENG_4_11_0_RELEASE direct to RELENG_5_4, or if I should instead go first to RELENG_5_0_0_RELEASE then to RELENG_5_4? I think the individual steps to follow and commands to execute during the upgrade are clear enough. But it's not obvious to me as to which precise CVSup targets should be used to pull down the source that would be compiled, etc.... -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: any ideas when 5.5 will be out
In the past, x.0 releases are meant for the adventurous not the production oriented. I never go before x.1. And I skipped 3.x completely. I just got my final server from 4.11 to 5.4 in July. 6.x is probably still 9-12 months away from prime time. But that's just a guess on my part. I do know that they are pushing on it harder than they did for 5.0. Sandro Noel. wrote: Why would 5.5 come out after 6.0, what's the use ? just upgrade to 6.0 ,.,, no? Sandro On 9/19/05, Eriq <[EMAIL PROTECTED]> wrote: I haven't noticed any word on this release, just 6.0 Most likely a month after 6.0 is released, as they are busy getting 6.0 ready for the release. Subject: Re: any ideas when 5.5 will be out From: "Scot Hetzel" <[EMAIL PROTECTED]> Date: Mon, 19 Sep 2005 17:22:00 + To: "Eriq" <[EMAIL PROTECTED]> To: "Eriq" <[EMAIL PROTECTED]> CC: freebsd-stable@freebsd.org Message-ID: <[EMAIL PROTECTED]> Return-Path: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Received: (qmail 20917 invoked by uid 78); 19 Sep 2005 17:47:44 - Received: from unknown (HELO ns-mr8.netsolmail.com) (205.178.149.7) by mail.networksolutionsemail.com with SMTP; 19 Sep 2005 17:47:44 - Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by ns-mr8.netsolmail.com (8.12.10/8.12.10) with ESMTP id j8JHlgES024686 for <[EMAIL PROTECTED]>; Mon, 19 Sep 2005 13:47:42 -0400 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id EC3E05C29D; Mon, 19 Sep 2005 17:22:39 + (GMT) (envelope-from [EMAIL PROTECTED]) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DA19A16A43A; Mon, 19 Sep 2005 17:22:35 + (GMT) (envelope-from [EMAIL PROTECTED]) X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D7FB16A41F for ; Mon, 19 Sep 2005 17:22:28 + (GMT) (envelope-from [EMAIL PROTECTED]) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8BF543D45 for ; Mon, 19 Sep 2005 17:22:27 + (GMT) (envelope-from [EMAIL PROTECTED]) Received: by xproxy.gmail.com with SMTP id i31so467787wxd for ; Mon, 19 Sep 2005 10:22:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=POP0UXXTEqg0LwMP1mR+0Vi8Sc9aIFO0f2nUS4lDSZrR8I/qW+fs1vXxtCkSetluK8cRoGHUfP39ecYTcQNGjCLdI/wfk8WOGSjHL7RbopvLftKgwPNEB5Rdx62N8dN5mgxCKIk42u7lsSlUcTa+GzbtUSGR9eVdjPlUg3TDuD0= Received: by 10.70.111.2 with SMTP id j2mr1418789wxc; Mon, 19 Sep 2005 10:22:27 -0700 (PDT) Received: by 10.70.53.4 with HTTP; Mon, 19 Sep 2005 10:22:27 -0700 (PDT) In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:[EMAIL PROTECTED]> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable> List-Post: <mailto:freebsd-stable@freebsd.org> List-Help: <mailto:[EMAIL PROTECTED]> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On 9/19/05, Eriq <[EMAIL PROTECTED]> wrote: I haven't noticed any word on this release, just 6.0 Most likely a month after 6.0 is released, as they are busy getting 6.0 ready for the release. ___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading RAM
It should just work. A long time ago (2.x and 3.x days), Compaq's wouldn't work right because of their junkie architecture. So you had to tell the kernel how much memory you had. That junkie architecture has moved to HP now, but at least that problem is no longer there. Øystein Holmen wrote: I have a machine running FreeBSD 5.4 with 512MB RAM. Now I want to install an extra RAM-module. Do I have to do something in my configuration, or is it "plug-and-play"? Sincerely, Øystein Holmen___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Incorrect super block--help!
You're trying to mount it as a rw disc and as a UFS file system mount -r -t cd9660 /dev/acd0 /cdrom Mark Space wrote: Hey, newb BSDer here with a question I've got a brand new 5.4 install. I'm trying to mount the CDROM. As root, I type: mount /dev/acd0 /cdrom and I get "incorrect super block" error message after a bit of CD activity, and no mount. I've tried a CD-RW I burned (the FreeBSD install disk I installed from) and an old copy of SimCity 2000, neither worked, same error message. I'm stuck. Any ideas? -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: telnet problem.
Vivek Khera <[EMAIL PROTECTED]> said: > The following message is a courtesy copy of an article > that has been posted to ml.freebsd.stable as well. > > > "PR" == Paul Root <[EMAIL PROTECTED]> writes: > > PR> This happens for both on and off network routers. Connection to > PR> the FreeBSD machine is through a Firewall-1 4.1 machine (sun). > > There was some discussion about firewalls losing state too early and > dropping/locking some connections. Your culprit is most likely the > Firewall-1 machine. Well, it would be nice to blame FW-1 on this, but I can't. I can open 2 windows from my Sun thru the firewall to the FreeBSD machine. With the first one, I do my normal things, working on the machine, with the second I telnet out. The first one never dies. I can have one window open all week long. The second one dies after an hour of idle time. The same thing will happen if I telnet (TeraTerm) from my Win2000 machine to the FreeBSD machine, that are on the same network. The same thing will happen if I telnet to the Win2000 machine. The only constant in all my synario's is the telnet client program on FreeBSD. -- This looks like a job for legal tender! - The Tick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
