Search results

I recall someone advising -O14 for kernel compiles in some slackware forum lo 10 or more years ago. I nearly choked on my kibble. Any physicist knows that optimizing above -O8 reduces all atomic operations to values below Planck's constant, thus creating micro-abrasions on the inner surface of...

Maybe an expert in freebsd-update can chime in, but it looks like freebsd-update.conf has IgnorePaths UpdateIfUnmodified & MergeChanges settings, which may be at least close to the right path. (you could always add /etc/ to IgnorePaths and run mergemaster separately, for instance)

I would say that 80% of custom kernel build failures are from enthusiastic "slimmers" who inevitably remove "device scbus" or "device da" because they don't have any SCSI disks.

Look at the -i & -U options to mergemaster to skip all that tedious upgrading of files you've never edited. As for the rest: yeah, it's a PITA, but it's better than blindly stabbing a musk ox from a moving bus.

This list may be in decreasing order of importance, if you think it is altq. And, err, 90 column console? You might see a bit of a speed-up on i386 if you remove cpu I486_CPU cpu I586_CPU (assuming you're running something as new-fangled as a pentium-pro, that is)...

Well, camcontrol can send pretty arbitrary junk to your devices, so dig out the specs and try the camcontrol cmd -a something -c somethingelse format. Or its philosophical equivalent. And that something and somethingelse will probably be obscure hexadecimal strings.

sendmail_enable="NONE" will disable all of it, but you'll get clogged up with periodic output unless you fiddle with /etc/periodic.conf. Probing the (empty) sdcard port seems to take a bit here, as with enumerating all the usb nonsense.

Ah, I find it annoying myself when the linux laptops automatically connect to random stuff like poorly configured HP print servers or known bad networks. It looks like someone was trying to port guh-nomes nm-applet back in 2009. No idea how that's gone or going. edit: additionally, there...

Bumping threads like that is less effective, because the thread will no longer show up as "unanswered". I suppose the solution is to calculate your track boundaries and try to line everything up, if you care. On the other hand I don't know that this warning is harmful in any way. Does it...

You probably have a deleted file in /var/ being written to, so the space hasn't been freed yet. You can try sysutils/lsof to track down the file and restart the application that's writing to it. Restarting is also usually effective in this case.

Just pull down a snapshot iso ( quo vide here e.g.: ftp://ftp2.freebsd.org/pub/FreeBSD/snapshots/ ) and mount it via mdconfig. Alternately, find a site with a full 9.x distribution, and point sysinstall at that.

Yes, being in the "wheel" group allows you to su to root. You can also install security/sudo and learn to append to the fore of every command a "sudo". I suppose if one were hacky enough one could make the ports directory owned by a user other than root. That sounds pretty difficult* and...

All of your header files are missing? I would guess that you caught a cvsup server in the midst of an update, or that you have something awry with your refuse files or some such. Have you tried another server?

We do have linprocfs & linsysfs, though I have no idea how you would fiddle them in. Perhaps see also /usr/src/sys/compat/linprocfs/linprocfs.c et /usr/src/sys/compat/linsysfs/linsysfs.c. But, as camelia suggests, it may be redundant.

Humm, I don't wander much with my FreeBSD laptop(s) & I shut them down mostly, so I don't get much moving from network to network (you'll excuse the diversion, as this is merely to exposit on the general theory that I haven't much real-world experience in this) but I would probably just do a...

Since you use portmaster, the only suggestion I can think of is touch /var/db/pkg/portdir/+IGNOREME If that doesn't tell portmaster to stop it I don't know what will.

Is there anything else in /usr/local/lost+found/? If not, you might be able to just rm -r /usr/local/lost+found If that fails, grab the inode with ls -li and try clri before you go whole hog into fsdb. fsdb can do a lot of damage really quickly, so be very careful using it.

Rampant anti-Saxonism on the moderator community. After 1066 all the the old Ænglisc terms become verboten & we had to suffer with using Latin to talk about filthy things like genitalia & excrement. Oh, that painfully off topic. Umm . . . I like net/tinyfugue & net/tintin++-devel...

the only reason I use the silly things is portability of the data, & that's (sadly) only available with fat32.

I guess you could poke in and see what mergemaster does when you pass -U or -F, it's just a shell script.