chroot (minimalistic) best practice

There are several mount points you have to retain over chroot-ing Linux root partition, namely dev (device descriptors), proc (processes), and sys (mainly the kernel control identifiers). If you do not, silly thing happens.

So, here's mostly you have to do to chroot:
mkdir /mnt 
mount /dev/sda1 /mnt 
cd /mnt 
mount -t proc proc proc/ 
mount -t sysfs sys sys/ 
mount -o bind /dev dev/ 
chroot /mnt /bin/bash 

Having just a shell in the chroot-ed environment is sometimes a nice idea, you could just exit to return to earlier environment.

pts: 0000000000000000

I've got a (virtual) server running Slackware on (physical) server running Centos.

In my ssh session (in Slackware box), just to check whether the files I downloaded last night have been finished, I do ps ax | grep wget,  and violaa:
ayu@slackware-cluster:~$ ps as | grep wget 
1001 18715 0000000000000000 0000000000000000 0000000000000000 0000000000000000 S+ pts/1 0:00 grep wget 
ayu@slackware-cluster:~$ ps as | grep wget 
1001 18717 0000000000000000 0000000000000000 0000000000000000 0000000000000000 R+ pts/1 0:00 grep wget 
ayu@slackware-cluster:~$ ps as | grep wget 
1001 18719 0000000000000000 0000000000000000 0000000000000000 0000000000000000 S+ pts/1 0:00 grep wget 

I screwed the pts? Obviously, this guy here had the same glitch. The system ran just fine afterwards (no silly 0s), it was just fun to watch some erroneous output. :D

Mother in law

Dear, can I have your mom as mine--I need an extra mother?

--something isn't quite right with me