Nov. 1st, 2015

oio11: (Default)
понедельник, 4 ноября 2013 г.

Ubuntu: Как полностью удалить Java

 
Удалить все пакеты Java (Sun, Oracle, OpenJDK, IcedTea plugins, GIJ):
sudo apt-get update apt-cache search java | awk '{print($1)}' | grep -E -e '^(ia32-)?(sun|oracle)-java' -e '^openjdk-' -e '^icedtea' -e '^(default|gcj)-j(re|dk)' -e '^gcj-(.*)-j(re|dk)' -e 'java-common' | xargs sudo apt-get -y remove sudo apt-get -y autoremove 
Очистить конфигурационные файлы:
dpkg -l | grep ^rc | awk '{print($2)}' | xargs sudo apt-get -y purge 
Удалить конфигурационный файл Java и кэш:
sudo bash -c 'ls -d /home/*/.java' | xargs sudo rm -rf 
Удалить виртуальные машины, установленные вручную:
sudo rm -rf /usr/lib/jvm/* 
Удалить все остальное:
for g in ControlPanel java java_vm javaws jcontrol jexec keytool mozilla-javaplugin.so orbd pack200 policytool rmid rmiregistry servertool tnameserv unpack200 appletviewer apt extcheck HtmlConverter idlj jar jarsigner javac javadoc javah javap jconsole jdb jhat jinfo jmap jps jrunscript jsadebugd jstack jstat jstatd native2ascii rmic schemagen serialver wsgen wsimport xjc xulrunner-1.9-javaplugin.so; do sudo update-alternatives --remove-all $g; done 
Поиск оставшихся директорий:
sudo updatedb sudo locate -b '\pack200' 
Если вывод предыдущей команды показал что-то вроде этого: /path/to/jre1.6.0_34/bin/pack200 , удалите родительский директорий bin, как здесь: sudo rm -rf /path/to/jre1.6.0_34.


http://eldoradozpua.blogspot.com/2013/11/ubuntu-java.html
oio11: (Default)

WiFi USB dongle

This article explains how to use a D-Link USB Wi-Fi adapters on your Acme Board.
The USB Wi-Fi adapter tested is:
  • DWA-131 D-Link WirelessN Nano USB adapter
    • HW Ver B1, F/W Ver 2.01
    • Chip RTL8192CU

Check the Kernel configuration

Access to the Kernel configuration panel using make arch=ARM menuconfig command and enable the following items:

Device Drivers  --->
  [*] USB support  ---> 
    <*> USB Wireless Device Management support

Device Drivers  --->
   [*] Network device support  --->    
     [*]   Wireless LAN  --->
       <*>   Realtek rtlwifi family of devices  ---> 
          <*>   Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter
          [*]   Debugging output for rtlwifi driver family (NEW)
Compile the Linux Kernel and reboot the board. To know how to compile the Linux Kernel follow the articles available on the tutorials page index)

Install the Realtek firmware


~# apt-get update
~# apt-get install firmware-realtek
Insert the Wi-Fi USB adapter on your Acme Board. These messages should appear on the debug port or by typing dmesg command:

~# dmesg
usb 2-3: new full-speed USB device number 3 using at91_ohci
usb 2-3: not running at top speed; connect to a high speed hub
usb 2-3: New USB device found, idVendor=2001, idProduct=330d
usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-3: Product: 802.11n WLAN Adapter
usb 2-3: Manufacturer: Realtek
usb 2-3: SerialNumber: 00e04c000001
Please note the idVendor=2001 and idProduct=330d of the USB dongle.
Use this number to tell to Linux which kernel driver to use with it:

~# echo 2001 330d > /sys/bus/usb/drivers/rtl8192cu/new_id
rtl8192cu: Chip version 0x11
rtl8192cu: MAC address: c0:a0:bb:e1:9d:98
rtl8192cu: Board Type 0
rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
root@ariag25:~# usb 2-3: Direct firmware load failed with error -2
usb 2-3: Falling back to user helper
rtlwifi: Loading alternative firmware rtlwifi/rtl8192cufw.bin
rtlwifi: wireless switch is on
When you get the right messages try to type this command:

debarm:~# cat /proc/net/wireless
Inter-| sta-|   Quality        |   Discarded packets               | Missed | WE
 face | tus | link level noise |  nwid  crypt   frag  retry   misc | beacon | 22
 wlan0: 0000    0.    0.    0.       0      0      0      0      0        0

Install the Wireless-tools

To configure and use the Wi-Fi adapter you need to install the Wireless tools for Linux, a package of Linux commands intended to support and facilitate the configuration of wireless devices.
To install this package type:

debarm:~# apt-get update
debarm:~# apt-get install wireless-tools
When finished type:

debarm:~# iwconfig
lo        no wireless extensions.
 
eth0      no wireless extensions.
 
wlan0     unassociated  Nickname:"rtl_wifi"
          Mode:Auto  Access Point: Not-Associated   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
which provides info about the wireless extensions of each network adapter (in this case wlan0).

Network configuration

As a first configuration example, we'll show you how to get access to an open Wi-Fi LAN. Edit the file /etc/network/interfaces and add these lines:

auto wlan0
iface wlan0 inet dhcp
  wireless-essid [your_essid] 
  wireless-mode managed 
Restart the network services typing:

debarm:~# /etc/init.d/networking restart
...
Listening on LPF/wlan0/5c:d9:98:a7:3a:fe                                        
Sending on   LPF/wlan0/5c:d9:98:a7:3a:fe                                        
Sending on   Socket/fallback                                                    
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5                     
DHCPOFFER from 192.168.1.1                                                      
DHCPREQUEST on wlan0 to 255.255.255.255 port 67                                 
DHCPACK from 192.168.1.1                                                        
bound to 192.168.1.2 -- renewal in 8171 seconds.                                
done.    

debarm:~# ifconfig
...
wlan0     Link encap:Ethernet  HWaddr 5c:d9:98:a7:3a:fe                         
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0        
          inet6 addr: fe80::5ed9:98ff:fea7:3afe/64 Scope:Link                   
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1                    
          RX packets:4057 errors:0 dropped:0 overruns:0 frame:0                 
          TX packets:327 errors:0 dropped:0 overruns:0 carrier:0                
          collisions:0 txqueuelen:1000                                          
          RX bytes:287147 (280.4 KiB)  TX bytes:21864 (21.3 KiB)         

Connect to a WEP-protected LAN

Edit the file /etc/network/interfaces and set wireless-key:

auto wlan0
iface wlan0 inet dhcp
  wireless-essid [your_essid]
  wireless-key [your_wep_key]
Restart the network services as in the previous section.

Install the wpa_supplicant for encrypt access

Wpa supplicant is a software implementation of an IEEE 802.11i supplicant for Linux that manages the authentication on the Wi-Fi link.
To install these packages type:

debarm:~# apt-get update
debarm:~# apt-get install wpasupplicant
Now add in the file /etc/network/interfaces the configuration for the wlan0 network adapter to add Wi-Fi Protected Access (WPA) or Wi-Fi Protected Access II (WPA2).

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid [your_essid]
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk [your_hex_key]
Change the fields [your_essid] with the SSID of your access point and [your_hex_key] with the WPA-PSK key.
To generate a WPA-PSK key from WPA ascii key use this command:

wpa_passphrase [your_essid] [your_ascii_key]
For example on my access point called "acme" that uses the ascii key "netusg20" the command is this:

debarm:/etc/init.d# wpa_passphrase acme netusg20
network={
        ssid="acme"
        #psk="netusg20"
        psk=38c309a773a6c936c31aeb8bcb5bc44d60539715524e77464759f29095bfc1f3
}
Copying the psk code the /etc/network/interfaces file becomes:

auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid acme
wpa-ap-scan 2
wpa-proto RSN
wpa-pairwise CCMP
wpa-group CCMP
wpa-key-mgmt WPA-PSK
wpa-psk 38c309a773a6c936c31aeb8bcb5bc44d60539715524e77464759f29095bfc1f3
Now type:

debarm:~# /etc/init.d/networking restart
After a while if the dhcp are working well you will obtain your interface up.
You can also detach the eth0 lan cable to try to access your board directly from the Wi-Fi link.

debarm:~# iwconfig wlan0
wlan0     IEEE 802.11bg  ESSID:"acme"  Nickname:"rtl_wifi"
          Mode:Managed  Frequency:2.447 GHz  Access Point: 00:21:29:69:C2:D8   
          Bit Rate:54 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=100/100  Signal level=100/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Related links

http://www.acmesystems.it/dlink_wifi
oio11: (Default)
Missing firmware in Debian? Learn how to deal with the problem by Raphaël Hertzog
You know it already, since Debian 6.0 non-free firmware are no longer provided by a standard Debian installation. This will cause some troubles to users who need them. I’m thus going to do a small overview on the topic and teach you what you need to know to deal with the problem.

What are firmware and how are they used?

From the user’s point of view, a firmware is just some data that is needed by some piece of hardware in order to function properly. The driver for that hardware typically loads the firmware on the device as part of its initialization.
In the Linux kernel, the drivers are all using a standardized interface (request_firmware) to retrieve the firmware before sending it to the device. Thanks to this standardization, it’s possible to either embed the firmware in the kernel or to have it request the firmware from user-space when needed.
Debian (like most distributions) has selected the latter option. Thus when the kernel needs a firmware, it sends out a request to user-space. udev is getting the request with the name of the firmware, and in its default configuration (see /lib/udev/rules.d/80-drivers.rules) it executes /lib/udev/firmware.agent in response.

Where are firmware stored?

firmware.agent is a simple shell script that tries to locate a firmware before sending it back to the kernel through a sysfs entry. It looks into the following directories:
  • /lib/firmware/$(uname -r)
  • /lib/firmware
  • /usr/local/lib/firmware
  • /usr/lib/hotplug/firmware
Firmware provided by packages are thus usually in /lib/firmware and you can use /usr/local/lib/firmware for manually installed firmware.

How do I know whether I need a firmware?

First of, you can notice messages from the kernel telling you that it tried to load a firmware but it failed. They look like this:
e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin": -2 
But you might be informed sooner. When you install a new version of the Linux kernel with the official Debian packages, the post-installation script will go through all loaded modules (those listed by lsmod) and it will verify whether this module as provided by the newly installed kernel might require firmware files. This information can be retrieved with modinfo:
$ modinfo -F firmware /lib/modules/2.6.32-5-amd64/kernel/drivers/net/e100.ko e100/d102e_ucode.bin e100/d101s_ucode.bin e100/d101m_ucode.bin 
If one (or more) of those firmware is (are) not yet available on the system, you will get a warning message similar to this one:































update-initramfs will also generate a similar warning on the terminal:
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 W: Possible missing firmware /lib/firmware/e100/d102e_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101s_ucode.bin for module e100 W: Possible missing firmware /lib/firmware/e100/d101m_ucode.bin for module e100 
The Debian installer also detects when you have hardware that might require a missing firmware file. You have the option to supply the missing files on a USB stick (either directly or through the corresponding package).

How do I find and install the missing firmware?

Now that you have the name of the firmware file that you want, it’s relatively easy to identify the package that provides the required file. You can use “apt-cache search <filename>” because the firmware packages embed the list of firmware files in their description. You can also use “apt-file” (provided by the package of the same name) or the web interface at packages.debian.org.
$ apt-cache search d101m_ucode.bin firmware-linux-nonfree - Binary firmware for various drivers in the Linux kernel $ apt-file search d101m_ucode.bin firmware-linux-nonfree: /lib/firmware/e100/d101m_ucode.bin 
If the above commands return nothing, you probably need to enable the “non-free” repository in your /etc/apt/sources.list (you can also enable it within synaptic). And you also want to run “sudo apt-file update” to have the latest information.
Now you can install the right package, in the example above it was firmware-linux-nonfree.

How do I install all firmware just to be sure I don’t miss any?

There’s no meta-package depending on all firmware packages so there’s no easy answer to this question. Furthermore not all firmware packages respect the naming convention “firmware-*” (there’s for example zd1211-firmware).
So your best bet is to look up all the packages with a generic search like this one:
$ apt-file --package-only search /lib/firmware/ atmel-firmware [...] 
And then install them all.

Are there DVD or CD images with non-free firmware?

Yes. Debian provides an unofficial netinst image for i386/amd64/powerpc with the non-free firmware, you can find it here: http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/.
I provide complete DVD sets with firmware, and Multi-Arch CD/DVD with firmware, it’s over there in my DVD shop: https://raphaelhertzog.com/go/debian-cd/ (i386/amd64 only)
When using those installation discs, the Debian-installer will be able to find the required firmware immediately. There’s no need for you to provide them on a USB stick.

Other questions?

I think I covered the most important things you have to know about firmware on Debian. But should you still have a question, feel free to share it in the comments so that I can improve this article.
https://raphaelhertzog.com/2011/03/14/missing-firmware-in-debian-learn-how-to-deal-with-the-problem/

Comments

Timo Juhani Lindfors says

$ apt-get source firmware-linux-free
$ sed -n 240,260p linux-2.6-2.6.32/firmware/keyspan_pda/keyspan_pda.S
movx @dptr, a
inc dptr
djnz r1, clear_rx_ring_loop
;;; turn on the RS-232 driver chip (bring the STANDBY pin low)
;; set OEB.1
mov a, #02H
mov dptr,OEB
movx @dptr,a
;; clear PB1
mov a, #00H
mov dptr,OUTB
movx @dptr,a
;; set OEC.[127]
mov a, #0x86
mov dptr,OEC
movx @dptr,a
;; set PORTCCFG.[01] to route TxD0,RxD0 to serial port
mov dptr, PORTCCFG
mov a, #0x03
movx @dptr, a
There, now you’ve seen source code of free firmware 😉

Raphaël Hertzog says
If you need the firmware for the early boot to work, yes, otherwise no. Just run update-initramfs -u or even update-initramfs -u -k all
oio11: (Default)
CHVT(1)         General Commands Manual         CHVT(1)

NAME top


       chvt - change foreground virtual terminal

SYNOPSIS top


       chvt N

DESCRIPTION top


       The command chvt N makes /dev/ttyN the foreground terminal.  (The
       corresponding screen is created if it did not exist yet.  To get rid
       of unused VTs, use deallocvt(1).)  The key combination
       (Ctrl-)LeftAlt-FN (with N in the range 1-12) usually has a similar
       effect.

COLOPHON top


       This page is part of the kbd (Linux keyboard tools) project.
       Information about the project can be found at 
       ⟨http://www.kbd-project.org/⟩.  If you have a bug report for this man‐
       ual page, send it to kbd@lists.altlinux.org.  This page was obtained
       from the project's upstream Git repository
       (git://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git) on
       2015-10-19.  If you discover any rendering problems in this HTML ver‐
       sion of the page, or you believe there is a better or more up-to-date
       source for the page, or you have corrections or improvements to the
       information in this COLOPHON (which is not part of the original man‐
       ual page), send a mail to man-pages@man7.org

                               26 January 1997                       CHVT(1)



            HTML rendering created 2015-10-19 by Michael Kerrisk, 
            author of The Linux Programming Interface, 
            maintainer of the Linux man-pages project.
        
http://man7.org/linux/man-pages/man1/chvt.1.html
oio11: (Default)
18 Oct 2012

How to remove and disable BlueTooth support on Debian GNU / Linux servers

 
How to remove / disable bluetooth support on Debian GNU / Linux servers


If you running Debian Squeeze Linux (as server Apache, MySQL, Qmail etc.) on brand new purchased hardware with bluetooth support; you will notice default Linux kernel will detect and load modules for Bluetooth
This would not be a problem only if Bluetooth does not pose possible errors or (even at cases even maybe system hangs ups?). The actual reason in my case to want to disable bluetooth on a productive Linux server operating like host was I found out in dmesg produced output, some errors related to Bluetooth, here they are:

root@deb:~# dmesg|grep -i 'call trace' -A 8
[323406.744439] Call Trace:
[323406.744440] [] ? lapic_next_event+0x18/0x1d
[323406.744450] [] ? __report_bad_irq+0x30/0x7d
[323406.744453] [] ? note_interrupt+0x105/0x16e
[323406.744455] [] ? handle_fasteoi_irq+0x93/0xb5
[323406.744458] [] ? handle_irq+0x17/0x1d
[323406.744460] [] ? do_IRQ+0x57/0xb6
[323406.744463] [] ? ret_from_intr+0x0/0x11
[323406.744464]
I saw this error and similar ones occuring, every now and then obviously displaying something wents wrongs with IRQs related to BlueTooth Communication with Kernel (as it keeps processing requests loaded in system memory) …
Well anyways having the bluetooth kernel module loaded on memory just takes up few chunks of useless assigned memory.
I don't have intention to use bluetoothever in future on these host so I decided to completely remove bluetooth support on those Debian.
1. Remove blueetoh support on Debian GNU / Linux
First to check info about the loaded kernel module bluetooth.ko and its assigned module load alias run:

root@deb:~# /sbin/modinfo bluetooth
filename: /lib/modules/2.6.32-5-amd64/kernel/net/bluetooth/bluetooth.ko
alias: net-pf-31
license: GPL
version: 2.15
description: Bluetooth Core ver 2.15
author: Marcel Holtmann
srcversion: 9FD5BF98FC88505DC637909
depends: rfkill
vermagic: 2.6.32-5-amd64 SMP mod_unload modversions
Secondly disable memory preloaded bluetooth.ko on the current host with cmds:

root@deb:~# rmmod -f bnep
root@deb:~# rmmod -f l2cap
root@deb:~# rmmod -f sco
root@deb:~# rmmod -f bluetooth
Default way to control if Bluetooth (on host support is ON or OFF) is through /etc/default/bluetooth. Inside /etc/default/bluetooth is a control variable:

BLUETOOTH_ENABLED=1
To shut it off change its value to 0:

BLUETOOTH_ENABLED=0
Then to permanently prevent bluetooth.ko from being ever in future loaded its also good idea to blacklist modules – bnep, btusb, bluetooth:

root@deb:~# echo 'blacklist bnep' >> /etc/modprobe.d/bluetooth.conf
root@deb:~# echo 'blacklist btusb' >> /etc/modprobe.d/bluetooth.conf
root@deb:~# echo 'blacklist bluetooth' >> /etc/modprobe.d/bluetooth.conf
Onwards re-build, current kernel initramfs:

root@deb:~# update-initramfs -u -k `uname -r` -v
......
......
Next update boot init scripts with update-rc.d to make sure bluetooth (service / daemon) is not started:

root@deb:~# update-rc.d bluetooth remove
......
That's all bluetooth will not load up anymore on next boot and at present time will not take up useless mem space.
2. Re-enable disabled blueetooth on Debian Linux

I've been asked in one of comments, what to do If you need to re-enable bluetooth on your Debian Linux at some time in future, so here are the steps to turn back blueetooth on again

/etc/modprobe.d/bluetooth.conf
Change variable:
BLUETOOTH_ENABLED=0
to
BLUETOOTH_ENABLED=1
Open /etc/modprobe.d/bluetooth.conf and remove any blacklisted modules, e.g:
'blacklist bnep'
'blacklist btusb'
&39;blacklist bluetooth'
Rebuild again kernel ramfs
root@deb:~# update-initramfs -u -k `uname -r` -v

Enjoy :)
http://pc-freak.net/blog/remove-disable-bluetooth-support-debian-gnu-linux-servers/
oio11: (Default)
17 Oct 2012

Debian Linux how to remove Xorg, Gnome / KDE, GDM and other graphical environment packages from a server
Lets say by mistake you install a package and apt installs as a package dependency a whole bunch of Xorg, GDM GNOME 2 / 3 (desktop environment) along with whole other multitude of meta packages just like, lets say xinit , nautilus, totem, gedit,remmina etc.:
Mistakenly installing a graphical environment happens common (at least in my experience as admin happed many, many times). Often installing GUI by mistake is done on already well configured productive server, serving thousand of HTTP, SQL and Mails daily.
Having a started GDM login on the server takes some from the CPU time and also is extends possibilities for security breach to the server, so as always if something is not used it is better to wipe it off …
Here are some apt-get remove commands which will (COMPLETELY) remove Xserver ( Xorg ), Graphical Login Manager (GDM), GNOME desktop environment and their surrounding stuff:

# apt-get remove xorg
# apt-get remove nautilus-data nautilus-sendto libnautilus-extension1
# apt-get remove desktop-base
# apt-get remove python-gnomedesktop
# apt-get remove gdm3
# apt-get remove totem seahorse remmina gedit-common gconf2 epipha gedit-common gconf-defaults-service xauth
# apt-get remove epiphany-browser-data evolution-webcal gconf2
# apt-get remove nautilus-data nautilus-sendto libnautilus-extension1
# apt-get remove x11-common
# apt-get autoremove --purge gnome*
Here something worthy to mention is in Debian and (its deb based linux erivatives including Ubuntu), there are the so called metapackages. For those who don’t know what a meta-package is?; it is a package linked to a group of packages. Actually the meta package itself is a pre-selected Packages ready to install / remove with apt, aptitude or rest of “intelligent” package management utils available for Debian.
Once a meta-package is installed, all linked package dependencies; be it binaries or libraries as well as the proper configurations are downloaded and installed.
Very useful thing hence is listing all install-able metapackages; to list all available metapackages in Debian Linux use:

# apt-cache search metapackage
....
.....
......
As of time of writing this post there are 276 apt installable metapackages existent on Debian Squeeze 6.0.5 Linux:

# apt-cache search metapackage|wc -l
276
Another more general way to see the basic types of metapackages, installable is via tasksel (tasksel is run and used during initial Debian Installer via install CD);
In tasksel, there are few meta-packages; Actually tasksel is very handy for sysadmins who install new servers :). Here is list of available meta-packs through it:

# tasksel --list-tasks
i web-server Web server
u print-server Print server
i dns-server DNS server
u file-server File server
u mail-server Mail server
u database-server SQL database
i ssh-server SSH server
u laptop Laptop
u manual manual package selection
u desktop Graphical desktop environment
i web-server Web server
u print-server Print server
i dns-server DNS server
u file-server File server
u mail-server Mail server
u database-server SQL database
i ssh-server SSH server
u laptop Laptop
u manual manual package selection
It is possible to also view sub-packages contained within, each of tasksel meta-packs, i.e..:

# tasksel --task-packages desktop
twm
eject
openoffice.org
xserver-xorg-video-all
cups-client
openoffice.org-help-en-us
hp-ppd
avahi-daemon
system-config-printer
openoffice.org-thesaurus-en-us
cpufrequtils
myspell-en-us
xdg-utils
pm-utils
cups
cups-bsd
xorg
iceweasel
xserver-xorg-input-all
hplip
desktop-base
alsa-base
libnss-mdns
browser-plugin-gnash
xterm
anacron
alsa-utils
cups-driver-gutenprint
foo2zjs
hpijs
gimp
menu
kerneloops
openoffice.org-gcj
libgl1-mesa-dri
foomatic-db-engine

Actually using tasksel is much more “intelligent” way to remove GNOME, GDM and Xorg from a server. It will completely wipe out everything previously installed for running Desktop Environment on the host.
To remove desktop environment with tasksel:

# tasksel remove desktop
Ncurses progress bar will appear displaying all removed packages …
In my case, during trying to figure out what packages I need to remove ImageMagick as long as few other packages got removed as dependencies so I had to install them over with:

apt-get install --yes imagemagick libice6 php5-imagick libxvmc1 \
libzbar0 libxt6 libsm6 libxres1 libxtst6 libxvmc1 x-ttcidfont-conf libxxf86dga1
For people who need to remove KDE desktop environment from a host to be used as a server, check out KDE meta-packages:

apt-cache search metapackage|grep -i kde
You can remove all KDE related meta-packs within a bash loop, like so:

for i in $(apt-cache search metapackage|grep -i kde|awk '{ print $1 }'); do \
apt-get remove $i; done
Removing all rc‘s from system can be done with:

# for i in $(dpkg -l | grep -i '^rc' | awk '{ print $2 }'); do \
dpkg --purge $i; \
done

Though, I tested this if you follow my tutorial be careful, something might break and some essenail package or lib for (your custom) services might be removed. Be careful what is offered to uninstall only approve it if you’re 1000% sure; Please don’t count me responsible if apt- removes something which breaks your productive server :)
Share this on

http://pc-freak.net/blog/debian-linux-remove-xorg-gnome-gdm-graphical-environment-packages-serverr/

oio11: (Default)
к посту   ---

ps command - LinuxCommand.org

http://linuxcommand.org/man_pages/ps1.html
ps. PS(1) Linux User's Manual PS(1). NAME. ps - report a snapshot of the current processes.
SYNOPSIS. ps [options]. DESCRIPTION. ps displays information ...

10 basic examples of Linux ps command Linux

By Silver Moon On Dec 1, 2013

Linux ps command

The ps command on linux is one of the most basic commands for viewing the processes running on the system. It provides a snapshot of the current processes along with detailed information like user id, cpu usage, memory usage, command name etc. It does not display data in real time like top or htop commands. But even though being simpler in features and output it is still an essential process management/monitoring tool that every linux newbie should know about and learn well.

In this post we are going to revise the basics of using the ps command to check the processes and filter and sort them in different ways to suit better.
Read more... ) http://www.binarytides.com/linux-ps-command/
oio11: (Default)
Apr 17th, 2012

Dwm: A Tutorial for Beginners

This tutorial explains how to install, set up, and customize
dwm. dwm is a window manager for X and the forerunner to xmonad and awesome, among others. As a tiling window manager, it automatically creates, adjusts, and moves windows for you so that you can focus on being productive. This means that it’s equally useful whether you’re using multiple large displays or a small netbook screen; it’s also stable and consumes little by way of system resources. dwm is hard to beat in terms of staying out of the way of the user and making the most of however much display real estate is available. Setting it up, however, is somewhat trickier – hence this tutorial.

Read more... )

http://rhunter.org/blog/2012/04/17/dwm-a-tutorial-for-beginners

October 2025

S M T W T F S
   1234
567891011
12131415161718
19202122 232425
262728293031 

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Mar. 28th, 2026 12:35 am
Powered by Dreamwidth Studios