From owner-freebsd-advocacy Mon Jul 31 3:37:18 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id 7D01A37B8A7; Mon, 31 Jul 2000 03:36:54 -0700 (PDT) (envelope-from wjv@cityip.co.za) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 13JCwC-0003zQ-00; Mon, 31 Jul 2000 12:36:48 +0200 Date: Mon, 31 Jul 2000 12:36:48 +0200 From: Johann Visagie To: chat@FreeBSD.ORG, advocacy@FreeBSD.ORG Subject: Re: Bioinformatics Open Source Conference, 17-18 Aug, San Diego Message-ID: <20000731123648.D91140@fling.sanbi.ac.za> References: <20000727122855.B414@fling.sanbi.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000727122855.B414@fling.sanbi.ac.za>; from wjv@cityip.co.za on Thu, Jul 27, 2000 at 12:28:55PM +0200 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote on 2000-07-27 (Thu) at 12:28:55 +0200: > > However, > the field is rooted in commercial Unix, and you can get a feel for some of > the Linux vs. Unix debate from these pages: > > http://www.portlandpress.com/biochemist/cyber/0006/default.htm > http://www2.mrc-lmb.cam.ac.uk/personal/rpg/CB/Linux.html Anyone interested in this, and interested in seeing how the ideas of open source / free software takes hold in a field as yet unaccustomed to the philosophical implications, may want to take a look at a current thread on the bionet.software newsgroup which started out called "Unix vs Linux - the movie" and has now morphed into "open source software for bioinformatics". -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Tue Aug 1 9:32:42 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from klapaucius.zer0.org (klapaucius.zer0.org [204.152.186.45]) by hub.freebsd.org (Postfix) with ESMTP id 4C7B037BF26 for ; Tue, 1 Aug 2000 09:32:38 -0700 (PDT) (envelope-from gsutter@daemonnews.org) Received: (from gsutter@localhost) by klapaucius.zer0.org (8.9.3/8.9.3) id JAA80249; Tue, 1 Aug 2000 09:32:37 -0700 (PDT) (envelope-from gsutter@daemonnews.org) X-Authentication-Warning: klapaucius.zer0.org: gsutter set sender to gsutter@daemonnews.org using -f Date: Tue, 1 Aug 2000 09:32:37 -0700 From: Gregory Sutter To: advocacy@freebsd.org, netbsd-advocacy@netbsd.org, openbsd-advocacy@openbsd.org Subject: Daemon News ezine, August 2000 Message-ID: <20000801093237.I70688@klapaucius.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organization: daemonnews Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The August 2000 issue of the Daemon News ezine is in the stands. http://www.daemonnews.org/ Content includes the last of our USENIX 2000 coverage (three articles), a Blueprints article on writing an ISA device driver, how to set up FreeBSD on a Compaq iPaq box, and more! Comments or suggestions for the ezine may be mailed to editors@daemonnews.org. We are always looking for articles! If you have something to contribute, mail articles@daemonnews.org with your idea, outline, or completed piece. Thanks very much for your support! Greg -- Gregory S. Sutter Bureaucrats cut red tape--lengthwise. mailto:gsutter@daemonnews.org PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Thu Aug 3 1:33:39 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (Postfix) with ESMTP id C4F2537B629 for ; Thu, 3 Aug 2000 01:33:36 -0700 (PDT) (envelope-from kuku@gilberto.physik.rwth-aachen.de) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.9.3/8.9.3) id KAA99774 for freebsd-advocacy@freebsd.org; Thu, 3 Aug 2000 10:33:38 +0200 (CEST) (envelope-from kuku) Date: Thu, 3 Aug 2000 10:33:38 +0200 (CEST) From: Christoph Kukulies Message-Id: <200008030833.KAA99774@gilberto.physik.rwth-aachen.de> To: freebsd-advocacy@freebsd.org Subject: FreeBSD in the web/internet Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, from time to time I stumble across a site which is using or mentioning that it is using FreeBSD with success. Can we (if not already set provisions for) collect these as links like "FreeBSD in the press"? In case someone is collecting these for uploading to the freebsd home page here is the one I just came across: http://www.qv.org/support-en.html#mlinfo -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Thu Aug 3 1:52: 3 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from freenix.no (atreides.freenix.no [213.188.21.6]) by hub.freebsd.org (Postfix) with ESMTP id 30A0737B838 for ; Thu, 3 Aug 2000 01:51:56 -0700 (PDT) (envelope-from morten@freenix.no) Received: from localhost (localhost.flipp.net [127.0.0.1]) by freenix.no (8.9.3/8.9.3) with ESMTP id KAA43002; Thu, 3 Aug 2000 10:51:42 +0200 (CEST) (envelope-from morten@freenix.no) Date: Thu, 3 Aug 2000 10:51:42 +0200 (CEST) From: "Morten A. Middelthon" To: Christoph Kukulies Cc: freebsd-advocacy@FreeBSD.ORG Subject: Re: FreeBSD in the web/internet In-Reply-To: <200008030833.KAA99774@gilberto.physik.rwth-aachen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Aug 2000, Christoph Kukulies wrote: > > Folks, > > from time to time I stumble across a site which is using or mentioning > that it is using FreeBSD with success. > > Can we (if not already set provisions for) collect these as links > like "FreeBSD in the press"? Like this? http://www.freebsd.org/news/press.html -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Fri Aug 4 9:15: 9 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id A127B37B8E5; Fri, 4 Aug 2000 09:14:58 -0700 (PDT) (envelope-from wjv@cityip.co.za) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 13Kk7H-0003mj-00; Fri, 04 Aug 2000 18:14:35 +0200 Date: Fri, 4 Aug 2000 18:14:35 +0200 From: Johann Visagie To: chat@freebsd.org, advocacy@freebsd.org Subject: Announcing a mailing list for FreeBSD users in the biosciences Message-ID: <20000804181435.A9671@fling.sanbi.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A new mailing list has been established for FreeBSD users in bioscientific fields, including bioinformatics, genomics, and all branches of computational biology. The aim of the list is not only to form a single point of contact for FreeBSD users in these fields, but also to form a staging area for porting bioscientific applications to FreeBSD. (Just watch the "biology" category in the ports tree during upcoming months! :-) For reasons which I have outlined before in these lists, I think that there is a need for a "bio-friendly" free Unix, and I would (of course) like FreeBSD to be it. For reasons which I have also outlined before, I think that such a bio-friendly OS could attract significant numbers of new users. Mail to this new mailing list may be addressed to . *** YES, that is .NET, and _NOT_ .ORG! *** The freebsd-bio list is in no way officially connected with or endorsed by the FreeBSD project or BSDi, Inc. To subscribe to the list, either: - Do so via the web front-end at: http://www.plig.net/mailman/listinfo/freebsd-bio - Send the word "subscribe" in the body of an email message to Thank you, -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 7:37: 1 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from slkcpop5.slkc.uswest.net (slkcpop5.slkc.uswest.net [206.81.128.5]) by hub.freebsd.org (Postfix) with SMTP id B80B537B898 for ; Sat, 5 Aug 2000 07:36:52 -0700 (PDT) (envelope-from jswarner@uswest.net) Received: (qmail 18161 invoked by alias); 5 Aug 2000 14:36:52 -0000 Delivered-To: fixup-freebsd-advocacy@freebsd.org@fixme Received: (qmail 18138 invoked by uid 0); 5 Aug 2000 14:36:50 -0000 Received: from unknown (HELO uswest.net) (63.224.105.149) by slkcpop5.slkc.uswest.net with SMTP; 5 Aug 2000 14:36:50 -0000 Message-ID: <398C2599.FB356E7E@uswest.net> Date: Sat, 05 Aug 2000 08:32:57 -0600 From: Joe Warner X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-newbies@freebsd.org, freebsd-advocacy@freebsd.org Subject: Newbie Learning Experience Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've had a real learning experience with my FreeBSD (3.4) system at work over the past couple of days and at the risk of making myself look like an idiot, I felt it important enough to share. Since I'm a newbie and hope to help other newbies when facing similar situations, this email is directed mainly at freebsd-newbies. However, I also felt it important enough to share with freebsd-advocacy because of how amazed I am with the OS. Instead of a little cartoon devil, maybe the mascot should be the Energizer Bunny? FreeBSD keeps going and going and going... 8^) Anyway, please bear with me. This is probably going to be pretty lengthy, so for those of you don't like to read or are uninterested, just close this email and delete it now. For the rest of you, read on... When I came into work last Thursday morning, I noticed that my PC (Compaq Deskpro 2000), running FreeBSD 3.4 was at the login prompt and my WIN NT machine was at the boot up password. I realized then that the inevitable had happened....Power Outage! Thinking that power outages/cold reboots meant death to most UNIX systems, I hurried to prevent this from happening again and hooked up an APC Smart-UPS 1000 that we had sitting in one of our storage closets. Hooking it up to my FreeBSD machine was easy enough. I just plugged the power cord into a receptacle and then plugged the power from the CPU and monitor into the back of the UPS. I finished by attaching the serial cable on the UPS to the serial port on the back of the CPU (COM1) - There is only one serial port available for Compaq Deskpro's. After hooking it up, I realized that I would need to install some software that could communicate with the UPS through the serial line and allow me to do a graceful shutdown in the event of power loss. I went to APC's web site and though they had their Powerchute software available for many commercial versions of UNIX, I didn't see anything that was designed specifically for any of the BSD's. They even had a Linux version and I learned later that at least one person was running this successfully under Linux emulation on his FreeBSD 3.4 system. I didn't want to run this under Linux emulation if I didn't have to. Later, I came across an application in the ports collection called UPSD - 2.0 that seemed to be designed specifically to work with the APC Smart-UPS models. I loaded the 4th CD from the CD ROM set and from /usr/ports/sysutils/upsd/ I typed make install and installed it. I noticed that there wasn't any documentation included with this port, not even a man page. It loaded only 2 files, the upsd executable in /usr/local/sbin and the configuration file (upsd.conf) in /usr/local/etc I su'd to root and attempted to spawn the daemon by cd'ng to /usr/local/sbin and typing # ./upsd At this point, my whole system locked up tighter than a drum! I couldn't kill X and couldn't switch to another terminal. Nothing! I had to cold-reboot my system again! After I booted back up, I looked at my logs and noticed a message indicating there was a permission problem with /dev/cuaa0 This device is owned by uucp and belongs to the dialer group. I su'd to root again and adjusted the permissions so that other users would have access and then tried to execute the program again. Same thing happened, complete lockup! At this point, I was pretty frustrated and none the information I had read in my books or the answers I received from posting to FreeBSD-Questions seemed to help. I cd'd to /usr/ports/sysutils/upsd and typed make deinstall and went home. When I came in Friday morning, I noticed an email from someone who said they were using a port called UPSMON - 2.1.3 with an APC Smart-UPS on their FreeBSD system without any problems. This port wasn't on the CD ROM set, so when I installed it, it had to fetch it from an ftp site. No problem, right? Wrong! I installed this port and decided to reboot. Big mistake! Now, during boot-up, my system would just hang at: local package initialization: Cannot open /dev/cuaa0: Permission denied upsmond<---(this is where it would hang) After hearing the voice of Ralph from the Simpsons in my head, going Ha! Ha!.., I thought, now what do I do! After going through all my books and documentation and trying to boot into single-user mode, fixit mode from the 2nd cd in the cd rom set and even from kernel.GENERIC, I realized I wasn't getting anywhere. My machine would always hang when trying to launch the upsmond daemon during boot up. As a last resort, I posted to FreeBSD-Questions and got the answer I was looking for. I was told to go into single-user mode. At the beginning of the boot-up process, there is a ten second count down that tells you to either hit enter or wait for the count down to finish for system boot-up. Before the counter finishes, you hit the space bar and you're presented with a prompt where you can specify different boot options. I specified "boot -s" for single user mode. In The Complete FreeBSD, it tells you to boot into single-user mode and run fsck on / by issuing: fsck -y / I ran this on / and /dev/wd0s1a, respectively. Then it tells you to mount / by typing: mount -u / I did this and it let me mount it. Lastly, it says to mount /usr by typing: mount /usr It would let me mount this but only with read access. I needed write access so that I could go into /usr/local/etc/rc.d/ and either remove or change the upsmond.sh file in there that was causing my system to hang. I got a response from someone telling me to mount /usr by typing the following: mount -rwf /usr This worked and I was able to edit upsmond.sh so that it was pointing to /dev/cuaa1 and not cuaa0. This got my system booting. I found out later that I could have successfully mounted /usr with r/w access if I would have first fsck'd it by issuing: fsck -y /usr (I probably should have done this for /var too) I got my system booting again (Whew!) but still haven't figured out why /dev/cuaa0 causes problems. I seems as if some kind of conflict is going on, maybe something else is using this device? I haven't found the answer to this yet. I got an email response back from APC, saying they did have an application that would work with FreeBSD but I would need to purchase their Simple UNIX Serial cable for $39.00 in order for it to work. So, now I don't know if it's a device conflict or the cable but I doubt I'll shell out the money for a new cable. Maybe my manager will let me order it and reimburse me? I've always thought that cold reboot/shutdowns were death to UNIX systems, especially if you did it more than 5 or 6 times. I've completely trashed my systems this way when I was using Red Hat 6.x and Caldera 2.x in the past. Cold booted more than 5 times and got the dreaded "kernel panic" message and had to reinstall. I ended up cold booting my FreeBSD system more than 12 times the last couple of days and it's still going! 8^) So, the moral of this story? FreeBSD is forgiving, you just need to tell it how to forgive you! And...forgive me for such a long story... 8^} Joe -- FreeBSD = The Power to Serve ..Simply put = FreeBSD Rocks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 9: 2:49 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id 83EB437B9F2; Sat, 5 Aug 2000 09:02:35 -0700 (PDT) (envelope-from fpawlak@execpc.com) Received: from john.execpc.com (d65.as3.nwbl1.wi.voyager.net [169.207.85.193]) by mailgw00.execpc.com (8.9.1) id LAA03620; Sat, 5 Aug 2000 11:02:28 -0500 Message-Id: <4.3.2.7.2.20000805110010.00b8d348@127.0.0.1> X-Sender: fpawlak/mail.execpc.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 05 Aug 2000 11:02:47 -0500 To: Joe Warner , freebsd-newbies@freebsd.org, freebsd-advocacy@freebsd.org From: Frank Pawlak Subject: Re: Newbie Learning Experience In-Reply-To: <398C2599.FB356E7E@uswest.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IMHO this is a great story. Perhaps this deserves a daemon news spot with some HOWTO implications. Regards, Frank At 08:32 AM 8/5/2000 -0600, Joe Warner wrote: >Hi all, > > I've had a real learning experience with my FreeBSD (3.4) system at >work over the past couple of days and at the risk of making myself look >like an idiot, I felt it important enough to share. Since I'm a newbie >and hope to help other newbies when facing similar situations, this >email is directed mainly at freebsd-newbies. However, I also felt it >important enough to share with freebsd-advocacy because of how amazed I >am with the OS. Instead of a little cartoon devil, maybe the mascot >should be the Energizer Bunny? FreeBSD keeps going and going and >going... 8^) Anyway, please bear with me. This is probably going to be >pretty lengthy, so for those of you don't like to read or are >uninterested, just close this email and delete it now. For the rest of >you, read on... > When I came into work last Thursday morning, I noticed that my PC >(Compaq Deskpro 2000), running FreeBSD 3.4 was at the login prompt and >my WIN NT machine was at the boot up password. I realized then that the >inevitable had happened....Power Outage! Thinking that power >outages/cold reboots meant death to most UNIX systems, I hurried to >prevent this from happening again and hooked up an APC Smart-UPS 1000 >that we had sitting in one of our storage closets. Hooking it up to my >FreeBSD machine was easy enough. I just plugged the power cord into a >receptacle and then plugged the power from the CPU and monitor into the >back of the UPS. I finished by attaching the serial cable on the UPS to >the serial port on the back of the CPU (COM1) - There is only one serial >port available for Compaq Deskpro's. After hooking it up, I realized >that I would need to install some software that could communicate with >the UPS through the serial line and allow me to do a graceful shutdown >in the event of power loss. I went to APC's web site and though they >had their Powerchute software available for many commercial versions of >UNIX, I didn't see anything that was designed specifically for any of >the BSD's. They even had a Linux version and I learned later that at >least one person was running this successfully under Linux emulation on >his FreeBSD 3.4 system. I didn't want to run this under Linux emulation >if I didn't have to. Later, I came across an application in the ports >collection called UPSD - 2.0 that seemed to be designed specifically to >work with the APC Smart-UPS models. I loaded the 4th CD from the CD ROM >set and from /usr/ports/sysutils/upsd/ I typed make install and >installed it. I noticed that there wasn't any documentation included >with this port, not even a man page. It loaded only 2 files, the upsd >executable in /usr/local/sbin and the configuration file (upsd.conf) in >/usr/local/etc I su'd to root and attempted to spawn the daemon by >cd'ng to /usr/local/sbin and typing # ./upsd At this point, my whole >system locked up tighter than a drum! I couldn't kill X and couldn't >switch to another terminal. Nothing! I had to cold-reboot my system >again! After I booted back up, I looked at my logs and noticed a >message indicating there was a permission problem with /dev/cuaa0 This >device is owned by uucp and belongs to the dialer group. I su'd to root >again and adjusted the permissions so that other users would have access >and then tried to execute the program again. Same thing happened, >complete lockup! At this point, I was pretty frustrated and none the >information I had read in my books or the answers I received from >posting to FreeBSD-Questions seemed to help. I cd'd to >/usr/ports/sysutils/upsd and typed make deinstall and went home. > When I came in Friday morning, I noticed an email from someone who >said they were using a port called UPSMON - 2.1.3 with an APC Smart-UPS >on their FreeBSD system without any problems. This port wasn't on the >CD ROM set, so when I installed it, it had to fetch it from an ftp >site. No problem, right? Wrong! I installed this port and decided to >reboot. Big mistake! Now, during boot-up, my system would just hang >at: > >local package initialization: Cannot open /dev/cuaa0: Permission denied >upsmond<---(this is where it would hang) > > After hearing the voice of Ralph from the Simpsons in my head, going >Ha! Ha!.., I thought, now what do I do! After going through all my >books and documentation and trying to boot into single-user mode, fixit >mode from the 2nd cd in the cd rom set and even from kernel.GENERIC, I >realized I wasn't getting anywhere. My machine would always hang when >trying to launch the upsmond daemon during boot up. As a last resort, I >posted to FreeBSD-Questions and got the answer I was looking for. I was >told to go into single-user mode. At the beginning of the boot-up >process, there is a ten second count down that tells you to either hit >enter or wait for the count down to finish for system boot-up. Before >the counter finishes, you hit the space bar and you're presented with a >prompt where you can specify different boot options. I specified "boot >-s" for single user mode. In The Complete FreeBSD, it tells you to boot >into single-user mode and run fsck on / by issuing: fsck -y / I >ran this on / and /dev/wd0s1a, respectively. Then it tells you to mount >/ by typing: mount -u / I did this and it let me mount it. Lastly, it >says to mount /usr by typing: mount /usr It would let me mount this but >only with read access. I needed write access so that I could go into >/usr/local/etc/rc.d/ and either remove or change the upsmond.sh file in >there that was causing my system to hang. I got a response from someone >telling me to mount /usr by typing the following: mount -rwf /usr This >worked and I was able to edit upsmond.sh so that it was pointing to >/dev/cuaa1 and not cuaa0. This got my system booting. I found out >later that I could have successfully mounted /usr with r/w access if I >would have first fsck'd it by issuing: fsck -y /usr (I probably should >have done this for /var too) > I got my system booting again (Whew!) but still haven't figured out >why /dev/cuaa0 causes problems. I seems as if some kind of conflict is >going on, maybe something else is using this device? I haven't found >the answer to this yet. I got an email response back from APC, saying >they did have an application that would work with FreeBSD but I would >need to purchase their Simple UNIX Serial cable for $39.00 in order for >it to work. So, now I don't know if it's a device conflict or the cable >but I doubt I'll shell out the money for a new cable. Maybe my manager >will let me order it and reimburse me? > I've always thought that cold reboot/shutdowns were death to UNIX >systems, especially if you did it more than 5 or 6 times. I've >completely trashed my systems this way when I was using Red Hat 6.x and >Caldera 2.x in the past. Cold booted more than 5 times and got the >dreaded "kernel panic" message and had to reinstall. I ended up cold >booting my FreeBSD system more than 12 times the last couple of days and >it's still going! 8^) So, the moral of this story? FreeBSD is >forgiving, you just need to tell it how to forgive you! And...forgive >me for such a long story... 8^} > >Joe > > >-- > > FreeBSD = The Power to Serve > ..Simply put = FreeBSD Rocks! > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-advocacy" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 9:14:38 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from slkcpop2.slkc.uswest.net (slkcpop2.slkc.uswest.net [206.81.128.2]) by hub.freebsd.org (Postfix) with SMTP id 11F2337BA24 for ; Sat, 5 Aug 2000 09:14:34 -0700 (PDT) (envelope-from jswarner@uswest.net) Received: (qmail 99373 invoked by alias); 5 Aug 2000 16:12:59 -0000 Delivered-To: fixup-freebsd-advocacy@freebsd.org@fixme Received: (qmail 99342 invoked by uid 0); 5 Aug 2000 16:12:58 -0000 Received: from unknown (HELO uswest.net) (63.224.105.177) by slkcpop2.slkc.uswest.net with SMTP; 5 Aug 2000 16:12:58 -0000 Message-ID: <398C3C21.CAB81AB4@uswest.net> Date: Sat, 05 Aug 2000 10:09:05 -0600 From: Joe Warner X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Frank Pawlak Cc: freebsd-newbies@freebsd.org, freebsd-advocacy@freebsd.org Subject: Re: Newbie Learning Experience References: <4.3.2.7.2.20000805110010.00b8d348@127.0.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Frank. Actually, I thought about posting it on Daemon News but it would probably be too long, since I don't have a URL to link it to. Oh well....such is the life of a lamer. 8^) Joe Frank Pawlak wrote: > IMHO this is a great story. Perhaps this deserves a daemon news spot with > some HOWTO implications. > > Regards, > Frank > > At 08:32 AM 8/5/2000 -0600, Joe Warner wrote: > >Hi all, > > > > I've had a real learning experience with my FreeBSD (3.4) system at > >work over the past couple of days and at the risk of making myself look > >like an idiot, I felt it important enough to share. Since I'm a newbie > >and hope to help other newbies when facing similar situations, this > >email is directed mainly at freebsd-newbies. However, I also felt it > >important enough to share with freebsd-advocacy because of how amazed I > >am with the OS. Instead of a little cartoon devil, maybe the mascot > >should be the Energizer Bunny? FreeBSD keeps going and going and > >going... 8^) Anyway, please bear with me. This is probably going to be > >pretty lengthy, so for those of you don't like to read or are > >uninterested, just close this email and delete it now. For the rest of > >you, read on... > > When I came into work last Thursday morning, I noticed that my PC > >(Compaq Deskpro 2000), running FreeBSD 3.4 was at the login prompt and > >my WIN NT machine was at the boot up password. I realized then that the > >inevitable had happened....Power Outage! Thinking that power > >outages/cold reboots meant death to most UNIX systems, I hurried to > >prevent this from happening again and hooked up an APC Smart-UPS 1000 > >that we had sitting in one of our storage closets. Hooking it up to my > >FreeBSD machine was easy enough. I just plugged the power cord into a > >receptacle and then plugged the power from the CPU and monitor into the > >back of the UPS. I finished by attaching the serial cable on the UPS to > >the serial port on the back of the CPU (COM1) - There is only one serial > >port available for Compaq Deskpro's. After hooking it up, I realized > >that I would need to install some software that could communicate with > >the UPS through the serial line and allow me to do a graceful shutdown > >in the event of power loss. I went to APC's web site and though they > >had their Powerchute software available for many commercial versions of > >UNIX, I didn't see anything that was designed specifically for any of > >the BSD's. They even had a Linux version and I learned later that at > >least one person was running this successfully under Linux emulation on > >his FreeBSD 3.4 system. I didn't want to run this under Linux emulation > >if I didn't have to. Later, I came across an application in the ports > >collection called UPSD - 2.0 that seemed to be designed specifically to > >work with the APC Smart-UPS models. I loaded the 4th CD from the CD ROM > >set and from /usr/ports/sysutils/upsd/ I typed make install and > >installed it. I noticed that there wasn't any documentation included > >with this port, not even a man page. It loaded only 2 files, the upsd > >executable in /usr/local/sbin and the configuration file (upsd.conf) in > >/usr/local/etc I su'd to root and attempted to spawn the daemon by > >cd'ng to /usr/local/sbin and typing # ./upsd At this point, my whole > >system locked up tighter than a drum! I couldn't kill X and couldn't > >switch to another terminal. Nothing! I had to cold-reboot my system > >again! After I booted back up, I looked at my logs and noticed a > >message indicating there was a permission problem with /dev/cuaa0 This > >device is owned by uucp and belongs to the dialer group. I su'd to root > >again and adjusted the permissions so that other users would have access > >and then tried to execute the program again. Same thing happened, > >complete lockup! At this point, I was pretty frustrated and none the > >information I had read in my books or the answers I received from > >posting to FreeBSD-Questions seemed to help. I cd'd to > >/usr/ports/sysutils/upsd and typed make deinstall and went home. > > When I came in Friday morning, I noticed an email from someone who > >said they were using a port called UPSMON - 2.1.3 with an APC Smart-UPS > >on their FreeBSD system without any problems. This port wasn't on the > >CD ROM set, so when I installed it, it had to fetch it from an ftp > >site. No problem, right? Wrong! I installed this port and decided to > >reboot. Big mistake! Now, during boot-up, my system would just hang > >at: > > > >local package initialization: Cannot open /dev/cuaa0: Permission denied > >upsmond<---(this is where it would hang) > > > > After hearing the voice of Ralph from the Simpsons in my head, going > >Ha! Ha!.., I thought, now what do I do! After going through all my > >books and documentation and trying to boot into single-user mode, fixit > >mode from the 2nd cd in the cd rom set and even from kernel.GENERIC, I > >realized I wasn't getting anywhere. My machine would always hang when > >trying to launch the upsmond daemon during boot up. As a last resort, I > >posted to FreeBSD-Questions and got the answer I was looking for. I was > >told to go into single-user mode. At the beginning of the boot-up > >process, there is a ten second count down that tells you to either hit > >enter or wait for the count down to finish for system boot-up. Before > >the counter finishes, you hit the space bar and you're presented with a > >prompt where you can specify different boot options. I specified "boot > >-s" for single user mode. In The Complete FreeBSD, it tells you to boot > >into single-user mode and run fsck on / by issuing: fsck -y / I > >ran this on / and /dev/wd0s1a, respectively. Then it tells you to mount > >/ by typing: mount -u / I did this and it let me mount it. Lastly, it > >says to mount /usr by typing: mount /usr It would let me mount this but > >only with read access. I needed write access so that I could go into > >/usr/local/etc/rc.d/ and either remove or change the upsmond.sh file in > >there that was causing my system to hang. I got a response from someone > >telling me to mount /usr by typing the following: mount -rwf /usr This > >worked and I was able to edit upsmond.sh so that it was pointing to > >/dev/cuaa1 and not cuaa0. This got my system booting. I found out > >later that I could have successfully mounted /usr with r/w access if I > >would have first fsck'd it by issuing: fsck -y /usr (I probably should > >have done this for /var too) > > I got my system booting again (Whew!) but still haven't figured out > >why /dev/cuaa0 causes problems. I seems as if some kind of conflict is > >going on, maybe something else is using this device? I haven't found > >the answer to this yet. I got an email response back from APC, saying > >they did have an application that would work with FreeBSD but I would > >need to purchase their Simple UNIX Serial cable for $39.00 in order for > >it to work. So, now I don't know if it's a device conflict or the cable > >but I doubt I'll shell out the money for a new cable. Maybe my manager > >will let me order it and reimburse me? > > I've always thought that cold reboot/shutdowns were death to UNIX > >systems, especially if you did it more than 5 or 6 times. I've > >completely trashed my systems this way when I was using Red Hat 6.x and > >Caldera 2.x in the past. Cold booted more than 5 times and got the > >dreaded "kernel panic" message and had to reinstall. I ended up cold > >booting my FreeBSD system more than 12 times the last couple of days and > >it's still going! 8^) So, the moral of this story? FreeBSD is > >forgiving, you just need to tell it how to forgive you! And...forgive > >me for such a long story... 8^} > > > >Joe > > > > > >-- > > > > FreeBSD = The Power to Serve > > ..Simply put = FreeBSD Rocks! > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-advocacy" in the body of the message -- FreeBSD = The Power to Serve ..Simply put = FreeBSD Rocks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 10:40:48 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id A13EF37BAA0; Sat, 5 Aug 2000 10:40:35 -0700 (PDT) (envelope-from fpawlak@execpc.com) Received: from john.execpc.com (d111.as27.nwbl1.wi.voyager.net [169.207.114.49]) by mailgw00.execpc.com (8.9.1) id MAA22273; Sat, 5 Aug 2000 12:40:31 -0500 Message-Id: <4.3.2.7.2.20000805123643.03128a88@127.0.0.1> X-Sender: fpawlak/mail.execpc.com@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 05 Aug 2000 12:40:30 -0500 To: Joe Warner From: Frank Pawlak Subject: Re: Newbie Learning Experience Cc: freebsd-newbies@freebsd.org, freebsd-advocacy@freebsd.org In-Reply-To: <398C3C21.CAB81AB4@uswest.net> References: <4.3.2.7.2.20000805110010.00b8d348@127.0.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Me thinks you sell yourself too short. I would touch it up a tad to highlight the process, otherwise the length appears to be OK. Am sure that someone can help with the link. Just my $0.02 Frank At 10:09 AM 8/5/2000 -0600, Joe Warner wrote: >Thanks Frank. Actually, I thought about posting it on Daemon News but it >would probably be too long, since I don't have a URL to link it to. Oh >well....such is the life of a lamer. 8^) > >Joe > > >Frank Pawlak wrote: > > > IMHO this is a great story. Perhaps this deserves a daemon news spot with > > some HOWTO implications. > > > > Regards, > > Frank > > > > At 08:32 AM 8/5/2000 -0600, Joe Warner wrote: > > >Hi all, > > > > > > I've had a real learning experience with my FreeBSD (3.4) system at > > >work over the past couple of days and at the risk of making myself look > > >like an idiot, I felt it important enough to share. Since I'm a newbie > > >and hope to help other newbies when facing similar situations, this > > >email is directed mainly at freebsd-newbies. However, I also felt it > > >important enough to share with freebsd-advocacy because of how amazed I > > >am with the OS. Instead of a little cartoon devil, maybe the mascot > > >should be the Energizer Bunny? FreeBSD keeps going and going and > > >going... 8^) Anyway, please bear with me. This is probably going to be > > >pretty lengthy, so for those of you don't like to read or are > > >uninterested, just close this email and delete it now. For the rest of > > >you, read on... > > > When I came into work last Thursday morning, I noticed that my PC > > >(Compaq Deskpro 2000), running FreeBSD 3.4 was at the login prompt and > > >my WIN NT machine was at the boot up password. I realized then that the > > >inevitable had happened....Power Outage! Thinking that power > > >outages/cold reboots meant death to most UNIX systems, I hurried to > > >prevent this from happening again and hooked up an APC Smart-UPS 1000 > > >that we had sitting in one of our storage closets. Hooking it up to my > > >FreeBSD machine was easy enough. I just plugged the power cord into a > > >receptacle and then plugged the power from the CPU and monitor into the > > >back of the UPS. I finished by attaching the serial cable on the UPS to > > >the serial port on the back of the CPU (COM1) - There is only one serial > > >port available for Compaq Deskpro's. After hooking it up, I realized > > >that I would need to install some software that could communicate with > > >the UPS through the serial line and allow me to do a graceful shutdown > > >in the event of power loss. I went to APC's web site and though they > > >had their Powerchute software available for many commercial versions of > > >UNIX, I didn't see anything that was designed specifically for any of > > >the BSD's. They even had a Linux version and I learned later that at > > >least one person was running this successfully under Linux emulation on > > >his FreeBSD 3.4 system. I didn't want to run this under Linux emulation > > >if I didn't have to. Later, I came across an application in the ports > > >collection called UPSD - 2.0 that seemed to be designed specifically to > > >work with the APC Smart-UPS models. I loaded the 4th CD from the CD ROM > > >set and from /usr/ports/sysutils/upsd/ I typed make install and > > >installed it. I noticed that there wasn't any documentation included > > >with this port, not even a man page. It loaded only 2 files, the upsd > > >executable in /usr/local/sbin and the configuration file (upsd.conf) in > > >/usr/local/etc I su'd to root and attempted to spawn the daemon by > > >cd'ng to /usr/local/sbin and typing # ./upsd At this point, my whole > > >system locked up tighter than a drum! I couldn't kill X and couldn't > > >switch to another terminal. Nothing! I had to cold-reboot my system > > >again! After I booted back up, I looked at my logs and noticed a > > >message indicating there was a permission problem with /dev/cuaa0 This > > >device is owned by uucp and belongs to the dialer group. I su'd to root > > >again and adjusted the permissions so that other users would have access > > >and then tried to execute the program again. Same thing happened, > > >complete lockup! At this point, I was pretty frustrated and none the > > >information I had read in my books or the answers I received from > > >posting to FreeBSD-Questions seemed to help. I cd'd to > > >/usr/ports/sysutils/upsd and typed make deinstall and went home. > > > When I came in Friday morning, I noticed an email from someone who > > >said they were using a port called UPSMON - 2.1.3 with an APC Smart-UPS > > >on their FreeBSD system without any problems. This port wasn't on the > > >CD ROM set, so when I installed it, it had to fetch it from an ftp > > >site. No problem, right? Wrong! I installed this port and decided to > > >reboot. Big mistake! Now, during boot-up, my system would just hang > > >at: > > > > > >local package initialization: Cannot open /dev/cuaa0: Permission denied > > >upsmond<---(this is where it would hang) > > > > > > After hearing the voice of Ralph from the Simpsons in my head, going > > >Ha! Ha!.., I thought, now what do I do! After going through all my > > >books and documentation and trying to boot into single-user mode, fixit > > >mode from the 2nd cd in the cd rom set and even from kernel.GENERIC, I > > >realized I wasn't getting anywhere. My machine would always hang when > > >trying to launch the upsmond daemon during boot up. As a last resort, I > > >posted to FreeBSD-Questions and got the answer I was looking for. I was > > >told to go into single-user mode. At the beginning of the boot-up > > >process, there is a ten second count down that tells you to either hit > > >enter or wait for the count down to finish for system boot-up. Before > > >the counter finishes, you hit the space bar and you're presented with a > > >prompt where you can specify different boot options. I specified "boot > > >-s" for single user mode. In The Complete FreeBSD, it tells you to boot > > >into single-user mode and run fsck on / by issuing: fsck -y / I > > >ran this on / and /dev/wd0s1a, respectively. Then it tells you to mount > > >/ by typing: mount -u / I did this and it let me mount it. Lastly, it > > >says to mount /usr by typing: mount /usr It would let me mount this but > > >only with read access. I needed write access so that I could go into > > >/usr/local/etc/rc.d/ and either remove or change the upsmond.sh file in > > >there that was causing my system to hang. I got a response from someone > > >telling me to mount /usr by typing the following: mount -rwf /usr This > > >worked and I was able to edit upsmond.sh so that it was pointing to > > >/dev/cuaa1 and not cuaa0. This got my system booting. I found out > > >later that I could have successfully mounted /usr with r/w access if I > > >would have first fsck'd it by issuing: fsck -y /usr (I probably should > > >have done this for /var too) > > > I got my system booting again (Whew!) but still haven't figured out > > >why /dev/cuaa0 causes problems. I seems as if some kind of conflict is > > >going on, maybe something else is using this device? I haven't found > > >the answer to this yet. I got an email response back from APC, saying > > >they did have an application that would work with FreeBSD but I would > > >need to purchase their Simple UNIX Serial cable for $39.00 in order for > > >it to work. So, now I don't know if it's a device conflict or the cable > > >but I doubt I'll shell out the money for a new cable. Maybe my manager > > >will let me order it and reimburse me? > > > I've always thought that cold reboot/shutdowns were death to UNIX > > >systems, especially if you did it more than 5 or 6 times. I've > > >completely trashed my systems this way when I was using Red Hat 6.x and > > >Caldera 2.x in the past. Cold booted more than 5 times and got the > > >dreaded "kernel panic" message and had to reinstall. I ended up cold > > >booting my FreeBSD system more than 12 times the last couple of days and > > >it's still going! 8^) So, the moral of this story? FreeBSD is > > >forgiving, you just need to tell it how to forgive you! And...forgive > > >me for such a long story... 8^} > > > > > >Joe > > > > > > > > >-- > > > > > > FreeBSD = The Power to Serve > > > ..Simply put = FreeBSD Rocks! > > > > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-advocacy" in the body of the message > >-- > > FreeBSD = The Power to Serve > ..Simply put = FreeBSD Rocks! > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-advocacy" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 10:44:21 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from tisch.mail.mindspring.net (tisch.mail.mindspring.net [207.69.200.157]) by hub.freebsd.org (Postfix) with ESMTP id C1ABF37BA78; Sat, 5 Aug 2000 10:44:07 -0700 (PDT) (envelope-from stuyman@confusion.net) Received: from confusion.net (user-2ive75l.dialup.mindspring.com [165.247.28.181]) by tisch.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id NAA26192; Sat, 5 Aug 2000 13:43:50 -0400 (EDT) Message-ID: <398C5216.E9153917@confusion.net> Date: Sat, 05 Aug 2000 13:42:46 -0400 From: Laurence Berland Organization: B.R.A.T.T. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Frank Pawlak Cc: Joe Warner , freebsd-newbies@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG Subject: Re: Newbie Learning Experience References: <4.3.2.7.2.20000805110010.00b8d348@127.0.0.1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd think maybe you can submit it as a story for the september monthly of daemon news. IMHO this is the sort of thing daemon news needs. Frank Pawlak wrote: > > IMHO this is a great story. Perhaps this deserves a daemon news spot with > some HOWTO implications. > > Regards, > Frank > > At 08:32 AM 8/5/2000 -0600, Joe Warner wrote: > >Hi all, > > > > I've had a real learning experience with my FreeBSD (3.4) system at > >work over the past couple of days and at the risk of making myself look > >like an idiot, I felt it important enough to share. Since I'm a newbie > >and hope to help other newbies when facing similar situations, this > >email is directed mainly at freebsd-newbies. However, I also felt it > >important enough to share with freebsd-advocacy because of how amazed I > >am with the OS. Instead of a little cartoon devil, maybe the mascot > >should be the Energizer Bunny? FreeBSD keeps going and going and > >going... 8^) Anyway, please bear with me. This is probably going to be > >pretty lengthy, so for those of you don't like to read or are > >uninterested, just close this email and delete it now. For the rest of > >you, read on... > > When I came into work last Thursday morning, I noticed that my PC > >(Compaq Deskpro 2000), running FreeBSD 3.4 was at the login prompt and > >my WIN NT machine was at the boot up password. I realized then that the > >inevitable had happened....Power Outage! Thinking that power > >outages/cold reboots meant death to most UNIX systems, I hurried to > >prevent this from happening again and hooked up an APC Smart-UPS 1000 > >that we had sitting in one of our storage closets. Hooking it up to my > >FreeBSD machine was easy enough. I just plugged the power cord into a > >receptacle and then plugged the power from the CPU and monitor into the > >back of the UPS. I finished by attaching the serial cable on the UPS to > >the serial port on the back of the CPU (COM1) - There is only one serial > >port available for Compaq Deskpro's. After hooking it up, I realized > >that I would need to install some software that could communicate with > >the UPS through the serial line and allow me to do a graceful shutdown > >in the event of power loss. I went to APC's web site and though they > >had their Powerchute software available for many commercial versions of > >UNIX, I didn't see anything that was designed specifically for any of > >the BSD's. They even had a Linux version and I learned later that at > >least one person was running this successfully under Linux emulation on > >his FreeBSD 3.4 system. I didn't want to run this under Linux emulation > >if I didn't have to. Later, I came across an application in the ports > >collection called UPSD - 2.0 that seemed to be designed specifically to > >work with the APC Smart-UPS models. I loaded the 4th CD from the CD ROM > >set and from /usr/ports/sysutils/upsd/ I typed make install and > >installed it. I noticed that there wasn't any documentation included > >with this port, not even a man page. It loaded only 2 files, the upsd > >executable in /usr/local/sbin and the configuration file (upsd.conf) in > >/usr/local/etc I su'd to root and attempted to spawn the daemon by > >cd'ng to /usr/local/sbin and typing # ./upsd At this point, my whole > >system locked up tighter than a drum! I couldn't kill X and couldn't > >switch to another terminal. Nothing! I had to cold-reboot my system > >again! After I booted back up, I looked at my logs and noticed a > >message indicating there was a permission problem with /dev/cuaa0 This > >device is owned by uucp and belongs to the dialer group. I su'd to root > >again and adjusted the permissions so that other users would have access > >and then tried to execute the program again. Same thing happened, > >complete lockup! At this point, I was pretty frustrated and none the > >information I had read in my books or the answers I received from > >posting to FreeBSD-Questions seemed to help. I cd'd to > >/usr/ports/sysutils/upsd and typed make deinstall and went home. > > When I came in Friday morning, I noticed an email from someone who > >said they were using a port called UPSMON - 2.1.3 with an APC Smart-UPS > >on their FreeBSD system without any problems. This port wasn't on the > >CD ROM set, so when I installed it, it had to fetch it from an ftp > >site. No problem, right? Wrong! I installed this port and decided to > >reboot. Big mistake! Now, during boot-up, my system would just hang > >at: > > > >local package initialization: Cannot open /dev/cuaa0: Permission denied > >upsmond<---(this is where it would hang) > > > > After hearing the voice of Ralph from the Simpsons in my head, going > >Ha! Ha!.., I thought, now what do I do! After going through all my > >books and documentation and trying to boot into single-user mode, fixit > >mode from the 2nd cd in the cd rom set and even from kernel.GENERIC, I > >realized I wasn't getting anywhere. My machine would always hang when > >trying to launch the upsmond daemon during boot up. As a last resort, I > >posted to FreeBSD-Questions and got the answer I was looking for. I was > >told to go into single-user mode. At the beginning of the boot-up > >process, there is a ten second count down that tells you to either hit > >enter or wait for the count down to finish for system boot-up. Before > >the counter finishes, you hit the space bar and you're presented with a > >prompt where you can specify different boot options. I specified "boot > >-s" for single user mode. In The Complete FreeBSD, it tells you to boot > >into single-user mode and run fsck on / by issuing: fsck -y / I > >ran this on / and /dev/wd0s1a, respectively. Then it tells you to mount > >/ by typing: mount -u / I did this and it let me mount it. Lastly, it > >says to mount /usr by typing: mount /usr It would let me mount this but > >only with read access. I needed write access so that I could go into > >/usr/local/etc/rc.d/ and either remove or change the upsmond.sh file in > >there that was causing my system to hang. I got a response from someone > >telling me to mount /usr by typing the following: mount -rwf /usr This > >worked and I was able to edit upsmond.sh so that it was pointing to > >/dev/cuaa1 and not cuaa0. This got my system booting. I found out > >later that I could have successfully mounted /usr with r/w access if I > >would have first fsck'd it by issuing: fsck -y /usr (I probably should > >have done this for /var too) > > I got my system booting again (Whew!) but still haven't figured out > >why /dev/cuaa0 causes problems. I seems as if some kind of conflict is > >going on, maybe something else is using this device? I haven't found > >the answer to this yet. I got an email response back from APC, saying > >they did have an application that would work with FreeBSD but I would > >need to purchase their Simple UNIX Serial cable for $39.00 in order for > >it to work. So, now I don't know if it's a device conflict or the cable > >but I doubt I'll shell out the money for a new cable. Maybe my manager > >will let me order it and reimburse me? > > I've always thought that cold reboot/shutdowns were death to UNIX > >systems, especially if you did it more than 5 or 6 times. I've > >completely trashed my systems this way when I was using Red Hat 6.x and > >Caldera 2.x in the past. Cold booted more than 5 times and got the > >dreaded "kernel panic" message and had to reinstall. I ended up cold > >booting my FreeBSD system more than 12 times the last couple of days and > >it's still going! 8^) So, the moral of this story? FreeBSD is > >forgiving, you just need to tell it how to forgive you! And...forgive > >me for such a long story... 8^} > > > >Joe > > > > > >-- > > > > FreeBSD = The Power to Serve > > ..Simply put = FreeBSD Rocks! > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-advocacy" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-advocacy" in the body of the message -- Laurence Berland <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Windows 98: n. useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition. http://stuy.debate.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 11:47:56 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from slkcpop2.slkc.uswest.net (slkcpop2.slkc.uswest.net [206.81.128.2]) by hub.freebsd.org (Postfix) with SMTP id D895C37BAA3 for ; Sat, 5 Aug 2000 11:47:52 -0700 (PDT) (envelope-from jswarner@uswest.net) Received: (qmail 80367 invoked by alias); 5 Aug 2000 18:47:52 -0000 Delivered-To: fixup-freebsd-advocacy@freebsd.org@fixme Received: (qmail 80352 invoked by uid 0); 5 Aug 2000 18:47:51 -0000 Received: from unknown (HELO uswest.net) (63.224.106.120) by slkcpop2.slkc.uswest.net with SMTP; 5 Aug 2000 18:47:51 -0000 Message-ID: <398C606F.62E181BA@uswest.net> Date: Sat, 05 Aug 2000 12:43:59 -0600 From: Joe Warner X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-newbies@freebsd.org, freebsd-advocacy@freebsd.org Subject: Re: Newbie Learning Experience Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Pawlak wrote: Me thinks you sell yourself too short. I would touch it up a tad to highlight the process, otherwise the length appears to be OK. Am sure that someone can help with the link. Just my $0.02 Frank And...Laurence Berland: I'd think maybe you can submit it as a story for the september monthly of daemon news. IMHO this is the sort of thing daemon news needs. ...I respond: Thanks for the vote of confidence, guys! 8^) I'll do my best to touch it up a bit and see if Daemon News wants it. I also plan to compose a related article, with step by step instructions on what to do when your system hangs and submit it to The FreeBSD Documentation Project. Thanks again, Joe -- FreeBSD = The Power to Serve ..Simply put = FreeBSD Rocks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 12:17: 0 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from mail2.rdc2.on.home.com (mail2.rdc2.on.home.com [24.9.0.41]) by hub.freebsd.org (Postfix) with ESMTP id 188E037B713 for ; Sat, 5 Aug 2000 12:16:57 -0700 (PDT) (envelope-from groberts3@home.com) Received: from home.com ([24.141.201.170]) by mail2.rdc2.on.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000805191655.DDSD25041.mail2.rdc2.on.home.com@home.com>; Sat, 5 Aug 2000 12:16:55 -0700 Message-ID: <398C6899.1FA1ABF8@home.com> Date: Sat, 05 Aug 2000 15:18:49 -0400 From: LCD X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Joe Warner , freebsd-advocacy@freebsd.org Subject: Re: Newbie Learning Experience References: <398C606F.62E181BA@uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think it might be a nice article for the freebsd diary as well, it's just the kind of thing you'd find there. Greg Roberts Joe Warner wrote: > > Frank Pawlak wrote: > > Me thinks you sell yourself too short. I would touch it up a tad to > > highlight the process, otherwise the length appears to be OK. Am sure > that > someone can help with the link. Just my $0.02 > > Frank > > And...Laurence Berland: > > I'd think maybe you can submit it as a story for the september > monthly > of daemon news. IMHO this is the sort of thing daemon news needs. > > ...I respond: > > Thanks for the vote of confidence, guys! 8^) I'll do my best to > touch it up a bit and see if Daemon News wants it. I also plan to > compose a related article, with step by step instructions on what to do > when your system hangs and submit it to The FreeBSD Documentation > Project. > > Thanks again, > > Joe > > -- > > FreeBSD = The Power to Serve > ..Simply put = FreeBSD Rocks! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-advocacy" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message From owner-freebsd-advocacy Sat Aug 5 23:41:26 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from q.closedsrc.org (ip233.gte15.rb1.bel.nwlink.com [209.20.244.233]) by hub.freebsd.org (Postfix) with ESMTP id 3703437B5F9; Sat, 5 Aug 2000 23:41:00 -0700 (PDT) (envelope-from lplist@closedsrc.org) Received: from localhost (lplist@localhost) by q.closedsrc.org (8.11.0/8.11.0) with ESMTP id e766e6w18947; Sat, 5 Aug 2000 23:40:06 -0700 (PDT) (envelope-from lplist@closedsrc.org) Date: Sat, 5 Aug 2000 23:40:06 -0700 (PDT) From: Linh Pham To: Laurence Berland Cc: Frank Pawlak , Joe Warner , freebsd-newbies@FreeBSD.ORG, freebsd-advocacy@FreeBSD.ORG Subject: Re: Newbie Learning Experience In-Reply-To: <398C5216.E9153917@confusion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Aug 2000, Laurence Berland mumbled: > I'd think maybe you can submit it as a story for the september monthly > of daemon news. IMHO this is the sort of thing daemon news needs. I sent in a semi-HOWTO article on setting up FreeBSD 4.0 on a Compaq iPaq and it was accepted... it's in this month's issue :) You may want to take a look at my article as a quick reference... but all you need to do is to break up your write-up into easy to follow paragraphs, and you should be set. // Linh Pham // http://closedsrc.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message