forum.excito.org

Thanks for the reply. I agree that this is a strange situation because I noticed I was getting "canonicalisation" error messages when using apt and found the reason was the root directory not owned by root. I have modified this and all works well.
In answer to your question, I installed using your ...

Having managed to install your excellent package for the recent Buster version of Debian and starting to just harden it with a firewall I discovered a warning that said the root, /usr & /etc are owned by UID 1000 which I discover is the excito user, is there any reason for this other than allowing ...

Just a heads-up about finding a compatible USB stick. I had similar problems and tried a variety of sticks and the one which worked for the installation of MouttE's excellent Debian Buster package was a Sandisk Cruzer. In spite of what Gordon said that it shouldn't exceed 8 Gb mine is 16Mb. It ...

Thanks Pressurised for the prompt reply and all the details of your modification. In fact, I have created the same setup in the fstab file after repartitioning with gparted using my dekstop. On refitting the hard drive everything worked as normal and I was able to make the modification to have a ...

A question to ask how I could correctly repartition my new 2TB drive that I finally managed to use for the installation of your Debian Buster package. I had problems finding the right USB key and it was a Sandisk that finally did the trick; then I had to modify the interfaces to get it to connect ...

Hi Makai & Cheeseboy,

Your posts are over a year old but I was wondering how you managed to get your internal LAN set up using a cable modem as the DHCP. According to the Excito doc on the B3 if you choose to use it as router for an internal LAN it automatically starts a DHCP server using 192.168 ...

Thanks to Binkem for his suggestion, but in spite of following the advice about using the Rescu system image to access my B3 via a USB stick, I was puzzled to find that the sshd_config file which I had modified and seems to be causing the blockage only appears as a hard link to /etc/bubba/sshd ...

I fear I have committed the irreparable after installing denyhosts and then attempting to tighten up access by limiting it to certain computers on my LAN. I'm not sure if it is this program or a misconfiguration of the sshd_config file that has caused me to have only the connection refused message ...