Re: patches and uname -a
On Thu, 12 Jan 2006, Roberto Nunnari wrote: Does anybody know how can you make uname report the real version? What if you recompile the kernel after patching the system? Would that do the trick? As far as I know, uname gets the version information from the kernel. So yes, if you recompile the kernel, you should be able to get the right version displayed. Yours, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4 on a Dell D800
On Wednesday 12 October 2005 15:44, Ugo Bellavance wrote: Hi, I tried installing 5.4 on my Dell D800 laptop. After the first boot, my keyboard stopped working. I don't know what to do from now or if it is even worth the effort. Should I try 6.0RC? On the FreeBSD Laptop Comptibility list, http://gerda.univie.ac.at/freebsd-laptops/, there are a few entries on the D800. Maybe there is something useful there? Good luck, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, jojo wrote: Hello, I have a problem with the filesystem. I am always getting those /: write failed, filesystem is full errors. If I have a look on df the root has 109% Capacity. How could that be? I had a file in /root with 3.3G that I have now deleted but with no success. The df output is as before. I am using Raid1(Mirror) with two 80Gig ST380011A/3.04 HDs. The filesystem always reserves a bit of space above 100%. Normal users can fill the filesystem up to 100%, and the root user can go to 110% (if I remember orrectly). Hence the 109%. du -hd1 1.5K./dev 2.5G./usr 555M./var 885M./www 2.4M./stand 1.5M./etc 2.0K./cdrom 2.0K./dist 7.3M./bin 18M./boot 2.0K./mnt 2.0K./proc 18M./root 21M./sbin 24K./tmp 76K./cgb 4.0G. The du output does not agree with the df output. Where are the 4.9Gig of / ? What can I do? Somebody had this problem before? As you can see, the contents of /var, /www and /usr are also counted, which are on another file system. You might try du -hx / in order to see only the contents of / and the directories on that file system. Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? Yours, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /: write failed, filesystem is full
On Wed, 5 Oct 2005, Jaap Boender wrote: Anyway, it seems as if your 3.3G file hasn't disappeared, since there is still 4.0G in the root directory...What kind of file was it? Oh, wait, I read you wrongly. The file from /root has disappeared all right (only 18M in there). The 4.0G you read includes the total of everything below it, such as the /usr and /www and so on. If you only want the / file system, try the -x option, as I said. Sorry, Jaap ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange bootloader problem
On Tue, 26 Jul 2005, Gary W. Swearingen wrote: Date: Tue, 26 Jul 2005 11:03:07 -0700 From: Gary W. Swearingen [EMAIL PROTECTED] To: Jaap Boender [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: Strange bootloader problem Jaap Boender [EMAIL PROTECTED] writes: So now I'm stumped. Does anyone have any advice? I'm running 5.4-STABLE, just cvsupped, built and installed an hour ago. Since you changed your BIOS, I'm suspecting something fishy with the BIOS settings for disk geometry, like not LBA or something, but you've probably already checked the BIOS setup... Read the boot(8) manpage paragraph starting with However, which says how to by-pass /boot/loader and maybe try that. Also, loader(8) manpage has a boot_verbose variable that might help. -- War is God's way of teaching Americans geography. -- Ambrose Bierce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange bootloader problem
[Sorry about the previous message, I hit the wrong key. X and C are very close together...] Since you changed your BIOS, I'm suspecting something fishy with the BIOS settings for disk geometry, like not LBA or something, but you've probably already checked the BIOS setup... I hadn't thought about the disk geometry, but I have looked at the BIOS, yes. Unfortunately, it being a DELL BIOS, there weren't many useful settings I could change (and 'disk geometry' wasn't even mentioned...) Read the boot(8) manpage paragraph starting with However, which says how to by-pass /boot/loader and maybe try that. Also, loader(8) manpage has a boot_verbose variable that might help. I've just tried them both, but Grub launches the loader immediately, without any possibility for bypassing. The FreeBSD boot manager just beeps when I try to boot FreeBSD (presumably due to the same problem). I've also tried loading the kernel directly from Grub, but the first time this resulted in a lock-up just after recognizing the ad0 device - and the second and later times I didn't get even that far. Nonetheless, the disk geometry avenue looks promising. I'll see if I can get anywhere using that. Resetting to defaults apparently isn't enough... Thanks, Jaap Boender -- War is God's way of teaching Americans geography. -- Ambrose Bierce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange bootloader problem
Hi all, Well, here's one for the books. I've got a Dell Latitude D610, and yesterday I upgraded the BIOS to its newest version (A04). This worked nicely, but after the upgrade, the third stage bootloader won't boot the kernel anymore. I can get to the boot loader from grub, but then it says 'can't find kernel' and that's it. If I try a ls it says 'no such file or directory' - incidentally, the file system itself is okay, if I boot from a fixit CD with -a and use the hard disk as the root partition, it all works fine. I've tried installing FreeBSD from scratch on another partition, with the same result. The only thing that goes wrong is /boot/loader not being able to load the kernel. Well, that and grub not being able to boot the kernel directly, but that might very well just be Grub... So now I'm stumped. Does anyone have any advice? I'm running 5.4-STABLE, just cvsupped, built and installed an hour ago. Thanks, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fsck_ext2fs problems
Hi all, I'd like to share a filesystem on the same computer between FreeBSD and Linux, and as it seems that FreeBSD supports ext2 better than Linux does ufs(2), I've created an ext2 filesystem. Mounting accessing Works fine, except when I try to fsck it, fsck_ext2fs fails with the error message: execve: No such file or directory. When I use the e2fsck program, however, I can fsck the filesystem just fine. Unfortunately, at boot time, FreeBSD wants to use fsck_ext2fs... A quick search on the Internet didn't show any solutions, so - does anybody here know what I can do to get rid of the error message? Thanks, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fsck_ext2fs problems
Are you running ext2fs from Linux? If you are running it from FreeBSD then try making a symlink in /sbin from fsck_ext2fs to wherever you have e2fsck and make sure that e2fsck will be available when fsck runs. That almost certainly means it has to bee on your root partition. (Or just copy it to /sbin). Yes, copying fsck_ext2fs and e2fsck to /sbin works - I've looked in files/fsck_ext2fs.c in the port and I noticed that it only looks for e2fsck in /sbin - hence the execve error. Thanks for the pointer! I got the impression that Linux doesn't support ufs2 at all, and, well, I just trust FreeBSD's ext2 implementation more than I do Linux's ufs one ;) Yours, Jaap Boender ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
