On Sun, Jan 02, 2011 at 11:49:06AM +, Camaleón wrote:
> On Sat, 01 Jan 2011 16:13:34 -0500, Thomas H. George wrote:
>
> > On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote:
>
> >> Those steps are about how to "sync" your music/photos, but I think the
> >> most important part is the "if
On Sat, 01 Jan 2011 16:13:34 -0500, Thomas H. George wrote:
> On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote:
>> Those steps are about how to "sync" your music/photos, but I think the
>> most important part is the "ifuse" package that allows the device to be
>> mounted as a mass storage
On Sat, Jan 01, 2011 at 04:56:50PM +, Camaleón wrote:
> On Sat, 01 Jan 2011 09:26:51 -0500, Thomas H. George wrote:
>
> > On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote:
>
> >> There is a Debian wiki page about the iphone/ipod:
> >>
> >> http://wiki.debian.org/iPhone
> >>
> > This
On Sat, 01 Jan 2011 09:26:51 -0500, Thomas H. George wrote:
> On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote:
>> There is a Debian wiki page about the iphone/ipod:
>>
>> http://wiki.debian.org/iPhone
>>
> This link got me a bit further but seems to apply just to the iPhone.
It shou
On Fri, Dec 31, 2010 at 08:54:28AM +, Camaleón wrote:
> On Thu, 30 Dec 2010 13:00:32 -0500, Thomas H. George wrote:
>
> > For Christmas I was given an ipod. When connected to a usb port the
> > system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the
> > following response.
>
> (
On Thu, 30 Dec 2010 13:00:32 -0500, Thomas H. George wrote:
> For Christmas I was given an ipod. When connected to a usb port the
> system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the
> following response.
(...)
Apple products are "special" devices. You need more than magic to
For Christmas I was given an ipod. When connected to a usb port the
system (Debian Squeeze, linux-2.6.32-5-amd64 stock kernel) gives the
following response.
Dec 30 10:14:22 dragon kernel: [ 3706.552517] usb 1-2: new high speed USB
device using ehci_hcd and address 10
Dec 30 10:14:23 dragon kerne
Justin Piszcz <[EMAIL PROTECTED]> writes:
> Anyone here have a Microtek SCSI scanner?
>
> In the past I've used scsiadd -s which would add the new device, this
> still works with udev but the symbolic link/permissions/etc are never
> created correctly.
>
> When I run the udev scan utility, my mode
Anyone here have a Microtek SCSI scanner?
In the past I've used scsiadd -s which would add the new device, this
still works with udev but the symbolic link/permissions/etc are never
created correctly.
When I run the udev scan utility, my model does not have a specific name,
just "Scanner" - bu
Kudret Güler <[EMAIL PROTECTED]> writes:
> udev creates /dev/hdc(burner) with permissions 640 and with owner
> root.hal. Therefore hal group members cannot burn. And any change is
> reversed on reboot. How can I tell udev to create it with permissions
> 660? Or should I just put it in a script to
On Thu, 09 Dec 2004 08:48:04 -0500, Adam Aube <[EMAIL PROTECTED]> wrote:
> root.cdrom. What version of udev do you have? Have you modified any files
> under /etc/udev?
I hadn't modified any files then. udev version is 0.046-6
Maintainer informed me that it was a bug resolved in the next version.
On Thu, 2004-12-09 at 02:37 -0500, Kudret Güler wrote:
> udev creates /dev/hdc(burner) with permissions 640 and with owner
> root.hal. Therefore hal group members cannot burn. And any change is
> reversed on reboot. How can I tell udev to create it with permissions
> 660? Or should I just put it in
Kudret Güler wrote:
> udev creates /dev/hdc(burner) with permissions 640 and with owner
> root.hal. Therefore hal group members cannot burn. And any change is
> reversed on reboot. How can I tell udev to create it with permissions
> 660? Or should I just put it in a script to chmod /dev/hdc on eve
> udev creates /dev/hdc(burner) with permissions 640 and with owner
> root.hal. Therefore hal group members cannot burn. And any change is
> reversed on reboot. How can I tell udev to create it with permissions
> 660? Or should I just put it in a script to chmod /dev/hdc on every
> boot?
1. Use
udev creates /dev/hdc(burner) with permissions 640 and with owner
root.hal. Therefore hal group members cannot burn. And any change is
reversed on reboot. How can I tell udev to create it with permissions
660? Or should I just put it in a script to chmod /dev/hdc on every
boot?
--
To UNSUBSCRIBE
Sorry it took so long to get back to you, but I've been somewhat busy.
Sam Halliday <[EMAIL PROTECTED]> writes:
>> Sam Halliday writes:
>> > however... there is one major problem! instead of creating the link to
>> > /dev/input/mouseX, it is creating to the link to /dev/input/ts2, which
>> > does
John L Fjellstad wrote:
> Sam Halliday writes:
> > however... there is one major problem! instead of creating the link to
> > /dev/input/mouseX, it is creating to the link to /dev/input/ts2, which
> > does not appear to be a valid mouse device. how can i fix it? (ts2
> > appears only when the usb m
Sam Halliday <[EMAIL PROTECTED]> writes:
> however... there is one major problem! instead of creating the link to
> /dev/input/mouseX, it is creating to the link to /dev/input/ts2, which
> does not appear to be a valid mouse device. how can i fix it? (ts2
> appears only when the usb mouse is plugg
Derrick 'dman' Hudson <[EMAIL PROTECTED]> writes:
> Alternatively use /dev/input/mice and your application will receive
> input from all attached mice. Simple. :-) (with kernel 2.6 that
> includes USB -and- PS/2 mice)
Interesting. I didn't know this. Just used the section that worked when
I u
John L Fjellstad wrote:
> Sam Halliday writes:
> > i would very much like to have a symlink set up by udev
> > (/dev/input/mousemain or similar) which points to the /dev/input/mouseX
> > unless it has been removed, in which case it should be pointed to
> > /dev/input/mouse1.
> >
> > unfortunately t
On Wed, Jul 07, 2004 at 12:24:39PM -0400, Derrick 'dman' Hudson wrote:
> On Wed, Jul 07, 2004 at 03:09:31AM +0100, Sam Halliday wrote:
> [...]
> | i want to DISABLE the touchpad when the usb mouse is plugged in.
>
> Oh. I don't know how to do that as I've never tried (and never wanted
> to). I t
Sam Halliday <[EMAIL PROTECTED]> writes:
>> You don't. In X, what you do is make one your primary mouse device,
>> and the other just sends mouse events to the primary mouse device. So,
>> at my place, the touchpad is the primary mouse device, and the usbmouse,
>> when plugged in, sends mouse e
On Wed, Jul 07, 2004 at 03:09:31AM +0100, Sam Halliday wrote:
[...]
| i want to DISABLE the touchpad when the usb mouse is plugged in.
Oh. I don't know how to do that as I've never tried (and never wanted
to). I think some BIOSes support that (at least for PS/2 mice).
Sorry I can't help with thi
Derrick 'dman' Hudson wrote:
> John L Fjellstad wrote:
> | Sam Halliday writes:
> |
> | > however that only solves half the problem... how can i make this
> | > /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1
> | > (the touchpad) when the usb mouse is not plugged in?
> |
> |
John L Fjellstad wrote:
> Sam Halliday <[EMAIL PROTECTED]> writes:
>
> > however that only solves half the problem... how can i make this
> > /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1
> > (the touchpad) when the usb mouse is not plugged in?
>
> You don't. In X, what
On Tue, Jul 06, 2004 at 10:51:10AM +0200, John L Fjellstad wrote:
| Sam Halliday <[EMAIL PROTECTED]> writes:
|
| > however that only solves half the problem... how can i make this
| > /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1
| > (the touchpad) when the usb mouse is not
Sam Halliday <[EMAIL PROTECTED]> writes:
> however that only solves half the problem... how can i make this
> /dev/usbmouse link (or whatever i call it) point to /dev/input/mouse1
> (the touchpad) when the usb mouse is not plugged in?
You don't. In X, what you do is make one your primary mouse
John L Fjellstad wrote:
> Sam Halliday writes:
> > i would very much like to have a symlink set up by udev
> > (/dev/input/mousemain or similar) which points to the /dev/input/mouseX
> > unless it has been removed, in which case it should be pointed to
> > /dev/input/mouse1.
> >
> > unfortunately
Sam Halliday <[EMAIL PROTECTED]> writes:
> i would very much like to have a symlink set up by udev (/dev/input/mousemain or
> similar) which points to the /dev/input/mouseX unless it has been removed, in
> which case it should be pointed to /dev/input/mouse1.
>
> unfortunately the /dev/input/mouse
hi there,
i was wondering if somebody could help me set up udev to make symlinks in a
specific way...
i have 2 mouse input devices... one is always connected (/dev/input/mouse1) and
another is a usbmouse and appears as (/dev/input/mouseX), with X increasing
every time i remove and reconnect it.
30 matches
Mail list logo
