Summary: | Updated LTModem Ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom P. <wqy5jdh02> |
Component: | New packages | Assignee: | SpanKY <vapier> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | 1.4_rc2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ltmodem-8.26_alpha9-r1.ebuild |
Description
Tom P.
2003-01-25 02:33:55 UTC
Created attachment 7619 [details]
ltmodem-8.26_alpha9-r1.ebuild
glad to know some of it was correct ;) i havent had a modem to test with ... ive added your changes to cvs, thanks http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/net-dialup/ltmodem/ltmodem-8.26_alpha9-r1.ebuild?rev=1.1&content-type=text/vnd.viewcvs-markup Ebuild doesn't work, missed a change - maybe I rambled on too much last time :-) In pkg_postinst() left out HUP to devfsd. Without the HUP devfsd won't read config files untill next reboot - therefore, ltmodem won't work untill next reboot. The only way to get devfsd to re-read config that I'm aware of is to send HUP signal using "killall -HUP devfsd". From the devfsd man SIGNALS devfsd responds to signals in a variety of ways: SIGHUP The configuration file is re-read and any shared objects are reloaded. Then the mounted device tree is scanned and synthetic REGISTER events are generated for each leaf node. From man killall killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent. Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1). Therefore, "killall -HUP devfsd" will send the signal HUP to devfsd causing it to re-read config files. Works for me. Without the HUP, I get the error "/dev/modem doesn't exist" untill I reboot or send the HUP signal to devfsd myself. Please fix this. Thanks again for the quick response, glad I could help. Tom what I don't understand is: what is your ebuild doing that mine (7805) wasn't already doing at least as well if not better (eg HUP). This is not meant in an unfriendly way. I just don't get it. i didnt add the killall since current kernmodules dont use it ... refer to nvidia-kernel, emu10k1, and alsa-driver ... ill look at it some more when i have some free time Denys, I never looked at your ebuild since its for an older ltmodem (ltmodem-8.22) and a newer ebuild existed in portage. If I'd known your ebuild was still maintained I would have started there. Why didn't you update to the later build scripts? I realize that the core code may not have changed, but I've worked with the developers in the past and updates to there build scripts are important to keep bug reports down. -------------------------------------------------------------------------- SpanKY The killall is needed by the device filesystem driver (devfs). My ebuild drops new config files for devfs but they won't be read until devfs is restarted by reboot or -HUP. See copy of man file in my above comment. With these config files, devfs will create the link from the ltmodem to /dev/ltmodem on demand. Without the killall, The ebuild doesn't work untill you reboot... Most users will have given up by then. I'll look at deny's build and see what the difference is. Thanks for the reply's, I'm just trying to help out and I appreciate everyone here! just for information, my ebuild (7805) is not for an older release of ltmodem, rather it started with an older release and a new ebuild was added as a newer attachment for the newer release of ltmodem. Thus the original title of the submission may now be misleading. Cheers, 4 months with no bug reports or other reported problems with ltmodem ebuild - could this be marked stable? Tom done |