The bug introduced into cifs-utils, stopping the mounting of smb shares, has now been fixed. Please update your deployments if you were affected by it.
1 Like
Some minor adjustments have been made to ensure a smoother experience with Zorin 18. There will likely be more, but it seems to be working relatively well as-is.
What if, instead of Chrome, you used Chromium?
en.wikipedia.org/wiki/Chromium_(web_browser)
It is available in the repositories of most Linux distributions and on snapcraft.io/chromium and lathub.org/en/apps/org.chromium.Chromium.
That's quite possible to do, I would expect the end-user of the script would adjust the installation line accordingly. I mainly do it this way because we are a Chrome-based Google School, so I try to keep it uniform for the students across Chromebooks and Desktops of all types.
Kerberos tickets were failing for logged in users during the fileserver mounting stage, and this was traced to a change in the handling of on-disk ticket files. The cifs.spnego.conf file is now updated with the addition of the -t parameter to fix this.
For deployments you already have, run the following:
sudo sed -i 's/cifs.upcall %k/cifs.upcall -t %k/' /etc/request-key.d/cifs.spnego.conf
A problem with deployment was spotted during the update process, this section has now been moved to the end of the script, so that a system is not left in a partially configured state.
The offending package is probably a transient issue, but playing it safe for potential future incidents seemed wise.
At this point, the script is working fine on Zorin 18, in our production environment.
I might add a few extra lines for MacBook support, given that's the donated hardware I'm currently deploying this on.
Thinking of which, on a MacBook Air you need to edit the linux kernel boot line to add:
intel_iommu=off
This will allow the SSD in those to be seen by the OS, and gparted.
After installation, you can edit the grub default at:
/etc/default/grub
adding it into the options for the line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
then run:
update-grub
which will allow such a laptop to boot normally from thereon.
Just a side-comment question. Can Chrome be locked down fulky to prevent students attempting to access unauthorised web sites?
I've not tried, I use an upstream filter for that - N4L handles MoE education institutes in NZ, so they flick on various defaults which are then handled by their filtering system; like safe mode only on google/bing search etc.
1 Like
Hi, thanks for your continuous updates.
I recently discovered that Q4OS was the only GNU/Linux distro was able to be deployed on redundant Chromebooks recently which uses Plasma and ia a rock solid rolling distro. (It's my second distro of choice after PCLOS Debian.)