On Wed, 18 Aug 1999, Gerd wrote:
> Hello Tomi, hello all,
> > I don't see the need for such an elaborate arrangement, at least if the
> > only reason was to replace the current "listen". Listen has no user
> > interaction and it should be pretty easy to make sure it has no buffer
> > overflows or other security risks. So there really isn't any reason a
> > sysop couldn't make it setuid root if he/she wants to. It's just that now
> > it isn't setuid root by default.
>
> A thing that should be mentioned in the HOWTO, though.
Of course.
> But I was thinking a little bit further. Packet Radio terminal
> programs that want to be able to monitor and show the traffic on
> the QRG (similar to let's say Eskay Packet under DOS) have to
> open and establish interaction with the same socket as the listen
> program.
Ahem, well, the reason Eskay Packet under DOS or similar systems under
DOS/Windows have a band monitoring tool built in is that on those
(stupid) platforms something as simple as "listen" is not possible. IMNSHO
there is _no_ reason to duplicate that kind of design in Linux. Linux is a
good multitasking operating system and the networking model nicely permits
running these things in separate programs that are well designed for their
purpose.
You won't run out of virtual consoles on Linux unless you are doing
something really weird to occupy all of them. With X there is of course no
limit in that sense.
> In another mail Heikki Hannikainen <[EMAIL PROTECTED]> mentioned
> setting only certain program parts UID root since this is only
> required to _open_ the socket. Is this at all possible? Until now, I
> thought that only whole programs could be set to run under UID root.
Yes, it is possible. I recommend reading the man pages Hessu mentioned and
the books too.
--
--- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
