Re: Error code 254
Mel Flynn wrote: On Tuesday 11 August 2009 12:56:40 Per olof Ljungmark wrote: Mel Flynn wrote: On Tuesday 11 August 2009 12:20:00 Per olof Ljungmark wrote: Mel Flynn wrote: On Tuesday 11 August 2009 10:53:21 Per olof Ljungmark wrote: Mel Flynn wrote: On Tuesday 11 August 2009 09:27:06 Mel Flynn wrote: On Tuesday 11 August 2009 08:53:59 Per olof Ljungmark wrote: Mel Flynn wrote: On Tuesday 11 August 2009 02:48:49 Per olof Ljungmark wrote: === Installing documentation in /usr/local/share/doc/pear/XML_Serializer. === Installing tests in /usr/local/share/pear/tests/XML_Serializer. === Installing examples in /usr/local/share/examples/pear/XML_Serializer. *** Error code 254 Hmmm, when I try portupgrade -fO pear the error pops up here too. Should I suspect the package database then? === Installing for pear-1.8.1 === pear-1.8.1 depends on file: /usr/local/include/php/main/php.h - found === pear-1.8.1 depends on file: /usr/local/lib/php/20060613/pcre.so - found === pear-1.8.1 depends on file: /usr/local/lib/php/20060613/xml.so - found === Generating temporary packing list *** Error code 254 Is it really at that point? Could you try a make -dl install again? If it's the package list generation for real, then I'm gonna suspect something on a system level, like IO errors or read-only mounts. If it is the same thing with pear install command, then perhaps you should pkg_delete -r pear-1.8.1 (careful, will uninstall anything depending on pear) and start over to see if the error persists. The pear command sure can use some more verbosity then. Yes, reinstalling pear made the problem go away. Unfortunately this will never tell us what was actually wrong but at least it works now. Thanks a lot for your input. -- per ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
loader halting
Good day. While server is booting, I see this: /boot.config: -Dh BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard serial port BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 637kB/3668864kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (em...@email, Fri Aug 7 14:18:25 MSD 2009) | And boot process is stopping. I tried to boot /boot/loader.old, tried to boot from other hdd (there is a mirror) - in all cases I see the same picture. Where I should look to find a source of troubles? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: please help to uninstall FreeBSD!!!
On Mon, Aug 10, 2009 at 01:00:31PM -0700, Raisa Brokhshtut typed: Hello, ? My old desktop has FreeBSD that I have never used. One of the friends of my son installed it long ago, but no one used that PC since then. Now I want to get rid of this program and to install Windows.?Every time when I boot this PC it prompts?for a user login which I don't know. This guy who intalled FreeBSD is not around anymore. ? Anyway, I would greatly appreciate if you would guide me how to uninstall that program. I don't have windows reskue cd. So I want to completly remove that FreeBSD from my PC and to install?the Windows operating system from CD. The FreeBSD program can not be uninstalled. Live with it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: location of user crontab files?
On Tue, Aug 11, 2009 at 07:21:08PM -0400, Karl Vogel typed: On Tue, 11 Aug 2009 10:50:54 -0400, Identry iden...@gmail.com said: I Where are user crontab files stored in the file system? I want to make I sure this info is backed up. They're in /var/cron/tabs. If you're using individual crontab files, be sure to rename /etc/crontab or you might have duplicated cronjobs running simultaneously. I don't think this is sound advise. Leaving /etc/crontab (the system crontab) to do the system maintenance jobs it is supposed to do and putting additional scripts and jobs in user tabs is normal practice and won't cause any problems. Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot sector f*ed
On Tue, 11 Aug 2009 17:52:29 +0200 Polytropon free...@edvax.de wrote: On Tue, 11 Aug 2009 09:34:13 -0400, PJ af.gour...@videotron.ca wrote: I've got another disk about the same size on the machine and I'm wonderiing how could I transfer the whole shebang to it? Maybe an 1:1 copy using dd with a bs=1m would work. Maybe it would, if the new disk size is = the old one. Would doing a minimum 7.2 install be enough, followed by copying all the slices to the corresponding slices on the new disk? I'm thinking of mounting the broken drive on the new one and then copying... does that sound about right? No. Does not. :-) The proper way of doing this - or at least ONE of the proper ways - is to use the intended tools for this task. These are dump and restore. First of all, you use a FreeBSD live system (such as FreeSBIE) or the livefs CD of the FreeBSD OS to run the OS. The goal is: Most minimal interaction with the drives. Good principles, but .. Let's assume ad0 is your source disk and ad1 the target disk. You can use the sysinstall tool to slice and partition the target disk. You can create the same layout as on the source disk. Of course, using tools like bsdlabel and newfs is valid, too. If you're done, things go like this: 1. Check the source. # fsck /dev/ad0s1a /dev/ad0s1e /dev/ad0s1f /dev/ad0s1g /dev/ad0s1h Er, from PJ's original message (and the subject line) the boot sector, sector 0, is hosed. So the partition/slice table is hosed, or at least untrustworthy. So what then can /dev/ad0s1a and the others refer to? dd may indeed be the best way to at least get a raw copy of the existing disk. After which perhaps the boot sector can be rewritten with the right values (if available?) so that such as fsck and dump can proceed. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: location of user crontab files?
Ruben de Groot wrote: On Tue, Aug 11, 2009 at 07:21:08PM -0400, Karl Vogel typed: On Tue, 11 Aug 2009 10:50:54 -0400, Identry iden...@gmail.com said: I Where are user crontab files stored in the file system? I want to make I sure this info is backed up. They're in /var/cron/tabs. If you're using individual crontab files, be sure to rename /etc/crontab or you might have duplicated cronjobs running simultaneously. I don't think this is sound advise. Leaving /etc/crontab (the system crontab) to do the system maintenance jobs it is supposed to do and putting additional scripts and jobs in user tabs is normal practice and won't cause any problems. I've learned not to touch /etc/crontab at all. Saves some time during upgrades/mergemaster. -- Frederique ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot sector f*ed
Ian Smith wrote: On Tue, 11 Aug 2009 17:52:29 +0200 Polytropon free...@edvax.de wrote: On Tue, 11 Aug 2009 09:34:13 -0400, PJ af.gour...@videotron.ca wrote: I've got another disk about the same size on the machine and I'm wonderiing how could I transfer the whole shebang to it? Maybe an 1:1 copy using dd with a bs=1m would work. Maybe it would, if the new disk size is = the old one. Would doing a minimum 7.2 install be enough, followed by copying all the slices to the corresponding slices on the new disk? I'm thinking of mounting the broken drive on the new one and then copying... does that sound about right? No. Does not. :-) The proper way of doing this - or at least ONE of the proper ways - is to use the intended tools for this task. These are dump and restore. First of all, you use a FreeBSD live system (such as FreeSBIE) or the livefs CD of the FreeBSD OS to run the OS. The goal is: Most minimal interaction with the drives. Good principles, but .. Let's assume ad0 is your source disk and ad1 the target disk. You can use the sysinstall tool to slice and partition the target disk. You can create the same layout as on the source disk. Of course, using tools like bsdlabel and newfs is valid, too. If you're done, things go like this: 1. Check the source. # fsck /dev/ad0s1a /dev/ad0s1e /dev/ad0s1f /dev/ad0s1g /dev/ad0s1h Er, from PJ's original message (and the subject line) the boot sector, sector 0, is hosed. So the partition/slice table is hosed, or at least untrustworthy. So what then can /dev/ad0s1a and the others refer to? dd may indeed be the best way to at least get a raw copy of the existing disk. After which perhaps the boot sector can be rewritten with the right values (if available?) so that such as fsck and dump can proceed. cheers, Ian Thanks, Ian... I'm actually at the stage of doing the save/copy/transfer or whatever you can call it: here's what I am thinking and on which I need clarification. I ran HDD regenerator and it immediately flagged the very first sector as being Bad. On bootint, just before the crash, the boot process started... hesitated, lurched forward, hesitated and then proceeded to load only some minutes later closing down with a 177mb dump. I knew then there was a problem.. :-) I have a 2nd disk just checked (with the regenerator - 12 hrs waiting on 2.4ghz cpu). If, indeed, the boot sector is the only thing mucked up, I should be able to copy the rest onto the 2nd(target) disk NP. The question, then, is how to deal with the boot sector. As I understand it, the boot sector has the partition information needed to run things for the rest of the disk. So, copying the damaged source disk will not give me the boot sector needed. I happen to have a another instance of 7.2 installed on a smaller disk but that boot sector, obviously will not be quite right, right? I presume that I can just boot up the spare 7.2 disk, do the dd stuff from source to target and we have stage 1 done. I get the impression to get this second stage (the boot stuff) I should do a minimal setup of the original configuration on a third disk the same size as the source and then copy the boot sector to the tartget. If for some reason, I haven't got the slices/partitions right, then I can just redo the whole shebang until I've got it right. A little tortured, but could work, or have I got it wrong? Of course, if there is a more elegant and simpler solution, shoot ! TIA PJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: please help to uninstall FreeBSD!!!
Hi, Am Montag, 10. Aug 2009, 13:00:31 -0700 schrieb Raisa Brokhshtut: My old desktop has FreeBSD that I have never used. [...] Now I want to get rid of this program and to install Windows. Anyway, I would greatly appreciate if you would guide me how to uninstall that program. [...] So I want to completly remove that FreeBSD from my PC and to install the Windows operating system from CD. This problem is best solved the common way Windows users do with any software: Just reinstall the desired program as often until it works. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: please help to uninstall FreeBSD!!!
Bertram Scharpf wrote: Hi, Am Montag, 10. Aug 2009, 13:00:31 -0700 schrieb Raisa Brokhshtut: My old desktop has FreeBSD that I have never used. [...] Now I want to get rid of this program and to install Windows. Anyway, I would greatly appreciate if you would guide me how to uninstall that program. [...] So I want to completly remove that FreeBSD from my PC and to install the Windows operating system from CD. This problem is best solved the common way Windows users do with any software: Just reinstall the desired program as often until it works. Are you suggesting that continuous reinstalling of a program numerous times until it works is a Windows-only tactic? ...have you ever had a port that wouldn't install properly/completely on the first, or fifth try? Give the guy some credit... he at least did enough homework to find this list. To the Original Poster: The easiest way to remove FreeBSD and get back to a Windows environment would be to simply boot from a Windows install CD, and have the installer delete all 'partitions' it finds (including unknown). This of course will require having the Windows install CD. Your desktop may still have a sticker with a license key on it, in which case, you can simply borrow the Windows CD from someone else if you don't own one. Steve smime.p7s Description: S/MIME Cryptographic Signature
Re: boot sector f*ed
On Wed, 12 Aug 2009, PJ wrote: Ian Smith wrote: On Tue, 11 Aug 2009 17:52:29 +0200 Polytropon free...@edvax.de wrote: [..] Let's assume ad0 is your source disk and ad1 the target disk. You can use the sysinstall tool to slice and partition the target disk. You can create the same layout as on the source disk. Of course, using tools like bsdlabel and newfs is valid, too. If you're done, things go like this: 1. Check the source. # fsck /dev/ad0s1a /dev/ad0s1e /dev/ad0s1f /dev/ad0s1g /dev/ad0s1h Er, from PJ's original message (and the subject line) the boot sector, sector 0, is hosed. So the partition/slice table is hosed, or at least untrustworthy. So what then can /dev/ad0s1a and the others refer to? dd may indeed be the best way to at least get a raw copy of the existing disk. After which perhaps the boot sector can be rewritten with the right values (if available?) so that such as fsck and dump can proceed. Thanks, Ian... I'm actually at the stage of doing the save/copy/transfer or whatever you can call it: here's what I am thinking and on which I need clarification. I ran HDD regenerator and it immediately flagged the very first sector as being Bad. On bootint, just before the crash, the boot process started... hesitated, lurched forward, hesitated and then proceeded to load only some minutes later closing down with a 177mb dump. I knew then there was a problem.. :-) The dump, presumably from a panic, may be related or a consequence of whatever hardware issue may have clobbered your boot sector, or it may not. Your disk may be really in trouble, or it may just need its boot sector rewriting, if not a 'hard' sector error. But first, backup .. I have a 2nd disk just checked (with the regenerator - 12 hrs waiting on 2.4ghz cpu). I don't know of this regenerator. dd'ing a drive to /dev/null is a pretty good way to surface test a disk, not taking a fraction that long. If, indeed, the boot sector is the only thing mucked up, I should be able to copy the rest onto the 2nd(target) disk NP. The question, then, Read man dd carefully, do some practice runs. You'll want conv=noerror to copy all but any bad sectors, or dd may fail. For any section with bad sectors, you may need to use bs=512 and maybe skip (source) and seek (destination) to keep things aligned. I'm no expert on dd, have't had to do that for years, nor am I so hot on fdisk, bsdlabel or boot0cfg on FreeBSD 7, but there are plenty of folks here that are. is how to deal with the boot sector. As I understand it, the boot sector has the partition information needed to run things for the rest of the disk. So, copying the damaged source disk will not give me the boot sector needed. That's right, and no, but if you salvage everything else, and you know which slice/s were used and how big its partition/s are, you should be ok. Once back up, apart from normal backups, having a copy of your boot sector plus fdisk / bsdlabel output on another disk - or even on paper - can be very handy :) I happen to have a another instance of 7.2 installed on a smaller disk but that boot sector, obviously will not be quite right, right? No, you don't want to copy another disk's boot sector; you'll want to use fdisk to make a new one that fits. If there's a jumper for it, write protect the bad drive first, and move it away from being ad0. Seek expert help on the commands, as above .. I presume that I can just boot up the spare 7.2 disk, do the dd stuff from source to target and we have stage 1 done. If the disk sizes match, should be good. I get the impression to get this second stage (the boot stuff) I should do a minimal setup of the original configuration on a third disk the same size as the source and then copy the boot sector to the tartget. If for some reason, I haven't got the slices/partitions right, then I can just redo the whole shebang until I've got it right. A little tortured, but could work, or have I got it wrong? Of course, if there is a more elegant and simpler solution, shoot ! Again, I wouldn't copy a boot sector (though on identical disks, that should work). fdisk will write a new boot sector, and if you've got the slice sizes right, then your old bsdlabels should still be there for your various BSD partitions. Now .. exit the clown and bring on the fdisk / bsdlabel experts, please. Good luck, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with pkg_delete *
Hi, I want to clean up and start again the installation of pkg since i did a broken update in python and qt and pretty much everything is broken portupgrade never ends, doing make in ports crash pretty much all the time . I tried # pkg_delete '*' Segmentation fault (core dumped) # pkg_delete 'kde*' Segmentation fault (core dumped) Failed both in multiuser so I tried to do this as monouser and was the same. Im running FreeBSD user.domain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Any suggestions? Thanks for any help. Damian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: please help to uninstall FreeBSD!!!
Are you suggesting that continuous reinstalling of a program numerous times until it works is a Windows-only tactic? Bad software exists on every platform, in proportion to the platform's installed base. To the Original Poster: The easiest way to remove FreeBSD and get back to a Windows environment would be to simply boot from a Windows install CD, and have the installer delete all 'partitions' it finds (including unknown). Correct, and counter to another posters statement that Windows attempts to wipe entire disks when installing. Yes, that's the default choice, which is perfectly reasonable, but no Windows Setup will erase entire disks without plenty of warnings and give users the opportunity to keep existing partitions, including types it does not recognize. Since Windows 2000, the Setup program allows for deletion of partitions, creating one or more new partitions, formatting them, etc. Same as the FreeBSD setup, without the disk slices. This of course will require having the Windows install CD. Your desktop may still have a sticker with a license key on it, in which case, you can simply borrow the Windows CD from someone else if you don't own one. In addition, most laptop companies will provide replacement media on request. Oftentimes, a new laptop ships with a manufacturer-specific recovery CD/DVD that contain OEM version of Windows, customized for that manufacturer. If that disk is not available, check the manufacturers support website on how to get a replacement. Downloading one might be an option. As you said Steve, the important thing is the COA sticker - Certificate of Authenticity/Proof of License. Usually on the bottom of the laptop, but sometimes affixed to printed materials included with the computer. Good luck to the original poster; maybe try out FreeBSD on another machine, or when the laptop is too old to run modern versions of Windows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with pkg_delete *
On 8/12/09, Sdävtaker sdavta...@gmail.com wrote: Hi, I want to clean up and start again the installation of pkg since i did a broken update in python and qt and pretty much everything is broken portupgrade never ends, doing make in ports crash pretty much all the time . I tried # pkg_delete '*' Segmentation fault (core dumped) # pkg_delete 'kde*' Segmentation fault (core dumped) which is taking your current directory and trying to remove them. not gonna happen. # pkg_delete -af Try that, it removes all installed ports. Alternatively, you can: # rm /usr/local/* /var/db/pkg/* and have the same result. Good luck. Failed both in multiuser so I tried to do this as monouser and was the same. Im running FreeBSD user.domain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Any suggestions? Thanks for any help. Damian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with pkg_delete *
On Wed, 12 Aug 2009, Sd?vtaker wrote: Hi, I want to clean up and start again the installation of pkg since i did a broken update in python and qt and pretty much everything is broken portupgrade never ends, doing make in ports crash pretty much all the time . I tried # pkg_delete '*' Segmentation fault (core dumped) # pkg_delete 'kde*' Segmentation fault (core dumped) Failed both in multiuser so I tried to do this as monouser and was the same. Im running FreeBSD user.domain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Any suggestions? Thanks for any help. Damian There was an earlier thread that discussed this issue http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg101896.html Perhaps this may help you. thanks Saifi. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Racoon VPN
On Tue, Aug 11, 2009 at 09:44:28PM +0200, get acoder wrote: Hi there, I am refering to your very detailed doc http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ipsec.html I am exactly looking for the same features and setup, my only issue is that I cant find racoon as you are describing here: /usr/local/etc/racoon/racoon.conf I installed ipsec tools, compiled my kernel for IPSec only to find out that racoon2 is only available Any idea how where I ca find racoon v1 regards and tx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org It appears that racoon2 has been removed from the ports. Superseded by: ipsec-tools [/usr/ports] x...@serenity$ make search name=racoon Port: racoon2-20071227e_1 Path: /usr/ports/security/racoon2 Info: Racoon2 IPsec daemon Maint: sumik...@freebsd.org B-deps: autoconf-2.61_2 autoconf-wrapper-20071109 m4-1.4.11,1 perl-5.8.8_1 R-deps: WWW:http://www.racoon2.wide.ad.jp/ Port: security/racoon Moved: security/ipsec-tools Date: 2005-11-18 Reason: removed, successor is ipsec-tools ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with pkg_delete *
Thanks for reply guys. I did the rm in both directories and worked great, installing all again from ports now. Damian On Wed, Aug 12, 2009 at 11:42, Saifi Khan saifi.k...@datasynergy.orgwrote: On Wed, 12 Aug 2009, Sd?vtaker wrote: Hi, I want to clean up and start again the installation of pkg since i did a broken update in python and qt and pretty much everything is broken portupgrade never ends, doing make in ports crash pretty much all the time . I tried # pkg_delete '*' Segmentation fault (core dumped) # pkg_delete 'kde*' Segmentation fault (core dumped) Failed both in multiuser so I tried to do this as monouser and was the same. Im running FreeBSD user.domain 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:57:44 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 Any suggestions? Thanks for any help. Damian There was an earlier thread that discussed this issue http://www.mail-archive.com/freebsd-sta...@freebsd.org/msg101896.html Perhaps this may help you. thanks Saifi. -- Sdävtaker prays to Rikku goddess for a good treasure. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel panic
Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault Aug 12 15:59:08 host savecore: writing core to vmcore.4 How to obtain which process cause system to reboot? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel panic
On Wednesday 12 August 2009 08:01:07 Коньков Евгений wrote: Aug 12 15:59:08 host savecore: reboot after panic: integer divide fault Aug 12 15:59:08 host savecore: writing core to vmcore.4 How to obtain which process cause system to reboot? kgdb /boot/kernel/kernel /var/crash/vmcore.4 -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot sector f*ed
On Wed, Aug 12, 2009 at 07:34:49AM -0400, PJ wrote: I'm actually at the stage of doing the save/copy/transfer or whatever you can call it: here's what I am thinking and on which I need clarification. I ran HDD regenerator and it immediately flagged the very first sector as being Bad. Is this the program you're talking about? http://store3.esellerate.net/store/ProductInfo.aspx?StoreIDC=STR793615240SkuIDC=SKU9923428806pc= I'm not an expert on harddisks, but the claims that this program makes seem too good to be true. I wonder what other on the list think of it? You may also find the following link about data recovery enlightening: http://www.mjmdatarecovery.co.uk/data-recovery-articles/bad-sector-errors.html Information encoding techniques on harddisks have changed dramatically over the years to help enable the ever increasing densities. The link to HDD regenerator talks about bad sectors showing. Current harddisks have a number of spare sectors available so that they can remap the data from unreadable sectors, using the error correction bits to restore unreadable data. All this is done in the harddisk itself, without even being visible to the user. AFAIK, a harddisk will only start showing re-allocated sectors in the SMART information after its spare sectors are exhausted. See [http://en.wikipedia.org/wiki/Bad_sector] If this is the case, the common advice it to decommission this drive ASAP. You should use 'smartctl' from the sysutils/smartmontools port to check if your harddisk is healthy or failing. 'smartctl -a /dev/diskname' should give complete information. Look at a line containing the text 'Reallocated_Sector_Ct'. If the last number on this line is greater than zero, the disk has run out of spare sectors, and it is time to get a new disk. On bootint, just before the crash, the boot process started... hesitated, lurched forward, hesitated and then proceeded to load only some minutes later closing down with a 177mb dump. I knew then there was a problem.. :-) Yes. But probably not a problem with the boot sector. Because the machine found and executed the boot code (because it booted). And it succeeded in finding and loading the kernel (because it wrote a dump). Now it is important to know _why_ the kernel dumped core. It could be that the kernel image was corrupted on disk, pointing to a disk problem. But it can also be something else. So try and see if you can read the slice table with fdisk as described below. If that works, the slice table should be OK. I have a 2nd disk just checked (with the regenerator - 12 hrs waiting on 2.4ghz cpu). If, indeed, the boot sector is the only thing mucked up, I should be able to copy the rest onto the 2nd(target) disk NP. The question, then, is how to deal with the boot sector. As I understand it, the boot sector has the partition information needed to run things for the rest of the disk. So, copying the damaged source disk will not give me the boot sector needed. If your boot sector is truly buggered, read the manual pages for the following utilities: - fdisk(8) - boot0cfg(8) You can re-install the boot code in sector 0 easily with FreeBSD's fdisk. E.g. if you are booting from the /dev/ad4 drive: 'fdisk -B /dev/ad4'. If you can boot from a FreeBSD livecd, try if you can read the slicetable correctly with fdisk to check if it is really damaged. Again assuming the bad drive is /dev/ad4, save the output of the following command to a file, and post the contents here. 'fdisk /dev/ad4'. A tip for the future. If you have a newly sliced disk, save the slice table to a file with 'fdisk -p /dev/ad4 slicetable-ad4.txt', and save this file away from the computer. If you ever damage the slice table, you can restore it using the file that you saved with 'fdisk -f slicetable-ad4.txt -i /dev/ad4'. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgptY6t3LYWFW.pgp Description: PGP signature
Re: Racoon VPN
On Wed, Aug 12, 2009 at 08:26:45AM -0700, Joseph Olatt wrote: It appears that racoon2 has been removed from the ports. Superseded by: ipsec-tools Look closely. security/racoon was removed, not security/racoon2! [/usr/ports] x...@serenity$ make search name=racoon Port: racoon2-20071227e_1 Path: /usr/ports/security/racoon2 Info: Racoon2 IPsec daemon Maint: sumik...@freebsd.org B-deps: autoconf-2.61_2 autoconf-wrapper-20071109 m4-1.4.11,1 perl-5.8.8_1 R-deps: WWW:http://www.racoon2.wide.ad.jp/ Port: security/racoon Moved: security/ipsec-tools Date: 2005-11-18 Reason: removed, successor is ipsec-tools Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpq5mdu9owug.pgp Description: PGP signature
Re: location of user crontab files?
On Tue, Aug 11, 2009 at 07:21:08PM -0400, Karl Vogel typed: K If you're using individual crontab files, be sure to rename /etc/crontab K or you might have duplicated cronjobs running simultaneously. On Wed, 12 Aug 2009 11:31:14 +0200, Ruben de Groot mai...@bzerk.org said: R I don't think this is sound advise. Leaving /etc/crontab (the system R crontab) to do the system maintenance jobs it is supposed to do and R putting additional scripts and jobs in user tabs is normal practice and R won't cause any problems. I don't like keeping similar information in multiple places (especially in different formats) because you have to access it in different ways. If I change my own crontab file using crontab -e, I want to do root's the same way; it's just one less exception for me to remember. -- Karl Vogel I don't speak for the USAF or my company The idea that 'the public interest' supersedes private interests and rights can have but one meaning: that the interests and rights of some individuals take precedence over the interests and rights of others. --Ayn Rand ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mathematica 7 license manager
I'm trying to run mathlm for mathematica version 7 under linux_base-fc-4_13 on freebsd 7.1-release-p7. It demonizes and appears to be happy until I try to run mathematica, then it crashes with signal 11. Even running monitorlm causes it to crash. Maxing out the loglevel doesn't produce any more info. Looking at the last access times in /compat/linux/etc, it opens host.conf, ld.so.cache and nsswitch.conf before dying. Has anyone seen this before? Any help would be much appreciated!! Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: A question for developers
Look, use Joe. You won't ever want anything else -- you'll soon forget about meta-escape-alt-@ while holding down the esc-tab-plus key, all the while wishing you had three hands. On Tue, Aug 11, 2009 at 10:40 PM, Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.netmel.flynn%2bfbsd.questi...@mailing.thruhere.net wrote: On Tuesday 11 August 2009 16:46:16 Steve Bertrand wrote: Steve Bertrand wrote: but may be handy until I become more fluent, as my first instinct is to hit the BACKSPACE ^H^H^H^H^H^H^H^H^H ^h key. terminal emulation fault. stty erase ctrl-vctrl-h should fix it, on the shell that is. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot sector f*ed
Roland Smith wrote: On Wed, Aug 12, 2009 at 07:34:49AM -0400, PJ wrote: I'm actually at the stage of doing the save/copy/transfer or whatever you can call it: here's what I am thinking and on which I need clarification. I ran HDD regenerator and it immediately flagged the very first sector as being Bad. Is this the program you're talking about? http://store3.esellerate.net/store/ProductInfo.aspx?StoreIDC=STR793615240SkuIDC=SKU9923428806pc= It sure looks like it. Don't recall the version. I'm not an expert on harddisks, but the claims that this program makes seem too good to be true. I wonder what other on the list think of it? You may also find the following link about data recovery enlightening: http://www.mjmdatarecovery.co.uk/data-recovery-articles/bad-sector-errors.html I'll look at it for sure. Information encoding techniques on harddisks have changed dramatically over the years to help enable the ever increasing densities. The link to HDD regenerator talks about bad sectors showing. Current harddisks have a number of spare sectors available so that they can remap the data from unreadable sectors, using the error correction bits to restore unreadable data. All this is done in the harddisk itself, without even being visible to the user. AFAIK, a harddisk will only start showing re-allocated sectors in the SMART information after its spare sectors are exhausted. See [http://en.wikipedia.org/wiki/Bad_sector] If this is the case, the common advice it to decommission this drive ASAP. You should use 'smartctl' from the sysutils/smartmontools port to check if your harddisk is healthy or failing. 'smartctl -a /dev/diskname' should give complete information. Look at a line containing the text 'Reallocated_Sector_Ct'. If the last number on this line is greater than zero, the disk has run out of spare sectors, and it is time to get a new disk. Will try it, too. On bootint, just before the crash, the boot process started... hesitated, lurched forward, hesitated and then proceeded to load only some minutes later closing down with a 177mb dump. I knew then there was a problem.. :-) Yes. But probably not a problem with the boot sector. Because the machine found and executed the boot code (because it booted). And it succeeded in finding and loading the kernel (because it wrote a dump). Now it is important to know _why_ the kernel dumped core. It could be that the kernel image was corrupted on disk, pointing to a disk problem. But it can also be something else. So try and see if you can read the slice table with fdisk as described below. If that works, the slice table should be OK. Well, I've been looking at the disk(s) and I have found some interesting shei**e that doesn't make sense. 1. The fbsd minimal installation that I had set up for recovery of the previous crash does not boot... Now, why in Hades is that? I hadn't touched the disk since last using it to look at the corrupted disk through an usb connection. The current crashed installetion was done afterwards and the only change was in the bios to set the boot disk to the new installation. The installation was finally completed with all the programs working fine... and then BOOM! 2. I tried booting from all the disks on the machine (4 disks) and only the current crashed one booted!... so, it's not the boot sector at all... something is screwy on this machine; either the motherboard is buggered (which I doubt, but not entirely), the disks are finished or theres some kind of gremlin lurking in the confines of the box. So, I will proceed to do some more reading and research on all this and then check out the procedures you've suggested below. I may not be able to respond too quickly as I've got a few other devils circling my head... like organizing and adjusting normal living conditions which include garbage, house repairs, sometimes sleeping and often running around the city getting stuff for just plain survival... :-( ;-) :'( I appreciate your response and have already learned quite a lot... it's rather heavy for my little brain, but I'll try to deal with it.. :-) I have a 2nd disk just checked (with the regenerator - 12 hrs waiting on 2.4ghz cpu). If, indeed, the boot sector is the only thing mucked up, I should be able to copy the rest onto the 2nd(target) disk NP. The question, then, is how to deal with the boot sector. As I understand it, the boot sector has the partition information needed to run things for the rest of the disk. So, copying the damaged source disk will not give me the boot sector needed. If your boot sector is truly buggered, read the manual pages for the following utilities: - fdisk(8) - boot0cfg(8) You can re-install the boot code in sector 0 easily with FreeBSD's fdisk. E.g. if you are booting from the /dev/ad4 drive: 'fdisk -B /dev/ad4'. If you can boot from a FreeBSD livecd, try if you can read the slicetable
Re: A question for developers
On Wed, 12 Aug 2009 15:49:17 -0400, Henry Olyer henry.ol...@gmail.com wrote: Look, use Joe. You won't ever want anything else -- you'll soon forget about meta-escape-alt-@ while holding down the esc-tab-plus key, all the while wishing you had three hands. That's not a very good way of describing editors/joe. It is unfair both to other editors and to joe itself. There *are* good points about joe, eg.: - It works very well even with pretty dumb terminals. - It has a very small footprint - It supports many features a `coder' expects (auto indentation, custom tab sizes, macros, etc.) It is much nicer to describe the *good* points about joe, instead of making silly jokes about keyboard shortcuts in other editors. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: boot sector f*ed
On Wed, Aug 12, 2009 at 03:54:31PM -0400, PJ wrote: Well, I've been looking at the disk(s) and I have found some interesting shei**e that doesn't make sense. 1. The fbsd minimal installation that I had set up for recovery of the previous crash does not boot... Now, why in Hades is that? I hadn't touched the disk since last using it to look at the corrupted disk through an usb connection. The current crashed installetion was done afterwards and the only change was in the bios to set the boot disk to the new installation. The installation was finally completed with all the programs working fine... and then BOOM! 2. I tried booting from all the disks on the machine (4 disks) and only the current crashed one booted!... so, it's not the boot sector at all... something is screwy on this machine; either the motherboard is buggered (which I doubt, but not entirely), the disks are finished or theres some kind of gremlin lurking in the confines of the box. This sounds more and more like hardware troubles. A few things to check (in order of decreasing likelyness IMHO): - Cables to the harddisks: Make sure they are properly connected. A machine of mine suddenly started getting disk read errors after I put in another graphics card. It turned out that the SATA connector to that drive had come partially loose. - Powersupply: check the voltages (preferably under load) with a monitoring app like mbmon. If that's not possible, check in the BIOS. A failing powersupply can give weird unreproducable errors. If you have ever heard a popping noise from the machine it could be a short in the powersupply caused by dust. I've seen that fry motherboards. - PCI cards: check that they are seated properly. Although in this case I'd say this seems the least likely. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpqOXQsb1Yl7.pgp Description: PGP signature
firefox 2.0.0.20_9,1
Hi! When I run ; portaudit -a Affected package: firefox-2.0.0.20_9,1 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/49e8f2ee-8147-11de-a994-0030843d3802.html but when I check above site I found: Affects: firefox 3.*,1 firefox 3.*,1 3.0.13,1 firefox 3.5.*,1 3.5.2,1 linux-firefox 3.*,1 linux-firefox 3.*,1 3.0.13,1 linux-firefox 3.5.*,1 3.5.2,1 linux-firefox-devel 3.5.2 seamonkey 0 linux-seamonkey 0 linux-seamonkey-devel 0 thunderbird 0 linux-thunderbird 0 Are problem with firefox-2.0.0.20_9,1 or not, please. -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: A question for developers
On Wed, Aug 12, 2009 at 9:53 PM, Polytroponfree...@edvax.de wrote: On Thu, 13 Aug 2009 00:08:52 +0300, Giorgos Keramidas keram...@ceid.upatras.gr wrote: There *are* good points about joe, eg.: - It works very well even with pretty dumb terminals. - It has a very small footprint - It supports many features a `coder' expects (auto indentation, custom tab sizes, macros, etc.) Syntax highlighting! Syntax highlighting! :-) Other points are automatic file backups, different modes (depending on $0) and so on. It is much nicer to describe the *good* points about joe, instead of making silly jokes about keyboard shortcuts in other editors. If you make jokes, use the recommended ones, such as the well-known escape-meta-alt-control-shift key combinations. :-) Don't forget about: C-x M-c M-butterfly [1] :-) [1] - http://xkcd.com/378/ -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: A question for developers
On Thu, 13 Aug 2009 00:08:52 +0300, Giorgos Keramidas keram...@ceid.upatras.gr wrote: There *are* good points about joe, eg.: - It works very well even with pretty dumb terminals. - It has a very small footprint - It supports many features a `coder' expects (auto indentation, custom tab sizes, macros, etc.) Syntax highlighting! Syntax highlighting! :-) Other points are automatic file backups, different modes (depending on $0) and so on. It is much nicer to describe the *good* points about joe, instead of making silly jokes about keyboard shortcuts in other editors. If you make jokes, use the recommended ones, such as the well-known escape-meta-alt-control-shift key combinations. :-) (Finally, I'm the wrong person to have an opinion here, because I never used emacs much; its magic didn't open up to me. But joe is really a great editor, powerful, and still easy to use.) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: please help to uninstall FreeBSD!!!
On Wed, 12 Aug 2009 10:32:20 -0400, Charles Oppermann chuc...@gmail.com wrote: Correct, and counter to another posters statement that Windows attempts to wipe entire disks when installing. Yes, that's the default choice, which is perfectly reasonable, but no Windows Setup will erase entire disks without plenty of warnings and give users the opportunity to keep existing partitions, including types it does not recognize. The average Windows user does not read what's on the screen anyway, so he will always next. :-) Since Windows 2000, the Setup program allows for deletion of partitions, creating one or more new partitions, formatting them, etc. Even DOS could do that. Good luck to the original poster; maybe try out FreeBSD on another machine, or when the laptop is too old to run modern versions of Windows. It usually is as soon as it is sold. :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: firefox 2.0.0.20_9,1
--On August 12, 2009 8:18:55 PM -0500 ajtiM lum...@gmail.com wrote: Hi! When I run ; portaudit -a Affected package: firefox-2.0.0.20_9,1 Type of problem: mozilla -- multiple vulnerabilities. Reference: http://portaudit.FreeBSD.org/49e8f2ee-8147-11de-a994-0030843d3802.html but when I check above site I found: Affects: firefox 3.*,1 firefox 3.*,1 3.0.13,1 firefox 3.5.*,1 3.5.2,1 linux-firefox 3.*,1 linux-firefox 3.*,1 3.0.13,1 linux-firefox 3.5.*,1 3.5.2,1 linux-firefox-devel 3.5.2 seamonkey 0 linux-seamonkey 0 linux-seamonkey-devel 0 thunderbird 0 linux-thunderbird 0 Are problem with firefox-2.0.0.20_9,1 or not, please. That port should probably be removed. It's ancient. Use /usr/ports/www/firefox3 or /usr/ports/www/firefox3.5 Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: firefox 2.0.0.20_9,1
On Wednesday 12 August 2009 18:16:20 Paul Schmehl wrote:
--On August 12, 2009 8:18:55 PM -0500 ajtiM lum...@gmail.com wrote:
Hi!
When I run
;
portaudit -a
Affected package: firefox-2.0.0.20_9,1
Type of problem: mozilla -- multiple vulnerabilities.
Reference:
http://portaudit.FreeBSD.org/49e8f2ee-8147-11de-a994-0030843d3802.html
but when I check above site I found:
Affects:
firefox 3.*,1
Given the above, it should be affected. Reading the original documents it
doesn't show. And I can't find anywhere that firefox 2 is End of Life.
firefox 3.*,1 3.0.13,1
firefox 3.5.*,1 3.5.2,1
linux-firefox 3.*,1
linux-firefox 3.*,1 3.0.13,1
linux-firefox 3.5.*,1 3.5.2,1
linux-firefox-devel 3.5.2
seamonkey 0
linux-seamonkey 0
linux-seamonkey-devel 0
thunderbird 0
linux-thunderbird 0
Are problem with firefox-2.0.0.20_9,1 or not, please.
That port should probably be removed. It's ancient.
If that's ancient, you should do a find /usr/ports -name Makefile -exec ident
{} +|grep ' 200[67]/'.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: firefox 2.0.0.20_9,1
--On August 12, 2009 9:48:04 PM -0500 Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote: Given the above, it should be affected. Reading the original documents it doesn't show. And I can't find anywhere that firefox 2 is End of Life. Firefox was EOL in December 2008. No security updates or fixes will be released for it. http://www.linuxjournal.com/print/1007661 http://en.wikipedia.org/wiki/Mozilla_Firefox It should be removed from the ports tree. Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
how to set the virtual host in fedora11
i try to set the virtual host in fedora11.but its not working i chage the etc/httpd/conf/httpd.conf and etc/hosts/ even also i am not able to get the virtual hosts,please suggest me how to make this. -- Regards, S.Malathi. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Fixit mode (live CD): can't find /etc/rc.conf
On my recently updated (as in world+ports are up-to-date) FreeBSD 6.4 box i tried to get Xorg running, and after building Xorg from ports and enabling hald and dbus in rc.conf, I get: Fatal trap 12: page fault while in kernel mode This happens when I boot. Now I'm trying to not start hald and dbus in rc.conf (I think that's what's causing the kernel problem). So I am using the installation CD and going into fixit mode. The problem is that I can't find rc.conf to edit. In /dev: ad0 ad0s1 ad0s1a ad0s1b ad0s1c ad0s1d ad0s1e ad0s1f I tried mounting all of these, and I realized that one of them is /usr and the other one must be /. Seemed that most of the files were there, except for /etc. It's missing altogether. fixit# mount /dev/ad0s1d /mnt fixit# cd /mnt fixit# find . -type f -name rc.conf I tried this with all of the devices above and cannot find it. Like I said I cannot find /etc at all. BTW it would be nice if I could fix the underlying kernel page fault issue, anyone know how? Uninstall Xorg is one way I guess. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Fixit mode (live CD): can't find /etc/rc.conf
On Wednesday 12 August 2009 21:07:30 Nerius Landys wrote: On my recently updated (as in world+ports are up-to-date) FreeBSD 6.4 box i tried to get Xorg running, and after building Xorg from ports and enabling hald and dbus in rc.conf, I get: Fatal trap 12: page fault while in kernel mode This happens when I boot. Now I'm trying to not start hald and dbus in rc.conf (I think that's what's causing the kernel problem). So I am using the installation CD and going into fixit mode. The problem is that I can't find rc.conf to edit. In /dev: ad0 ad0s1 ad0s1a By convention /etc should be on ad0s1a. If it's not, but /boot is there, you may need to fsck. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Fixit mode (live CD): can't find /etc/rc.conf
By convention /etc should be on ad0s1a. If it's not, but /boot is there, you may need to fsck. Yeah, When I tired to mount ad0s1a, it gave me something like permission denied or bad superblock. How do I fix this with fsck from the live CD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
