Debian: Difference between revisions
m (→FAQ) |
m (→FAQ) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 51: | Line 51: | ||
*http://wiki.debian.org/AptPinning | *http://wiki.debian.org/AptPinning | ||
=HOWTO= | |||
==Modules== | |||
===Set module parameters=== | |||
in '''/etc/modprobe.d/somename.conf''' | |||
options somemodule paramname=2 | |||
= FAQ = | = FAQ = | ||
==Installer== | |||
===Select a boot disk=== | |||
Depends a bit, customer installer would insist on that, but expects /boot to be a separate partition? | |||
==APT== | ==APT== | ||
===What version is going to be installed?=== | |||
apt-cache policy packagename | |||
===Repository changed its 'Version' value=== | ===Repository changed its 'Version' value=== | ||
Try | Try |
Latest revision as of 13:34, 18 November 2024
Sites
Security
- http://lists.debian.org/debian-security-announce/
- debsecan
- debsum
Links
Netboot/PXE
- https://wiki.debian.org/DebianInstaller/NetbootAssistant
- Preseed
- Install Debian 9 (Stretch) via PXE Network Boot Server
Documentation
- Compiling kernels the Debian way
- aptitude is often nicer than apt-get, but be careful
- apt-file to find package providing a certain file
Networking on Debian
Bonding
https
https on debian testing is a mess, ignore:
- make-ssl-cert
- apache2-ssl-certificate in apache2.2-common only?
- http://www.debian-administration.org/articles/349
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?
APT
What version is going to be installed?
apt-cache policy packagename
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
change default editor
update-alternatives --config editor
change timezone
dpkg-reconfigure tzdata
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 migh run into the usual warnings when installing packaged. To Be Documented. For example:
deb [trusted=yes]
Show more package information
apt-cache show packagename*
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
apt-cache rdepends aptitude why
What package does a file belong to?
dpkg -S /path/to/file