You should not attempt to get a fixed /dev/sdX name at all. You should just not use such a name directly.
What you should do is reference your disk (or disk's partition) by an autodetected identifier provided under /dev/disk/. Among the choices available there, /dev/disk/by-id/ has entries tied to the serial number of a disk device. So even two identical ...
If the root login has its shell set to nologin, instead of logging in it runs the nologin command.
Check out the manpage of nologin for more information.
As pointed out in the manpage, you can create a text file at /etc/nologin.txt to display a custom message. Otherwise it will use the default message.
grep "42$" questionnaires.txt > test42 | cut -d '/' -f 1 test42
doesn't do anything like you think it does.
The first part:
grep "42$" questionnaires.txt > test42
That writes the output of grep to test42. The output of that is nothing.
So that nothing then gets passed to
cut -d '/' -f 1 test42
Which is trying to read the file you'...
In Ubuntu 16.04, php 7.0.33 is really the most recent version.
ubuntu@ ~> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
ubuntu@ ~> php -v
PHP 7.0.33-0ubuntu0.16.04.12 (cli) ( NTS )
If you need 7.1 series, either install from a PPA or update your ...
Hypothesis: the filesystem is case insensitive and therefore Mechanics and mechanics address the same directory.
It may be possible to rename mechanics to Mechanics via a temporary name:
mv mechanics foo
mv foo Mechanics
Then the directory may appear as Mechanics but you will still be able to refer to it as mechanics or even mECHaniCS.
The pdfjam utility is the de facto standard for this kind of manipulation. A pdfnup wrapper may be available but it was recently removed from pdfjam. It is available in Ubuntu in the package texlive-extra-utils.
If I understand your requirements correctly, it's very simple:
pdfjam --nup 2x1 HalfA4V.pdf -o a4.pdf
The issue it turns out that for some reason systemd-resolved kept editing /etc/resolvd.conf nameserver entry to 127.0.0.53. Manually changing that to a working DNS server did resolve the issue, however on networking service restart/system reboot the issue returned.
To fix from that happening run:
systemctl stop systemd-resolved
systemctl mask systemd-...
If the purpose is to provision the machine without incurring in a locking error, the simplest and most stable solution is to run the provisioner remote command (or the apt-related commands) while locking the apt-daily lock file. No service masking/disabling/waiting etc.etc.
In Ubuntu server, the package update programs (apt-daily, unattended-upgrades, cloud-...
mv evaluateA2P/ action2pose_bk/ evaluateA2P/
The result of that command would be to move the action2pose_bk directory into the evaluateA2P directory. To undo that, simply move it back by running:
mv action2pose_bk/evaluateA2P .