Tag Info

Hot answers tagged


I think you can use UDEV to do what you want. Creating a rules file such as/etc/udev/rules.d/99-thumbdrives.rules you'd simply add a rule that will allow either a Unix group or user access to arbitrary USB thumb drives. KERNEL=="sd*", SUBSYSTEM=="block", ENV{DEVTYPE}=="disk", OWNER="<user>", GROUP="<group>", MODE="0660" Would create the device ...


Your problem is that you try to enter C code into a shell prompt, this doesn't work for obvious reasons. You could either put it into a correct C file, compile it and get a valid binary you could execute: #include <linux/kd.h> #include <sys/ioctl.h> #include <fcntl.h> #include <unistd.h> #include <err.h> #include ...


USB 2.0 or 3.0 is a hardware specification and has little to do with the OS. There's no way to downgrade (or upgrade) an specific USB version. What you can do is plugging your device in a 2.0 hub. USB 3.0 is totally backwards compatible with 2.0 and 1.1 devices, but some glichs can appear in the kernel implementation of the specification, in such cases is ...


Boot with: quiet loglevel=3 For info: quiet [KNL] Disable most log messages loglevel= All Kernel Messages with a loglevel smaller than the console loglevel will be printed to the console. It can also be changed with klogd or other programs. The loglevels are defined as follows: 0 (KERN_EMERG) system is ...


That C code would not work anyway -- fdopen() requires more than one argument and returns a file stream, not a file descriptor. I can remember doing this a few years ago, I thought via Xlib, but I could not find my old code (occasionally the collection gets purged) but I figured someone must have a simple app for this on github or something. Low and ...


The proper way to do so is (as described on the Arch Linux Wiki) # dd bs=4M if=/path_to_arch_.iso of=/dev/sdX && sync using GNU dd.


If /dev/video1 exists, it is probably attached to something. Try pulling the second camera out of the hub, wait a few seconds, and ls /dev | grep video -- the node should disappear. Likewise, when you plug it in, it should appear. This would clarify whether or not it is using that node.


If Miroslav Koskar's suggestion regarding kernel loglevel did not help (you might as well use 2 or 1 there instead of 3, IMO), have a look in your /etc/syslog.conf (or rsyslog.conf) for a line containing /dev/console. This indicates the level of messages that are passed to the console by the system logger, which maybe the case if the kernel isn't doing it ...


Magic numbers (or in this case, identifiers) are most of the time random, through sometimes funny (think hexadecimal DEADBEEF). These numbers could or couldn't be incidental, but there's no reason why they would want to be "close anagram" of anything. I would brush off as mere coincidence.

Only top voted, non community-wiki answers of a minimum length are eligible