1) 'b' bounces the message completely unmodified to a new address
2) 'Esc E' uses a current message as a template for a new message,
can modify attachments and text
*) Esc F to clear the "From" address (Esc F) from the send men
*) S to change subject
ls $1 | xargs -I {} -t mv $1/{} $2/{}
here the I command says use {} to replace the piped output
thus we use
find . -iname '*nons*' -print0 |xargs --null -I {} cp {} ../nonstandard-analysis/{}
to deal with
1) spaces in output file names from find we use -print0 and
correspondingly to match we use xargs --null
2) to deal with the xargs applied command which has multiple arguments we use the -I {}
to fill in for the xargs output
cool!
apt-get install dh-make-perl
tar -pzxvf Locale-Hebrew-1.04
dh-make-perl Locale-Hebrew-1.04/
cd Locale-Hebrew-1.04
debuild
cd ..
ls *.deb
dpkg -i liblocale-hebrew-perl_1.04-1_amd64.deb
it works nicely.
gs -dNOPAUSE -sDEVICE=pdfwrite -sOUTPUTFILE=firstANDsecond.pdf -dBATCH first.pdf second.pd
say we have a volume group data on a physical volume 'data'
vgchange -ay data
(if it was formally exported before from old system (fat chance) then you can do
vgimport data
mkdir /data
then
mount /dev/data/ /data
say to load the information
see
http://tldp.org/HOWTO/LVM-HOWTO/recipemovevgtonewsys.html
-----------
2. Lets say to start a new physicalvolume and create a volume group
vgcreate volgroup1 /dev/sda1
vgdisplay
lvcreate -L5G -n logicalvolume
mkfs.ext3 /dev/volgroup1/logicalvolume
then can mount it
mount /dev/volgroup1/logicalvolume /data
say.
To fix this, the best answer I could find was this one, where you simply install a deb package to add a file to the Xsession.d directory, which gets run every time your start X. Here's are contents:
# Starts the Synaptic daemon which deactivates the touchpad while typing
# This executes for all users
SYNDAEMON=/usr/bin/syndaemon
SYN_IDLE=1 #Seconds to wait after last key press before enabling touchpad
if [ -x $SYNDAEMON ]; then
$SYNDAEMON -i $SYN_IDLE -d
fi
This is a very simple and elegant way to fix the problem. Click here to download the package directly.
dpkg -L xserver-xorg-input-synapticsapt-get install dh-make-perl
apt-get install buildessential
debscripts (debuild)
then follow
http://www.debian-administration.org/articles/78
dh-make-perl PDL-X/
cd PDL-X
debuild
cd ..
then
dpkg -i pdl_2.4.3-7_amd64.deb
dpkg -i libpgplot-perl_2.20-1_amd64.deb
wget http://www.bbc.co.uk/radio/aod/rpms/hitchhikers.ram
cat hitchhikers.ram
rtsp://rmv8.bbc.net.uk/radio4/comedy/thu2300.ra
mplayer -dumpstream rtsp://rmv8.bbc.net.uk/radio4/comedy/thu2300.ra
(Time passes while mplayer writes a file named “stream.dump”.)
Now convert the stream.dump file to pcm/wave:
mplayer -ao pcm stream.dump
(Time passes while mplayer writes a file named “audiodump.wav”.)
Convert that wave file into mp3:
lame --preset standard --tt "Episode 1" --ta "BBC Radio 4" --tl "The Hitchhiker's Guide to the Galaxy, Tertiary Phase" --ty "2004" --tn 1 audiodump.wav episode1.mp3
Hooray! One down side I’ve seen so far: the stream.dump RealAudio file is just under 10Mb, while the mp3 produced by this process is over 37Mb. I should probably use different options when running lame.
DocMGR is a complete, web-based Document Management System (DMS). It allows for the storage of any file type, and supports full-text indexing of the most popular document formats. It is available in many different languages and is easy to translate into new languages. DocMGR runs on PHP, the Apache webserver, and Postgresql. It optionally uses tsearch2 for full-text indexing which provides for faster search results and result ranking. DocMGR supports LDAP authentication, the ability to easily add and remove "objects" for storage in the system, document workflow, object subscriptions, WebDAV access, and an ever-growing set of features revolving around content storage.
The rest of the document has to do with configuring xournal in such a way that it is more convenient to use it to highlight text inside PDF files. Although some of these settings can be set from within xournal’s graphical interface, I recommend editing the configuration file directly: /home/gnot/.xournal/config, since it contains more options than those available in the GUI.
The ruler exists in order to make life easier when you highlight text. It is highly recommended that you enable it for text highlighting:
startup_ruler=true
If highlighting text is your main use of xournal, then you can make it the startup tool as well.
startup_tool=highlighter
The following options make xournal’s window to start maximized and set the initial zoom to 150% respectively.
window_maximize=true
initial_zoom=150
The following options configure the highlighter. You can set the 3 pre-defined levels of thickness and which one will be the default one, set the default color and finally set the opacity (the default opacity level of 50% is just too much).
highlighter_thicknesses=2.83;8.50;19.84
highlighter_thickness=2
highlighter_color=yellow
highlighter_opacity=0.20
No one said that annotating PDF files in Linux is an easy task. I have tried many open source tools for that job, but xournal seems to be the best one at the time of writing.
How do you create your images? Do you want to have a BIG file or a SMALL file
qemu-img create debian.img 5G
this creates a large file
which is SPARSE thus is capable of being compressed
via
tar -cjSf debian.tar.bz2 debian.img
which can be moved.
On the other hand you can make a qcow small file to begin with.
qemu-img create debian.img -f qcow 5G
this is a small file.
And can make a copy file to use.
qemu-img create -b debian.img -f qcow stable.ovl
this second is a very tiny copy file, just stores the diffs.
I have a Windows XP SP2 installation that I use for work, while my current personal OS of choice is Windows Vista. I only work weekends, so rebooting wasn’t too bothersome initially. Over time it has become more and more of a chore, as I can’t easily switch from one development environment to another without rebooting. I decided it was time to make my work installation a virtual machine.
I had some additional complications that made the process a little non-standard. I originally tried using VMWare’s converter tool, but it would fail at 97% of the creation of the disk. I then tried using a Windows port of the Unix utility ‘dd’ to create a raw image of the disk, but because the Windows volume manager was accessing the disk, dd would give me access errors. Additionally, the VMWare converter doesn’t support converting from a raw image (…grr…), so Qemu’s qemu-img tool would have to be used to convert the raw image to a disk in VMWare’s vmdk format.
The steps to reach our goal aren’t too complicated, and can be replicated by others easily. To do it, I used:
I started by booting into my Linux install. Linux only mounts the disks it uses (hint hint, Microsoft) so we can access all sectors of the partition to make a dump of the disk with dd. I first had to mount the partition where I wanted the output file to reside, which uses NTFS:
ntfs-3g /dev/sdb1 /mnt/external
Next, create the image. I did this with the following (substitute your device/partition and output file):
dd if=/dev/hdc3 of=/mnt/external/diskImage/XPSP2.img bs=1024
When that finishes, the file specified with the ‘of’ option in dd will contain a block-by-block exact copy of your partition. However, it is in a raw format - we need it in a format VMWare can read. This is where Qemu comes in. Qemu is distributed with qemu-img, a tool used for creating, manipulating, and converting images. Specifically, our goal is to use qemu-img’s convert functionality to convert from a raw image format to the vmdk format. This is accomplished with:
qemu-img convert -f raw /mnt/external/diskImage/XPSP2.img -O vmdk /mnt/external/diskImage/XPSP2.vmdk
Be prepared to wait. For a 40gb image, this process took roughly 12 hours. Since qemu-img provides no status as to how far it has come, I kept tabs on it just by monitoring the filesize of the output image. This is entirely unnecessary, but if you want to do the same, just open a new terminal and type the following:
while [1 -gt 0 ]; do du -hs /mnt/external/diskImage/XPSP2.vmdk; sleep 10; clear; done
This will just print out the size of the file on your screen so you can watch it grow.
When the process is completed, boot back into Windows (or if you are using Linux as the host, stay put) and create a virtual machine around your new disk image. Don’t forget to remove the original img created with dd, it is a huge waste of disk space :)
[Notes]
In my last post I chronicled the time consuming process of converting an image produced using the Unix dd utility to a vmware VMDK virtual disk. The process does work, but VMWare will only load it if the image contains a master boot record that still contains the appropriate information when removed from the rest of the system. Additionally, I think it is appropriate to mention again how terribly slow it is. We can circumvent these problems with Live View for Windows, a program developed for forensic work by Carnegie Mellon University.
The process for creating the image with dd is the same as last time, IE, by doing something along the lines of:
dd if=/dev/hdc3 of=/mnt/external/diskImage/XPSP2.img bs=1024
Once that image is generated and you are back in Windows, simply launch the Live View utility and… the rest is pretty self explanatory. Once the dd image is generated, the Live View program takes only a couple minutes to create the new vmdk, configure the virtual machine, and launch it. Sweet, sweet efficiency!
This version adds support for third party image formats such as EnCase with the use of image mounting software such as Mount Image Pro or Physical Disk Emulator. This release also adds support for the newest versions of Java and VMware, improves the boot preparation process to allow a wider variety of system configurations to boot successfully, and fixes a number of bugs. For more information, see the changelog.
We appreciate the feedback and encourage you to continue to report bugs and make suggestions to help make this tool more useful for everyone. The best way to do this is to post to the forums.
Live View is a Java-based graphical forensics tool that creates a VMware virtual machine out of a raw (dd-style) disk image or physical disk. This allows the forensic examiner to "boot up" the image or disk and gain an interactive, user-level perspective of the environment, all without modifying the underlying image or disk. Because all changes made to the disk are written to a separate file, the examiner can instantly revert all of his or her changes back to the original pristine state of the disk. The end result is that one need not create extra "throw away" copies of the disk or image to create the virtual machine.
Live View is capable of booting
Containing the following operating systems
Behind the scenes, Live View automates a wide array of technical tasks. Some of these include: resolving hardware conflicts resulting from booting on hardware other than that on which the OS was originally installed; creating a customized MBR for partition-only images; and correctly specifying a virtual disk to match the original image or physical disk.
I recently wanted to shift to a UTF-8 locale, because I wanted to play with stuff like writing in Arabic, and because it seems to be the road forward.
So I switched and GNU Emacs starts to enter garbage in my buffers. I type “������ ��“, but Emacs gives me “æøå��� éí�“. Ever so slightly less useful, and less readable too.
I tried fiddling with “Options | Mule | Language Environments” and “Options | Mule | Set Coding System”, but to no avail.
Somewhat deluded I gave up and went back to Latin 1, mostly at least. Every once in a while I tried again, and one day I stumbled over a reference to the Emacs file etc/PROBLEMS, a section on problems with UTF-8 support in GNU Emacs. Unfortunately the section was gone from my copy, but I found it on the net.
The solution to all my problems: add the following lines to ~/.emacs:
(setq locale-coding-system 'utf-8)
(set-terminal-coding-system 'utf-8)
(set-keyboard-coding-system 'utf-8)
(set-selection-coding-system 'utf-8)
(prefer-coding-system 'utf-8)
The problem went away and haven’t been seen since.
BTW, I’m using GNU Emacs 21.3.1, installed from Debian testing and unstable (tried them both).
Tags: Linux
Take this small gtkmm application:
hello.cpp:
//--------------------------------------------------------
#ifdef USE_PCH
#include "precompiled.h"
#else
#include
#endif
int main(int argc, char* argv[])
{
Gtk::Main kit(argc, argv);
Gtk::Window window;
Gtk::Main::run(window);
return 0;
}
precompiled.h
//--------------------------------------------------------
#ifndef PRECOMPILED_H
#define PRECOMPILED_H
#include
#endif
The command to create the precompiled header was:
g++ -o precompiled.h.gch precompiled.h `pkg-config --cflags gtkmm-2.4`
The command to compile hello was:
time g++ -o hello hello.cpp `pkg-config --cflags --libs gtkmm-2.4` -DUSE_PCH
The results are below:
With PCH Normal
--------------------
0m1.172s 0m6.955s
0m1.168s 0m6.930s
0m1.173s 0m7.154s
-------- --------
0m1.171s 0m7.013s
The compilation was ~6 (six) times faster with precompiled headers!!!
Precompiled headers rulle!!!
Cheers,
Cristi.
Cristian Adam wrote:
OK - I'm seeing similar results now (even with more complex examples - about 4 times faster). I guess my problem was that the precompiled header should be named gtkmm.h.gch and not gtkmm.gch. However, I quickly stumbled across GCC bug 13675 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13675), which was rather easily worked around by using 2 include files like:The compilation was ~6 (six) times faster with precompiled headers!!!
Precompiled headers rulle!!!
A.h:and then precompiling B.h, while including A.h in my source files. So it seems that it's not quite ready for prime time yet, but I still think it'd be rather interesting to have a build target for gtkmm.h.pch in the standard gtkmm makefile.
#ifndef A_INCLUDED
#define A_INCLUDED
#include "B.h"
#endif
B.h:
#include
--
Christer Palm
and from
http://www.gtkmm.org/docs/gtkmm-2.4/docs/tutorial/html/sec-visual-studio-new-project.html
The next thing to alter is thestdafx.hprecompiled
header file. At the time of this writing, many Windows programmers are
familiar with the concept of precompiled headers. However, many Unix
programmers are not, as precompiled header support was only recently added
to GCC (in version 3.4) and is still not used in most open source projects.
Unix programmers may be tempted to just disable precompiled headers
altogether, but think carefully before doing this. Proper use of precompiled
headers provides a much improved compile time when using gtkmm, and will
save you many hours over the course of a project.
If a buffer is read-only, then you cannot change its contents, although you may change your view of the contents by scrolling and narrowing.
Read-only buffers are used in two kinds of situations:
Here, the purpose is to inform the user that editing the buffer with the aim of saving it in the file may be futile or undesirable. The user who wants to change the buffer text despite this can do so after clearing the read-only flag with C-x C-q.
nil.
u may be able to skip the dd command. Try this command:
qemu-img convert -f raw /dev/hdc3 -O vmdk boot.vmdk
I think this should work just fine. dd is just reading from the disk and qemu-img would not know the difference.
I tested on /dev/hda1 (/boot) and it worked just fine.
t
Further to my previous post - I think you may have stumbled on the single most simple way of converting the system from physical to virtual.
I think the following procedure would work, however I have not had time to test it.
on the machine to be converted (physical machine) nfs mount vmware host drive where you will be putting the virtual disks. Then run the qemu-img convertion from /dev/hda putting the output on the nfs mounted partition. This will be a one step conversion directly to the final location. It might be best to shut down as many processes as possible on the source host.
I’ll give this a go and report back.
http://www.robertpeaslee.com/index.php/raw-image-to-vmdk-the-easy-way/
If that doesn’t work, then… well, I have ideas, but they aren’t fun :) Let me know if LiveView works for you. Good luck mate!
1 March 2008, 5:07 pm