pikpik
unread,May 20, 2012, 10:47:45 PM5/20/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to minix3
Hi,
On May 20, 10:04 pm, in reply to "Trouble linker" pikpik wrote:
> I followed the guide as well, and I found that it is a bit outdated in
> some places.
[...]
> Basically, the examples need to be updated. I was about to, but I
> don't know what is preferred for some sections.
If anyone has advice, one specific example is where the page says:
"Starting, stopping and restarting device drivers must be done using
the service(8) command. To start the hello program, enter the
following command:
# service up /usr/sbin/hello
Hello, World!
RS: restarting /usr/sbin/hello, restarts 0
And what a surprise, it displays the Hello, World! message Stop the
driver with:
# service down hello"
(After that follows a lengthy explanation of RS and SEF as applicable
to driver programming.)
What I'm confused about is how the message from RS, "RS: restarting /
usr/sbin/hello, restarts 0," seems to have not been in MINIX's source
code since release 3.1.7. The current behavior, upon the "service up"
of Hello, is a DoS in the form of the console being flooded by "Hello,
World!" messages.
An option I thought of would be to change the example to use "service
run" instead, but this probably require the loss or writing of the
useful explanation of RS' interactions with the driver.
So:
(a) What should happen when RS restarts a driver and it causes a DoS?
This seems to be the same as the driver being stuck in an infinite
loop, but in a different situation.
(b) Would it make any sense to bring back RS' default run-once
behavior for drivers that don't have SEF integrated (if that's the
case)? (I don't think this would be a good idea, since the present
"run"-once or start-"up" repeatedly situation seems much better
delineated.)
Thank you,
pikpik