-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
also had some private discussions about this, especially one with Lubek. It turned out that most people will either use etherwake or wol, but normally not both. For example I never got wol to work correctly, but etherwake worked right from the start. So the combined uci support would only be meaningful for a few or no user. Hence I re-created uci support for etherwake similar to the current wol package. The init script can wake up targets on boot, but also wake up special targets when called with "start <targetname> <targetname>". ftp://ftp.maddes.net/openwrt/kamikaze/orion/patches/etherwake/ On 03.08.2009 22:31, Jo-Philipp Wich wrote: > The UCI handling looks good, but why separate commands for the uci version? > > Wouldn't it be better to have for example a "wol" script that calls > "wol.real"? If the "wol" script is called without arguments, it'll use > the uci configuration, if flags are provided it operates as usual. > > What do you think about this? Also had the idea for a wrapper script, but skipped it immediately as I didn't dare to rename an executable. The wrapper script should handle three situations: no parameter - wake up all targets that are marked for 'wakeuponboot' target name - wake up the target from the uci config mac - wake up the given mac target "no parameter" is typically an init script. "mac" is typically the original executable itself. Hence adding the "target name" functionality to the init script was straight forward. Regards Matthias "Maddes" Bücher -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkp7RQkACgkQUXXT+9wZdbXC9QCg4k0jrxvhWnCDQrS5wQ2TlF/L 52UAoIkEReNZ+HnVyfqMoTj8aEizWRMS =Lgh2 -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
