Search results

It depends on how big/convoluted a build tree, how much RAM, and I/O speed. If you are not limited by RAM and using hard disks rather than SSDs try 17.

Agree that you should definitely consider a fresh install on new(er) hardware. It is likely to be much faster and easier than the multiple upgrade steps you will need to go through to get from 9.3 to, say, 12.1. To say nothing of dealing with required configuration file changes on the way...

Do you have the fusefs-ntfs package or sysutils/fusefs-ntfs port installed? Did you kldload fusefs? Check with kldstat to be sure. Does the /mnt/windows directory exist? It must exist before you can mount over it.

That device you showed us info for isn't an ethernet port. I'm guessing that the system isn't seeing the card (damaged? not fully seated? bad slot?). How about you show us the PCI info for just that card from the old system (i.e. pciconf -lv as root), and see if you get something comparable...

You probably can't boot a recent FreeBSD distribution on hardware that old because the kernel as distributed assumes the presence of an APIC (Advanced Programmable Interrupt Controller), and ACPI (Advanced Configuration and Power Interface). And SMP needs an APIC. So you probably need to build...

242136 submitted

Working with stable/12 revision 354853 on amd64. Problem also occurs with releng/12.1 revision 354894 on amd64. I can build the GENERIC kernel just fine. As soon as I try to remove BPF the kernel fails to link. The following simple kernel config is enough to show the problem: include...

I had the same problem running out of /tmp on 11.0 with a Banana Pi. I don't know how much space was actually needed to solve this problem. I had plugged in a 2TB SATA drive and mounted /usr on it anyway, so I just soft-linked /tmp to /usr/tmp. I think it took about 30 hours to build world...

Quantity makes a big difference. If you needed a million units then it would pay to design exactly what you need on a single board. I assume you need a few tens of units (or less) so you don't have any board design funds in your budget. If I was in your position, and had enough time, I would...

I tried building synth on armv6. I get the following error: ===> gcc6-aux-20160822 is only for amd64 i386, while you are running armv6. Is there another version of the ADA compiler available that can build synth so I can make it run native on ARM?

No. Not on FreeBSD. Use ntpd like the previous posters suggested.

The classic solution in these cases, and the only one guaranteed to work, is to fix or replace the failing disk subsystem hardware, then restore from a recent backup.

There is some chance that upgrading to the latest BIOS firmware might improve the situation (if you are not already running the latest).

Note that those are APIC (advanced programmable interrupt controller) errors, not ACPI errors.

After installing from the memstick image, you should be able to dd the DVD iso image to a flash drive and mount it something like mount -t cd9660 /dev/da0 /mnt to use the packages.

I did a source upgrade from 10-stable revision 306935 to 11-stable on Friday. So perhaps you should start by updating to the latest 10-stable (or that recent revision if you prefer).

I have one low-priority production machine and a couple of test machines running 11-stable (for bug fixes). The important stuff will wait until I am really comfortable, or more likely until 11.1 is out.

I like Synth. Good job. Is it possible, or do you have any plans to make it possible, to cross-build ports from, say, amd64 to armv6? What would it take to accomplish that?

When you say "manual reboot" you mean shutdown -r now, right?

If you want emacs without X11 (i.e. just text, no GUI) then the package will be called emacs-nox11-24. As a port it will be editors/emacs-nox11.