I realize that this question is rather old, but just in case someone stumbles upon this, here is the answer:
The reason for the swap label being ignored is that the installer uses mkswap from busybox, which cannot set labels. [To verify this just boot into a netboot installer, switch to the second console (Alt+F2) and look at the mkswap binary.]
As a ...
/proc/mounts and mount don’t show settings which are included in the default settings, so you can assume that an entry which doesn’t show the contrary is using the defaults (see the documentation there for defaults):
rw, suid, dev, exec, auto, nouser, and async.
If /proc/mounts doesn’t list noexec, then the file system is mounted with the exec permission....
Long time research and digging on google's deep depth finally find the problem.But i'm do not what is root cause.
The problem was CPU.Firstly we create the VM 2*4 vCPU then today i read about Debian bug forum archive about Intel(R) Xeon(R) CPU E5-2xxx family then the holy moment dunk my head. Reduce the vCPU 1x1. Problem solved.
The simplest way to fix this is to manually download the debian-archive-keyring package and install that, then run apt update again. You’ll also need to restore the permissions on /etc/apt/trusted.gpg:
sudo chmod 444 /etc/apt/trusted.gpg
The Translations problem is a bad file on the servers, there’s nothing you can do about that.
A better and more alternative debootstrap is debuerreotype: reproducible, snapshot-based Debian rootfs builder to create the images.
Creates tarballs of the rootfs.
It's also the base of the official Docker images.
You don't need to add the yarnpkg repository. yarn and yarnpkg are available on debian Buster:
Disable the yarnpkg repo:
# sed -i 's/^/#/' /etc/apt/sources.list.d/yarn.list
then install yarn from debian repository:
sudo apt update
sudo apt install yarn
It will install cmdtest which provide yarn command (/usr/bin/yarn).
There’s nothing wrong with your setup, the problem here is the package pool and the web site. The rust-doc package was disabled with the 1.24.1+dfsg1-1~deb9u1 upload:
Disable -doc package, requires packages not found in stretch and
docs are available online anyway
As a result the package is no longer included in the indexes and isn’t available ...
"(none of the subdomain virtual host logs have error messages)"
That was (should have been) your clue. :)
There are several (conf) files in play here. I'm guessing you've (basically) omitted the extra/httpd-vhosts.conf. Which defines all/any of your virtual hosts.
version 2.4 has become more modular than it's predecessors. So most of the old methods either ...
I had a similar problem that by the time I had played the 10,000 moneys scene was exactly this, and I had been trying to add the missing stuff to /e/n/i.d/etho
But studying the man page for interfaces, I noted that ALL of the set of examples had only 2 lines of real data, the ipv4 address/24, and a gateway line specifying the address of my router. So I ...
One reasonable way of going about this is as follows:
divert all the files you modify, so that dpkg no longer replaces them, but instead installs them with a different name;
make your Rakefile do its work using the newly-named files instead of the originals, reading the newly-named files and writing the originals;
install a post-invoke dpkg hook in /etc/...
Never mind, I figured it out. It was monit monitoring the SSH deamon. I'm a dumbass. I stopped monit (service monit stop), tailed the auth.log and, whaddayaknow, no more entries. So mystery solved and monit was restarted. Now I know the cause, I don't mind these loglines as much.
Exim has a compile-time setting FIXED_NEVER_USERS which disallows delivering to root: https://github.com/Exim/exim/wiki/Q0039#question. There is no way around this without building your own debian package.
The setserial package will restore the serial settings at boot time.
Once installed, simply edit the file /var/lib/setserial/autoserial.conf
###PORT STATE GENERATED USING AUTOSAVE-ONCE###
# If you want to configure this file by hand, use
# dpkg-reconfigure setserial
# and change the configuration mode of the file to MANUAL.
# If you ...
Edit your sources.list (as root):
with the following lines:
deb http://deb.debian.org/debian stretch main
deb-src http://deb.debian.org/debian stretch main
deb http://deb.debian.org/debian-security/ stretch/updates main
deb-src http://deb.debian.org/debian-security/ stretch/updates main
deb http://deb.debian.org/debian stretch-...
I just dealt with this problem, so I'd like to put the answer here, as the documentation does not make it obvious.
As you may know, Windows supports setting up SMB shares natively through Explorer (the "Sharing" option in the right-click menu for a directory). This link, found in a GitHub Gist collection, suggests that the proper way to share from Windows ...
Assuming you're attempting to create a USB stick from an iso, or other bootable image file:
dd if=./unbuntu-boot-install.iso of=/dev/sd(a-z) bs=1m conv=sync
where (a-z) will be the letter associated with your USB device. Best means of determining that letter is to compare the output of an ls /dev before, and after plugging in your USB stick. Taking note of ...
This error comes if you haven't rebooted after installation, so that should be it.
#shutdown -r now OR #reboot
then as root or sudo rum:
Also be sure you have the development-tools installed:
#sudo apt update
#sudo apt install build-essential
Solved only with rescue mode:
boot into "rescue mode" - probably available at most VPS
mount appropiate drive
change root entry to root:x:0:0:root:/root:/bin/bash
save, exit and reboot without rescue mode
Different approaches like
user1@hostname: ~$ su -s /bin/sh
user1@hostname: ~$ su -s /bin/sh -c /bin/sh
Sounds like your local script is being run at login when Caja should only be starting to manage the desktop rather than to show a particular directory.
A quick-and-dirty solution would be to name your script something else, have a script create a symlink (named caja and pointing to your Caja launch script) at login but after the desktop is up and running, ...
Seems like I have installed a non compatible libapt-pkg5.0 for my debian 9 so I just downloaded the right version of that lib,
and install it through,
dpkg -i dpkg -i libapt-pkg5.0_1.4.9_amd64.deb
and it came back to live again.
Your original command will work if you have the heirloom-mailx package installed.
sudo apt-get install heirloom-mailx
Then you can:
mailx -s "Test" -a /home/user/filename.xlsx email@example.com < /root/emailbody.txt
To "attach" a uuencoded file really just means providing that as the body of the email; as a result, you cannot also redirect a body in from a file; you'd use:
uuencode /home/user/filename.xlsx filename.xlsx | mail -s "Test" firstname.lastname@example.org
I am sorry to say but your system is probably broken beyond reasonable repair. Trying to work backwards to determine what has happened, you say that you are running a Debian 9 system, but you have the libc6 package installed from Debian 10 (2.28). This is often caused by attempting to mix use repositories from multiple versions of Debian or from Debian ...
I had this issue after accidentally changing the permission/ownership rights. I've been able to revert things by issuing the following commands:
sudo chown -R postgres:postgres /var/lib/postgresql/11/
sudo chmod -R u=rwX,go= /var/lib/postgresql/11/
and then reloading the service
sudo service postgresql restart
That's because on desktop machines, KDE Connect works as a server, and phone apps are connecting to it. This shouldn't really be an issue, as all the incoming connections are being authenticated first (you have to “accept pairing” from a device in order for it to be able to do anything with your PC), but if you want, you can disable the kdeconnectd service (...
debi installs all the packages listed in the .changes file produced during the build, so yes, it ends up installing all the packages produced by the build, including development packages and debug symbols.
If you want to limit the set of packages which are installed, without having to figure out their version or architecture, you can use debi with a list of ...
the commands you posted will be executed one by one, not in parallel, so halt will execute only after sync completed.
if you added & to sync, so
halt - f
sync would work in background and coukd not finish in time, as halt would run at the same time.
summing up, you're safe with sync executing in full before halt is invoked.
Both packages’ descriptions follow a typical format used for related packages: they share a common section,
The Berkeley Internet Name Domain (BIND) implements an Internet domain
name server. BIND is the most widely-used name server software on the
Internet, and is supported by the Internet Software Consortium, www.isc.org.
and a package-specific ...
On Debian, to set up the keyboard (and font) on VTs not running X, you should run setupcon. To reconfigure the default keyboard, and set it up, you should run dpkg-reconfigure keyboard-configuration.
setupcon can use multiple variants of its configuration files, which would allow you to quickly switch between keyboard layouts.
The system’s keyboard ...
I'm not using Debian or Ubuntu so I can't check this, but it might be related to the printing service CUPS. There is a confirmed bug in Ubuntu which reports a problem with the cups-browsed service sending a large amount of UDP requests on ports 8610 and 8612.
You could try to stop any CUPS service and see if the scans stop.
You won't be able to send emails that claim to be from a Gmail domain unless they really come from Gmail's servers. (Well, I suppose you can send them but they'll be tagged as probable forgeries by the recipient servers.)
The reason for this is that Gmail, along with most other email providers, identifies valid SMTP sender addresses in its SPF record, and ...
Consider adding the following rule to your ~/.ssh/config:
Assuming your SSH server got the following line in /etc/ssh/sshd_config:
AcceptEnv LANG LC_*
Check also: man ssh_config and man sshd_config.
The following steps were needed:
remove third party sources that may have bad dependencies (MS VS CODE and SKYPE repos)
Remove installed items that came up in the error list.
INSTALL the items that came up in the error list as bad dependencies, but which were not installed.
Afterwards having completely uninstalled KDE (which seems to have been broken by ...
~ Version 0.1.1 ~ Released: 2007-10-23
Send SIGQUIT and then SIGKILL after a little delay, so we can clean up the backends nicely by unlocking when we cancel (Richard Hughes)
Stopping systemd-logind fixed it for me:
sudo systemctl stop systemd-logind
This is suggested as a workaround in this github issue on the nvidia-xrun github page:
Good news guys, systemd-logind is the culprit here. The current
workaround is to run the following command after logging out from the
"nvidia-xrun" session sudo systemctl stop systemd-...
1) Download the latest CUDA Toolkit
2) Switch to tty3 by pressing Ctl+Alt+F3
3) Unload nvidia-drm before proceeding.
3a) Isolate multi-user.target
sudo systemctl isolate multi-user.target
3b) Note that nvidia-drm is currently in use.
lsmod | grep nvidia.drm
3c) Unload nvidia-drm
sudo modprobe -r nvidia-drm
4d) Note that nvidia-drm ...
Run killall -q gpg-agent if the other solutions do not work. It may work.
I was getting a similar error for a PPA repository on Ubuntu 18.04 and after trying various solutions on the internet for the last month, I just stumbled on the gpg-agent and killed it. Then the PPA repositries started to update on doing sudo apt-get update. I know it may compromise ...
Yes, it is. All that can go wrong is that you end up attempting to select packages which have been removed; in that situation,
unknown packages will be ignored with a warning.
(See the dpkg manpage.)
You could also end up selecting deprecated packages; however you’ll end up with the appropriate transitional packages. (This could be more troublesome if ...