Posts tagged ‘debian’
the following steps are required to adjust a fresh ubuntu to my personal language-preferences, including the default character encoding for gnome-terminal set to UTF-8
# install the required packages to generate the appropriate locales: sudo aptitude install language-pack-de-base language-pack-de # set the default environment variables: echo ' # locale stuff LANG= LC_ALL= # Character classification and case conversion: LC_CTYPE="de_DE.utf8" # Date and time formats: LC_TIME="de_DE.utf8" # Non-monetary numeric formats: LC_NUMERIC="de_DE.utf8" # Collation order: LC_COLLATE="POSIX" LC_MONETARY="de_DE.utf8" LC_MESSAGES="POSIX" LC_PAPER="de_DE.utf8" LC_NAME="de_DE.utf8" LC_ADDRESS="de_DE.utf8" LC_TELEPHONE="de_DE.utf8" LC_MEASUREMENT="de_DE.utf8" LC_IDENTIFICATION="de_DE.utf8" ' | sudo tee -a /etc/environment
IMPORTANT: you have to log out after these changes to make them work!!
hp-snmp-agents error: Service snmp has to be enabled to start service hp-snmp-agents
If you get an error like:
Setting up hp-snmp-agents (188.8.131.52.1-2) ... insserv: Service snmp has to be enabled to start service hp-snmp-agents insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing hp-snmp-agents (--configure): subprocess installed post-installation script returned error exit status 1
Edit the file:
and change the “update-rc.d “ to “update-rc.d -f “, then
apt-get -f install
and you should be back in business.
(copied 1-on-1 from craighoffman)
this is based on redmine-1.0.0
we need a more recent version of
rubygems than those shipped with lenny, so first add the backports-repository to your sources.list:
deb http://www.backports.org/debian lenny-backports main contrib non-free
then, update your package list:
sudo apt-get update
and install the above mentioned packages Continue reading ‘installing redmine on debian/lenny using mod_passenger’ »
aptitude has a specific list-category to display those when using the curses-GUI, but I do not like it. fortunately, you can use the search-command from the cli-interface with the appropriate search-pattern:
aptitude search "?obsolete"
or as a shorthand:
aptitude search "~o"
See the aptitude Reference Guide for more information.
to restore a dump from a MySQL database created on a debianish Linux system, just feed the dumped SQL to the command-line mysql client like this:
mysql -u root -p < mysql-all-2010-03-28-0515.sql
since the whole content of all MySQL databases are overwritten with that stored in the dump, credentials are affected as well. that’s the reason why debian’s system tools won’t work any more after restoring the old dump, since debian creates a maintenance-user called “debian-sys-maint” during the installation and stores the randomly generated credentials in “/etc/mysql/debian.cnf” so it’s sufficient to just copy the “password” values from the old file into the new one and restart mysql. otherwise, you will run into an error like this:
/etc/mysql/debian-start: Running 'mysqlcheck'... /etc/mysql/debian-start: /usr/bin/mysqlcheck: Got error: 1045: Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) when trying to connect /etc/mysql/debian-start: FATAL ERROR: Upgrade failed
“schroot” is a secure chroot tool that allows a non-privileged user on a system to switch to a chroot in a secure manner. This can be used to set up automated builds etc. that don’t have to run as root.
Unfortunately, RedHat Enterprise doesn’t ship with schroot-packages, so here’s a way to build them: Continue reading ‘building “schroot” on RHEL-5.4’ »
want to know which files in /etc have been changed on your debian-like Linux system?
one part can be done with the package debsums, which compares the md5sums delivered with a debian-package with those of the current files:
$ sudo debsums -a -s . . debsums: checksum mismatch apache2.2-common file /etc/apache2/sites-available/default debsums: checksum mismatch apache2.2-common file /etc/apache2/ports.conf . .
Note 1: this does NOT cover configuration files that are not part of the .deb-package itself, e.g. those manually created by a user AND as well those built by a package’s configuration/post-install scripts. You have been warned!
Note 2: debsums can give hints about a compromised system, but it’s absolutely no guarantee that a non-suspicious output comes from a clean system – if the system’s compromised, an attacker could as well change the md5sums-database of a package (residing in /var/lib/dpkg/info/PKGNAME.md5sums)
just to remember how to test if a certain directory and its files are included in the backup using the TSM commandline interface:
./dsmc preview backup -console /path/to/dir/
delete one or more files from your backup (NOTE: the quotes in the second command are important, otherwise bash will expand the pattern and produce a list of files, which will confuse the TSM-client):
./dsmc delete backup /backups/mysql/mysqldump-complete-2010-01-20-1823.sql.gz ./dsmc delete backup '/backups/mysql/*.gz'