View Single Post
Posts: 62 | Thanked: 35 times | Joined on Mar 2008 @ Fort Gratiot, Michigan
#35
Originally Posted by EasternPA View Post
I think the biggest issue here is figuring out how the internal card is detected by the installation host when the USB is attached. Apparently Ubuntu sees the card as /dev/sdc but for me on CentOS, the card was detected as /dev/sda. And does it register as a different scsi device if the usb cable is connected to a different usb port? With all of the different distros out there and kernel module options, I don't think there's an easy way to tell which scsi device is the tablet. Perhaps do an fdisk -l and look for the only 2GB scsi drive? Is there something in proc that shows the vendor of each attached drive?

I'm waiting for approval to formally host the project at a community development site. Once that gets up and running, perhaps we can get some more visibility and start up an installer sub-project. I know someone who knows dialog. Its just a matter of getting his time. As I've said before, my ultimate goal is to publish a bootable USB key for each release.
The /dev/sdc was just an example. The script works like this:

Code:
mount|grep -e /dev/sd
It then asks you for the last result, which would be the just-plugged-in tablet. It then asks for it again without the number on the end, then with a 3 on the end. These entries are used as variables that are referred to during the partitioning, mounting, etc.

The problem with looking by size is that different people have different sizes (that's what she said) of SD cards and having used a bunch of them, many have weird sizes when coming from strange places in Shenzhen, China. (931MB instead of 1024MB)