Hi All, 64studio Testers: Preparing for the next iso\image release. 1) Post any errors, issues you find to forum\mailing list. Post as much info about your computer\system as possible. This makes helping with the issues easier & faster.
> To help you search your bash_history. > Increase your bash_history save size by adding the following > to your .bashrc > > $ gedit .bashrc > > export HISTSIZE=1000000 HISTFILESIZE=1000000 > > At the bottom of the file in the alias section add: > > alias h="history|grep " > > now run: ". .bashrc" without the quotes > (to save you having to log out & back in to your desktop) > Then you can search your bash_history with: > > $ h sudo > $ h install > $ h remove > $ h gedit > > etc., > > Ref .bashrc > http://paste.ubuntu.com/137987/ > > $ cp .bash_history bh090326.txt > > $ grep sudo bh090326.txt > $ grep cp bh090326.txt > $ grep install bh090326.txt > $ grep remove bh090326.txt > > $ h grep > > $ cp bh090321.txt /media/data/backups/ > > grep & find inside many files in a directory. > > If you have a directory with many files inside and you > want to search for a string in all the files inside. e.g. > I keep a directory with all my .bash_history backups then: > > cd /media/data/backups/ > > $ grep install * > $ grep remove * > $ grep sudo > > etc., > > When testing these tools can save a great deal of time. > The new install can be quickly configured to your preferences, > and build-software\favourite software reinstalled without fuss. > Today's .bash_history is tomorrows install routine. > B) Package Management. Package management using the terminal is one of the main advantages of using the Debian system. $ sudo apt-cache search "packagename" $ sudo apt-cache show "packagename" $ sudo apt-cache policy "packagename" $ sudo apt-get build-dep "packagename" $ sudo dpkg -l |grep "packagename" $ sudo dpkg -l |grep 64studio $ sudo dpkg -s 64studio $ sudo dpkg -s dpkg $ sudo dpkg -s apt Without the quotes. If you've configured ".bashrc .bash_history" Ref above. $ h cache $ h show $ h policy $ h build-dep $ h dpkg To help find/remove unwanted software run: $ dpkg --get-selections > software1 and again $ dpkg --get-selections > software2 This will create 2 files in your ~/ directory, software1 software2 These list the software installed, leave software1. $ sudo grep cups software2 $ sudo grep blue software2 $ sudo grep "packagename" software2 etc., only you know what is not needed. $ sudo apt-get remove --purge "packagename" Watch very carefully for shared libs and others apt might try to remove. This method will also keep a .bash_history of the software you have removed. Check package dependencies with: $ sudo dpkg -s "packagename" $ cp .bash_history bh090327.txt $ grep install bh090327.txt $ grep remove bh090327.txt $ grep dpkg bh090327.txt Once you have removed software re-run: dpkg --get-selections > software2 software1 (default_installed_software) software2 (installed_software) You could also research\install\remove the packages using synaptic. C) System Administration System Logs. Most users don't spend much time with system logs but 64studio "Testers" need to be able to report issues upstream or post to forums. Better to be able to send details regarding just the issues you are dealing with instead of the full system log file. Main Menu > System > Administration > System Log. or once you have key words search your logs using grep, e.g. keywords, acpi boot hda sda etc., $ ls -a /var/log/ $ sudo grep acpi /var/log/messages $ sudo grep hda /var/log/messages $ sudo grep sda /var/log/messages $ sudo grep acpi /var/log/syslog $ sudo grep hda /var/log/syslog $ sudo grep sda /var/log/syslog $ sudo grep boot /var/log/boot $ sudo grep boot /var/log/dmesg $ sudo grep boot /var/log/kern.log $ sudo grep boot /var/log/lastlog $ sudo grep boot /var/log/messages $ sudo grep boot /var/log/syslog boot is just an example, use keywords that relate to the query you are interested in e.g. CPU PCI USB usb device etc., $ dmesg $ dmesg >64s30b3-dmesg.txt The second command will create 64s30b3-dmesg.txt file in your ~/ directory $ grep CPU 64s30b3-dmesg.txt $ grep PCI 64s30b3-dmesg.txt $ grep USB 64s30b3-dmesg.txt $ grep usb 64s30b3-dmesg.txt $ grep Warning 64s30b3-dmesg.txt $ grep warning 64s30b3-dmesg.txt $ cat /var/log/messages >64s30b3-messages.txt Will create 64s30b3-messages.txt file in your ~/ directory You can grep 64s30b3-messages.txt in exactly the same way you did 64s30b3-dmesg.txt System Administration Xorg.0.log $ grep WW /var/log/Xorg.0.log $ grep EE /var/log/Xorg.0.log $ grep II /var/log/Xorg.0.log $ cp .bash_history bh090327.txt $ cp bh090327.txt /media/data/backups/ If you use these methods on your present install. Today's .bash_history is tomorrows install routine. Happy Testing :-) Cheers! Dave. http://www.64studio.com/node/1028 http://trac.64studio.com/pdk/ <http://paste.ubuntu.com/> _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
