Debian: Difference between revisions

From DWIKI
Tony (talk | contribs)
Tag: wikieditor
Tony (talk | contribs)
mNo edit summary
 
(6 intermediate revisions by the same user not shown)
Line 27: Line 27:


==Networking on Debian==
==Networking on Debian==
* [https://wiki.debian.org/NetworkConfiguration Debian Network Configuration]
===Bonding===
===Bonding===
* https://wiki.debian.org/Bonding
* https://wiki.debian.org/Bonding
*[https://enterprise-support.nvidia.com/s/article/howto-create-linux-bond--lag--interface-over-infiniband-network Bonding on Infiniband]
*[https://enterprise-support.nvidia.com/s/article/howto-create-linux-bond--lag--interface-over-infiniband-network Bonding on Infiniband]


==https==
==https==
Line 63: Line 64:
Depends a bit, customer installer would insist on that, but expects /boot to be a separate partition?
Depends a bit, customer installer would insist on that, but expects /boot to be a separate partition?


 
==Check if a reboot is required==
==APT==
Check
 
  /var/run/reboot-required.pkgs
===What version is going to be installed?===
or
apt-cache policy packagename
  needrestart -k -b
 
===Repository changed its 'Version' value===
Try
  apt-get --allow-releaseinfo-change update
 
 
== the following packages have been kept back: ==
 
Time to apt-get dist-upgrade. But it could be different things.
See https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it
Perhaps:
apt-get upgrade package-that-is-kept-back
or try
  apt install package-that-is-kept-back


== change default editor ==
== change default editor ==
Line 121: Line 108:


==apt-get update throwing KEYEXPIRED==
==apt-get update throwing KEYEXPIRED==
Ignore that, it updated just fine. You migh run into the usual warnings when installing packaged. To Be Documented.
Ignore that, it updated just fine. You might run into the usual warnings when installing packaged. To Be Documented.
For example:
For example:
  deb [trusted=yes]
  deb [trusted=yes]
==Missing key==
Missing key D9A7E9F52B9754A34443ED1DC9A78F8C43D8720A, which is needed to verify signature
Find the key and add it to apt keyring, like
curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg


=Show more package information=
=Show more package information=
  apt-cache show packagename*
  apt-cache show packagename*
==List installed packages==
apt list --installed




Line 152: Line 149:


==show dependencies==
==show dependencies==
  apt-cache rdepends
===What depens on package?===
  apt-cache rdepends <package>
 
  aptitude why
  aptitude why


==What package does a file belong to?==
==What package does a file belong to?==
  dpkg -S /path/to/file
  dpkg -S /path/to/file

Latest revision as of 08:01, 5 June 2026

Sites

Security

Links

Netboot/PXE

Documentation


Networking on Debian

Bonding

https

https on debian testing is a mess, ignore:

http://www.eclectica.ca/howto/ssl-cert-howto.php looks promising

Handling packages

Pinning

HOWTO

Modules

Set module parameters

in /etc/modprobe.d/somename.conf

options somemodule paramname=2

FAQ

Installer

Select a boot disk

Depends a bit, customer installer would insist on that, but expects /boot to be a separate partition?

Check if a reboot is required

Check

/var/run/reboot-required.pkgs

or

needrestart -k -b

change default editor

update-alternatives --config editor

change timezone

dpkg-reconfigure tzdata


Change system language

dpkg-reconfigure locales

and

setlocale

kernel packages

  • kernel-image
  • kernel-source
volatile


clean cache

apt-get clean
      

E: Unable to correct problems, you have held broken packages.

First try

dpkg --get-selections | grep hold

reportbug: The following newer release(s) are available in the Debian archive:

Ignore than and just continue ( see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900254 )


apt-get update throwing KEYEXPIRED

Ignore that, it updated just fine. You might run into the usual warnings when installing packaged. To Be Documented. For example:

deb [trusted=yes]

Missing key

Missing key D9A7E9F52B9754A34443ED1DC9A78F8C43D8720A, which is needed to verify signature

Find the key and add it to apt keyring, like

curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg

Show more package information

apt-cache show packagename*

List installed packages

apt list --installed


W: GPG error:

http://ftp2.de.debian.org etch/volatile Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EC61E0B0BBE55AB3

gpg --keyserver wwwkeys.eu.pgp.net --recv-keys EC61E0B0BBE55AB3
#and that other thing

Or just:

apt-get --allow-unauthenticated install debian-archive-keyring
      

Or

apt-key adv  --keyserver pgp.mit.edu --recv-keys 8B48AD6246925553

Or

gpg --keyserver keyserver.ubuntu.com --recv-key 03BBF595D4DFD35C
gpg -a --export 03BBF595D4DFD35C | apt-key add -

show dependency tree

apt-cache dotty
apt-rdepends

show dependencies

What depens on package?

apt-cache rdepends <package>
aptitude why

What package does a file belong to?

dpkg -S /path/to/file