forum.excito.com

Right. Seems I was a bit too thorough reviewing the files in /etc and I wiped the executable bit from the start/stop scripts in /etc/local.d The system should in fact be up, it's just the front led colour not being changed to indicate that it has reached its running state. I'm also noticing now that...

Yes, you really need serial console access to manipulate the u-boot environment. I actually do have one live system that boots straight from USB, but that's only to overcome the problem that the installed SSD is not recognized by u-boot. The USB really only contains the preboot kernel that allows me...

Sorry. There was a tiny mix-up with file naming. Should be fine now. PS did you download an earlier release of Bubbagen? Might be interested to know that if you are running an older version you don't actually need to write the image to a USB stick. The new installer allows that you loop mount the un...

RAID is overrated. A common mistake is that people don't watch the logs and end up running with one of the disks broken for an extended period of time. To really protect your data you need to make backups and you should preferably store these off-site. So no, the disks will not be readable on a Wind...

Hi, I've just released version 1.13 of the Bubbagen live-USB image for B3 on GitHub. https://raw.githubusercontent.com/gordonb3/cache/master/Bubba/bubbagen-screenshots.jpg This release fixes a number of installation issues and eases maintenance by Bubbagen owning key portage config files required to...

Hi, I fear the problem may be in the Bubbagen bootloader that at least in the openrc version was found to target the harddisk for the kernel instead of the USB stick. I'm currently finishing up on version 1.13 which should be up in about half an hour from now and fixes (amongst other) this issue. Go...

It's also not just the repo site. The update sites are down as well and so is ns1, the primary domain server for the easyfind service.

I'm less worried by cronjob emails as I've configured them to be sent to me rather than b3's root. While I suppose this means that they'll still be stored somewhere in the first partition (likely /var?), at least I would become aware of a growing problem because my email traffic would become tediou...

The apt full-upgrade itself from Stretch worked flawless, but unfortunately it left me a working system without a working printer and a LMS that won't start. I guess it could be fixed quite easy if you play Linux daily, but I don't so I definitely rather consider running a rescue install with Stret...

guyran, it was Gordon who mentioned putting the swap partition close to the start... Correct. I did. Need to note that your system partition seems a bit too tiny. You should take care of logs growing faster than you expect them to do, applications storing data in /var/lib and emails (from cron syst...

I guess this requires some additional explaining. There are four possible methods for using php: command line execution - this is not web accessible as an Apache module - all scripts will be executed as the www/apache user as a dedicated service - this is commonly referred to as FastCGI or FPM metho...

Agreed, I myself actually like to have folders that are exposed to external users to be separated from the root partition. That way, if they cause an out of disk space it won't crash the whole system. Should you go ahead and split of `home` I would suggest that you keep the swap partition as the sec...

Did a quick scan on the installer as published on GitHub. Seems like the Debian installation uses the full disk as 'system' except for the last bit being used as swap? If you convert that to ext4 you will not be able to boot the B3 because u-boot requires the partition that holds the kernel uImage t...

Ah... yes. Haven't run Debian for a while ;) www-data sounds familiar. Crontab being empty is a positive but does not guarantee that a worm can't restart itself when being killed. The well known entrance on your OS version is php.cgi by the way and this is not needed to run your system; you should l...

Uhm... Are you still running the original Debian based system? If you see a lot of CPU activity on perl you may want to verify whether these processes are running as user `www`. Also check the crontab for user www, this should be empty but I suspect it won't be.