Can you ever with these things?
It all boils down to the fact that ioctls are very lowlevel, system specific and you shouldn't poke around with them unless you know what you are doing. By implementing my suggestion, you can implement default ioctls for "standard" functions and the user can easily implement her own ioctls as needed.
But, since this is dangerous stuff for the average user-joe, I would suggest making it a compiletime feature which has to be enabled with --enable-user-ioctls or something similar.
/ Marcus Agehall (PacketFront)
Previous text:
2004-08-17 13:35: Subject: managing comport settings in linux
Can you guarantee that the process wont crash if you don't feed it the wrong information?
/ Mirar
You can always try to make your own c-level module that does this.
/ Martin Nilsson (DivX Networks)
Previous text:
2004-08-17 13:48: Subject: managing comport settings in linux
Can you ever with these things?
It all boils down to the fact that ioctls are very lowlevel, system specific and you shouldn't poke around with them unless you know what you are doing. By implementing my suggestion, you can implement default ioctls for "standard" functions and the user can easily implement her own ioctls as needed.
But, since this is dangerous stuff for the average user-joe, I would suggest making it a compiletime feature which has to be enabled with --enable-user-ioctls or something similar.
/ Marcus Agehall (PacketFront)
Speaking about non-official module sources (eg, the module repository), it would be useful if the modules are automatically installed where it says they are going to be installed, regardless of the makefile.
Basically this requires some fiddling with 'pike -x module install' or perhaps preferably 'pike -x monger'.
As it is it's a pain to ensure that modules actually end up where they are supposed to (there is no easy way to put C-modules anywhere except in the toplevel in the pike build-system)
/ Per Hedbor ()
Previous text:
2004-08-17 14:04: Subject: managing comport settings in linux
A System.Ioctl. Way, way away from the official source.
/ Peter Bortas
I'm not sure I follow... I've created C-modules in places like Public.XSLT...
The setting:
MODDIR=Public.pmod/Network.pmod/
Basically defines the "root" of the module installation. Does this not do what you have in mind?
Bill
Speaking about non-official module sources (eg, the module repository), it would be useful if the modules are automatically installed where it says they are going to be installed, regardless of the makefile.
Basically this requires some fiddling with 'pike -x module install' or perhaps preferably 'pike -x monger'.
As it is it's a pain to ensure that modules actually end up where they are supposed to (there is no easy way to put C-modules anywhere except in the toplevel in the pike build-system)
/ Per Hedbor ()
Previous text:
2004-08-17 14:04: Subject: managing comport settings in linux
A System.Ioctl. Way, way away from the official source.
/ Peter Bortas
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Marcus Agehall (PacketFront) ＠ Pike (-) developers forum -
Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum
-
Per Hedbor () ＠ Pike (-) developers forum
-
Peter Bortas ＠ Pike developers forum