Ubuntu.eskimo.com is now upgraded to 18.04 LTS Bionic Beaver and bionic.eskimo.com is discontinued.
For those wishing to get a preview of the next long term release of Ubuntu, there is a shell server temporarily available until the official release of Bionic Beaver later this month.
The machine is bionic.eskimo.com. You can access it with ssh and x2go. If you use x2go, be sure there is not a ‘mesg n’ or other terminal related command in your .profile or your login will fail.
When Bionic Beaver is officially released, providing they haven’t broken anything severely, ubuntu.eskimo.com will be upgraded to this version, 18.04LTS.
I built a new server and set it up with 18.04 LTS which is still in beta but it works better than 17.10 or 16.04 LTS which are stable. So our network is back operational. There still may be some shell servers not properly sync’d. If you encounter a problem accessing your home directory please let me know BUT be sure to tell me which server you are on.
My cat, Monster, did not survive. He had a stroke today which left half his body paralyzed, then after sleeping about 15 minutes had a very violent nasty grand mal seizure from which he never regained consciousness. I took him to a vet to have him euthanized as I did not want to have him wake up again with half his body paralyzed or go through another massive seizer like that, and his breath was becoming increasingly shallow but by the time I got to the vet he was already dead.
Bye Bye Monster and Thank you for the wonderful time we shared.
I tried to upgrade Iglulik’s nfs server to fix a common problem with NFS becoming resynchronized and it broke things worse, the 17.10 version won’t work with NFSv2 needed by Eskimo and some servers I use for user administration. To make things work Ubuntu has removed 17.04 because it’s past end-of-life so I can’t easily go back. I’ve got an install disk so I am trying to extract the necessary packages from it but it’s not easy.
So the long and short is until I get this fixed, the eskimo.com shell server won’t be operational and I won’t be able to credit user accounts.
My cat has also crashed again and I don’t think he is going to make it this time. He is basically non-responsive now, I think his central nervous system is pretty much shut down and there isn’t anything left but to put him down. Great cat, really a drag.
All in all this weekend has been shit. I guess it wasn’t so good for Jesus so could be worse I suppose. At least Jesus resurrected, kind of doubt my cat will.
I updated NextCloud to version 13.01 and along with that update I also installed a bunch of new applications including a radio app that allows you to listen to a number of different station around the world.
If you don’t have a NextCloud App on your I-phone or Android device, visit your play store and pick one up. You can access anything you have stored here if you make it available, as well as many cool apps.
You can also visit from any web browser at https://www.eskimo.com/nextcloud.
The login and password are the same ones you use for e-mail, shell, and ftp access.
OCR Applications on Shell Servers
- gocr and unpaper
- tesseract and unpaper
- gocr, ocrad, ocrfeeder, ocrmypdf, ocrdjvu, python-pyocr andpython3-pyocr, tesseract-ocr
- gocr, ocrad
- cuniform, gocr, gocr-tk, gscan2pdf, tesseract, unpaper, ocr, ocrfeeder, python-pyocr, python3-pyocr
- gimagereader, gocr, gocr-tk, kooka-trinity, ocrad, ocrfeeder, pdfsandwich, python-pyocr, python3-pyocr, scantailor, unpaper, gscan2pdf, lios
- gocr, gocr-gui, kooka, ocrad, tessearact-ocr
- gocr, tesseract, unpaper
- tesseract, unpaper, zinnia
- cuneiform, didjvu, gimagereader, gocr, gocr-tk, kooka-trinity, ocrad, ocrfeeder, ocrmypdf, ocrodjvu, python-pyocr, python3-pyocr, tesseract-ocr, zinnia-utils
- cuneiform, didjvu, gimagereader, gocr, gocr-tk, ocrad, ocrfeeder, ocrdjvu, pdfsandwich, python-pyocr, python3-pyocr, unpaper
In general the debian derived systems have a much richer software base.
Well no it won’t be down again tonight as I tried the fix on a less traffic’d machine first and it did not work. Code Intel claims fixes the problem doesn’t. So it’s back to the drawing board for now.
I was able to obtain microcode from Intel that is supposed to mitigate spectre variant 2. I’ve found documentation as to where to put it so that the kernel picks it up at boot time. However, for reasons I do not understand even though I have copy host CPU information checked and the host is a Broadwell i7-6850k, KVM/Qemu keeps changing that to Skylake as soon as the machine boots so the microcode does not apply correctly. I am thinking perhaps this is because this was originally installed on Skylake so to work around this I may move this virtual domain back to a Skylake based machine.
CentOS 6 and Scientific Linux 6 will both be down for about an hour tonight to migrate them back to the hardware they were initially installed on.
I am going to take MxLinux down for about 90 minutes to image the machine, now that the x2go issues are resolved, so that if I have to restore it from backups, it is restored in to a working state.