Sep
15
2008
0

Generating Patches for Linux Sources

gendiff is better or diff -uNrp

Share
Written by in: development,linux | Tweet This
Sep
15
2008
0

USB TV BOX

Just got a noname MODEL:USB2.OBOX (or 0BOX?) and attached to my D630 running EL5U2 (i386).. Attaching gives
Jul 30 13:19:55 localhost kernel: usb 2-1: new high speed USB device using ehci_hcd and address 7
Jul 30 13:19:55 localhost kernel: usb 2-1: configuration #1 chosen from 1 choice

in messages and got a brand new

Bus 002 Device 007: ID 6000:0001

from lsusb. Got some hopeless response from ubuntuforums and tv-cards. Still proceeding…

$ lsusb -d 6000:0001 -v

Bus 002 Device 007: ID 6000:0001
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x6000
idProduct 0x0001
bcdDevice 0.01
iManufacturer 16
iProduct 32
iSerial 64
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 78
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 48
bmAttributes 0x80
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x1400 3x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
can’t get device qualifier: Operation not permitted
can’t get debug descriptor: Operation not permitted

this is not much helpful (yet)..

The

idVendor 0x6000
idProduct 0x0001
bcdDevice 0.01
iManufacturer 16
iProduct 32
iSerial 64

tells
me that this is actually some common chip / device. Still I doubt a
generic driver to be around. Shall check with Fedora 9 too.

Now testing via VMWare workstation on XP .. Just to be sure that the device is working..

–>
And VMWare installation fails with a blue screen .. Maybe it is vmware
or worse it is the device itself .. I shall test this on a native
environment .. Maybe that Toshiba Satellite notebook.. Hmm..

Tuesday, July 29, 2008


A basic LVM Setup

# fdisk -l

Disk /dev/hda: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 522 4088542+ 8e Linux LVM

Disk /dev/hdb: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 522 4192933+ 83 Linux

# pvcreate /dev/hdb1
Physical volume “/dev/hdb1” successfully created
# vgcreate vg1 /dev/hdb1
Volume group “vg1” successfully created

# lvcreate –size 1G vg1
Logical volume “lvol0” created
# ls -l /dev/vg1/lvol0
lrwxrwxrwx 1 root root 21 Jul 29 20:27 /dev/vg1/lvol0 -> /dev/mapper/vg1-lvol0
# mkfs.ext3 /dev/vg1/lvol0
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
131072 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

# mount /dev/vg1/lvol0 /mnt
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2967320 860884 1955704 31% /
/dev/hda1 101086 10199 85668 11% /boot
none 254472 0 254472 0% /dev/shm
/dev/mapper/vg1-lvol0
1032088 34092 945568 4% /mnt

Share
Sep
15
2008
0

A basic LVM Setup

# fdisk -l

Disk /dev/hda: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 522 4088542+ 8e Linux LVM

Disk /dev/hdb: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 522 4192933+ 83 Linux

# pvcreate /dev/hdb1
Physical volume “/dev/hdb1” successfully created
# vgcreate vg1 /dev/hdb1
Volume group “vg1” successfully created

# lvcreate –size 1G vg1
Logical volume “lvol0” created
# ls -l /dev/vg1/lvol0
lrwxrwxrwx 1 root root 21 Jul 29 20:27 /dev/vg1/lvol0 -> /dev/mapper/vg1-lvol0
# mkfs.ext3 /dev/vg1/lvol0
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
131072 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=268435456
8 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.

# mount /dev/vg1/lvol0 /mnt
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
2967320 860884 1955704 31% /
/dev/hda1 101086 10199 85668 11% /boot
none 254472 0 254472 0% /dev/shm
/dev/mapper/vg1-lvol0
1032088 34092 945568 4% /mnt

Share
Written by in: linux,storage,sysadm | Tweet This
Sep
15
2008
0

Accessing NTFS Partitions from Linux

This is basically done by two methods:
– The NTFS kernel module
– The NTFS user space programs
from the kernel source or http://www.linux-ntfs.org/

The NTFS Kernel Module
Have a check at the wiki page

You
might find an appropriate prebuilt driver for your current kernel
version. Then you can do normal mounts etc on NTFS partitions. One
problem here is that if you upgrade your kernel, you’ll need to have a
new kernel module. Or eventually build from source.

Alternatively
with 2.6 kernels there is the NTFS support. But with enterprise distros
(like OEL or RHEL) that support is not compiled in and rebuilt kernels
are not supported.

The NTFS Userspace Programs

That is the kernel-version-free solution and it is quite effective. One can get the source from Linux-NTFS Download or more precisely the 2.0.0 version here.

This is the option that I prefer…

Note
that there is an option to have ntfsmount too (–enable-ntfsmount) ..
But that requires FUSE support where enterprise distros generally
discard / disable FUSE support due to security reasons.

# tar jxvf ntfsprogs-2.0.0.tar.bz2
ntfsprogs-2.0.0/
ntfsprogs-2.0.0/doc/
ntfsprogs-2.0.0/doc/attributes.txt
ntfsprogs-2.0.0/doc/CodingStyle

ntfsprogs-2.0.0/COPYING
ntfsprogs-2.0.0/TODO.ntfsprogs
ntfsprogs-2.0.0/CREDITS
ntfsprogs-2.0.0/ntfsprogs.spec
# cd ntfsprogs-2.0.0
# ./configure
checking build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking target system type… i686-pc-linux-gnu

config.status: config.h is unchanged
config.status: executing depfiles commands
# make && make install
make all-recursive
make[1]: Entering directory `/home/oyuksel/projects/ntfsprogs-2.0.0′

make[2]: Leaving directory `/home/oyuksel/projects/ntfsprogs-2.0.0′
make[1]: Leaving directory `/home/oyuksel/projects/ntfsprogs-2.0.0′
# export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
# ntfsls -l /dev/sdb2
0 May 31 15:23 2008 data
0 Feb 12 15:59 2007 data1
0 Feb 12 15:59 2007 data2
0 Mar 30 15:43 2007 muzik
0 Feb 13 15:21 2007 MyVM
0 Feb 13 15:59 2007 RECYCLER
0 Feb 4 23:14 2007 System Volume Information
42004 Jul 28 16:13 2008 testfile
# ntfscat /dev/sdb2 testfile > testfile
# ls -l testfile
-rw-r–r– 1 root root 42004 Jul 28 16:15 testfile

For more information see Linux-NTFS Wiki

Share
Written by in: linux,storage,sysadm | Tweet This
Sep
15
2008
0

Linux DVD9 to DVD5

Found and used dvd95 and that works quite nice with gnome – also with kde .. But has problems with some dvds..
Testing k9copy. That is exclusively for KDE .. But EL and fedora does it nicely along.

Has
tested k9copy .. That is nice too .. But did not solve the some-dvd
issues .. It seems now I have managed to get dvd95 right along with
fedora 9 .

Share

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com