FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 06-12-2011, 04:55 AM
 
Default Huawei e122 - how to make symlink to usb modem?

I have e122 modem. I would have symlink to /dev/ttyUSBX. (modem device)
But simple rule:

--8<---------------cut here---------------start------------->8---
SUBSYSTEM=="tty",ATTRS{idVendor} == "12d1" , ATTRS{idProduct} == "1003", SYMLINK+="e122"
--8<---------------cut here---------------end--------------->8---

does not work.
WWhen I get rid of 'SUBSYSTEM=="tty"' symlink is created, but points to
sdX device.

Any ideas?
KJ

--
http://blogdebart.pl/2010/03/17/dalsze-przygody-swinki-w-new-jersey/
Jak ktoś ma pecha, to złamie ząb podczas seksu oralnego (S.Sokół)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87pqmjsl66.fsf@alfa.kjonca">http://lists.debian.org/87pqmjsl66.fsf@alfa.kjonca
 
Old 06-12-2011, 11:38 AM
Camaleón
 
Default Huawei e122 - how to make symlink to usb modem?

On Sun, 12 Jun 2011 06:55:45 +0200, Kamil Jońca wrote:

> I have e122 modem. I would have symlink to /dev/ttyUSBX. (modem device)
> But simple rule:
>
> --8<---------------cut here---------------start------------->8---
> SUBSYSTEM=="tty",ATTRS{idVendor} == "12d1" , ATTRS{idProduct} == "1003", SYMLINK+="e122"
> --8<---------------cut here---------------end--------------->8---
>
> does not work.
> WWhen I get rid of 'SUBSYSTEM=="tty"' symlink is created, but points to
> sdX device.
>
> Any ideas?

What's the output for udevinfo on that device?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.12.11.38.35@gmail.com">http://lists.debian.org/pan.2011.06.12.11.38.35@gmail.com
 
Old 06-12-2011, 11:38 AM
Camaleón
 
Default Huawei e122 - how to make symlink to usb modem?

On Sun, 12 Jun 2011 06:55:45 +0200, Kamil Jońca wrote:

> I have e122 modem. I would have symlink to /dev/ttyUSBX. (modem device)
> But simple rule:
>
> --8<---------------cut here---------------start------------->8---
> SUBSYSTEM=="tty",ATTRS{idVendor} == "12d1" , ATTRS{idProduct} == "1003", SYMLINK+="e122"
> --8<---------------cut here---------------end--------------->8---
>
> does not work.
> WWhen I get rid of 'SUBSYSTEM=="tty"' symlink is created, but points to
> sdX device.
>
> Any ideas?

What's the output for udevinfo on that device?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.12.11.38.35@gmail.com">http://lists.debian.org/pan.2011.06.12.11.38.35@gmail.com
 
Old 06-12-2011, 02:14 PM
 
Default Huawei e122 - how to make symlink to usb modem?

Camaleón <noelamac@gmail.com> writes:

> On Sun, 12 Jun 2011 06:55:45 +0200, Kamil Jońca wrote:
>
>> I have e122 modem. I would have symlink to /dev/ttyUSBX. (modem device)
>> But simple rule:
>>
>> --8<---------------cut here---------------start------------->8---
>> SUBSYSTEM=="tty",ATTRS{idVendor} == "12d1" , ATTRS{idProduct} == "1003", SYMLINK+="e122"
>> --8<---------------cut here---------------end--------------->8---
>>
>> does not work.
>> WWhen I get rid of 'SUBSYSTEM=="tty"' symlink is created, but points to
>> sdX device.
>>
>> Any ideas?
>
> What's the output for udevinfo on that device?
>
> Greetings,
--8<---------------cut here---------------start------------->8---
custom logging function 0x7f28b0658010 registered
selinux=0
runtime dir '/dev/.udev'
calling: info
device 0x7f28b065a4c0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0/ttyUSB0/tty/ttyUSB0'
device 0x7f28b0658530 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0/ttyUSB0'
device 0x7f28b0658ad0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0'
device 0x7f28b06596d0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10'
device 0x7f28b065ba00 has devpath '/devices/pci0000:00/0000:00:02.1/usb1'
device 0x7f28b065d780 has devpath '/devices/pci0000:00/0000:00:02.1'
device 0x7f28b065ecb0 has devpath '/devices/pci0000:00'

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0/ttyUSB0/tty/ttyUSB0':
KERNEL=="ttyUSB0"
SUBSYSTEM=="tty"
DRIVER==""

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0/ttyUSB0':
KERNELS=="ttyUSB0"
SUBSYSTEMS=="usb-serial"
DRIVERS=="option1"
ATTRS{port_number}=="0"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.0':
KERNELS=="1-10:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="option"
ATTRS{bInterfaceNumber}=="00"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bNumEndpoints}=="03"
ATTRS{bInterfaceClass}=="ff"
ATTRS{bInterfaceSubClass}=="ff"
ATTRS{bInterfaceProtocol}=="ff"
ATTRS{supports_autosuspend}=="1"
ATTRS{interface}=="3G Modem"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10':
KERNELS=="1-10"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 4"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="500mA"
ATTRS{urbnum}=="239"
ATTRS{idVendor}=="12d1"
ATTRS{idProduct}=="1003"
ATTRS{bcdDevice}=="0000"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="41"
ATTRS{devpath}=="10"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="HUA WEI"
ATTRS{product}=="Huawei Mobile"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="989"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0002"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="10"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.38+3-64 ehci_hcd"
ATTRS{product}=="EHCI Host Controller"
ATTRS{serial}=="0000:00:02.1"
ATTRS{authorized_default}=="1"

looking at parent device '/devices/pci0000:00/0000:00:02.1':
KERNELS=="0000:00:02.1"
SUBSYSTEMS=="pci"
DRIVERS=="ehci_hcd"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x005b"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{subsystem_device}=="0x815a"
ATTRS{class}=="0x0c0320"
ATTRS{irq}=="21"
ATTRS{local_cpus}=="1"
ATTRS{local_cpulist}=="0"
ATTRS{dma_mask_bits}=="32"
ATTRS{consistent_dma_mask_bits}=="31"
ATTRS{enable}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
ATTRS{companion}==""

looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
--8<---------------cut here---------------end--------------->8---




--
http://blogdebart.pl/2009/12/22/mamy-chorych-dzieci/
"In order to form an immaculate member of a flock
of sheep one must, above all, be a sheep"
- Albert Einstein


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87d3ijrvaa.fsf@alfa.kjonca">http://lists.debian.org/87d3ijrvaa.fsf@alfa.kjonca
 
Old 06-12-2011, 02:54 PM
Camaleón
 
Default Huawei e122 - how to make symlink to usb modem?

On Sun, 12 Jun 2011 16:14:53 +0200, Kamil Jońca wrote:

> Camaleón <noelamac@gmail.com> writes:
>
>> What's the output for udevinfo on that device?

(...)

> Udevadm info starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device found,
> all possible attributes in the udev rules key format. A rule to match,
> can be composed by the attributes of the device and the attributes from
> one single parent device.

(...)

Okay... then according to this doc:

http://reactivated.net/writing_udev_rules.html#udevinfo

You can't mix attributes from different parent devices, so

SUBSYSTEM=="tty"

cannot go with

ATTRS{idVendor} == "12d1"

You may try with:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1003", SYMLINK+="e122"

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.12.14.54.26@gmail.com">http://lists.debian.org/pan.2011.06.12.14.54.26@gmail.com
 
Old 06-12-2011, 04:19 PM
 
Default Huawei e122 - how to make symlink to usb modem?

Camaleón <noelamac@gmail.com> writes:

> On Sun, 12 Jun 2011 16:14:53 +0200, Kamil Jońca wrote:
>
>> Camaleón <noelamac@gmail.com> writes:
>>
>>> What's the output for udevinfo on that device?
>
> (...)
>
>> Udevadm info starts with the device specified by the devpath and then
>> walks up the chain of parent devices. It prints for every device found,
>> all possible attributes in the udev rules key format. A rule to match,
>> can be composed by the attributes of the device and the attributes from
>> one single parent device.
>
> (...)
>
> Okay... then according to this doc:
>
> http://reactivated.net/writing_udev_rules.html#udevinfo
>
> You can't mix attributes from different parent devices, so
>
> SUBSYSTEM=="tty"
Erm.
--8<---------------cut here---------------start------------->8---
legal to combine the attributes from the device in question and a single parent device
--8<---------------cut here---------------end--------------->8---
SUBSYSTEM=="tty" is from "device in question" Am I wrong?

>
> cannot go with
>
> ATTRS{idVendor} == "12d1"
>
> You may try with:
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1003", SYMLINK+="e122"

Unfortunately /dev/sdc match these rule, and somehow "takes precedence"
and I ends with symlink to sdc.

--8<---------------cut here---------------start------------->8---
%sudo udevadm info --query=all --attribute-walk --name=sdc
custom logging function 0x7f52d1ee2010 registered
selinux=0
runtime dir '/dev/.udev'
calling: info
device 0x7f52d1ee44c0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0/76:0:0:0/block/sdc'
device 0x7f52d1ee3160 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0/76:0:0:0'
device 0x7f52d1ee4e20 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0'
device 0x7f52d1ee51b0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76'
device 0x7f52d1ee55f0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3'
device 0x7f52d1ee61f0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1/1-10'
device 0x7f52d1ee7db0 has devpath '/devices/pci0000:00/0000:00:02.1/usb1'

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0/76:0:0:0/block/sdc':
KERNEL=="sdc"
SUBSYSTEM=="block"
DRIVER==""
ATTR{range}=="16"
ATTR{ext_range}=="256"
ATTR{removable}=="1"
ATTR{ro}=="0"
ATTR{size}=="0"
ATTR{alignment_offset}=="0"
ATTR{discard_alignment}=="0"
ATTR{capability}=="51"
ATTR{stat}==" 0 0 0 0 0 0 0 0 0 0 0"
ATTR{inflight}==" 0 0"
ATTR{events}=="media_change"
ATTR{events_async}==""
ATTR{events_poll_msecs}=="-1"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0/76:0:0:0':
KERNELS=="76:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{device_blocked}=="0"
ATTRS{type}=="0"
ATTRS{scsi_level}=="3"
ATTRS{vendor}=="HUAWEI "
ATTRS{model}=="SD Storage "
ATTRS{rev}=="2.31"
ATTRS{state}=="running"
ATTRS{timeout}=="30"
ATTRS{iocounterbits}=="32"
ATTRS{iorequest_cnt}=="0x7"
ATTRS{iodone_cnt}=="0x7"
ATTRS{ioerr_cnt}=="0x6"
ATTRS{evt_media_change}=="0"
ATTRS{queue_depth}=="1"
ATTRS{queue_type}=="none"
ATTRS{max_sectors}=="240"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76/target76:0:0':
KERNELS=="target76:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3/host76':
KERNELS=="host76"
SUBSYSTEMS=="scsi"
DRIVERS==""

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10:1.3':
KERNELS=="1-10:1.3"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceNumber}=="03"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bNumEndpoints}=="02"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{supports_autosuspend}=="1"
ATTRS{interface}=="USB MASS STORAGE"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1/1-10':
KERNELS=="1-10"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 4"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bMaxPower}=="500mA"
ATTRS{urbnum}=="239"
ATTRS{idVendor}=="12d1"
ATTRS{idProduct}=="1003"
ATTRS{bcdDevice}=="0000"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="43"
ATTRS{devpath}=="10"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="0"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="HUA WEI"
ATTRS{product}=="Huawei Mobile"

looking at parent device '/devices/pci0000:00/0000:00:02.1/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="1033"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0002"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="480"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{devpath}=="0"
ATTRS{version}==" 2.00"
ATTRS{maxchild}=="10"
ATTRS{quirks}=="0x0"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.38+3-64 ehci_hcd"
ATTRS{product}=="EHCI Host Condevice 0x7f52d1ee9b30 has devpath '/devices/pci0000:00/0000:00:02.1'
device 0x7f52d1eeb060 has devpath '/devices/pci0000:00'
troller"
ATTRS{serial}=="0000:00:02.1"
ATTRS{authorized_default}=="1"

looking at parent device '/devices/pci0000:00/0000:00:02.1':
KERNELS=="0000:00:02.1"
SUBSYSTEMS=="pci"
DRIVERS=="ehci_hcd"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x005b"
ATTRS{subsystem_vendor}=="0x1043"
ATTRS{subsystem_device}=="0x815a"
ATTRS{class}=="0x0c0320"
ATTRS{irq}=="21"
ATTRS{local_cpus}=="1"
ATTRS{local_cpulist}=="0"
ATTRS{dma_mask_bits}=="32"
ATTRS{consistent_dma_mask_bits}=="31"
ATTRS{enable}=="1"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
ATTRS{companion}==""

looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
--8<---------------cut here---------------end--------------->8---


--
http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewskiej-wprowadzenie/
"Nie można wlecieć w trzecie tysiaclecie
na drzwiach od stodoły" - biskup polowy WP Sławoj Leszek Głódź.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 878vt7rpi4.fsf@alfa.kjonca">http://lists.debian.org/878vt7rpi4.fsf@alfa.kjonca
 
Old 06-12-2011, 05:59 PM
 
Default Huawei e122 - how to make symlink to usb modem?

kjonca@poczta.onet.pl (Kamil Jońca) writes:

> I have e122 modem. I would have symlink to /dev/ttyUSBX. (modem device)
> But simple rule:
>
> SUBSYSTEM=="tty",ATTRS{idVendor} == "12d1" , ATTRS{idProduct} == "1003", SYMLINK+="e122"
>
> does not work.

It was enough to put rule in /etc/udev/rules.d/zz-local.rules
instead of /etc/udev/rules.d/00-local.rules

KJ


--
http://sporothrix.wordpress.com/2011/01/16/usa-sie-krztusza-kto-nastepny/
Keyboard error press F1 continue


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 871uyzrkv6.fsf@alfa.kjonca">http://lists.debian.org/871uyzrkv6.fsf@alfa.kjonca
 
Old 06-13-2011, 01:04 PM
Camaleón
 
Default Huawei e122 - how to make symlink to usb modem?

On Sun, 12 Jun 2011 18:19:47 +0200, Kamil Jońca wrote:

> Camaleón <noelamac@gmail.com> writes:
>
>> Okay... then according to this doc:
>>
>> http://reactivated.net/writing_udev_rules.html#udevinfo
>>
>> You can't mix attributes from different parent devices, so
>>
>> SUBSYSTEM=="tty"

> Erm.
> --8<---------------cut here---------------start------------->8---
> legal to combine the attributes from the device in question and a single
> parent device
>--8<---------------cut here---------------end--------------->8---
> SUBSYSTEM=="tty" is from "device in question" Am I wrong?

(...)

Hum... yes, I didn't realize that "tty" was the top device and the other
two were on the same node, so your original rule should be right.

And I just have read that you've already sorted it out in another post,
good :-)

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.13.13.04.25@gmail.com">http://lists.debian.org/pan.2011.06.13.13.04.25@gmail.com
 

Thread Tools




All times are GMT. The time now is 07:10 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org