/l3/users/eb/2009/linux3/root :1 :2 :3 :4 :5 :6 :7 :8 :9 :10 :11 :12 :13 :14 :15 :16 :17 :18 :19 :20 :21 :22 :23 :24 :25 :26 :27 :28 :29 :30 :31 :32 :33 :34 :35 :36 :37 :38
[ править ]

Журнал лабораторных работ

Содержание

Журнал

Понедельник (06/01/09)

/dev/pts/6
09:53:08
#vgcreate --help 
  vgcreate: Create a volume group
vgcreate
        [-A|--autobackup {y|n}]
        [--addtag Tag]
        [--alloc AllocationPolicy]
        [-c|--clustered {y|n}]
        [-d|--debug]
        [-h|--help]
        [-l|--maxlogicalvolumes MaxLogicalVolumes]
        [-M|--metadatatype 1|2]
        [-p|--maxphysicalvolumes MaxPhysicalVolumes]
        [-s|--physicalextentsize PhysicalExtentSize[kKmMgGtTpPeE]]
        [-t|--test]
        [-v|--verbose]
        [--version]
        VolumeGroupName PhysicalVolume [PhysicalVolume...]
/dev/pts/5
09:53:08
#vgcreate --help
  vgcreate: Create a volume group
vgcreate
        [-A|--autobackup {y|n}]
        [--addtag Tag]
        [--alloc AllocationPolicy]
        [-c|--clustered {y|n}]
        [-d|--debug]
        [-h|--help]
        [-l|--maxlogicalvolumes MaxLogicalVolumes]
        [-M|--metadatatype 1|2]
        [-p|--maxphysicalvolumes MaxPhysicalVolumes]
        [-s|--physicalextentsize PhysicalExtentSize[kKmMgGtTpPeE]]
        [-t|--test]
        [-v|--verbose]
        [--version]
        VolumeGroupName PhysicalVolume [PhysicalVolume...]
/dev/pts/6
09:53:37
#vgcreate VG1 /dev/md0 
  Volume group "VG1" successfully created
/dev/pts/5
09:53:37
#vgcreate VG1 /dev/md0
  Volume group "VG1" successfully created
/dev/pts/6
09:54:16
#vgdisplay 
  --- Volume group ---
  VG Name               VG1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  1
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               9.31 GB
  PE Size               4.00 MB
  Total PE              2384
  Alloc PE / Size       0 / 0
  Free  PE / Size       2384 / 9.31 GB
  VG UUID               Phwjpa-RBzh-WyPH-r8wM-P4OD-tQ4f-6wgmj0
/dev/pts/5
09:54:16
#vgdisplay
  --- Volume group ---
  VG Name               VG1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  1
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                0
  Open LV               0
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               9.31 GB
  PE Size               4.00 MB
  Total PE              2384
  Alloc PE / Size       0 / 0
  Free  PE / Size       2384 / 9.31 GB
  VG UUID               Phwjpa-RBzh-WyPH-r8wM-P4OD-tQ4f-6wgmj0
/dev/pts/6
09:54:22
#lvcreate --help 
  lvcreate: Create a logical volume
lvcreate
        [-A|--autobackup {y|n}]
        [--addtag Tag]
        [--alloc AllocationPolicy]
        [-C|--contiguous {y|n}]
        [-d|--debug]
        [-h|-?|--help]
        [-i|--stripes Stripes [-I|--stripesize StripeSize]]
        {-l|--extents LogicalExtentsNumber |
...
        {-l|--extents LogicalExtentsNumber[%{VG|LV|PVS|FREE}] |
         -L|--size LogicalVolumeSize[kKmMgGtTpPeE]}
        [-M|--persistent {y|n}] [--major major] [--minor minor]
        [-n|--name LogicalVolumeName]
        [-p|--permission {r|rw}]
        [-r|--readahead ReadAheadSectors|auto|none]
        [-t|--test]
        [-v|--verbose]
        [--version]
        OriginalLogicalVolume[Path] [PhysicalVolumePath...]
/dev/pts/5
09:54:22
#lvcreate --help
  lvcreate: Create a logical volume
lvcreate
        [-A|--autobackup {y|n}]
        [--addtag Tag]
        [--alloc AllocationPolicy]
        [-C|--contiguous {y|n}]
        [-d|--debug]
        [-h|-?|--help]
        [-i|--stripes Stripes [-I|--stripesize StripeSize]]
        {-l|--extents LogicalExtentsNumber |
...
        {-l|--extents LogicalExtentsNumber[%{VG|LV|PVS|FREE}] |
         -L|--size LogicalVolumeSize[kKmMgGtTpPeE]}
        [-M|--persistent {y|n}] [--major major] [--minor minor]
        [-n|--name LogicalVolumeName]
        [-p|--permission {r|rw}]
        [-r|--readahead ReadAheadSectors|auto|none]
        [-t|--test]
        [-v|--verbose]
        [--version]
        OriginalLogicalVolume[Path] [PhysicalVolumePath...]
/dev/pts/6
09:54:41
#lvcreate -n vol1 /dev/VG1 
  Please specify either size or extents (not both)
  Run `lvcreate --help' for more information.
/dev/pts/5
09:54:41
#lvcreate -n vol1 /dev/VG1 
  Please specify either size or extents (not both)
  Run `lvcreate --help' for more information.
/dev/pts/6
09:58:31
#lvcreate -L 4G -n vol1 /dev/VG1 
  Logical volume "vol1" created
/dev/pts/5
09:58:31
#lvcreate -L 4G -n vol1 /dev/VG1
  Logical volume "vol1" created
/dev/pts/6
09:58:53
#lvdisplay 
  --- Logical volume ---
  LV Name                /dev/VG1/vol1
  VG Name                VG1
  LV UUID                3JCL6p-HRZ6-R0g9-W94J-NUWI-VYZB-Amfoul
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                4.00 GB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
/dev/pts/5
09:58:53
#lvdisplay
  --- Logical volume ---
  LV Name                /dev/VG1/vol1
  VG Name                VG1
  LV UUID                3JCL6p-HRZ6-R0g9-W94J-NUWI-VYZB-Amfoul
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                4.00 GB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0
/dev/pts/6
09:59:00
#lvs 
  LV   VG   Attr   LSize Origin Snap%  Move Log Copy%  Convert
  vol1 VG1  -wi-a- 4.00G
/dev/pts/5
09:59:00
#lvs
  LV   VG   Attr   LSize Origin Snap%  Move Log Copy%  Convert
  vol1 VG1  -wi-a- 4.00G
/dev/pts/6
09:59:12
#mkfs.ext3 /dev/VG1/vol1 
mke2fs 1.41.5 (23-Apr-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
262144 inodes, 1048576 blocks
52428 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1073741824
32 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
/dev/pts/5
09:59:12
#mkfs.ext3 /dev/VG1/vol1
mke2fs 1.41.5 (23-Apr-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
262144 inodes, 1048576 blocks
52428 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1073741824
32 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
/dev/pts/6
09:59:49
#mount /dev/VG1/vol1 /mnt 










/dev/pts/5
09:59:49




#mount /dev/VG1/vol1 /mnt












/dev/pts/6
10:00:07




#mount





tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/mapper/VG1-vol1 on /mnt type ext3 (rw)











/dev/pts/5
10:00:07




#mount


tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/mapper/VG1-vol1 on /mnt type ext3 (rw)











/dev/pts/6
10:00:10




#ls -l /mnt/





total 16
drwx------ 2 root root 16384 2009-06-01 09:59 lost+found











/dev/pts/5
10:00:10




#ls -l /mnt/


total 16
drwx------ 2 root root 16384 2009-06-01 09:59 lost+found











/dev/pts/6
10:00:18




#lvs





  LV   VG   Attr   LSize Origin Snap%  Move Log Copy%  Convert
  vol1 VG1  -wi-ao 4.00G











/dev/pts/5
10:00:18




#lvs


  LV   VG   Attr   LSize Origin Snap%  Move Log Copy%  Convert
  vol1 VG1  -wi-ao 4.00G











/dev/pts/6
10:01:20




#vgdisplay





  --- Volume group ---
  VG Name               VG1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               9.31 GB
  PE Size               4.00 MB
  Total PE              2384
  Alloc PE / Size       1024 / 4.00 GB
  Free  PE / Size       1360 / 5.31 GB
  VG UUID               Phwjpa-RBzh-WyPH-r8wM-P4OD-tQ4f-6wgmj0











/dev/pts/5
10:01:20




#vgdisplay


  --- Volume group ---
  VG Name               VG1
  System ID
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               9.31 GB
  PE Size               4.00 MB
  Total PE              2384
  Alloc PE / Size       1024 / 4.00 GB
  Free  PE / Size       1360 / 5.31 GB
  VG UUID               Phwjpa-RBzh-WyPH-r8wM-P4OD-tQ4f-6wgmj0











/dev/pts/6
10:02:05




#pvdisplay





  --- Physical volume ---
  PV Name               /dev/md0
  VG Name               VG1
  PV Size               9.31 GB / not usable 2.50 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              2384
  Free PE               1360
  Allocated PE          1024
  PV UUID               E1faHP-vz6x-9vbJ-hxHU-eOnP-zRdE-lTsNNN











/dev/pts/5
10:02:05




#pvdisplay


  --- Physical volume ---
  PV Name               /dev/md0
  VG Name               VG1
  PV Size               9.31 GB / not usable 2.50 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              2384
  Free PE               1360
  Allocated PE          1024
  PV UUID               E1faHP-vz6x-9vbJ-hxHU-eOnP-zRdE-lTsNNN











/dev/pts/6
10:02:16




#cat /proc/mdstat





Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/5
10:02:16




#cat /proc/mdstat


Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/6
10:02:34




#ьщÐmount





tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/mapper/VG1-vol1 on /mnt type ext3 (rw)











/dev/pts/5
10:02:34




#ьщÐmount


tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)
/dev/mapper/VG1-vol1 on /mnt type ext3 (rw)









прошло 24 минуты




/dev/pts/6
10:26:54




#mdadm --help





mdadm is used for building, managing, and monitoring
Linux md devices (aka RAID arrays)
Usage: mdadm --create device options...
            Create a new array from unused devices.
       mdadm --assemble device options...
            Assemble a previously created array.
       mdadm --build device options...
            Create or assemble an array without metadata.
       mdadm --manage device options...
            make changes to an existing array.
...
            Shorthand for --manage.
Any parameter that does not start with '-' is treated as a device name
or, for --examine-bitmap, a file name.
The first such name is often the name of an md device.  Subsequent
names are often names of component devices.
 For detailed help on the above major modes use --help after the mode
 e.g.
         mdadm --assemble --help
 For general help on options use
         mdadm --help-options











/dev/pts/5
10:26:54




#mdadm --help


mdadm is used for building, managing, and monitoring
Linux md devices (aka RAID arrays)
Usage: mdadm --create device options...
            Create a new array from unused devices.
       mdadm --assemble device options...
            Assemble a previously created array.
       mdadm --build device options...
            Create or assemble an array without metadata.
       mdadm --manage device options...
            make changes to an existing array.
...
            Shorthand for --manage.
Any parameter that does not start with '-' is treated as a device name
or, for --examine-bitmap, a file name.
The first such name is often the name of an md device.  Subsequent
names are often names of component devices.
 For detailed help on the above major modes use --help after the mode
 e.g.
         mdadm --assemble --help
 For general help on options use
         mdadm --help-options











/dev/pts/6
10:33:46




#mdadm --detail /dev/md0





/dev/md0:
        Version : 0.90
  Creation Time : Sat May 30 19:05:30 2009
     Raid Level : raid1
     Array Size : 9767424 (9.31 GiB 10.00 GB)
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent
    Update Time : Mon Jun  1 10:00:07 2009
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
           UUID : 4c837b29:665f67d3:3800bd94:de07ae80
         Events : 0.4
    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       22        1      active sync   /dev/sdb6











/dev/pts/5
10:33:46




#mdadm --detail /dev/md0


/dev/md0:
        Version : 0.90
  Creation Time : Sat May 30 19:05:30 2009
     Raid Level : raid1
     Array Size : 9767424 (9.31 GiB 10.00 GB)
  Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent
    Update Time : Mon Jun  1 10:00:07 2009
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
           UUID : 4c837b29:665f67d3:3800bd94:de07ae80
         Events : 0.4
    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8       22        1      active sync   /dev/sdb6











/dev/pts/6
10:35:02




#umount /mnt















/dev/pts/5
10:35:02




#umount /mnt












/dev/pts/6
10:39:13




#lvdisplay





  --- Logical volume ---
  LV Name                /dev/VG1/vol1
  VG Name                VG1
  LV UUID                3JCL6p-HRZ6-R0g9-W94J-NUWI-VYZB-Amfoul
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                4.00 GB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0











/dev/pts/5
10:39:13




#lvdisplay


  --- Logical volume ---
  LV Name                /dev/VG1/vol1
  VG Name                VG1
  LV UUID                3JCL6p-HRZ6-R0g9-W94J-NUWI-VYZB-Amfoul
  LV Write Access        read/write
  LV Status              available
  # open                 0
  LV Size                4.00 GB
  Current LE             1024
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0











/dev/pts/6
10:40:06




#pvdisplay





  --- Physical volume ---
  PV Name               /dev/md0
  VG Name               VG1
  PV Size               9.31 GB / not usable 2.50 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              2384
  Free PE               1360
  Allocated PE          1024
  PV UUID               E1faHP-vz6x-9vbJ-hxHU-eOnP-zRdE-lTsNNN











/dev/pts/5
10:40:06




#pvdisplay


  --- Physical volume ---
  PV Name               /dev/md0
  VG Name               VG1
  PV Size               9.31 GB / not usable 2.50 MB
  Allocatable           yes
  PE Size (KByte)       4096
  Total PE              2384
  Free PE               1360
  Allocated PE          1024
  PV UUID               E1faHP-vz6x-9vbJ-hxHU-eOnP-zRdE-lTsNNN











/dev/pts/6
10:45:57




#cat /proc/mdstat





Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/5
10:45:57




#cat /proc/mdstat


Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/6
10:46:09




#df -h /mnt





Filesystem            Size  Used Avail Use% Mounted on
rootfs                294G  2.0G  277G   1% /











/dev/pts/5
10:46:09




#df -h /mnt


Filesystem            Size  Used Avail Use% Mounted on
rootfs                294G  2.0G  277G   1% /











/dev/pts/6
10:46:42




#ls





1  hdddisk.img  mnt1  screen.dot  screen.png  t1.txt











/dev/pts/5
10:46:42




#ls


1  hdddisk.img  mnt1  screen.dot  screen.png  t1.txt











/dev/pts/6
10:46:52




#cp hdddisk.img /mnt/















/dev/pts/5
10:46:52




#cp hdddisk.img /mnt/












/dev/pts/6
10:47:07




#ls -l /mnt/





total 205004
-rw-r--r-- 1 root root 209715200 2009-06-01 10:47 hdddisk.img











/dev/pts/5
10:47:07




#ls -l /mnt/


total 205004
-rw-r--r-- 1 root root 209715200 2009-06-01 10:47 hdddisk.img











/dev/pts/6
10:48:06




#mdadm --manage --help





Usage: mdadm arraydevice options component devices...
This usage is for managing the component devices within an array.
The --manage option is not needed and is assumed if the first argument
is a device name or a management option.
The first device listed will be taken to be an md array device, and
subsequent devices are (potential) components of that array.
Options that are valid with management mode are:
  --add         -a   : hotadd subsequent devices to the array
  --remove      -r   : remove subsequent devices, which must not be active
  --fail        -f   : mark subsequent devices a faulty
  --set-faulty       : same as --fail
  --run         -R   : start a partially built array
  --stop        -S   : deactivate array, releasing all resources
  --readonly    -o   : mark array as readonly
  --readwrite   -w   : mark array as readwrite











/dev/pts/5
10:48:06




#mdadm --manage --help


Usage: mdadm arraydevice options component devices...
This usage is for managing the component devices within an array.
The --manage option is not needed and is assumed if the first argument
is a device name or a management option.
The first device listed will be taken to be an md array device, and
subsequent devices are (potential) components of that array.
Options that are valid with management mode are:
  --add         -a   : hotadd subsequent devices to the array
  --remove      -r   : remove subsequent devices, which must not be active
  --fail        -f   : mark subsequent devices a faulty
  --set-faulty       : same as --fail
  --run         -R   : start a partially built array
  --stop        -S   : deactivate array, releasing all resources
  --readonly    -o   : mark array as readonly
  --readwrite   -w   : mark array as readwrite











/dev/pts/6
10:48:23




#mdadm --manage /dev/md0 --fail /dev/sdb1





mdadm: set /dev/sdb1 faulty in /dev/md0











/dev/pts/5
10:48:23




#mdadm --manage /dev/md0 --fail /dev/sdb1


mdadm: set /dev/sdb1 faulty in /dev/md0











/dev/pts/6
10:50:09




#mdadm --manage /dev/md0 --remove /dev/sdb1





mdadm: hot removed /dev/sdb1











/dev/pts/5
10:50:09




#mdadm --manage /dev/md0 --remove /dev/sdb1


mdadm: hot removed /dev/sdb1











/dev/pts/6
10:50:37




#mdadm --manage /dev/md0 --add /dev/sdb1





mdadm: re-added /dev/sdb1











/dev/pts/5
10:50:37




#mdadm --manage /dev/md0 --add /dev/sdb1


mdadm: re-added /dev/sdb1











/dev/pts/6
10:51:45




#watch cat /proc/mdstat















/dev/pts/5
10:51:45




#watch cat /proc/mdstat












/dev/pts/6
10:59:35




#mount





tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)











/dev/pts/5
10:59:35




#mount


tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
rootfs on / type rootfs (rw)











/dev/pts/6
10:59:51




#mkfs.ext3 /dev/md1





mke2fs 1.41.5 (23-Apr-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
612000 inodes, 2443872 blocks
122193 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2503999488
75 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 30 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.











/dev/pts/5
10:59:51




#mkfs.ext3 /dev/md1


mke2fs 1.41.5 (23-Apr-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
612000 inodes, 2443872 blocks
122193 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2503999488
75 block groups
32768 blocks per group, 32768 fragments per group
8160 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 30 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.











/dev/pts/6
11:00:19




#cat /proc/mdstat





Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sdb2[0]
      9775488 blocks [2/1] [U_]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/5
11:00:19




#cat /proc/mdstat


Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sdb2[0]
      9775488 blocks [2/1] [U_]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>











/dev/pts/6
11:00:29




#mount /dev/md1 /mnt















/dev/pts/5
11:00:29




#mount /dev/md1 /mnt












11:01:16




#rsync -av --exclude={\/proc,\/sys,\/dev} /* /mnt/





etc/sgml/xml-core.cat
etc/sgml/docbook-xml/
etc/sgml/docbook-xml/4.0/
etc/sgml/docbook-xml/4.0/dbgenent.ent
etc/sgml/docbook-xml/4.1.2/
etc/sgml/docbook-xml/4.1.2/dbgenent.mod
etc/sgml/docbook-xml/4.2/
etc/sgml/docbook-xml/4.2/dbgenent.mod
etc/sgml/docbook-xml/4.3/
etc/sgml/docbook-xml/4.3/dbgenent.mod
...
etc/ssl/certs/DST_Root_CA_X3.pem -> /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt
etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt
etc/ssl/certs/DigiCert_Global_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt
etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_1.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_1.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_2.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_2.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_3.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_3.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_4.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_4.crt
etc/ssl/certs/Entrust.net_Global_Secure_Personal_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Personal_CA.crt
etc/ssl/certs/Entrust.net_Global_Secure_Server_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Server_CA.crt











/dev/pts/6
11:01:16




#rsync -av --exclude={\/proc,\/sys,\/dev} /* /mnt/





etc/sgml/xml-core.cat
etc/sgml/docbook-xml/
etc/sgml/docbook-xml/4.0/
etc/sgml/docbook-xml/4.0/dbgenent.ent
etc/sgml/docbook-xml/4.1.2/
etc/sgml/docbook-xml/4.1.2/dbgenent.mod
etc/sgml/docbook-xml/4.2/
etc/sgml/docbook-xml/4.2/dbgenent.mod
etc/sgml/docbook-xml/4.3/
etc/sgml/docbook-xml/4.3/dbgenent.mod
...
etc/ssl/certs/DST_Root_CA_X3.pem -> /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt
etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt
etc/ssl/certs/DigiCert_Global_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt
etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_1.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_1.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_2.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_2.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_3.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_3.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_4.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_4.crt
etc/ssl/certs/Entrust.net_Global_Secure_Personal_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Personal_CA.crt
etc/ssl/certs/Entrust.net_Global_Secure_Server_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Server_CA.crt











11:11:12




#rm /mnt/*





rm: cannot remove `/mnt/bin': Is a directory
rm: cannot remove `/mnt/boot': Is a directory
rm: cannot remove `/mnt/etc': Is a directory
rm: cannot remove `/mnt/home': Is a directory
rm: cannot remove `/mnt/lib': Is a directory
rm: cannot remove `/mnt/lost+found': Is a directory
rm: cannot remove `/mnt/media': Is a directory
rm: cannot remove `/mnt/mnt': Is a directory
rm: cannot remove `/mnt/opt': Is a directory
rm: cannot remove `/mnt/root': Is a directory
rm: cannot remove `/mnt/sbin': Is a directory
rm: cannot remove `/mnt/selinux': Is a directory
rm: cannot remove `/mnt/srv': Is a directory
rm: cannot remove `/mnt/tmp': Is a directory
rm: cannot remove `/mnt/usr': Is a directory
rm: cannot remove `/mnt/var': Is a directory











/dev/pts/5
11:11:12




#rm /mnt/*





rm: cannot remove `/mnt/bin': Is a directory
rm: cannot remove `/mnt/boot': Is a directory
rm: cannot remove `/mnt/etc': Is a directory
rm: cannot remove `/mnt/home': Is a directory
rm: cannot remove `/mnt/lib': Is a directory
rm: cannot remove `/mnt/lost+found': Is a directory
rm: cannot remove `/mnt/media': Is a directory
rm: cannot remove `/mnt/mnt': Is a directory
rm: cannot remove `/mnt/opt': Is a directory
rm: cannot remove `/mnt/root': Is a directory
rm: cannot remove `/mnt/sbin': Is a directory
rm: cannot remove `/mnt/selinux': Is a directory
rm: cannot remove `/mnt/srv': Is a directory
rm: cannot remove `/mnt/tmp': Is a directory
rm: cannot remove `/mnt/usr': Is a directory
rm: cannot remove `/mnt/var': Is a directory











/dev/pts/6
11:11:42




#rm -rf /mnt/*















/dev/pts/5
11:11:42




#rm -rf /mnt/*












11:12:03




#rsync -av --exclude={\/proc,\/sys,\/dev,\/mnt} /* /mnt/





etc/sgml/xml-core.cat
etc/sgml/docbook-xml/
etc/sgml/docbook-xml/4.0/
etc/sgml/docbook-xml/4.0/dbgenent.ent
etc/sgml/docbook-xml/4.1.2/
etc/sgml/docbook-xml/4.1.2/dbgenent.mod
etc/sgml/docbook-xml/4.2/
etc/sgml/docbook-xml/4.2/dbgenent.mod
etc/sgml/docbook-xml/4.3/
etc/sgml/docbook-xml/4.3/dbgenent.mod
...
etc/ssl/certs/DST_Root_CA_X3.pem -> /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt
etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt
etc/ssl/certs/DigiCert_Global_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt
etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_1.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_1.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_2.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_2.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_3.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_3.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_4.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_4.crt
etc/ssl/certs/Entrust.net_Global_Secure_Personal_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Personal_CA.crt
etc/ssl/certs/Entrust.net_Global_Secure_Server_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Server_CA.crt











/dev/pts/6
11:12:03




#rsync -av --exclude={\/proc,\/sys,\/dev,\/mnt} /* /mnt/


etc/sgml/xml-core.cat
etc/sgml/docbook-xml/
etc/sgml/docbook-xml/4.0/
etc/sgml/docbook-xml/4.0/dbgenent.ent
etc/sgml/docbook-xml/4.1.2/
etc/sgml/docbook-xml/4.1.2/dbgenent.mod
etc/sgml/docbook-xml/4.2/
etc/sgml/docbook-xml/4.2/dbgenent.mod
etc/sgml/docbook-xml/4.3/
etc/sgml/docbook-xml/4.3/dbgenent.mod
...
etc/ssl/certs/DST_Root_CA_X3.pem -> /usr/share/ca-certificates/mozilla/DST_Root_CA_X3.crt
etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt
etc/ssl/certs/DigiCert_Global_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt
etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem -> /usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_1.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_1.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_2.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_2.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_3.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_3.crt
etc/ssl/certs/Digital_Signature_Trust_Co._Global_CA_4.pem -> /usr/share/ca-certificates/mozilla/Digital_Signature_Trust_Co._Global_CA_4.crt
etc/ssl/certs/Entrust.net_Global_Secure_Personal_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Personal_CA.crt
etc/ssl/certs/Entrust.net_Global_Secure_Server_CA.pem -> /usr/share/ca-certificates/mozilla/Entrust.net_Global_Secure_Server_CA.crt











11:16:17




#grub-install --help





Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
  -h, --help              print this message and exit
  -v, --version           print the version information and exit
  --root-directory=DIR    install GRUB images under the directory DIR
                          instead of the root directory
  --grub-shell=FILE       use FILE as the grub shell
  --no-floppy             do not probe any floppy drive
  --force-lba             force GRUB to use LBA mode even for a buggy
                          BIOS
  --recheck               probe a device map even if it already exists
INSTALL_DEVICE can be a GRUB device name or a system device filename.
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Report bugs to <bug-grub@gnu.org>.











/dev/pts/5
11:16:17




#grub-install --help


Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
  -h, --help              print this message and exit
  -v, --version           print the version information and exit
  --root-directory=DIR    install GRUB images under the directory DIR
                          instead of the root directory
  --grub-shell=FILE       use FILE as the grub shell
  --no-floppy             do not probe any floppy drive
  --force-lba             force GRUB to use LBA mode even for a buggy
                          BIOS
  --recheck               probe a device map even if it already exists
INSTALL_DEVICE can be a GRUB device name or a system device filename.
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Report bugs to <bug-grub@gnu.org>.











/dev/pts/6
11:17:11




#grub-install --no-floppy --root-directory /mnt/boot/grub /dev/md1





Unrecognized option `--root-directory'
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
  -h, --help              print this message and exit
  -v, --version           print the version information and exit
  --root-directory=DIR    install GRUB images under the directory DIR
                          instead of the root directory
  --grub-shell=FILE       use FILE as the grub shell
  --no-floppy             do not probe any floppy drive
  --force-lba             force GRUB to use LBA mode even for a buggy
                          BIOS
  --recheck               probe a device map even if it already exists
INSTALL_DEVICE can be a GRUB device name or a system device filename.
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Report bugs to <bug-grub@gnu.org>.











/dev/pts/5
11:17:11




#grub-install --no-floppy --root-directory /mnt/boot/grub /dev/md1





Unrecognized option `--root-directory'
Usage: grub-install [OPTION] install_device
Install GRUB on your drive.
  -h, --help              print this message and exit
  -v, --version           print the version information and exit
  --root-directory=DIR    install GRUB images under the directory DIR
                          instead of the root directory
  --grub-shell=FILE       use FILE as the grub shell
  --no-floppy             do not probe any floppy drive
  --force-lba             force GRUB to use LBA mode even for a buggy
                          BIOS
  --recheck               probe a device map even if it already exists
INSTALL_DEVICE can be a GRUB device name or a system device filename.
grub-install copies GRUB images into the DIR/boot directory specfied by
--root-directory, and uses the grub shell to install grub into the boot
sector.
Report bugs to <bug-grub@gnu.org>.











/dev/pts/6
11:18:44




#grub-install --no-floppy --root-directory=/mnt/boot /dev/md1





The file /mnt/boot/boot/grub/stage2 not read correctly.











/dev/pts/5
11:18:44




#grub-install --no-floppy --root-directory=/mnt/boot /dev/md1





The file /mnt/boot/boot/grub/stage2 not read correctly.











/dev/pts/6
11:19:36




#grub-install --no-floppy --root-directory=/mnt /dev/md1





Installation finished. No error reported.
This is the contents of the device map /mnt/boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
(hd0)   /dev/loop0
(hd1)   /dev/sdb
(hd2)   /dev/sdc











/dev/pts/5
11:19:36




#grub-install --no-floppy --root-directory=/mnt /dev/md1


Installation finished. No error reported.
This is the contents of the device map /mnt/boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
(hd0)   /dev/loop0
(hd1)   /dev/sdb
(hd2)   /dev/sdc











/dev/pts/6
11:20:02




#qemu /dev/md1





Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory
commandline read: qemu
commandline read: /dev/md1
   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.7 |~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2008  The world wide DirectFB Open Source Community
        (c) 2000-2004  Convergence (integrated media) GmbH
      ----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2009-03-09 17:25)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
    --> Initialization error!
Could not initialize SDL - exiting











/dev/pts/5
11:20:02




#qemu /dev/md1





Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory
commandline read: qemu
commandline read: /dev/md1
   ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.2.7 |~~~~~~~~~~~~~~~~~~~~~~~~~~
        (c) 2001-2008  The world wide DirectFB Open Source Community
        (c) 2000-2004  Convergence (integrated media) GmbH
      ----------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2009-03-09 17:25)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
    --> No such file or directory
(!) DirectFB/FBDev: Error opening framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not initialize 'system_core' core!
    --> Initialization error!
Could not initialize SDL - exiting











/dev/pts/6
11:20:24




#echo 3 /proc/





Display all 153 possibilities? (y or n)











/dev/pts/5
11:20:24




#echo 3 /proc/





Display all 153 possibilities? (y or n)











/dev/pts/6
11:20:24




#echo 3 > /proc/sys/vm/drop_caches















/dev/pts/5
11:20:24




#echo 3 > /proc/sys/vm/drop_caches












/dev/pts/9
11:23:38




#qemu /dev/md1


Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory











11:24:01




#qemu -hda /dev/md1


Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory











11:24:33




#file -s /dev/sda


/dev/sda: x86 boot sector; GRand Unified Bootloader, stage1 version 0x3, stage2 address 0x2000, stage2 segment 0x200; partition 1: ID=0x83, active, starthead 1, startsector 63, 625137282 sectors, code offset 0x48, OEM-ID "      м", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, head











11:24:47




#grub-install --no-floppy --root-directory=/mnt /dev/md1


Installation finished. No error reported.
This is the contents of the device map /mnt/boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.
(hd0)   /dev/loop0
(hd1)   /dev/sdb
(hd2)   /dev/sdc











/dev/pts/6
11:26:37




#mkdir /mnt/proc















/dev/pts/5
11:26:37




#mkdir /mnt/proc












/dev/pts/6
11:26:54




#mkdir /mnt/sys










Файлы
  • /proc/mdstat
    • /proc/mdstat
    

    >
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sdb2[0]
      9775488 blocks [2/1] [U_]
md0 : active raid1 sdb1[0] sdb6[1]
      9767424 blocks [2/2] [UU]
unused devices: <none>

    Статистика
    Время первой команды журнала09:53:08 2009- 6- 1
    Время последней команды журнала11:26:54 2009- 6- 1
    Количество командных строк в журнале101
    Процент команд с ненулевым кодом завершения, %13.86
    Процент синтаксически неверно набранных команд, % 0.00
    Суммарное время работы с терминалом *, час 1.56
    Количество командных строк в единицу времени, команда/мин 1.08
    Частота использования команд
    mdadm12|===========| 11.65%
    grub-install9|========|  8.74%
    mount8|=======|  7.77%
    cat6|=====|  5.83%
    ls6|=====|  5.83%
    lvcreate6|=====|  5.83%
    qemu4|===|  3.88%
    vgcreate4|===|  3.88%
    mkfs.ext34|===|  3.88%
    pvdisplay4|===|  3.88%
    rm4|===|  3.88%
    echo4|===|  3.88%
    lvdisplay4|===|  3.88%
    rsync4|===|  3.88%
    lvs4|===|  3.88%
    vgdisplay4|===|  3.88%
    mkdir3|==|  2.91%
    umount2|=|  1.94%
    cp2|=|  1.94%
    ьщÐmount2|=|  1.94%
    drop_caches2|=|  1.94%
    watch2|=|  1.94%
    df2|=|  1.94%
    file1||  0.97%
    ____
    *) Интервалы неактивности длительностью 30 минут и более не учитываются
    Справка
        Для того чтобы использовать LiLaLo, не нужно знать ничего особенного:
    всё происходит само собой.
    Однако, чтобы ведение и последующее использование журналов
    было как можно более эффективным, желательно иметь в виду следующее:
    
      
    
    1.  
    В журнал автоматически попадают все команды, данные в любом терминале системы.
    
      2. 
    
    2. 
    Для того чтобы убедиться, что журнал на текущем терминале ведётся, 
    и команды записываются, дайте команду w.
    В поле WHAT, соответствующем текущему терминалу, 
    должна быть указана программа script.
    
      3. 
    
    3. 
    Команды, при наборе которых были допущены синтаксические ошибки, 
    выводятся перечёркнутым текстом:

      

      


      $ l s-l
      

      bash: l: command not found

      
      		

      

      

      
    
      4. 
    
    4. 
    Если код завершения команды равен нулю, 
    команда была выполнена без ошибок.
    Команды, код завершения которых отличен от нуля, выделяются цветом.

      

      


      $ test 5 -lt 4
      

      		

      

      
    Обратите внимание на то, что код завершения команды может быть отличен от нуля
    не только в тех случаях, когда команда была выполнена с ошибкой.
    Многие команды используют код завершения, например, для того чтобы показать результаты проверки

      
    
      5. 
    
    5. 
    Команды, ход выполнения которых был прерван пользователем, выделяются цветом.

      

      


      $ find / -name abc
      

      find: /home/devi-orig/.gnome2: Keine Berechtigung
find: /home/devi-orig/.gnome2_private: Keine Berechtigung
find: /home/devi-orig/.nautilus/metafiles: Keine Berechtigung
find: /home/devi-orig/.metacity: Keine Berechtigung
find: /home/devi-orig/.inkscape: Keine Berechtigung
^C

      
      		

      

      

      
    
      6. 
    
    6. 
    Команды, выполненные с привилегиями суперпользователя,
    выделяются слева красной чертой.

      

      


      # id
      

      uid=0(root) gid=0(root) Gruppen=0(root)

      
      		

      

      
    
      
    
      7. 
    
    7. 
    Изменения, внесённые в текстовый файл с помощью редактора, 
    запоминаются и показываются в журнале в формате ed.
    Строки, начинающиеся символом "<", удалены, а строки,
    начинающиеся символом ">" -- добавлены.

      

      


      $ vi ~/.bashrc
      

      2a3,5
>    if [ -f /usr/local/etc/bash_completion ]; then
>         . /usr/local/etc/bash_completion
>        fi

      		

      

      
    
      
    
      8. 
    
    8. 
    Для того чтобы изменить файл в соответствии с показанными в диффшоте
    изменениями, можно воспользоваться командой patch.
    Нужно скопировать изменения, запустить программу patch, указав в
    качестве её аргумента файл, к которому применяются изменения,
    и всавить скопированный текст:

      

      


      $ patch ~/.bashrc
      
      		

      

      
    В данном случае изменения применяются к файлу ~/.bashrc
    
      9. 
    
    9. 
    Для того чтобы получить краткую справочную информацию о команде, 
    нужно подвести к ней мышь. Во всплывающей подсказке появится краткое
    описание команды.
    
      
    
      
    Если справочная информация о команде есть, 
    команда выделяется голубым фоном, например: vi.
    Если справочная информация отсутствует,
    команда выделяется розовым фоном, например: notepad.exe.
    Справочная информация может отсутствовать в том случае, 
    если (1) команда введена неверно; (2) если распознавание команды LiLaLo выполнено неверно;
    (3) если информация о команде неизвестна LiLaLo.
    Последнее возможно для редких команд.
    
      10. 
    
    10. 
    Большие, в особенности многострочные, всплывающие подсказки лучше 
    всего показываются браузерами KDE Konqueror, Apple Safari и Microsoft Internet Explorer.
    В браузерах Mozilla и Firefox они отображаются не полностью, 
    а вместо перевода строки выводится специальный символ.
    
      11. 
    
    11. 
    Время ввода команды, показанное в журнале, соответствует времени 
    начала ввода командной строки, которое равно тому моменту, 
    когда на терминале появилось приглашение интерпретатора
    
      12. 
    
    12. 
    Имя терминала, на котором была введена команда, показано в специальном блоке.
    Этот блок показывается только в том случае, если терминал
    текущей команды отличается от терминала предыдущей.
    
      13. 
    
    13. 
    Вывод не интересующих вас в настоящий момент элементов журнала,
    таких как время, имя терминала и других, можно отключить.
    Для этого нужно воспользоваться формой управления журналом
    вверху страницы.
    
      14. 
    
    14. 
    Небольшие комментарии к командам можно вставлять прямо из командной строки.
    Комментарий вводится прямо в командную строку, после символов #^ или #v.
    Символы ^ и v показывают направление выбора команды, к которой относится комментарий:
    ^ - к предыдущей, v - к следующей.
    Например, если в командной строке было введено:

      $ whoami

      

      user

      

      $ #^ Интересно, кто я?

      
    в журнале это будет выглядеть так:
    

      $ whoami

      

      user

      

      

        Интересно, кто я?
       
       
    
      15. 
    
    15. 
    Если комментарий содержит несколько строк,
    его можно вставить в журнал следующим образом:

      $ whoami

      

      user

      

      $ cat > /dev/null #^ Интересно, кто я?

      

      Программа whoami выводит имя пользователя, под которым 
мы зарегистрировались в системе.
-
Она не может ответить на вопрос о нашем назначении 
в этом мире.

      
    В журнале это будет выглядеть так:

      

      


      $ whoami
      

      user

      

      Интересно, кто я?
      
Программа whoami выводит имя пользователя, под которым
      
мы зарегистрировались в системе.
      

      
Она не может ответить на вопрос о нашем назначении
      
в этом мире.
      

      
      		

      

      
    Для разделения нескольких абзацев между собой
    используйте символ "-", один в строке.
    
      

      16. 
    
    16. 
    Комментарии, не относящиеся непосредственно ни к какой из команд, 
    добавляются точно таким же способом, только вместо симолов #^ или #v 
    нужно использовать символы #=
    
      17. 

    
    17. 
    Содержимое файла может быть показано в журнале.
    Для этого его нужно вывести с помощью программы cat.
    Если вывод команды отметить симоволами #!, 
    содержимое файла будет показано в журнале
    в специально отведённой для этого секции.
    
      18. 

    
      
    
    18. 
    Для того чтобы вставить скриншот интересующего вас окна в журнал,
    нужно воспользоваться командой l3shot.
    После того как команда вызвана, нужно с помощью мыши выбрать окно, которое
    должно быть в журнале.
    
      19. 
    
      

    
      
    
    19. 
    Команды в журнале расположены в хронологическом порядке.
    Если две команды давались одна за другой, но на разных терминалах,
    в журнале они будут рядом, даже если они не имеют друг к другу никакого отношения.

      1
    2
3   
    4

      
    Группы команд, выполненных на разных терминалах, разделяются специальной линией.
    Под этой линией в правом углу показано имя терминала, на котором выполнялись команды.
    Для того чтобы посмотреть команды только одного сенса, 
    нужно щёкнуть по этому названию.
    
      20. 
    
      

    

    О программе
        
    
    LiLaLo (L3) расшифровывается как Live Lab Log.
    
    Программа разработана для повышения эффективности обучения Unix/Linux-системам.
    
    (c) Игорь Чубин, 2004-2008
    
    
    
$Id$