Re: Android usb tethering
On Tue 2/11/10 11:37 AM , freebsd-questi...@herveybayaustralia.com.au wrote: On Tue 2/11/10 10:11 AM , Alejandro Imass wrote:On Mon, Nov 1, 2010 at 6:25 PM, Ivan Voras wrote: On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. Yes. One has to remember that USB is just the bus just like pci, microchannel, etc. Even though you have access to the device on the bus you still need a driver for that specific ethernet chip your kernel. This is analogous to having a video card on the pci bus, you still need for the kernel to drive the specific chipset of the card regardless if it can see it on the bus. I have an HTC Nexus One so I may fiddle with this and see if I can help some more here. I am wishful that at least we can get a tty just like other gsm modems and from there it's pretty straight forward using wvdial or alike. If it's only the Ethernet over usb like you mention, then the chipset driver would have to be translated/ported to the FBSD kernel, if it's not already there ? Ok. But I will clarify here: The HTC Android systems uses an Internet Sharing feature- essentially Google has coded in routing/nat system into the base OS (probably moding the leftover code already in the linux base), and is trying to allow similar using bluetooth and wifi at a later date as well. The RNDIS is a M$ system that allows sharing anything over USB (network, files, etc- but all essentially operated as network anyway), something they've been playing with for some years- I was looking for an A-A USB cable since around 2003 or so to quickly transfer files when needed. Apparently M$ opened the specs a year or two ago and everyone's jumped on to use it. So where Google started was to start allowing the use of the router/nat via RNDIS USB - somehow this was easier than allowing bluetooth or wifi (probably security and available hardware features). So yes, apparently the phone hooks up as a usb mass storage device, uploads a file to the computer, and disconnects and becomes a network device. Here is the output from linux: usb 2-2.2: new high speed USB device using ehci_hcd and address 4 usb 2-2.2: configuration #1 chosen from 1 choice scsi9 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ff9 usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usb-storage: device scan complete scsi 9:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 sd 9:0:0:0: [sdf] Attached SCSI removable disk sd 9:0:0:0: Attached scsi generic sg6 type 0 usb 2-2.2: USB disconnect, address 4 usb 2-2.2: new high speed USB device using ehci_hcd and address 5 usb 2-2.2: configuration #1 chosen from 1 choice usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ffe usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usbcore: registered new interface driver cdc_ether usb0: register 'rndis_host' at usb-:00:04.1-2.2, RNDIS device, ae:f6:3d:da:20:39 usbcore: registered new interface driver rndis_host usbcore: registered new interface driver rndis_wlan usb0: no IPv6 routers present usb 2-2.2: USB disconnect, address 5 usb0: unregister 'rndis_host' usb-:00:04.1-2.2, RNDIS device So. What would be my next step to make this work? OpenMoko have something similar and I tried moding some of their scripts (they've made theirs work with ALL OS- not just linux and Winblow$! Take heed manufacturers!) but it didn't mesh on the Android. I still end up with a generic host. As I mentioned, I tried modifying the cdce driver and the device list but that didn't help either, so when I moded the scripts and devd.conf I figured that was the missing piece of my puzzle. I'd actually pay someone to do this, but I do need to figure this out for myself anyway so I'm diving in deep and going to keep on struggling till I get it. I need it figured out before the year's end so I'm not going to sit on my laurels :) That, and a usb mass storage device emulator to trick a dumb digital photo frame So I have more on this: sourceforge.jp has a project rndis for freebsd. Its a little hard to navigate, but I downloaded the source code and tried to build it on 8.0. No go, but I'm not sure what usb library its using. I think it said usb2, but I'm not exactly sure what that meant (usb2.0, or libusb2, whatever). Now, I've only just quickly grabbed it and tried to
Re: Android usb tethering
On Thu 4/11/10 10:28 PM , four.harris...@googlemail.com wrote: On Tue 2/11/10 11:37 AM , wrote: On Tue 2/11/10 10:11 AM , Alejandro Imass wrote:On Mon, Nov 1, 2010 at 6:25 PM, Ivan Voras wrote: On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. Yes. One has to remember that USB is just the bus just like pci, microchannel, etc. Even though you have access to the device on the bus you still need a driver for that specific ethernet chip your kernel. This is analogous to having a video card on the pci bus, you still need for the kernel to drive the specific chipset of the card regardless if it can see it on the bus. I have an HTC Nexus One so I may fiddle with this and see if I can help some more here. I am wishful that at least we can get a tty just like other gsm modems and from there it's pretty straight forward using wvdial or alike. If it's only the Ethernet over usb like you mention, then the chipset driver would have to be translated/ported to the FBSD kernel, if it's not already there ? Ok. But I will clarify here: The HTC Android systems uses an Internet Sharing feature- essentially Google has coded in routing/nat system into the base OS (probably moding the leftover code already in the linux base), and is trying to allow similar using bluetooth and wifi at a later date as well. The RNDIS is a M$ system that allows sharing anything over USB (network, files, etc- but all essentially operated as network anyway), something they've been playing with for some years- I was looking for an A-A USB cable since around 2003 or so to quickly transfer files when needed. Apparently M$ opened the specs a year or two ago and everyone's jumped on to use it. So where Google started was to start allowing the use of the router/nat via RNDIS USB - somehow this was easier than allowing bluetooth or wifi (probably security and available hardware features). So yes, apparently the phone hooks up as a usb mass storage device, uploads a file to the computer, and disconnects and becomes a network device. Here is the output from linux: usb 2-2.2: new high speed USB device using ehci_hcd and address 4 usb 2-2.2: configuration #1 chosen from 1 choice scsi9 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ff9 usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usb-storage: device scan complete scsi 9:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 sd 9:0:0:0: [sdf] Attached SCSI removable disk sd 9:0:0:0: Attached scsi generic sg6 type 0 usb 2-2.2: USB disconnect, address 4 usb 2-2.2: new high speed USB device using ehci_hcd and address 5 usb 2-2.2: configuration #1 chosen from 1 choice usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ffe usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usbcore: registered new interface driver cdc_ether usb0: register 'rndis_host' at usb-:00:04.1-2.2, RNDIS device, ae:f6:3d:da:20:39 usbcore: registered new interface driver rndis_host usbcore: registered new interface driver rndis_wlan usb0: no IPv6 routers present usb 2-2.2: USB disconnect, address 5 usb0: unregister 'rndis_host' usb-:00:04.1-2.2, RNDIS device So. What would be my next step to make this work? OpenMoko have something similar and I tried moding some of their scripts (they've made theirs work with ALL OS- not just linux and Winblow$! Take heed manufacturers!) but it didn't mesh on the Android. I still end up with a generic host. As I mentioned, I tried modifying the cdce driver and the device list but that didn't help either, so when I moded the scripts and devd.conf I figured that was the missing piece of my puzzle. I'd actually pay someone to do this, but I do need to figure this out for myself anyway so I'm diving in deep and going to keep on struggling till I get it. I need it figured out before the year's end so I'm not going to sit on my laurels :) That, and a usb mass storage device emulator to trick a dumb digital photo frame So I have more on this: sourceforge.jp has a project rndis for freebsd. Its a little hard to navigate, but I downloaded the source code and tried to build it on 8.0. No go, but I'm not sure what usb library its using. I think it said usb2, but I'm
Re: Android usb tethering
On Tue 2/11/10 11:37 AM , freebsd-questi...@herveybayaustralia.com.au wrote: On Tue 2/11/10 10:11 AM , Alejandro Imass wrote:On Mon, Nov 1, 2010 at 6:25 PM, Ivan Voras wrote: On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. Yes. One has to remember that USB is just the bus just like pci, microchannel, etc. Even though you have access to the device on the bus you still need a driver for that specific ethernet chip your kernel. This is analogous to having a video card on the pci bus, you still need for the kernel to drive the specific chipset of the card regardless if it can see it on the bus. I have an HTC Nexus One so I may fiddle with this and see if I can help some more here. I am wishful that at least we can get a tty just like other gsm modems and from there it's pretty straight forward using wvdial or alike. If it's only the Ethernet over usb like you mention, then the chipset driver would have to be translated/ported to the FBSD kernel, if it's not already there ? Ok. But I will clarify here: The HTC Android systems uses an Internet Sharing feature- essentially Google has coded in routing/nat system into the base OS (probably moding the leftover code already in the linux base), and is trying to allow similar using bluetooth and wifi at a later date as well. The RNDIS is a M$ system that allows sharing anything over USB (network, files, etc- but all essentially operated as network anyway), something they've been playing with for some years- I was looking for an A-A USB cable since around 2003 or so to quickly transfer files when needed. Apparently M$ opened the specs a year or two ago and everyone's jumped on to use it. So where Google started was to start allowing the use of the router/nat via RNDIS USB - somehow this was easier than allowing bluetooth or wifi (probably security and available hardware features). So yes, apparently the phone hooks up as a usb mass storage device, uploads a file to the computer, and disconnects and becomes a network device. Here is the output from linux: usb 2-2.2: new high speed USB device using ehci_hcd and address 4 usb 2-2.2: configuration #1 chosen from 1 choice scsi9 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ff9 usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usb-storage: device scan complete scsi 9:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 sd 9:0:0:0: [sdf] Attached SCSI removable disk sd 9:0:0:0: Attached scsi generic sg6 type 0 usb 2-2.2: USB disconnect, address 4 usb 2-2.2: new high speed USB device using ehci_hcd and address 5 usb 2-2.2: configuration #1 chosen from 1 choice usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ffe usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usbcore: registered new interface driver cdc_ether usb0: register 'rndis_host' at usb-:00:04.1-2.2, RNDIS device, ae:f6:3d:da:20:39 usbcore: registered new interface driver rndis_host usbcore: registered new interface driver rndis_wlan usb0: no IPv6 routers present usb 2-2.2: USB disconnect, address 5 usb0: unregister 'rndis_host' usb-:00:04.1-2.2, RNDIS device So. What would be my next step to make this work? OpenMoko have something similar and I tried moding some of their scripts (they've made theirs work with ALL OS- not just linux and Winblow$! Take heed manufacturers!) but it didn't mesh on the Android. I still end up with a generic host. As I mentioned, I tried modifying the cdce driver and the device list but that didn't help either, so when I moded the scripts and devd.conf I figured that was the missing piece of my puzzle. I'd actually pay someone to do this, but I do need to figure this out for myself anyway so I'm diving in deep and going to keep on struggling till I get it. I need it figured out before the year's end so I'm not going to sit on my laurels :) That, and a usb mass storage device emulator to trick a dumb digital photo frame So I have more on this: sourceforge.jp has a project rndis for freebsd. Its a little hard to navigate, but I downloaded the source code and tried to build it on 8.0. No go, but I'm not sure what usb library its using. I think it said usb2, but I'm not exactly sure what that meant (usb2.0, or libusb2, whatever). Now, I've only just quickly grabbed it and tried to
Android usb tethering
Anyone tried the data tethering feature on the Android phones? I've tried cdce and tried modifying cdce but no luck. I need to regenerate the device list, but I haven't had any luck yet- simply running make doesn't work, and I've read Makefiles and googled out the wazoo. I tried modifying the details off the openmoko site for their data tether system (for FreeBSD8, mind), still no luck. Apparently it uses the cdc_ether RNDIS according to my Fedora shit media system. usbconfig concurs. Any hints, suggestions on how to further my investigations and getting this thing working? Anyone happen to be working on this? Cheers - Message sent via Atmail Open - http://atmail.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Android usb tethering
On Mon, Nov 1, 2010 at 6:54 AM, freebsd-questi...@herveybayaustralia.com.au wrote: Anyone tried the data tethering feature on the Android phones? Just my .02: I'm not sure but I think there are several issues you have to overcome, at least from my Linux experience: Assuming you are using USB (Bluetooth is similar in some ways...): 1) When you connect the Android usb port to your PC you have a multi-function usb port and you must select the correct option (or choice as their are named in Linux), this means that you should be able to either select the mass storage (sd card) or the tty. So you first need to figure out how to do that. I use CyanogenMod that has several usb debugging features but I haven't had a chance to experiment with tethering yet. Anyway, you must use soemthing at the usb layer level that handles the multi-function usb port. 2) I suspect that tethering works like most usb gsm modems in Linux, simply by mounting ttyUSB0 and the using something like wvdial with your provider's APN. So I think that once you figure out (1) you should have a tty and you can simply dial #777 or whatever your phone carrier specifies in their APN. I've tried cdce and tried modifying cdce but no luck. I need to regenerate the device list, but I haven't had any luck yet- simply running make doesn't work, and I've read Makefiles and googled out the wazoo. I tried modifying the details off the openmoko site for their data tether system (for FreeBSD8, mind), still no luck. Apparently it uses the cdc_ether RNDIS according to my Fedora shit media system. usbconfig concurs. Any hints, suggestions on how to further my investigations and getting this thing working? Anyone happen to be working on this? Cheers - Message sent via Atmail Open - http://atmail.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Android usb tethering
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/01/2010 03:54, freebsd-questi...@herveybayaustralia.com.au wrote: Anyone tried the data tethering feature on the Android phones? I have, it works. Attaching via usb in the proper mode should attach the umodem device which you can then use the published serial device with the userland ppp(8). Defining the correct section name for tethering can be a little daunting however. Google for things like 'telstra GSM ppp.conf' or such and then you just have to convert any linux scripts you find into freebsd ppp.conf. If you're lucky you may find freebsd specific configurations. Or, someone on the list may have one to share. - -Mark -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzO0fEACgkQrDN5kXnx8ybfHwCffDLttNzAL8g1kUxhYbYv1/Z+ 9fEAnjqr0IT7BU1+T2zSvQR82LnLp+js =8Res -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Android usb tethering
On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/01/2010 03:54, freebsd-questi...@herveybayaustralia.com.au wrote: Anyone tried the data tethering feature on the Android phones? I have, it works. Attaching via usb in the proper mode should attach the umodem device which you can then use the published serial device with the userland ppp(8). Defining the correct section name for tethering can be a little daunting however. Google for things like 'telstra GSM ppp.conf' or such and then you just have to convert any linux scripts you find into freebsd ppp.conf. If you're lucky you may find freebsd specific configurations. Or, someone on the list may have one to share. I believe it depends on the phone manufacturer. HTC phones apparently use some kind of Ethernet over USB which is well supported under Windows and Linux but not FreeBSD: Nov 1 23:20:52 betelgeuse kernel: (da4:umass-sim1:1:0:0): lost device Nov 1 23:20:52 betelgeuse kernel: (da4:umass-sim1:1:0:0): removing device entry Nov 1 23:20:53 betelgeuse root: Unknown USB device: vendor 0x0bb4 product 0x0ffe bus uhub5 Nov 1 23:20:53 betelgeuse kernel: ugen4.4: HTC at usbus4 In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Android usb tethering
On Mon, Nov 1, 2010 at 6:25 PM, Ivan Voras ivo...@freebsd.org wrote: On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. Yes. One has to remember that USB is just the bus just like pci, microchannel, etc. Even though you have access to the device on the bus you still need a driver for that specific ethernet chip your kernel. This is analogous to having a video card on the pci bus, you still need for the kernel to drive the specific chipset of the card regardless if it can see it on the bus. I have an HTC Nexus One so I may fiddle with this and see if I can help some more here. I am wishful that at least we can get a tty just like other gsm modems and from there it's pretty straight forward using wvdial or alike. If it's only the Ethernet over usb like you mention, then the chipset driver would have to be translated/ported to the FBSD kernel, if it's not already there ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Android usb tethering
On Tue 2/11/10 10:11 AM , Alejandro Imass wrote:On Mon, Nov 1, 2010 at 6:25 PM, Ivan Voras wrote: On 11/01/10 15:42, Mark Atkinson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [...] In the above messages, the kernel detaches the storage device (umass) and tries to attach the new device, which doesn't have a driver so it's attached as ugen - generic USB. Yes. One has to remember that USB is just the bus just like pci, microchannel, etc. Even though you have access to the device on the bus you still need a driver for that specific ethernet chip your kernel. This is analogous to having a video card on the pci bus, you still need for the kernel to drive the specific chipset of the card regardless if it can see it on the bus. I have an HTC Nexus One so I may fiddle with this and see if I can help some more here. I am wishful that at least we can get a tty just like other gsm modems and from there it's pretty straight forward using wvdial or alike. If it's only the Ethernet over usb like you mention, then the chipset driver would have to be translated/ported to the FBSD kernel, if it's not already there ? Ok. But I will clarify here: The HTC Android systems uses an Internet Sharing feature- essentially Google has coded in routing/nat system into the base OS (probably moding the leftover code already in the linux base), and is trying to allow similar using bluetooth and wifi at a later date as well. The RNDIS is a M$ system that allows sharing anything over USB (network, files, etc- but all essentially operated as network anyway), something they've been playing with for some years- I was looking for an A-A USB cable since around 2003 or so to quickly transfer files when needed. Apparently M$ opened the specs a year or two ago and everyone's jumped on to use it. So where Google started was to start allowing the use of the router/nat via RNDIS USB - somehow this was easier than allowing bluetooth or wifi (probably security and available hardware features). So yes, apparently the phone hooks up as a usb mass storage device, uploads a file to the computer, and disconnects and becomes a network device. Here is the output from linux: usb 2-2.2: new high speed USB device using ehci_hcd and address 4 usb 2-2.2: configuration #1 chosen from 1 choice scsi9 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ff9 usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usb-storage: device scan complete scsi 9:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 sd 9:0:0:0: [sdf] Attached SCSI removable disk sd 9:0:0:0: Attached scsi generic sg6 type 0 usb 2-2.2: USB disconnect, address 4 usb 2-2.2: new high speed USB device using ehci_hcd and address 5 usb 2-2.2: configuration #1 chosen from 1 choice usb 2-2.2: New USB device found, idVendor=0bb4, idProduct=0ffe usb 2-2.2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb 2-2.2: Product: Android Phone usb 2-2.2: Manufacturer: HTC usb 2-2.2: SerialNumber: SH07TNX00726 usbcore: registered new interface driver cdc_ether usb0: register 'rndis_host' at usb-:00:04.1-2.2, RNDIS device, ae:f6:3d:da:20:39 usbcore: registered new interface driver rndis_host usbcore: registered new interface driver rndis_wlan usb0: no IPv6 routers present usb 2-2.2: USB disconnect, address 5 usb0: unregister 'rndis_host' usb-:00:04.1-2.2, RNDIS device So. What would be my next step to make this work? OpenMoko have something similar and I tried moding some of their scripts (they've made theirs work with ALL OS- not just linux and Winblow$! Take heed manufacturers!) but it didn't mesh on the Android. I still end up with a generic host. As I mentioned, I tried modifying the cdce driver and the device list but that didn't help either, so when I moded the scripts and devd.conf I figured that was the missing piece of my puzzle. I'd actually pay someone to do this, but I do need to figure this out for myself anyway so I'm diving in deep and going to keep on struggling till I get it. I need it figured out before the year's end so I'm not going to sit on my laurels :) That, and a usb mass storage device emulator to trick a dumb digital photo frame ___ mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions [3] target=_blankhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to ___ mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions [6] target=_blankhttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to - Message sent via Atmail Open -
