OpenVZ Forum


Home » General » Support » *WORKED AROUND* Add /proc/bus/usb inside VE ?
Re: *WORKED AROUND* Add /proc/bus/usb inside VE ? [message #33592 is a reply to message #33548] Fri, 24 October 2008 07:59 Go to previous messageGo to previous message
Aefron is currently offline  Aefron
Messages: 10
Registered: July 2008
Junior Member
Well nope : for the printers, both run in their own dedicated VE, with a headless CUPS for each (I do this on purpose : only the drivers of respective interest are installed on each one, so I can hack on one CUPS, without wreaking havocs in the other, and still have a lightweight ensemble)... and it goes the same way for the scanner, with a headless sane/scanbuttond/lpr combo.

All of this used to run within the same VE, when I was using VServer, and I used to simply share "/proc/bus/usb" to access the hardware. But this can be done through sharing "/dev/bus/usb" as well, and an even better solution could be to add a custom udev rule on the HN that makes /dev/usbscanner0 appear (or such thing : I think I will tweak udev to make a symlink inside "/dev/containers_dev/", with indisputable name, eg scanner_1670, for an Epson Perfection 1670, and such, to be sure the right device is picked up).

To be fair, one of the reasons I do not use desktop-distro is that I have the feeling I am lost with those : so many things are installed by default that I never know which things I am reasonably in control of, and which I am not. As for the rest, ie a couple (two is a classic couple) of unredistributable binary firmwares (laser printer and scanner) is the most that I need, and, I guess, the most that a desktop distro could eventually (and not even necessarily) bring me : for the rest, Debian should not have such a different support in USB materials than any other distro, IMHO (well, I am already now using the next stable, aka Lenny... it will grow older in a couple of years, when I'll probably be waiting for its successor Squeeze, but for now, it is shiny new, not even released yet as stable, to be exact, and in the league with the pack for "bleeding edgeness").

The only annoyance I must deal with is the problems inherent to the use of udev in a container (needed, for instance, to load the firmware of my laser printer... well, this can be done on the HN, where udev works right) - I am still quite reluctant with it, as I have known the painful era when it was just an all-but-ready outsider (not that pure static /dev was not painful either)... as far as I understood, its use in the VE is unadvisable no matter which distro one uses (I came across those recommandations in Gentoo's documentation as well, for instance ; and in a couple of others), which is another problem, as makedev support and such things may tend to disappear in a few years from now ; which was the thing I was wondering about in the end of my second post (Lenny will surely still be supported in at least something like 3 years from now, but I already wonder how I will manage things if udev is to become a mandatory dependency, without alternatives, for things I put in containers ; better to be worried much too early, than much too late).

Sorry if I may have been a bit rough, in my previous answer - I really should sleep more, these times. I hope you'll better undestand my way of viewing things, with those details.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: VLAN not working in VE? <SOLVED>
Next Topic: How to make changes to resource limits take effect without a vps restart?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Aug 21 05:27:39 GMT 2025

Total time taken to generate the page: 0.05816 seconds
Powered by FUDforum Powered by Virtuozzo Containers