Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le 30.10.2011 01:31, Daniel O'Connor a écrit : On 30/10/2011, at 24:40, David Marec wrote: But, now running FreeBSD 9, I get new usb/devd behavior issues. First, the ulpt module is always loaded. Is there any elegant way to get rid of this 'self loading' behavior, except to remove it from /boot/modules ? Anyway, it sounds like HPLIP is now working with the ulpt module loaded. I'm not sure what would load it automatically - it may be built into the kernel though. Anyway, as you say it should work with ulpt loaded anyway. I'm quite sure it was not; I mean, if ulpt.ko has been manually removed from /boot/modules, this module is not loaded when I plugged in the printer. And, how to handle them with devd ? I have a similar problem.. [ ATTACH statement in devd.conf] However this doesn't seem to work anymore, it certainly used to.. :( Yep, sounds like it is the same here. I tried adding the system, subsystem type parts and changing device-name to cdev but no luck.. I also tried to add entries into /usr/local/etc/devd/devd.conf instead of /etc/devd.conf. And some more unsuccessful attempts, like changing system/subsystem and others, as you did. -- David Marec, mailto:david.ma...@davenulle.org http://user.lamaiziere.net/david/Site http://www.diablotins.org/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le 29.10.2011 21:58, Jilles Tjoelker a écrit :
On Sat, Oct 29, 2011 at 04:10:46PM +0200, David Marec wrote:
So, what's should be the news groupuser's rights required by HPLIP/cups
on FreeBSD 9 ?
And, how to handle them with devd ?
Use devfs rules.
Doing this, device rights become unreliable.
[devfsrules_mybox=10]
add path 'fd0*' mode 660
What are the user rights that the devfs interface should set ?
mode 0666 for all usb entries ('usb*') ?
- ugen stands for generic usb support. -
Setting 'cups:hplip' rights for 'ugen[0-9]' doesn't do the trick
anymore: HPlip needs the suitable rights on 'usb/x.y.*' too, which are
now targeted by the ugenx.y links.
--
David Marec, mailto:david.ma...@davenulle.org
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
It would be nice, If somebody would write updated manual documenting whole process of setting up hplip. In past, I could only get it to the point of printing test pages (sigh...) Before release preferably? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-USB-HPLIP-what-s-the-new-right-way-to-manage-hplip-usb-plugged-printers-running-Free9-tp4948737p4949780.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Or just extend hplip section in handbook. http://www.freebsd.org/doc/handbook/printing-lpd-alternatives.html It could be roughly based upon this: http://freebsd.kde.org/howtos/hplip.php -- View this message in context: http://freebsd.1045724.n5.nabble.com/Freebsd-9-amd64-USB-HPLIP-what-s-the-new-right-way-to-manage-hplip-usb-plugged-printers-running-Free9-tp4948737p4949796.html Sent from the freebsd-current mailing list archive at Nabble.com. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le 30.10.2011 10:04, Jakub Lach a écrit : Or just extend hplip section in handbook. http://www.freebsd.org/doc/handbook/printing-lpd-alternatives.html It should be a good idea, I agree. Especially in this case, where nobody now knows how and where HPLIP rights have to be settled. It could be roughly based upon this: http://freebsd.kde.org/howtos/hplip.php This one is really outdated. It seems that `hpiod` and `hpssd` are not useful in any way, and, mostly, the use of devfs stands for :setting rights for everyone (or close to) on USB system. -- Et je vais rater ma béarnaise si je continue à répondre. http://user.lamaiziere.net/david/Site http://www.diablotins.org/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le 30.10.2011 08:28, David Marec a écrit :
I have a similar problem..
Le 30.10.2011 08:28, David Marec a écrit :
I have a similar problem..
A new behavior occurs since I updated the world kernel this morning.
`devd` now executes the entry for hplip, as I defined it inside
/usr/local/etc/devd/devd.conf.
But, with `ulpt0` forwarded as device node.
That sounds ok since ulpt has been loaded and attached by devd (or some
other stuff, i dont know);
What comes now as the major issue.
hold it... since the update, ulpt keeps on being quiet while the printer
gets plugged..
So, I changed my script to:
#!/bin/sh
#
# set up /dev/$1.$2.* to cups:hplip -rw-rw---
#
logger HPLIP printer found on $1.$2
logger setting suitable rights for $1.$2
/usr/sbin/chown cups:hplip /dev/usb/$1.$2.[0-9]
/bin/chmod g+rw /dev/usb/$1.$2.[0-9]
...and used the nomatch key instead of the attach key into
/usr/local/etc/devd/devd.conf
nomatch 100 {
match vendor 0x03f0;
match product 0x4712;
action /root/sbin/ugen-hdle $port $devaddr;
};
'looks like it works .
--
David Marec, mailto:david.ma...@davenulle.org
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
A new behavior occurs since i update the world kernel this morning.
`devd` now executes the entry for hplip, as I defined it inside
/usr/local/etc/devd/devd.conf.
But, with `ulpt0` forwarded as device node.
That sounds ok since ulpt has been loaded and attached by devd (or some
other stuff, i dont know);
What comes now as the major issue.
And, up to now, ulpt keep on being stuck.
So, i change my script to
#!/bin/sh
#
# set up /dev/$1.$2.* to cups:hplip -rw-rw---
#
logger HPLIP printer found on $1.$2
logger setting suitable rights for $1.$2
/usr/sbin/chown cups:hplip /dev/usb/$1.$2.[0-9]
/bin/chmod g+rw /dev/usb/$1.$2.[0-9]
And uses nomatch instead of attach into /usr/local/etc/devd/devd.conf
nomatch 100 {
match vendor 0x03f0;
match product 0x4712;
action /root/sbin/ugen-hdle $port $devaddr;
};
seems to work finally.
--
Délicieuse cette béarnaise.
http://user.lamaiziere.net/david/Site
http://www.diablotins.org/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
On Sunday 30 October 2011 01:31:21 Daniel O'Connor wrote: I'm not sure what would load it automatically - it may be built into the kernel though. Anyway, as you say it should work with ulpt loaded anyway. Hi, ulpt is autoloaded by /etc/devd/usb.conf --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
On Sat, Oct 29, 2011 at 04:10:46PM +0200, David Marec wrote: So, what's should be the news groupuser's rights required by HPLIP/cups on FreeBSD 9 ? And, how to handle them with devd ? Use devfs rules. Pasting from http://www.stack.nl/~jilles/unix/freebsd-devfs.txt Create or edit /etc/devfs.rules and put something like this in it: [devfsrules_mybox=10] add path 'fd0*' mode 660 See man 8 devfs for more information. Then put in /etc/rc.conf devfs_system_ruleset=devfsrules_mybox If you want to edit other /dev mountpoints (e.g. for jails) use something like devfs_set_rulesets=/usr/jails/jail1/dev=devfsrules_jail1 /usr/jails/jail2/dev=devfsrules_jail2 -- Jilles Tjoelker ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
Le Sat, 29 Oct 2011 21:58:53 +0200, Jilles Tjoelker jil...@stack.nl a écrit : On Sat, Oct 29, 2011 at 04:10:46PM +0200, David Marec wrote: So, what's should be the news groupuser's rights required by HPLIP/cups on FreeBSD 9 ? And, how to handle them with devd ? Use devfs rules. Pasting from http://www.stack.nl/~jilles/unix/freebsd-devfs.txt Create or edit /etc/devfs.rules and put something like this in it: [devfsrules_mybox=10] add path 'fd0*' mode 660 The problem is that the printer appears as ugenXXX.Y, but other usb devices (disk, usb-key, ...) also have an entry in /dev/ugen/ You really don't want to allow the users to access these devices, but *only* the printer. This is why we use a devd rule that test the type of the device. I don't think we can do this with devfs. And the ugen number differs if the usb port is not always the same. Regards. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [Freebsd 9] [amd64] [USB] [HPLIP] what's the (new) right way to manage hplip usb-plugged printers, running Freebsd 9
On 30/10/2011, at 24:40, David Marec wrote:
But, now running FreeBSD 9, I get new usb/devd behavior issues.
First, the ulpt module is always loaded. Is there any elegant way to get rid
of this 'self loading' behavior, except to remove it from /boot/modules ?
Anyway, it sounds like HPLIP is now working with the ulpt module loaded.
I'm not sure what would load it automatically - it may be built into the kernel
though. Anyway, as you say it should work with ulpt loaded anyway.
But, devd never sets the suitable rights on ugen.
Moreover, switching to the 'action' that only logs something, reveals that
devd never executes this entry.
So, what's should be the news groupuser's rights required by HPLIP/cups on
FreeBSD 9 ?
And, how to handle them with devd ?
I have a similar problem..
Looking at /etc/devd/uath.conf I see..
notify 100 {
match system USB;
match subsystem DEVICE;
match typeATTACH;
match vendor 0x168c;
match product 0x0002;
action /usr/sbin/uathload -d /dev/$cdev;
};
Also, I have devd entries for NUT (UPS software) which look like so..
attach 100 {
match vendor 0x0463;
match product 0x;
action chown :uucp /dev/$device-name; chmod 660 /dev/$device-name;
};
However this doesn't seem to work anymore, it certainly used to.. :(
I tried adding the system, subsystem type parts and changing device-name to
cdev but no luck..
I ran devd -Dd and checked the output but while it says it parses nut.conf it
doesn't seem to match the entries.
devd output looks like so..
Processing event '!system=USB subsystem=DEVICE type=ATTACH ugen=ugen1.3
cdev=ugen1.3 vendor=0x046
3 product=0x devclass=0x00 devsubclass=0x00 sernum=0
release=0x4241 mode=host port=
3 parent=ugen1.1'
Pushing table
setting system=USB
setting subsystem=DEVICE
setting type=ATTACH
setting ugen=ugen1.3
setting cdev=ugen1.3
setting vendor=0x0463
setting product=0x
setting devclass=0x00
setting devsubclass=0x00
setting sernum=0
setting release=0x4241
setting mode=host
setting port=3
setting parent=ugen1.1
Processing notify event
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
