Latest activity

has nothing to do with what I wrote... L2ARC requires memory for its allocation tables; roughly 100MB per 1GB stored in L2ARC as a rule of thumb. So L2ARC is always the wrong tool against memory pressure on such low-end systems as you will...

I went through the basic install (triggered my mbr/bsdlabel ptsd) and got it running just fine. # uname -a FreeBSD 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Sat Jun 7 09:22:34 GMT 2003 root@hammer.corp.yahoo.com:/usr/obj/usr/src/sys/GENERIC...

Hope can I tell if I have set up sockets correctly? ls -l /var/run/php-fpm.sock does not find anything. Should it get created when you start fpm?

There is another solution to this conundrum. You're not limited to having a single PC on your home network. It's how I started too, first just one PC, dual booting FreeBSD and Windows (think it was 95 or 98). Got sick and tired of rebooting to...

they are a) too slow and b) *will* die quite often. just don't. L2ARC is basically only a very last resort if you are completely maxed out on RAM and absolutely need some data to stay in a slightly-faster-than-the-disks-cache. L2ARC also needs...

4.9 ISO creates the root filesystem successfully.

Of course, it's always easier to get things up and running, if everything is allowed by default, instead of you need to think of each you need to allow, and explicitely allow it first. And in theory - when you respect everything - it makes no...

well, you can block anything you like, but when after an update suddenly telnet is active and you don't block that - you get 'problems'.

I bought 2 poor-to-medium quality NVMe drives, used, 256 GB. The board has PCIe 3 x 4 lanes IIRC, and NVMe 1.3. So plugging in hyper-dyper-throw-your-money-at-me NVMe drives just doesn't make sense. These are already much faster than the...

Grrr, same result. kernel isn't loaded. `ls` output is a bit different. Hit [Enter] to boot immediately, or any other key for command p Booting [kernel]... can't load 'kernel' can't load 'kernel.old' Type '?' for a list of...

sysinstall failed to install the base system, saying the /dev/ entry for the root filesystem does not exist. However, it partitioned the drive and installed the bootloader. I'm unpacking my tarfile now after newfsing in a md mapped file.

deskutils/joplin-desktop/ It works, no linuxulator needed.

Ah. Confirmed. Adding hda make it enter the installer. Thanks for that.

Had the same issue, seems to be related to not having a disk. Hence my example above with -hda.

Thanks for that. I always hated FreeBSD-5. Looks like this machine never made the switch to 5. And three cheers to the FreeBSD docs team!

I think Python is gross, but I'm just a weak-minded Java programmer. I can probably be ignored safely. I recently ran into something like this at work: def __getattr__(self, name: str): # If class is extened, or name doesn't start with...

Oh. I was using -nographics. With graphics on it loads the kernel. My apologies. However, it bombs out as follow. Also on a Mac's qemu. qemu-system-x86_64 \ -cdrom 5.1-RELEASE-amd64-miniinst.iso qemu-system-x86_64 -m 2048 \ -cdrom...

Thanks for that. I always hated FreeBSD-5. Looks like this machine never made the switch to 5. And three cheers to the FreeBSD docs team!

Also, if you don't like Python there's always Ruby at a similar level.

If it were my system, I would get a pair of quality NVMe SSDs as large as I could afford. Consider heatsinks as the design stage. Mirror them using ZFS. But see the caveat bellow about copy-on-write file systems -- you may wish to use a GEOM...

Yep. Hopefully 4.9? Vs.

Yep. Hopefully 4.9? Vs.

I would do a quick experiment with both (C++ and Python). Make a very simple program that reads pixels in from OpenCV and displays them on a simple GUI window. This is useful because it gives you a taster of setting the project up and how...

Fetched some random 5.1 ISO image and did: qemu-img create -f qcow2 test.qcow2 10G qemu-system-x86_64 -m 2048 -hda test.qcow2 -cdrom 5.1-RELEASE-amd64-miniinst.iso and booted it straight to installer ( 10.1.0 on osx ).

On the other hand, always have a "beginner's mind"! Devoid of preconceptions and with an openness.

99% sure. Internal 1 x USB 2, external 2 x USB 3 (dont know 3.0/.1/.2). I thought what is needed often from the OS will be cached by the MFU cache in RAM more or less quickly, so the speed of the storage is generally of minor importance. If you...

Fetched some random 5.1 ISO image and did: qemu-img create -f qcow2 test.qcow2 10G qemu-system-x86_64 -m 2048 -hda test.qcow2 -cdrom 5.1-RELEASE-amd64-miniinst.iso and booted it straight to installer ( 10.1.0 on osx ).

Fetched some random 5.1 ISO image and did: qemu-img create -f qcow2 test.qcow2 10G qemu-system-x86_64 -m 2048 -hda test.qcow2 -cdrom 5.1-RELEASE-amd64-miniinst.iso and booted it straight to installer ( 10.1.0 on osx ).

On the other hand, always have a "beginner's mind"! Devoid of preconceptions and with an openness.

Hmmm, the 5.1 install CD wants the kernel to be in /boot/kernel/kernel, which my old tarfile does not have. I have /kernel. Maybe my install was even older? QEMU hangs after the beastie logo when booting the install CD. Encountering a lot of...

On the other hand, always have a "beginner's mind"! Devoid of preconceptions and with an openness.

If it were my system, I would get a pair of quality NVMe SSDs as large as I could afford. Consider heatsinks as the design stage. Mirror them using ZFS. But see the caveat bellow about copy-on-write file systems -- you may wish to use a GEOM...

Interesting project. I'm assuming version 5.3. Do lsdev or show currdev report anything curious? (Love "Syntax for devices is odd." in the man page.)

The kernel doesn't get loaded in the first place. But the boot code might be unable to read the filesystem.

They are the old versions. But the bootstrap code in the MBR is not. Unfortunately I can't just copy it and I forgot the magic to cross-install it. So full install it is.

It doesn't load manually either, like load /kernel + boot but instead it goes to this "bad path" situation? Really weird, like the kernel doesn't understand the initial / tree...

No change.

I am creating a script !!! I presume you know what cat <<EOF > apache.scr does.

Oh, I missed this one when I was replying to your question. I thought you have actual working disk from the past. So legacy boot is from up-to-date version of FreeBSD ? That could mess things up.

I think the problem is that the bootloader I have in the MBR is too new. I have downloaded FreeBSD-5.1 ISOs to properly install from there first. Using i386 QEMU didn't make a difference.

Can you point me to a guide for doing this?

He's already in loader at that time.

It's hard to troubleshoot without actual disk. I'd start with the bare minimum first: qemu-system-i386 -hda root2.raw and go from there (ignoring warning about "guessing raw"). Passing -cpu host to old FreeBSD could mess things up too (but here...

I have the old kernel in /kernel

It is today's QEMU. I don't think I need the 32 bit version, but I will try that. So far I am using: qemu-system-x86_64 \ -cpu host \ -machine type=pc,accel=kvm \ -object rng-random,id=rng0,filename=/dev/urandom \ -device...

What is your full qemu command? 2004 would be most likely 32b version, are you using qemu-system-i386? I see you did ls in the loader, could you try ls / too?

I have to adjust many things to be really usable. It's a CLI and GTK3 program with common ports management module and trying to make a TUI too, all in node and gjs JavaScript with no npm packages. Then (as last step) move all work on a daemon...

Well, either way. I carry around a USB mass storage device (a NVMe in a USB enclosure) that has a FreeBSD and a Linux on it in dual-boot. Fully configured with my user account and my utils and packages I need. I use that in situations where I...

Rip a kernel from an old ISO? 2004? Must be around the 5.x releases.

No, all ports installed on my systems are built with my program