[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [MiNT] kernel development
> From: owner-mint@fishpool.com [mailto:owner-mint@fishpool.com]On Behalf
> Of Guido Flohr
> Sent: Thursday, June 24, 1999 11:05 PM
> To: MiNT mailing list
> Subject: Re: [MiNT] kernel development
>
>
> Hi Julian,
>
> On Thu, Jun 24, 1999 at 04:24:54PM +0200, Julian Reschke wrote:
> > > Right, but the base for Martin's idea is ok to me. Why not make
> > > gethostname and sethostname kernel calls? Sethostname should
> either be
> > > called by /etc/rc.net or - which I think makes more sense
> with MiNT - in
> > > mint.cnf. Whatever program sets the hostname could also update
> > > /etc/hostname for compatibility with old software.
> >
> > Sounds good. But please do not invent more and more system calls for
> > cosmetic things. A new opcode for Ssystem () or something
> similar should be
> > just fine.
>
> I think the kernel is a good place even for cosmetic things. The more
> intelligence is packed into the kernel, the better. Right now it would
Yes, but don't invent new calls where a new opcode to an existing call is
just fine. I would opcode creep.
> even make sense to have a kernel regex or printf call because the kernel
> is the only shared lib we have and this strategy saves memory, both
> permanent and volatile.
In fact in the case of regexp it doesn't save any memory out of the box as
the kernel doesn't need regexp, right?
Funny enough I am planning to ship a shared library regexp with my next
release of the MetaDOS shared library loader. Unfortunately we *still* don*t
have shared libraries in the kernel, though they would by MUCH more
important then having hostname support, right?
>
> No, don't add Xregcomp and Fprintf to your mintbin.h. Just an example.