Linux device management - Revision history

Woozle: /* Notes / umm, I meant*...

2007-04-12T14:42:01Z

Notes: umm, I *meant*...

← Older revision		Revision as of 14:42, 12 April 2007
Line 23:		Line 23:
	Bus 001 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub		Bus 001 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
	Bus 001 Device 001: ID 0000:0000		Bus 001 Device 001: ID 0000:0000
	* Look inside '''/dev/bus/usb'''. In the case of the above results, you would see the folder '''/dev/bus/usb/001''', and inside that a device called '''~~007~~'''. Change the permissions of ~~007~~ so it is readable and writable by your user account.		* Look inside '''/dev/bus/usb'''. In the case of the above results, you would see the folder '''/dev/bus/usb/001''', and inside that a device called '''013'''. Change the permissions of 013 so it is readable and writable by your user account.

	Various things may reset this permission before you can actually view it for files, so if you get a message that the camera can't be read, try resetting the permissions again (without closing anything) and retry accessing the camera.		Various things may reset this permission before you can actually view it for files, so if you get a message that the camera can't be read, try resetting the permissions again (without closing anything) and retry accessing the camera.

Woozle: /* Text */ notes about digikam not being able to read C360

2007-04-12T14:41:05Z

Text: notes about digikam not being able to read C360

← Older revision		Revision as of 14:41, 12 April 2007
Line 14:		Line 14:

	[[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the kernel, and exports basic information about the devices currently plugged into your system. udev can use this information to create device nodes corresponding to your hardware. sysfs is mounted at /sys and is browsable. You may wish to investigate some of the files stored there before getting to grips with udev. Throughout this document, I will use the terms /sys and SYSFS interchangeably.		[[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the kernel, and exports basic information about the devices currently plugged into your system. udev can use this information to create device nodes corresponding to your hardware. sysfs is mounted at /sys and is browsable. You may wish to investigate some of the files stored there before getting to grips with udev. Throughout this document, I will use the terms /sys and SYSFS interchangeably.
			==Notes==
			Mysterious message where digiKam (or other digital camera app) used to be able to talk to a camera (in our case, the [[Kodak EasyShare C360]] and suddenly can't: the problem seems to be with permissions on the device; you need to be able to ''write'' as well as read to it. This is probably a change in the udev configuration or something related, and I'll figure that out later, but for now the way to get it working is:
			* Run {{linuxcmd\|lsusb}} (on some distros, you need to type '''/sbin/lsusb''') – sample output:
			woozle@gonzo:~$ lsusb
			Bus 002 Device 001: ID 0000:0000
			{{hilite\|Bus 001 Device 013: ID 040a:0589 Kodak Co.}}
			Bus 001 Device 007: ID 0923:010f IC Media Corp. SIIG MobileCam
			Bus 001 Device 002: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
			Bus 001 Device 001: ID 0000:0000
			* Look inside '''/dev/bus/usb'''. In the case of the above results, you would see the folder '''/dev/bus/usb/001''', and inside that a device called '''007'''. Change the permissions of 007 so it is readable and writable by your user account.

			Various things may reset this permission before you can actually view it for files, so if you get a message that the camera can't be read, try resetting the permissions again (without closing anything) and retry accessing the camera.

Woozle: Device management moved to Linux device management

2005-10-14T18:03:47Z

Device management moved to Linux device management

← Older revision	Revision as of 18:03, 14 October 2005
(No difference)

Woozle: cleaned up by copying directly from hypertwiki

2005-10-14T18:03:25Z

cleaned up by copying directly from hypertwiki

← Older revision		Revision as of 18:03, 14 October 2005
Line 1:		Line 1:
	[[Linux]]:		[[Computing]]: [[Linux]]: [[Linux device management\|device management]]
	[[~~Device~~ management]]
	==Notes==		==Notes==
	This text seemed like it might be useful information, even if it		This text seemed like it might be useful information, even if it contained some inaccuracies. Original document was published under [http://www.gnu.org/licenses/gpl.html GNU General Public License, Version 2], and those with appropriate knowledge should feel free to edit or expand the text.
	contained some inaccuracies. Original document was published under
	[http://www.gnu.org/licenses/gpl.html GNU General Public License,
	Version 2], and those with appropriate knowledge should feel free to
	edit or expand the text.
	==Edit Log==		==Edit Log==
	* '''2005-10-05''' Copied from		* '''2005-10-05''' Copied from http://www.reactivated.net/writing_udev_rules.html, with minor editing for clarity; the below was originally part of the udev article but seemed to belong here instead. The rest of the article should be checked to make sure it still makes sense without the introduction.
	http://www.reactivated.net/writing_udev_rules.html, with minor editing
	for clarity; the below was originally part of the udev article but
	seemed to belong here instead. The rest of the article should be
	checked to make sure it still makes sense without the introduction.
	==Text==		==Text==
	A basic introduction only, might not be totally accurate.		A basic introduction only, might not be totally accurate.
	On typical linux-based systems, the /dev directory is used to store
	file-like device nodes which refer to certain devices in the system.		On typical linux-based systems, the /dev directory is used to store file-like device nodes which refer to certain devices in the system. Each node points to a part of the system (a device), which might or might not exist. Userspace applications can use these device nodes to interface with the systems hardware, for example, XFree86 will "listen to" /dev/input/mice so that it can relate the users mouse movements to moving the visual mouse pointer.
	Each node points to a part of the system (a device), which might or
	might not exist. Userspace applications can use these device nodes to		The original /dev directories were just populated with every device that might possibly appear in the system. /dev directories were typically very large because of this. devfs came along to provide a more managable approach (noticably, it only populated /dev with hardware that is plugged into the system), as well as some other functionality, but the system proved to have problems which could not be easily fixed.
	interface with the systems hardware, for example, XFree86 will "listen
	to" /dev/input/mice so that it can relate the users mouse movements to		[[udev]] is the "new" way of managing /dev directories, designed to clear up some issues with previous /dev implementations, and provide a robust path forward. In order to create and name /dev device nodes corresponding to devices that are present in the system, udev relies on matching information provided by sysfs with rules provided by the user.
	moving the visual mouse pointer.
	The original /dev directories were just populated with every device		[[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the kernel, and exports basic information about the devices currently plugged into your system. udev can use this information to create device nodes corresponding to your hardware. sysfs is mounted at /sys and is browsable. You may wish to investigate some of the files stored there before getting to grips with udev. Throughout this document, I will use the terms /sys and SYSFS interchangeably.
	that might possibly appear in the system. /dev directories were
	typically very large because of this. devfs came along to provide a
	more managable approach (noticably, it only populated /dev with
	hardware that is plugged into the system), as well as some other
	functionality, but the system proved to have problems which could not
	be easily fixed.
	[[udev]] is the "new" way of managing /dev directories, designed to
	clear up some issues with previous /dev implementations, and provide a
	robust path forward. In order to create and name /dev device nodes
	corresponding to devices that are present in the system, udev relies on
	matching information provided by sysfs with rules provided by the user.
	[[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the
	kernel, and exports basic information about the devices currently
	plugged into your system. udev can use this information to create
	device nodes corresponding to your hardware. sysfs is mounted at /sys
	and is browsable. You may wish to investigate some of the files stored
	there before getting to grips with udev. Throughout this document, I
	will use the terms /sys and SYSFS interchangeably.

Woozle: /* Edit Log */

2005-10-06T01:29:09Z

Edit Log

← Older revision		Revision as of 01:29, 6 October 2005
Line 10:		Line 10:
	* '''2005-10-05''' Copied from		* '''2005-10-05''' Copied from
	http://www.reactivated.net/writing_udev_rules.html, with minor editing		http://www.reactivated.net/writing_udev_rules.html, with minor editing
	for clarity		for clarity; the below was originally part of the udev article but
			seemed to belong here instead. The rest of the article should be
			checked to make sure it still makes sense without the introduction.
	==Text==		==Text==
	A basic introduction only, might not be totally accurate.		A basic introduction only, might not be totally accurate.

Woozle: added "edit log"

2005-10-05T22:51:17Z

added "edit log"

← Older revision		Revision as of 22:51, 5 October 2005
Line 1:		Line 1:
	[[Linux]]:		[[Linux]]:
	~~Devices~~		[[Device management]]
	==Notes==		==Notes==
	*Copied from http://www.reactivated.net/writing_udev_rules.html because		This text seemed like it might be useful information, even if it
	it seemed like it might be useful information, even if it contained		contained some inaccuracies. Original document was published under
	some inaccuracies. Original document was published under
	[http://www.gnu.org/licenses/gpl.html GNU General Public License,		[http://www.gnu.org/licenses/gpl.html GNU General Public License,
	Version 2].		Version 2], and those with appropriate knowledge should feel free to
	==~~Original~~ Text==		edit or expand the text.
			==Edit Log==
			* '''2005-10-05''' Copied from
			http://www.reactivated.net/writing_udev_rules.html, with minor editing
			for clarity
			==Text==
	A basic introduction only, might not be totally accurate.		A basic introduction only, might not be totally accurate.
	On typical linux-based systems, the /dev directory is used to store		On typical linux-based systems, the /dev directory is used to store

Woozle: /* Original Text */ internal links for udev & sysfs

2005-10-05T22:47:11Z

Original Text: internal links for udev & sysfs

← Older revision		Revision as of 22:47, 5 October 2005
Line 23:		Line 23:
	functionality, but the system proved to have problems which could not		functionality, but the system proved to have problems which could not
	be easily fixed.		be easily fixed.
	udev is the "new" way of managing /dev directories, designed to clear		[[udev]] is the "new" way of managing /dev directories, designed to
	up some issues with previous /dev implementations, and provide a robust		clear up some issues with previous /dev implementations, and provide a
	path forward. In order to create and name /dev device nodes		robust path forward. In order to create and name /dev device nodes
	corresponding to devices that are present in the system, udev relies on		corresponding to devices that are present in the system, udev relies on
	matching information provided by sysfs with rules provided by the user.		matching information provided by sysfs with rules provided by the user.
	sysfs is a new filesystem to the 2.6 kernels. It is managed by the		[[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the
	kernel, and exports basic information about the devices currently		kernel, and exports basic information about the devices currently
	plugged into your system. udev can use this information to create		plugged into your system. udev can use this information to create

Woozle at 22:34, 5 October 2005

2005-10-05T22:34:22Z

New page

[[Linux]]:
Devices
==Notes==
*Copied from http://www.reactivated.net/writing_udev_rules.html because
it seemed like it might be useful information, even if it contained
some inaccuracies. Original document was published under
[http://www.gnu.org/licenses/gpl.html GNU General Public License,
Version 2].
==Original Text==
A basic introduction only, might not be totally accurate.
On typical linux-based systems, the /dev directory is used to store
file-like device nodes which refer to certain devices in the system.
Each node points to a part of the system (a device), which might or
might not exist. Userspace applications can use these device nodes to
interface with the systems hardware, for example, XFree86 will "listen
to" /dev/input/mice so that it can relate the users mouse movements to
moving the visual mouse pointer.
The original /dev directories were just populated with every device
that might possibly appear in the system. /dev directories were
typically very large because of this. devfs came along to provide a
more managable approach (noticably, it only populated /dev with
hardware that is plugged into the system), as well as some other
functionality, but the system proved to have problems which could not
be easily fixed.
udev is the "new" way of managing /dev directories, designed to clear
up some issues with previous /dev implementations, and provide a robust
path forward. In order to create and name /dev device nodes
corresponding to devices that are present in the system, udev relies on
matching information provided by sysfs with rules provided by the user.
sysfs is a new filesystem to the 2.6 kernels. It is managed by the
kernel, and exports basic information about the devices currently
plugged into your system. udev can use this information to create
device nodes corresponding to your hardware. sysfs is mounted at /sys
and is browsable. You may wish to investigate some of the files stored
there before getting to grips with udev. Throughout this document, I
will use the terms /sys and SYSFS interchangeably.