[Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
Robert Winder wrote:
I give up.
It has something to do with the vfs implementation. But where it goes
wrong excactly i really can't tell. But what i said earlier
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
in misc.py still stands. Device shows up in menu but doesn't get
mounted. Pretty useless plugin then without the mounting part ;-)
Of course the USB HOTPLUG cmd can be used for mounting but i know
from personal experience that it mounted and umounted the usb device
whithout prob in freevo 1.4
Sorry for the _very_ late answer. Does it work with rc4 and if not,
can you tell me which file need what changes?
Dischi
--
Disc space -- the final frontier!
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
Sunday, July 11, 2004, 4:04:24 PM, Dirk wrote:
Robert Winder wrote:
I give up.
It has something to do with the vfs implementation. But where it goes
wrong excactly i really can't tell. But what i said earlier
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
in misc.py still stands. Device shows up in menu but doesn't get
mounted. Pretty useless plugin then without the mounting part ;-)
Of course the USB HOTPLUG cmd can be used for mounting but i know
from personal experience that it mounted and umounted the usb device
whithout prob in freevo 1.4
Sorry for the _very_ late answer. Does it work with rc4 and if not,
can you tell me which file need what changes?
Heh, thats indeed some time ago.. ;-) But the above still stands with
1.5.0-rc3 and i believe rc-4 as well because misc.py isn't changed.
Output on my 2.6.6. kernel from
cat /proc/bus/usb/devices
I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
While searching for mass storage it obviously doesn't find anything.
As far as i recall when searching for storage in /proc/bus/usb/devices
you cover most situations in 2.4 and 2.6 kernels.
Never figured out why auto-mounting didn't work though. Used entries
in fstab before last year without prob and it did mount the usb
storage device automagicly. With freevo 1.4 it did not. Switched to
autofs and automount and is better anyway especially if one have some
samba shares in the network. With autofs it worked without a prob.
Dischi
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
- Original Message -
From: Robert Winder [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 11, 2004 6:07 PM
Subject: Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED
!!!
Sunday, July 11, 2004, 4:04:24 PM, Dirk wrote:
Robert Winder wrote:
I give up.
It has something to do with the vfs implementation. But where it goes
wrong excactly i really can't tell. But what i said earlier
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
in misc.py still stands. Device shows up in menu but doesn't get
mounted. Pretty useless plugin then without the mounting part ;-)
Of course the USB HOTPLUG cmd can be used for mounting but i know
from personal experience that it mounted and umounted the usb device
whithout prob in freevo 1.4
Sorry for the _very_ late answer. Does it work with rc4 and if not,
can you tell me which file need what changes?
Heh, thats indeed some time ago.. ;-) But the above still stands with
1.5.0-rc3 and i believe rc-4 as well because misc.py isn't changed.
Output on my 2.6.6. kernel from
cat /proc/bus/usb/devices
I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
While searching for mass storage it obviously doesn't find anything.
As far as i recall when searching for storage in /proc/bus/usb/devices
you cover most situations in 2.4 and 2.6 kernels.
Never figured out why auto-mounting didn't work though. Used entries
in fstab before last year without prob and it did mount the usb
storage device automagicly. With freevo 1.4 it did not. Switched to
autofs and automount and is better anyway especially if one have some
samba shares in the network. With autofs it worked without a prob.
Dischi
getting automount to work is pretty easy (in my case fedore core 2)
cd /etc
cat auto.master
__
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc /etc/auto.misc --timeout=60
/misc /etc/auto.misc --timeout=60
#/net /etc/auto.net
__
cat auto.misc
__
#
# $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $
#
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom
# the following entries are samples to pique your imagination
#linux -ro,soft,intr ftp.example.org:/pub/linux
#boot -fstype=ext2:/dev/hda1
#floppy -fstype=auto:/dev/fd0
#floppy -fstype=ext2:/dev/fd0
#e2floppy -fstype=ext2:/dev/fd0
#jaz-fstype=ext2:/dev/sdc1
#removable -fstype=ext2:/dev/hdd
usb -fstype=auto:/dev/sda1
usb2-fstype=auto:/dev/sdb1
_
Create a directory /misc
addition to local_conf.py:
__
plugin.activate('usb')
# 2 possible USB storage devices (camara and usbstick)
plugin.activate('usbstorage', type='image', args=('USB Storage', '/misc/usb'))
plugin.activate('usbstorage', type='image', args=('USB Data','/misc/usb2'))
_
cd /etc/init.d
./autofs restart
This should do the job, it worked for me on freevo 1.4rc
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
[Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
Robert Winder wrote: While searching for mass storage it obviously doesn't find anything. As far as i recall when searching for storage in /proc/bus/usb/devices you cover most situations in 2.4 and 2.6 kernels. OK, fixed it by searching for mass storage _and_ mass-storage. Still, this is a very bad plugin. Better would be: o insert a mass storage device, the kernel sets this to /dev/something o find out what this something is and as root mount it to a pre-defined dir. One other reason why this is bad: umount is missing. Or is it done by the menu, maybe... Dischi -- A man generally has two reasons for doing a thing. One that sounds good, and a real one. --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
Thanks for your help robert, at least nw the menu bit can work.. which
is the most important from an end users perspective.. I can always short
cut the mounting side of things with the usb.py plugin i sent to the
devel list. It adds an option for a command to issue when a particular
device disapeear.. (so unmount also..)
Mick
On Sat, 2004-05-01 at 00:42, Robert Winder wrote:
I give up.
It has something to do with the vfs implementation. But where it goes
wrong excactly i really can't tell. But what i said earlier
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
in misc.py still stands. Device shows up in menu but doesn't get
mounted. Pretty useless plugin then without the mounting part ;-)
Of course the USB HOTPLUG cmd can be used for mounting but i know
from personal experience that it mounted and umounted the usb device
whithout prob in freevo 1.4
/Robert
Friday, April 30, 2004, 12:23:26 PM, Robert wrote:
Hi,
oohps half way there, device shows up in menu but doesn't get mounted
automaticly. Gonna look a bit further into it.
/Robert
Friday, April 30, 2004, 11:05:21 AM, Robert wrote:
Hi,
Duh, a search through /proc/bus/usb/devices revealed the culprit.
Found the problem in misc.py line 300
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
Probably kernel 2.4 and 2.6 usb/mass storage module naming is
different. A find for 'storage' is enough to get it going for both
modules
my cat /proc/bus/usb/devices
If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
Or changing back to usb_id as an identifier is maybe a better solution
if one has multiple usb-storage devices.
/Robert
Wednesday, April 28, 2004, 7:11:59 PM, Robert wrote:
Mick,
Sorry no i didn't wrote this stuff but last week i did give it another
try, but as i replied earlier i couldn't make it work also. What i
recall it did work somewhere last august, september. Early this year
camera.py changed into usbstorage.py but from what i can see in CVS
nothing changed substantially when doing a diff. The mounting and
making the mounted dir visible is indeed hacked away somewhere in the
process..
So imo there are two options:
- Find a freevo tarball from august, september last year and debug it
with this code. Problem is i can't find any freevo tarball 1.4 . If
someone can point me to it ? (complete tarball is bit easier then
browsing cvs, i think)
- as dischi stated earlier this week devel is a bit slow now and if
you doesn't want it to be buried in this list file it as a bug report.
Haven't got the time to this myself right know because i have to leave i
a few secs.
/Robert
Wednesday, April 28, 2004, 6:29:08 AM, Mick wrote:
Hi Robert.
I tried the best I could, and I cannot get this going...
Did you write the plugin? I think wether or not the directory is
mounting is relavtily easy to fix, the problem is making the directoy
visible in freevo only when the device is available.. This part of the
code I simply connot reverse engineer. To be honest, it looks like this
part of the code does not exist.. It seems so simple i'm a little bit
peaved I can't work out whats going on..
Maybe it is something inferred by something else.. Like the Dir item..
In any case i can only appoligise for being stupid.. But can someone
help me with this?
Mick
On Wed, 2004-04-21 at 02:49, Robert Winder wrote:
Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote:
Mick wrote:
Dischi,
Can you please explain to me how usbtorage.py is meant to funtion with
refference to usb.py?
No, I didn't wrote usbtorage.py. I can only say that usb.py will force
a menu rebuild when you add/remove usb devices.
I can't see any refference to calling mount or umount.. I'm happy to
make this my first contribution, but need your advice as to how its
meant to work..
It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it
used an automounter.
It doesn't.. so it's a bug then. Strange thing is i got it working with
camera.py a while ago without using automount. And usbstorage.py is
basicly the same code as camera.py was. Not sure where it goes wrong
but i look into it and i'll try to find out what the diff is. Probably
tomorrow.
Its such a simple process that I don't see the need to patch a
kernel or install another dependancy to get it going..
It should work using mount and umount.
What i meant was that for usb storage devices some kernelside options
are needed. In other words make sure if USB mounting works outside
freevo. :-) But we probably passed that stage.
/Robert
---
This SF.Net email is
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] FIXED !!!
Hi,
Duh, a search through /proc/bus/usb/devices revealed the culprit.
Found the problem in misc.py line 300
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
Probably kernel 2.4 and 2.6 usb/mass storage module naming is
different. A find for 'storage' is enough to get it going for both
modules
my cat /proc/bus/usb/devices
If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
Or changing back to usb_id as an identifier is maybe a better solution
if one has multiple usb-storage devices.
/Robert
Wednesday, April 28, 2004, 7:11:59 PM, Robert wrote:
Mick,
Sorry no i didn't wrote this stuff but last week i did give it another
try, but as i replied earlier i couldn't make it work also. What i
recall it did work somewhere last august, september. Early this year
camera.py changed into usbstorage.py but from what i can see in CVS
nothing changed substantially when doing a diff. The mounting and
making the mounted dir visible is indeed hacked away somewhere in the
process..
So imo there are two options:
- Find a freevo tarball from august, september last year and debug it
with this code. Problem is i can't find any freevo tarball 1.4 . If
someone can point me to it ? (complete tarball is bit easier then
browsing cvs, i think)
- as dischi stated earlier this week devel is a bit slow now and if
you doesn't want it to be buried in this list file it as a bug report.
Haven't got the time to this myself right know because i have to leave i
a few secs.
/Robert
Wednesday, April 28, 2004, 6:29:08 AM, Mick wrote:
Hi Robert.
I tried the best I could, and I cannot get this going...
Did you write the plugin? I think wether or not the directory is
mounting is relavtily easy to fix, the problem is making the directoy
visible in freevo only when the device is available.. This part of the
code I simply connot reverse engineer. To be honest, it looks like this
part of the code does not exist.. It seems so simple i'm a little bit
peaved I can't work out whats going on..
Maybe it is something inferred by something else.. Like the Dir item..
In any case i can only appoligise for being stupid.. But can someone
help me with this?
Mick
On Wed, 2004-04-21 at 02:49, Robert Winder wrote:
Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote:
Mick wrote:
Dischi,
Can you please explain to me how usbtorage.py is meant to funtion with
refference to usb.py?
No, I didn't wrote usbtorage.py. I can only say that usb.py will force
a menu rebuild when you add/remove usb devices.
I can't see any refference to calling mount or umount.. I'm happy to
make this my first contribution, but need your advice as to how its
meant to work..
It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it
used an automounter.
It doesn't.. so it's a bug then. Strange thing is i got it working with
camera.py a while ago without using automount. And usbstorage.py is
basicly the same code as camera.py was. Not sure where it goes wrong
but i look into it and i'll try to find out what the diff is. Probably
tomorrow.
Its such a simple process that I don't see the need to patch a
kernel or install another dependancy to get it going..
It should work using mount and umount.
What i meant was that for usb storage devices some kernelside options
are needed. In other words make sure if USB mounting works outside
freevo. :-) But we probably passed that stage.
/Robert
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] FIXED !!!
Hi,
oohps half way there, device shows up in menu but doesn't get mounted
automaticly. Gonna look a bit further into it.
/Robert
Friday, April 30, 2004, 11:05:21 AM, Robert wrote:
Hi,
Duh, a search through /proc/bus/usb/devices revealed the culprit.
Found the problem in misc.py line 300
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
Probably kernel 2.4 and 2.6 usb/mass storage module naming is
different. A find for 'storage' is enough to get it going for both
modules
my cat /proc/bus/usb/devices
If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
Or changing back to usb_id as an identifier is maybe a better solution
if one has multiple usb-storage devices.
/Robert
Wednesday, April 28, 2004, 7:11:59 PM, Robert wrote:
Mick,
Sorry no i didn't wrote this stuff but last week i did give it another
try, but as i replied earlier i couldn't make it work also. What i
recall it did work somewhere last august, september. Early this year
camera.py changed into usbstorage.py but from what i can see in CVS
nothing changed substantially when doing a diff. The mounting and
making the mounted dir visible is indeed hacked away somewhere in the
process..
So imo there are two options:
- Find a freevo tarball from august, september last year and debug it
with this code. Problem is i can't find any freevo tarball 1.4 . If
someone can point me to it ? (complete tarball is bit easier then
browsing cvs, i think)
- as dischi stated earlier this week devel is a bit slow now and if
you doesn't want it to be buried in this list file it as a bug report.
Haven't got the time to this myself right know because i have to leave i
a few secs.
/Robert
Wednesday, April 28, 2004, 6:29:08 AM, Mick wrote:
Hi Robert.
I tried the best I could, and I cannot get this going...
Did you write the plugin? I think wether or not the directory is
mounting is relavtily easy to fix, the problem is making the directoy
visible in freevo only when the device is available.. This part of the
code I simply connot reverse engineer. To be honest, it looks like this
part of the code does not exist.. It seems so simple i'm a little bit
peaved I can't work out whats going on..
Maybe it is something inferred by something else.. Like the Dir item..
In any case i can only appoligise for being stupid.. But can someone
help me with this?
Mick
On Wed, 2004-04-21 at 02:49, Robert Winder wrote:
Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote:
Mick wrote:
Dischi,
Can you please explain to me how usbtorage.py is meant to funtion with
refference to usb.py?
No, I didn't wrote usbtorage.py. I can only say that usb.py will force
a menu rebuild when you add/remove usb devices.
I can't see any refference to calling mount or umount.. I'm happy to
make this my first contribution, but need your advice as to how its
meant to work..
It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it
used an automounter.
It doesn't.. so it's a bug then. Strange thing is i got it working with
camera.py a while ago without using automount. And usbstorage.py is
basicly the same code as camera.py was. Not sure where it goes wrong
but i look into it and i'll try to find out what the diff is. Probably
tomorrow.
Its such a simple process that I don't see the need to patch a
kernel or install another dependancy to get it going..
It should work using mount and umount.
What i meant was that for usb storage devices some kernelside options
are needed. In other words make sure if USB mounting works outside
freevo. :-) But we probably passed that stage.
/Robert
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi] NOT FIXED !!!
I give up.
It has something to do with the vfs implementation. But where it goes
wrong excactly i really can't tell. But what i said earlier
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
in misc.py still stands. Device shows up in menu but doesn't get
mounted. Pretty useless plugin then without the mounting part ;-)
Of course the USB HOTPLUG cmd can be used for mounting but i know
from personal experience that it mounted and umounted the usb device
whithout prob in freevo 1.4
/Robert
Friday, April 30, 2004, 12:23:26 PM, Robert wrote:
Hi,
oohps half way there, device shows up in menu but doesn't get mounted
automaticly. Gonna look a bit further into it.
/Robert
Friday, April 30, 2004, 11:05:21 AM, Robert wrote:
Hi,
Duh, a search through /proc/bus/usb/devices revealed the culprit.
Found the problem in misc.py line 300
if line.lower().find('mass storage') != -1:
should be
if line.lower().find('storage') != -1:
Probably kernel 2.4 and 2.6 usb/mass storage module naming is
different. A find for 'storage' is enough to get it going for both
modules
my cat /proc/bus/usb/devices
If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=ff Prot=01 Driver=usb-storage
Or changing back to usb_id as an identifier is maybe a better solution
if one has multiple usb-storage devices.
/Robert
Wednesday, April 28, 2004, 7:11:59 PM, Robert wrote:
Mick,
Sorry no i didn't wrote this stuff but last week i did give it another
try, but as i replied earlier i couldn't make it work also. What i
recall it did work somewhere last august, september. Early this year
camera.py changed into usbstorage.py but from what i can see in CVS
nothing changed substantially when doing a diff. The mounting and
making the mounted dir visible is indeed hacked away somewhere in the
process..
So imo there are two options:
- Find a freevo tarball from august, september last year and debug it
with this code. Problem is i can't find any freevo tarball 1.4 . If
someone can point me to it ? (complete tarball is bit easier then
browsing cvs, i think)
- as dischi stated earlier this week devel is a bit slow now and if
you doesn't want it to be buried in this list file it as a bug report.
Haven't got the time to this myself right know because i have to leave i
a few secs.
/Robert
Wednesday, April 28, 2004, 6:29:08 AM, Mick wrote:
Hi Robert.
I tried the best I could, and I cannot get this going...
Did you write the plugin? I think wether or not the directory is
mounting is relavtily easy to fix, the problem is making the directoy
visible in freevo only when the device is available.. This part of the
code I simply connot reverse engineer. To be honest, it looks like this
part of the code does not exist.. It seems so simple i'm a little bit
peaved I can't work out whats going on..
Maybe it is something inferred by something else.. Like the Dir item..
In any case i can only appoligise for being stupid.. But can someone
help me with this?
Mick
On Wed, 2004-04-21 at 02:49, Robert Winder wrote:
Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote:
Mick wrote:
Dischi,
Can you please explain to me how usbtorage.py is meant to funtion with
refference to usb.py?
No, I didn't wrote usbtorage.py. I can only say that usb.py will force
a menu rebuild when you add/remove usb devices.
I can't see any refference to calling mount or umount.. I'm happy to
make this my first contribution, but need your advice as to how its
meant to work..
It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it
used an automounter.
It doesn't.. so it's a bug then. Strange thing is i got it working with
camera.py a while ago without using automount. And usbstorage.py is
basicly the same code as camera.py was. Not sure where it goes wrong
but i look into it and i'll try to find out what the diff is. Probably
tomorrow.
Its such a simple process that I don't see the need to patch a
kernel or install another dependancy to get it going..
It should work using mount and umount.
What i meant was that for usb storage devices some kernelside options
are needed. In other words make sure if USB mounting works outside
freevo. :-) But we probably passed that stage.
/Robert
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi]
Mick, Sorry no i didn't wrote this stuff but last week i did give it another try, but as i replied earlier i couldn't make it work also. What i recall it did work somewhere last august, september. Early this year camera.py changed into usbstorage.py but from what i can see in CVS nothing changed substantially when doing a diff. The mounting and making the mounted dir visible is indeed hacked away somewhere in the process.. So imo there are two options: - Find a freevo tarball from august, september last year and debug it with this code. Problem is i can't find any freevo tarball 1.4 . If someone can point me to it ? (complete tarball is bit easier then browsing cvs, i think) - as dischi stated earlier this week devel is a bit slow now and if you doesn't want it to be buried in this list file it as a bug report. Haven't got the time to this myself right know because i have to leave i a few secs. /Robert Wednesday, April 28, 2004, 6:29:08 AM, Mick wrote: Hi Robert. I tried the best I could, and I cannot get this going... Did you write the plugin? I think wether or not the directory is mounting is relavtily easy to fix, the problem is making the directoy visible in freevo only when the device is available.. This part of the code I simply connot reverse engineer. To be honest, it looks like this part of the code does not exist.. It seems so simple i'm a little bit peaved I can't work out whats going on.. Maybe it is something inferred by something else.. Like the Dir item.. In any case i can only appoligise for being stupid.. But can someone help me with this? Mick On Wed, 2004-04-21 at 02:49, Robert Winder wrote: Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote: Mick wrote: Dischi, Can you please explain to me how usbtorage.py is meant to funtion with refference to usb.py? No, I didn't wrote usbtorage.py. I can only say that usb.py will force a menu rebuild when you add/remove usb devices. I can't see any refference to calling mount or umount.. I'm happy to make this my first contribution, but need your advice as to how its meant to work.. It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it used an automounter. It doesn't.. so it's a bug then. Strange thing is i got it working with camera.py a while ago without using automount. And usbstorage.py is basicly the same code as camera.py was. Not sure where it goes wrong but i look into it and i'll try to find out what the diff is. Probably tomorrow. Its such a simple process that I don't see the need to patch a kernel or install another dependancy to get it going.. It should work using mount and umount. What i meant was that for usb storage devices some kernelside options are needed. In other words make sure if USB mounting works outside freevo. :-) But we probably passed that stage. /Robert --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi]
Hi Robert. I tried the best I could, and I cannot get this going... Did you write the plugin? I think wether or not the directory is mounting is relavtily easy to fix, the problem is making the directoy visible in freevo only when the device is available.. This part of the code I simply connot reverse engineer. To be honest, it looks like this part of the code does not exist.. It seems so simple i'm a little bit peaved I can't work out whats going on.. Maybe it is something inferred by something else.. Like the Dir item.. In any case i can only appoligise for being stupid.. But can someone help me with this? Mick On Wed, 2004-04-21 at 02:49, Robert Winder wrote: Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote: Mick wrote: Dischi, Can you please explain to me how usbtorage.py is meant to funtion with refference to usb.py? No, I didn't wrote usbtorage.py. I can only say that usb.py will force a menu rebuild when you add/remove usb devices. I can't see any refference to calling mount or umount.. I'm happy to make this my first contribution, but need your advice as to how its meant to work.. It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it used an automounter. It doesn't.. so it's a bug then. Strange thing is i got it working with camera.py a while ago without using automount. And usbstorage.py is basicly the same code as camera.py was. Not sure where it goes wrong but i look into it and i'll try to find out what the diff is. Probably tomorrow. Its such a simple process that I don't see the need to patch a kernel or install another dependancy to get it going.. It should work using mount and umount. What i meant was that for usb storage devices some kernelside options are needed. In other words make sure if USB mounting works outside freevo. :-) But we probably passed that stage. /Robert --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: [Freevo-users] Re: usb mass storage help please [attn Dischi]
Tuesday, April 20, 2004, 5:01:50 PM, Dirk wrote: Mick wrote: Dischi, Can you please explain to me how usbtorage.py is meant to funtion with refference to usb.py? No, I didn't wrote usbtorage.py. I can only say that usb.py will force a menu rebuild when you add/remove usb devices. I can't see any refference to calling mount or umount.. I'm happy to make this my first contribution, but need your advice as to how its meant to work.. It should mount. If it doesn't, it's a bug. Maybe the guy who wrote it used an automounter. It doesn't.. so it's a bug then. Strange thing is i got it working with camera.py a while ago without using automount. And usbstorage.py is basicly the same code as camera.py was. Not sure where it goes wrong but i look into it and i'll try to find out what the diff is. Probably tomorrow. Its such a simple process that I don't see the need to patch a kernel or install another dependancy to get it going.. It should work using mount and umount. What i meant was that for usb storage devices some kernelside options are needed. In other words make sure if USB mounting works outside freevo. :-) But we probably passed that stage. /Robert --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
