
Thanks for looking into, SlashBeast!SlashBeast wrote:lsusb here goes thru /dev/bus/usb and /sys/bus/usb/devices, check if you have anything on given paths.
Code: Select all
# ls /proc/bus/
input pci
# ls /dev/bus
ls cannot access /dev/bus: No such file or directory
#
Code: Select all
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
[ X.xxxxxx] ALSA device list:
[ X.xxxxxx] No soundcards found.
[ X.xxxxxx] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ X.xxxxxx] ata2.00: ATA-8: ST20000M001-... UDMA/133
[ X.xxxxxx] ata2.00: 3987029568 sectors, multi 16: ... NCQ
[ X.xxxxxx] ata2:00: configured for UDMA/133
[ X.xxxxxx] scsi 1:0:0:0: Direct-Access ATA ST20000M001-...
[ X.xxxxxx] sd 1:0:0:0; [sda] ...
[ X.xxxxxx] sd 1:0:0:0; Attached scsi generic sg0 type 0
[ X.xxxxxx] sd 1:0:0:0; 4096-byte physical blocks
[ X.xxxxxx] sd 1:0:0:0;
[ X.xxxxxx] sd 1:0:0:0;
[ X.xxxxxx] sda: sda1 sda2 sda3 ...
[ X.xxxxxx] ata3: SATA link up 1.5 Gbps
[ X.xxxxxx]
[ X.xxxxxx]
[ X.xxxxxx]
[ X.xxxxxx] scsi 2:0:0:0: CD-ROM HD-DT-ST BD-RE ...
[ X.xxxxxx] sr0: scsi3-mmc drive 40x/40x writer ...
[ X.xxxxxx] cdrom
[ X.xxxxxx] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ X.xxxxxx] psmouse serial: alps: Unknown ALPS touchpad: E8=10 00 64, EC=10 ...
[ X.xxxxxx] input: InPS/2 Generic Wheel Mouse as
/devices/platform/i8042/serio1/input/input4
[ X.xxxxxx] md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
[ X.xxxxxx] EXT4-fs (sda3): couldn't mount as ext3 due to feature incompatibilities
[ X.xxxxxx] EXT4-fs (sda3): couldn't mount as ext2 due to feature incompatibilities
[ X.xxxxxx] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ X.xxxxxx] VFS: Mounted root (ext4 filesystem) readonly on device 8:3.
[ X.xxxxxx] Switched to clocksource tsc
[ X.xxxxxx] Freeing unused kernel memory: 1064K (fffffff..... )
[ X.xxxxxx] grsec: exec of /sbin/init (/sbin/init ) by /sbin/init(swapper/0:1]
uid/euid:0/0 gid/egid:0/0, parent /[swapper/0:0] uid/eudi:0/0 gid/egid:0/0
INIT: version 2.08 booting
[ X.xxxxxx]grsec: exec of /sbin/rc ... parent /sbin/init ...
[ X.xxxxxx]grsec: chdir to / by /sbin/rc ... parent /sbin/init ...
[ X.xxxxxx]random: nonblocking pool is initilized
[ X.xxxxxx]grsec: exec of /lib64/rc/sh/init-early.sh parent /sbin/rc
[ X.xxxxxx]grsec: exec of /usr/bin/kbd_mode (kbd_mode -u -C /dev/console ) ...
parent /lib64/rc/sh/init-early.sh ...
[ X.xxxxxx]grsec: exec of /usr/bin/loadkeys (loadkeys -q /lib64/rc/console/keymap ) ...
OpenRC 0.12.4 is starting up Gentoo Linux (x86_64)
[ X.xxxxxx] grsec: exec of /lib64/rc/sh/init.sh ... parent /sbin/rc ...
[ X.xxxxxx] grsec: exec of /sbin/rc (eval_ecolors ) ... parent /lib64/rc/sh/init.sh
[ X.xxxxxx] grsec: exec of /sbin/rc (ebegin Mounting /proc ) ... parent
/lib64/rc/sh/init.sh
* Mounting /proc
[ X.xxxxxx] grsec: exec of /sbin/rc (fstabinfo --mount /proc ) ... parent
/lib64/rc/sh/init.sh
[ X.xxxxxx] grsec: exec of /bin/mount (mount -n -t proc -o noexec,nosuid,nodev
proc /proc ) by /bin/mount[init.sh:1262] uid/euid:0/0 gid/egid:0:0
[ X.xxxxxx] grsec: mount of proc to /proc by /bin/mount ... parent /lib64/rc/sh/init.sh
[ X.xxxxxx] grsec: exec of /bin/rc (eend 0) by /sbin/rc
[ X.xxxxxx] grsec: exec of /sbin/rc (rc --sys ) by
[ X.xxxxxx] grsec: chdir to / by /sbin/rc
[ X.xxxxxx] grsec: exec of /sbin/rc (mountinfo -q /run ) by /sbin/rc
[ X.xxxxxx] grsec: exec of /sbin/rc (ebagin Mounting /run )
* Mounting /run ...
[ X.xxxxxx] grsec: exec of /sbin/rc (fstabinfo --mount /run ) by /sbin/rc
[ X.xxxxxx] grsec: exec of /bin/mount (mount -t tmpfs -o
mode=0755,nosuid,nodev,size=10% tmpfs /run ) by /bin/mount ... parent
/lib64/sh/init.sh ...
[ X.xxxxxx] grsec: mount of tmpfs to /run ...
[ X.xxxxxx] grsec: exec of /sbin/rc (checkpath -d /run/openrc )
* /run/openrc: creating directory
[ X.xxxxxx] grsec: exec of /sbin/rc (checkpath -d -m 0775 -o root:uucp/run/lock
* /run/lock: creating directory
[ X.xxxxxx] grsec: exec of /bin/grep (grep -Eq [[:space:]]+xenfs$
/proc/filesystems ) by /bin/grep[init.sh:1273] uid/euid ... parent ... init.sh
...
[ X.xxxxxx] grsec: exec of /bin/cp (cp -p /lib64/rc/cache/depconfig
/lib64/rc/cache/deptree /lib64/rc/cache/nettree /lib64/rc/cache/rc.log
/lib64/rc/cache/softlevel) ...
[ X.xxxxxx] grsec: exec of /etc/init.d/devfs (/etc/init.d/devfs --lockfd 5 start )
[ X.xxxxxx] grsec: chdir to / by /etc/init.d/devfs...
[ X.xxxxxx] grsec: exec of /lib64/rc/sh/runscript.sh (/lib64/rc/sh/runscript.sh
/etc/init.d/devfs start ) ...
[ X.xxxxxx] grsec: exec of /sbin/rc (eval_ecolors ... parent /lib64/rc/sh/rumscript.sh
[ X.xxxxxx] grsec: exec of grep ... mqueue ... /proc/filesystems
[ X.xxxxxx] grsec: exec of mountinfo -q /dev/mqueue
[ X.xxxxxx] grsec: exec of /bin/mkdir (mkdir -m 1777 -p /dev/mqueue ...
[ X.xxxxxx] grsec: chdir to /dev
[ X.xxxxxx] grsec: exec of ebegin Mounting mqueue ...
* Mounting /dev/mqueue ...
...
...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
* Mounting /dev/pts ...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
[ X.xxxxxx] grsec: exec of ...
* Mounting /sys ...
* Mounting debug filesystem ...
* Mounting cgroup filesystem ...
* setting up tmpfiles.d entries for /dev ...
* Mounting /dev (mdev) ...
* Setting up mdev as hotplug agent ...
* Loading kernel modules for detected hardware ...
* Mounting /dev/pts ...
* Mounting /dev/shm ...
* Setting system clock using the hardware clock [UTC]... [ok]
* Loading module snd-hda-intel ... [ok]
* Autoloaded 1 module(s) [ok]
* Starting lvmetad ... [ok]
* Setting up the Logical Volume Manager ... [ok]
* Checking local filesystems ...
/dev/sda2 ...
/dev/sda3 ... [ok]
* Remounting root filesystem read/write ..
* Remounting filesystems ..
* Updating /etc/mtab ... [ok]
* activating swap devices ... [ok]
* Mounting local filesystems ...
* Configuring kernel param...
* Creating user login records ..
* Wiping /tmp...
* Restoring Mixer Levels ...
* Setting hostname...
* Setting terminal encoding [UTF-8] ...
* Setting keyboard mode [UTF-8] ...
* Loading key mappings...
...

I do.SlashBeast wrote:Are you using mine mdev-like-a-boss?
Do you have anything in /sys/bus/usb/devices/?
Code: Select all
ls -l /sys/but/usb/
total 0
drwx------ 2 root root 0 2014-06-06 19:56 devices
....
Code: Select all
# ls -l /sys/bus/usb/devices/
total 0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 10-0:1.0 -> ../../../devices/pci0000:00/0000:00:0a.0/0000:03:00.0/usb10/10-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:12.2/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 11-0:1.0 -> ../../../devices/pci0000:00/0000:00:0a.0/0000:03:00.0/usb11/11-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:13.2/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 3-0:1.0 -> ../../../devices/pci0000:00/0000:00:16.2/usb3/3-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 4-0:1.0 -> ../../../devices/pci0000:00/0000:00:12.0/usb4/4-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 5-0:1.0 -> ../../../devices/pci0000:00/0000:00:13.0/usb5/5-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 6-0:1.0 -> ../../../devices/pci0000:00/0000:00:14.5/usb6/6-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 7-0:1.0 -> ../../../devices/pci0000:00/0000:00:16.0/usb7/7-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 8-0:1.0 -> ../../../devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8/8-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 18:52 9-0:1.0 -> ../../../devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb9/9-0:1.0
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb1 -> ../../../devices/pci0000:00/0000:00:12.2/usb1
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb10 -> ../../../devices/pci0000:00/0000:00:0a.0/0000:03:00.0/usb10
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb11 -> ../../../devices/pci0000:00/0000:00:0a.0/0000:03:00.0/usb11
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb2 -> ../../../devices/pci0000:00/0000:00:13.2/usb2
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb3 -> ../../../devices/pci0000:00/0000:00:16.2/usb3
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb4 -> ../../../devices/pci0000:00/0000:00:12.0/usb4
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb5 -> ../../../devices/pci0000:00/0000:00:13.0/usb5
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb6 -> ../../../devices/pci0000:00/0000:00:14.5/usb6
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb7 -> ../../../devices/pci0000:00/0000:00:16.0/usb7
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb8 -> ../../../devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8
lrwxrwxrwx 1 root root 0 2014-06-06 19:57 usb9 -> ../../../devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb9
#
Code: Select all
/sys/bus/usb/devices/10-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/1-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
port5
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/11-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/2-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
port5
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/3-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/4-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
port5
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/5-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
port5
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/6-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/7-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
port3
port4
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/8-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/9-0:1.0
bAlternateSetting
bInterfaceClass
bInterfaceNumber
bInterfaceProtocol
bInterfaceSubClass
bNumEndpoints
driver
ep_81
modalias
port1
port2
power
subsystem
supports_autosuspend
uevent
----------------------
/sys/bus/usb/devices/usb1
1-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb10
10-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb11
11-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb2
2-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb3
3-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb4
4-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb5
5-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb6
6-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb7
7-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb8
8-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
/sys/bus/usb/devices/usb9
9-0:1.0
authorized
authorized_default
avoid_reset_quirk
bcdDevice
bConfigurationValue
bDeviceClass
bDeviceProtocol
bDeviceSubClass
bmAttributes
bMaxPacketSize0
bMaxPower
bNumConfigurations
bNumInterfaces
busnum
configuration
descriptors
dev
devnum
devpath
driver
ep_00
idProduct
idVendor
ltm_capable
manufacturer
maxchild
power
product
quirks
removable
remove
serial
speed
subsystem
uevent
urbnum
version
----------------------
Absolutely so.SlashBeast wrote:Are you using mine mdev-like-a-boss?

Code: Select all
#!/bin/sh
for i in /sys/bus/usb/devices/*; do
case "${i##*/}" in
[0-9]*-[0-9]*)
printf 'add' > "$i/uevent"
;;
esac
doneCode: Select all
SUBSYSTEM=usb;DEVTYPE=usb_device;.* root:root 660 */opt/mdev/helpers/proc-bus-usbA.S.A.P, but in a while, due to non-online system.SlashBeast wrote:Try to run as root:
You can save it as script and run, that's should poke mdev to create nodes for usb,Code: Select all
#!/bin/sh for i in /sys/bus/usb/devices/*; do case "${i##*/}" in [0-9]*-[0-9]*) printf 'add' > "$i/uevent" ;; esac done
You should have someting like it in /etc/mdev.conf:And script should exist /opt/mdev/helpers/proc-bus-usbCode: Select all
SUBSYSTEM=usb;DEVTYPE=usb_device;.* root:root 660 */opt/mdev/helpers/proc-bus-usb
Try to check on it first.
Code: Select all
case "${i##*/}" inCode: Select all
prinf 'add' > "$i/uevent"Code: Select all
#!/bin/bash
for i in `ls -1d /sys/bus/usb/devices/1-0\:1.0/*` ; do
if [ -d "$i" ] ; then
cd "$i" ;
pwd ;
for j in `ls -1` ; do
echo $j ;
ls -l $j ;
if [ ! -d "$j" ] ; then
echo "$j" ;
ls -l "$j" ;
cat "$j" ;
read FAKE ;
else cd "$j" ;
for k in `ls -1` ; do
cat "$k" ;
read FAKE ;
cd - ;
done ;
fi ;
read FAKE ;
done ;
cd - ;
else cat "$i" ;
read FAKE ;
fi ;
read FAKE ;
done ;
Code: Select all
unable to initialize libusb: -99
Wow.But so far, I have found nowhere in that dir reference to
/opt/mdev/helpers/proc-bus-usb .

My understanding is if /etc/portage/package.use containsmiroR wrote:There are unclarities on the use of eudev and hwid programs, and some other minor compiaints, though, so who knows?
Code: Select all
sys-fs/eudev -*
sys-fs/udev -*Code: Select all
sys-fs/udev-init-scripts-10
sys-fs/udev-init-scripts-26Code: Select all
sys-fs/udev-208
sys-fs/udev-212I ran it. I thought it was just a script that searches through and reads something somewhere in that dir.SlashBeast wrote:Wow.But so far, I have found nowhere in that dir reference to
/opt/mdev/helpers/proc-bus-usb .
The snippet I've provided you just send 'add' event for usb devices as simple `mdev -s` does not goes thru usb devices.
My script just reads (with simple 'cat') any entries in those dirs that are files (if it can, some it can't for some reason), and if not, it descends into those dirs and tries to read files in that dir. I thought I needed to find the string /opt/mdev/helpers/proc-bus-usb for some reason in those files in some of those dirs.SlashBeast wrote:I have no idea why you write another script that does... something special but anyway, its just to make sure that mdev-like-a-boss's script populate /dev/bus/usb.
I wish I knew these things and were able to post only pertinent replies. I addressed this in the top of this post. Sorry! I can't know before I learn, to be able to act as you would like me to.SlashBeast wrote:Also, try write less and not post under own posts, personaly I have really hard time trying to understand what you wanted to share with us here.
Sure, kde, gnome, lxde, most DE, dbus is a must. I read but forgot if SlashBeast may use some of DE or not..But most of us here prefer non-bloat.jonathan183 wrote:The thread started out as dbus and *kit free systems, *kit free is certainly possible - dbus free depends on other packages you have installed. Your remaining issues appear to be related to choice of device manager and how to configure it ...
Code: Select all
# emerge -s dbus | grep -B2 -A4 'version installed: [0-9a-zA-Z]'
#
Not. I put them in the package.mask instead.jonathan183 wrote:My understanding is if /etc/portage/package.use containsmiroR wrote:There are unclarities on the use of eudev and hwid programs, and some other minor compiaints, though, so who knows?Code: Select all
sys-fs/eudev -* sys-fs/udev -*
Tractor Gir wrote:I was also considering switching to mdev but for now I'll stick with eudev.
Now it is that things are even less clear. You, jonathan183 actually are much more advanced than me, and you didn't miss the point that I have busybox with mdev use flag and clone the SlashBeast mdev-like-a-boss git to manually install the /etc/init.d/mdev and /etc/mdev.conf from his git? You sure didn't miss that, did you?jonathan183 wrote:and /etc/portage/profile/package.provided hasYou should be able to rebuild either eudev or udev and not have udev-init-scripts installed.Code: Select all
sys-fs/udev-init-scripts-10 sys-fs/udev-init-scripts-26
I probably undestand this package,provided functionality now for the first time, and I read 'man emerge' and 'man portage' lots of times...jonathan183 wrote:If you want hwid without udev or eudev installed then you should be able to do this if /etc/portage/profile/package.provided also containsCode: Select all
sys-fs/udev-208 sys-fs/udev-212
SlashBeast, please accept my thanks too! I like Poles, and you are one, Piotr. I respect your nation, know some pages of your history, as well as strongly support your neighbors Ukrainians in their defence, also because with them my nation is related, if I am allowed this digression.jonathan183 wrote:IAs I put in my previous post I still have eudev on my system because mesa would not compile without it - which at some point I may fix (but have not had time to do this yet).
mdev-like-a-boss contains lots of useful information but is not essential for a system using mdev as a device manager, I'm using some of the configuration on my laptop (manually downloaded rather than using an overlay) but my desktop has a few modifications to the busybox mdev installed in the way indicated in the mdev wiki page. I may change that in future but both methods work for me ... and it's always good to have choice
@SlashBeast - thanks for mdev-like-a-boss it has certainly helped me sort out a few things with my configuration

OK so you have no dbus, have sys-fs/udev in package.mask. You also removed sys-fs/eudev from package.mask when you installed it.miroR wrote:No dbus on my system.
if /etc/portage/package.use containsNot. I put them in the package.mask instead.Code: Select all
sys-fs/eudev -* sys-fs/udev -*
And as for eudev.
"Removed sys-fs/eudev from package.mask"
Yes you can have mdev and eudev on the same system, but you can't have them both acting as the device manager at the same time, so your current situation with eudev and mdev is OK - just as long as you don't try starting them both manually or with open-rc.miroR wrote:And, unfortunately only now I see that I probably mixed things up. Probably you go either the mdev (why did it take me so long to figure out that mdev is just a kind of busybox module, a busybox functionality, that mdev is not a separate program... Because I thought it was a separate program...) or the eudev way, and I have mixed those two on my system. I have both installed. eudev as the package, mdev as busybox functionality. Or maybe they can be mixed...
See that I start with the dilemma whether mbus can't live with eudev?
Luckily, they can, and in jonathan183's box, both are installed.
You don't have to make a choice between mdev and eudev, you just can't use both as a device manager at the same time. You should be able to keep the udev-init-scripts as well if you want, but I think the guidance was really put together for someone wanting to use mdev as the device manager - so it will attempt to minimise leftover udev or eudev stuff.miroR wrote:I have busybox with mdev use flag and clone the SlashBeast mdev-like-a-boss git to manually install the /etc/init.d/mdev and /etc/mdev.conf from his git? You sure didn't miss that, did you?jonathan183 wrote:and /etc/portage/profile/package.provided hasYou should be able to rebuild either eudev or udev and not have udev-init-scripts installed.Code: Select all
sys-fs/udev-init-scripts-10 sys-fs/udev-init-scripts-26
So it is possible to mix that kind of mdev-like-a-boss install and eudev? Is it?
I think of package.provided as telling portage you have something manually installed so portage should not start trying to update it - but it also fools portage into thinking things are installed when they are not.miroR wrote:I probably undestand this package,provided functionality now for the first time, and I read 'man emerge' and 'man portage' lots of times...jonathan183 wrote:If you want hwid without udev or eudev installed then you should be able to do this if /etc/portage/profile/package.provided also containsCode: Select all
sys-fs/udev-208 sys-fs/udev-212
Code: Select all
# man portage
# mkdir /etc/portage/profile
# cat > /etc/portage/profile/package.provided
sys-fs/udev-init-scripts-26
#
Code: Select all
Since I had added truetype (good for mplayer, ffmpeg and other packages) to my
useflags in make.conf, I decided to test this configuration update.
# emerge -tuDN @world # I have --verbose and --ask in
# make.conf's EMERGE_DEFAULT_OPTS
[ some six packages to reinstall and 1 new: media-libs/ftgl-xxx ]
#
Code: Select all
# cat >> /etc/portage/package.use
# required by sys-fs/eudev-1.6[keymap,hwdb]
=sys-apps/hwids-20140317 udev
Code: Select all
# emerge -c
Code: Select all
# emerge @preserved-rebuild
# rebuild-rebuild
Code: Select all
gbn miro # emerge -s udev | grep -B2 -A4 'installed: [0-9a-zA-Z]'
* sys-fs/eudev
Latest version available: 1.6
Latest version installed: 1.6
Size of files: 1,688 kB
Homepage: https://github.com/gentoo/eudev
Description: Linux dynamic and persistent device naming support (aka
userspace devfs)
License: LGPL-2.1 MIT GPL-2
--
* virtual/libudev
Latest version available: 208
Latest version installed: 208
Size of files: 0 kB
Homepage:
Description: Virtual for libudev providers
License:
--
* virtual/udev
Latest version available: 208-r2
Latest version installed: 208-r2
Size of files: 0 kB
Homepage:
Description: Virtual to select between different udev daemon providers
License:
gbn miro #
That's really some signal on khayyam part and no noise, really all clean!khayyam wrote:Yes, its called Descartes Demon ... I was however going to say "No", because such is the nature of the my deceit ... and having said that you might now wonder if this is simply a double bluff.miroR wrote:Does, in GNU/Linux, precisely in the kernel, from www.kernel.org, exist the infrastructure that an attacker could use to, once he/she can observe a system, remotely of course, in real time: to bind mount a new filesystem over an existing one to backdoor any binary on the system
( the same topic as first link below https://forums.gentoo.org/viewtopic-t-1 ... ml#7661502 )khayyam wrote:too much noise too little signal
[and tell me whether this] is a sufficient explanation to understand that my correction was wrong, please!khayyam wrote:miro ... no, you didn't. Besides the fact that the method/namespace we currently use is inherently broken a "local" overlay does not belong under /var/lib/layman and the originaly provided /usr/local/portage in the wiki is at least seperated from "layman" managed overlays. Your "corrected" namespace will look the following:miroR wrote:Just corrected:
/var/lib/layman/overlayA
/var/lib/layman/overlayB
/var/lib/layman/overlayC
/var/lib/layman/<category>/<package>
/var/lib/layman/profiles
/var/lib/layman/metadata/
So, I'm not sure why you think that "/var/lib/layman [...] is the default since long" but your correction just adds to what is a confused namespace ... I suggest you revert the change.
best ... khay

[...]miroR wrote:[1] What I saw this morning (Europe), just a few minutes ago when I opened this topic, which I needed in support of some efforts in Debian Forums, was very disturbing to me.
This topic of mine:
Uninstalling dbus and *kits (to Unfacilitate Remote Seats)
http://forums.gentoo.org/viewtopic-t-99 ... vious.html
you can see that it is marked previous.
And a completely different and unrelated topic is gotten if "-view-previous" is removed from the string.
Of course I may not technically understand what happened. Of course. Not an expert, but the string "previous" and another topic if that is removed...
Those are links from the “View previous topic” and/or ”View next topic“ links you can find on the top of the threads, right below “Report this topic”. ^^miroR wrote:How DuckDuckGo got that string to show this topic, I don't know.
I'm just going to leave that gem there, for posterity.miroR wrote:That's really some signal on khayyam part and no noise, really all clean!
Then FFS go to bed and stop typing. Most of all please stop with the cut'n'paste-and-quote-myself-and refer-the-poor-reader-to-another part-of-the-same-thread.Who is khayyam that when he says "jump" I pronto go and jump, if I may kindly ask?
Did he really prove that he never made mistakes?
What is any of you, the Dalai Lama? The Ayatollah? The Pope? for me to not question what you write if it is not sufficiently explained.
Had it been sufficiently explained for me to grasp it, and you can't say I were stupid, I have health and old age issues, such as having been sick for the last maybe 15 hours, and such as with memory
Funny, I have a feeling that's how khayyam feels. If so, I know how he feels.I hope this doesn't go much further, as I also don't have the strength, nor the time for it.
steve ... as an example of logical incongruity? If I were *perfect* I'm sure I could offer a self-criticism, but as I'm not I'll simply make a point of comparison ... my posts, miroR's posts ... which of these has the greater level of signal-to-noise?steveL wrote:I'm just going to leave that gem there, for posterity.miroR wrote:That's really some signal on khayyam part and no noise, really all clean!
Logical fallacy framed as a innocuous question as nowhere have you been asked to "jump" when I so order.miroR wrote:Who is khayyam that when he says "jump" I pronto go and jump, if I may kindly ask?
Logical fallacy of the "impossible demand" ...miroR wrote:Did he really prove that he never made mistakes?
"Masked man" fallacy coupled with "taring" ... the fact that anyone points out your errors and/or general tendency to resist criticism does not make the person in question despotic (or a religious leader).miroR wrote:What is any of you, the Dalai Lama? The Ayatollah? The Pope? for me to not question what you write if it is not sufficiently explained.
"Special pleading" ... what has your health to do with criticisms of your posting style? I've been drawing your attention to this for some time, the fact that it continues to be stated is I think due to your not having taken those criticisms seriously (and/or used them as a spring board into further long-winded "explanations"). In the above your simply illustrating how unstable your arguments are because, besides the fallacies pointed to above (of which there are many more) anyone need only compare our respective posting history to come to some tentative conclusion about which of us is clearer in our expression.miroR wrote:Had it been sufficiently explained for me to grasp it, and you can't say I were stupid, I have health and old age issues, such as having been sick for the last maybe 15 hours, and such as with memory
Another great little help form you Chiitoo, Yes, I see now.Chiitoo wrote:[...]miroR wrote:[1] What I saw this morning (Europe), just a few minutes ago when I opened this topic, which I needed in support of some efforts in Debian Forums, was very disturbing to me.
This topic of mine:
Uninstalling dbus and *kits (to Unfacilitate Remote Seats)
http://forums.gentoo.org/viewtopic-t-99 ... vious.html
you can see that it is marked previous.
And a completely different and unrelated topic is gotten if "-view-previous" is removed from the string.
Of course I may not technically understand what happened. Of course. Not an expert, but the string "previous" and another topic if that is removed...
Those are links from the “View previous topic” and/or ”View next topic“ links you can find on the top of the threads, right below “Report this topic”. ^^miroR wrote:How DuckDuckGo got that string to show this topic, I don't know.
Long before I got even this far in this thread I'd got to totally skipping any posts by miroR and scanning for knowledgeable posters like khayyam.khayyam wrote:miro ... *if* you want users to pay attention to your posts you need to rethink your method of presentation, I nolonger read anything posted by you as its simply too much work to wade through so much noise ... and discover so little signal.miroR wrote:Pls., dear GNU/Linuxers, go and study my latest posts, I believe there is a little to learn from them!
best ... khay
+1Gentree wrote:Long before I got even this far in this thread I'd got to totally skipping any posts by miroR and scanning for knowledgeable posters like khayyam.khayyam wrote:miro ... *if* you want users to pay attention to your posts you need to rethink your method of presentation, I nolonger read anything posted by you as its simply too much work to wade through so much noise ... and discover so little signal.miroR wrote:Pls., dear GNU/Linuxers, go and study my latest posts, I believe there is a little to learn from them!
best ... khay