Is stdout from /etc/rc captured anywhere?
During boot, does FreeBSD capture the output of /etc/rc anywhere? dmesg is for the kernel only. syslogd is not used to capture simple 'echo' commands from /etc/rc. If you can't see the physical console as the system boots up, is there another method to see this /etc/rc output later? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gpilotd headaches!?!?!
Hello all... I have been 'round n circles with this error message when I try to connect my palm with gnome palm pilot conduits.. The Application gpilotd has quit unexpectedly. then in the console... (gpilotd-control-applet:922): gpilotd-WARNING **: gnome-pilot-client.gob:819: Caught exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0 I have installed everything on this 5.2.1 box from ports after a cvs-up. I even tried 4.10 with no luck. I am using: evolution-1.4.6_1 gnomepilot2-2.0.10_2 libIDL-0.8.3_2 pilot-link-0.11.8_3 ORBit2-2.10.3 ORBit-0.5.17_2 gob2-2.0.8 I have seen other people with this error, but I haven't seen anyone who fixed it. I can get pilot-link to work with 5.2.1, but gpilotd still crashes. Maybe there is a way to sync evo directly with pilot-link?? Any suggestions would be helpful because I have been working on this for a week. David This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, or an employee or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error please notify us immediately by replying to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck not recognizing vinum filesystem type
Nate Lawson [EMAIL PROTECTED] 12/09/03 11:13AM On Tue, 9 Dec 2003, DAVID THOMPSON wrote: I am a relatively new FreeBSD user and I have never posted a request for help before so I hope I am doing this right and not plugging up the board with irrelevant and out of context questions. My apologies if I am. Here is my problem: Welcome to the club! I have vinum installed on my FreeBSD 5.1-Release box. Vinum starts and actually it is 5.0-Release...my mistake runs fine, but I can't fsck any of the volumes because it says... fsck: Could not determine filesystem type. If I do a fsck -t ufs /dev/vinum/??? it will work fine, but it's when I don't explicity tell fsck what the filesystem type is that I get this error. You probably didn't disklabel the disk. Do a man disklabel. In particular, you should do: disklabel -w /dev/vinum/??? auto Edit the disklabel: disklabel -e /dev/vinum/??? Then newfs: newfs /dev/vinum/??? Note that you can potentially trash the system with all this, so please read the section in the handbook on setting up vinum and/or disklabels before doing this on a production system. In fact, test on a scratch disk first. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-vinum.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html -Nate unfortunately I did run the disklabel route and everything checks out. I have fdisk'd, disklabel'd, and reconfigured my drives so many times I have dreams about it. The only difference between my box at home and the one at work is that I ran a cvsup and portupgrade on my one at home when I was doing the initial install. Is there a possiblity that the fsck binary is somehow the wrong rev.? I am trying to understand how fsck determines the filesystem, and I thought this was done by checking the superblock. However, it seems that the superblock only denotes one definition of filesystem type (e.g. FreeBSD, vinum, etc.) and not the other definition (e.g. ufs, ext3, etc...). At least these are the two definitions of fstype that I know of. So I am still stuck at trying to determine how fsck automatically determines the second definition of fstype. Remember that fsck works if I explicitly tell it to use ufs. My other theory is that maybe my newfs binary isn't doing it's thing. My understanding was that in version 5.0 ufs2 would be the default, but it seems like my newfs uses ufs1 as it's default. This makes me wonder if maybe other things aren't working as they should. Any ideas, leads, thoughts, or suggestions are always appreciated... thanks again. Dave. This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, or an employee or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error please notify us immediately by replying to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck not recognizing vinum filesystem type
Hello all... I am a relatively new FreeBSD user and I have never posted a request for help before so I hope I am doing this right and not plugging up the board with irrelevant and out of context questions. My apologies if I am. Here is my problem: I have vinum installed on my FreeBSD 5.1-Release box. Vinum starts and runs fine, but I can't fsck any of the volumes because it says... fsck: Could not determine filesystem type. If I do a fsck -T ufs /dev/vinum/??? it will work fine, but it's when I don't explicity tell fsck what the filesystem type is that I get this error. Everything relating to vinum seems to work fine and the configuration is identical to the one I made at work (that works) except that the server at work is a 5.0 box. This wouldn't be a big deal, but when the server recycles fsck Could not determine filesystem type and dumps me into single user mode so I can fsck my volumes. This is a problem!! I wonder if I could tell fsck to use -T ufs in the rc.conf file, but I feel like I am just sidestepping the issue. FSCK should be able to detemine the filesystem type without help as far as I know, but I'm not sure what the problem could be. Any help or suggestions would be greatly appreciated. Thanks. This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, or an employee or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error please notify us immediately by replying to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
