On Debian Sid i have seen that ufw service is stopped on logrotate!!
Its a bad known bug! REMARK ufw 3.5.X fails with iptables 1.8! Cause iptables 1.8.1 is very BUGGY! USE 1.6!
- Set all Services like Dovecot, Postfix to listen on LOCALHOST (127.0.0.1) if not needed over Internet
- Enable ONLY encrypted AUTH (Login) to Postfix! (TLS 1.2)
- Disable unneeded Services ! like Samba, FTP…
- move config from /etc/logrotate.d/ufw to /root/ to disable ufw logrotate !!
- edit /etc/ufw/ufw.conf set LOGLEVEL to „off“
- restart the Server and check open Ports next Days from outside with:
$sudo nmap -PN my.server.com
Under heavy load the Debian Kernel 4.14-13 crashes on high memory load and let the CPU freeze. Not really funny so rollback to older version
Apparmor has a current bug with the Kernel 4.14 on Debian and seems Ubuntu too, it blocks MySQL and other services from clean run. Bug touches Network Stack of the Kernel
If you search for a slim twitter client on desktops try the small „surf“ browser
sudo apt-get install surf
Now you have a slim and clean Twitter Timeline like on Tablets, it can be resized to Banner or Fullscreen.
If you run Debian Servers, you read last weeks about security problems of systemd service manager.
On several tests i have seen much systems having problems on service starts on boot like on debian, raspian ..
This is a result of not clean redesigned scripts of the services by the Maintainers like the Proxy Server „privoxy“ Package…
For Tests i decided to try the new Debian Fork Replacement DEVUAN for Desktop and a standard Debian Server Setup without systemd!
Howto purge Systemd on a Debian System read this external Wiki:
or try Devuan for Server and Desktop:
Remark: Devuan is tested for Desktop usage cause customized scripts and packages like polkit for EASY setup!
If you work on older Laptops and you use a Console only System Setup like on Debian there is a Bug on systemd and the console-setup package since years. After reboot all Font Settings seems gone. But the Settings are not real gone, cause systemd does not pull the settings on boot!
How to fix?
- edit the crontab of root by
sudo su -
- insert the /bin/setupcon command on „@reboot“ means on every boot!
@reboot /bin/setupcon > /dev/null 2>&1
- save and exit, reboot now
- now the PC should echo big Fonts for old eyes „Terminus 20×12 Frambuffermode“
Current is a UNFIXED Bug on Debian 9.0 Stretch which makes impossible to easy install DKMS Nvidia-Legacy Drivers 304/340 for older Geforce Cards
To run nouveau on upgrade 8.0 to 9.0 go to /etc/modprobe.d and remove MANUAL all blacklist configs (*.conf) of nvidia cause some glued on upgrade and are not purged automatic by the upgrade. Cause they will block nouveau load at boot (xserver-xorg-video-nouveau)
Then run on Terminal:
$sudo update-initramfs -u -k all
- Older Hardware isn’t supported by Legacy Drivers after Nvidia-375!!
- If you not forced to upgrade to 9.0, then WAIT! up to 3 Month! and checkout Bug Lists.
- I tried Nvidia Installer Files too (*.run) they don’t work too, seems a API of the Kernel is changed
- Nouveau Version on Debian Stretch is able to run Kodi (glx)! seen on Geforce 8400GS 256MB
- On Onboard Geforce Chips like older Laptops HOLD Debian 8.0
Current the acd_cli tool for amazon drive mount offers no „fsid“ (device /dev) point, that you cant export and share the amazon drive at your home local network.
On the latest raspberry pi OS (jessie) you can use a small workaround to get a NFS Shared Amazon Cloud Backup Uploader (needs python3.4 !)
If you now put files on the /sendtoamazon nfs share from a PC, the raspberry pi will grab and push it into the cloud via the „acd_cli mount“ a python3 script, remark 10 minutes is ok for small files! on bigger files use over „40“ minutes between pushes. If acd_cli fails check for correct python version! and last python modules!!! (python3-appdirs python3-dateutil python3-requests python3-sqlalchemy python3-pip pip3)
If you have a SMALL BANDWITH for upload you can use „rsync -avz“ instead mv (move) with „throttle“ option to upload files slowly!!
Howto acd_cli for amazon mount on git
The last 12 month have been a „golden“ time of the upcomming embedded linux devices, but the custom OS’s offers some problems, you should know for projects:
- embedded PC’s like the ARM based pi2 / pi3 uses a own compiled OS
- not every known debian package is available
- not all compile scripts to rebuild are available on git
- slow performance can let you run into unuseable problems (heat, load, I/O), correct written scripts run into freezes without any error made by you!
- you should take time for a closer look at buying them
- calc the costs of non-x86 systems, later you cant often upgrade, cause embedded systems are not made for
- dealers take too much money for less performance!
- embedded devices can’t be grown up for additional precs like compression based on chips!
- embedded devices need less energy, but can hangup by load over 65%, cause no cooling
- the are made for learning and small control jobs
- for NAS / Server jobs take x86 m-atx / micro-atx, cause you can access easy full debian packages
- not all python + libs packages are available to run projects (example: acd_cli amazon cloud nas backup)
- current embedded pc livetime at multimedia usage may be 24month cause to much and faster changes
May be that the arm os package trees may grow up, then we can talk again, but current x86 is the cheapest way to build systems without stress! And you have always the reserve to buildin new things of hardware..
If you boot your PC on a Setup CD into „live“ mode after some time the Desktop Unity or Gnome starts. After successful testing the PC with the current Drivers and Kernel you can select „Install“ by pressing the icon left on the desktop. But here the Problem appear that you dont see any informations about bugs, crashes, or other major messages during the setup. Without this you are not able to find any errors later, or you cant tell a supporter what happend!
- Always open a gnome-terminal as first step instead of pressing the installer icon!
- move the gnome-terminal window on lower screen area to 100% width!!!
- Enter there:
$sudo tail -f /var/log/syslog # some Linux uses /var/log/messages!
- Now press Installer icon! and view Log in realtime
Hope this help to fix bugs like freezes of often seen SSD Errors I/O…
If you want to update the SSD Firmware of a device you should know some things:
- Do you REALLY need the update? Bugs? If NOT exit here!
- Firmwareupdates can destroy DATA on Drives!
- Data cant be restored if the Controller fails after Update
- Downgrade a Firmware to older is most IMPOSSIBLE!!
.. now you need a USB Stick 4GB and the ISO File of the Firmware Disk of the Manufacter then open the Gnome Terminal or Console and:
$sudo su - #become root
$apt-get update && apt-get install unetbootin gparted # install the tools
$dd if=/dev/null of=/dev/sdc bs=10240 count=1 # delete usbstick unmounted with zeros (factory reset)
$gparted /dev/sdc #create new Primary Partition with FAT32, set "managed flags" to "boot lba", now exit gparted
$mount /dev/sdc1 /mnt #mount usbstick to /mnt
$unetbootin #select FreeDOS at Menu, and select /dev/sdc1 and create the FreeDOS Stick, then exit unetbootin WITHOUT reboot!
$mkdir /iso && mount -o loop /home/yourusername/firmware-cd.iso /iso # mount the CDImage to /iso readonly
$cd /iso && cp firmware.img /mnt/firmware.img # copy firmware-data to usbstick
- NOW, reboot and unplug other HDDs of the PC, ONLY the SSD must be insert!
- Boot the PC on the usbstick, on the unetbootin Menu PRESS „Tab“ to get the „Unetbootin-Console“!
- Here change the value of „initrd=/ubinit“ to „initrd=firmware.img“ and PRESS ENTER
- Follow now the Firmware Update Dialog and Reboot with disconnected usbstick and replugged Drives…