Re: Intent To Split: netbase
Am Mon, 17 Jul 2000 22:16:36 Anthony Towns Sie:
> On Mon, Jul 17, 2000 at 10:58:26AM +0200, Marcus Brinkmann wrote:
> > > I intend to split netbase into a plethora of little packages based on
> > > how they're distributed upstream. [...]
> > more power to you. Can we work it out that netbase can be installed on the
> > Hurd as well? If it ends up as a binary-all package, this might be a bit
> > difficult (because of /etc/init.d/networking), but I am sure we can get
> > to it. I can then drop the bits I have from netbase in the inetutils
package
> > (update-inetd and such).
>
> That sounds good. The dependencies (logically) are:
>
> network-config
> ifupdown
> firewalling
> masq-support
> internet-superserver
> tcpd
> ping
> portmap
> rpc-tools
>
> You've already got tcpd, and network-config presumably exists too
> (inetutils?).
I don't know what network-config does. inetutils source produces
inetutils (inetd), syslog, telnet, telnetd, ftp, ftpd, and soon a whois.
GNU inetutils is now getting more attention than in the past, and it
might
grow up to a good alternative even on Linux. But currently, a Hurd only
solution is satisfactory.
> How about firewalling?
Hurd can't do that.
> It'd be nicer to just have
> firewalling tools available almost always on every Debian install. I guess
> you probably don't have masq-support packages yet, but I'm inclined to
> downgrade them anyway, so *shrug*.
The Hurds requirement are really modest. We only support one network
interface, and there is little setup to be done. Most is automagic
by use of translators, and there is no need for an init script on
the Hurd.
> Presumably you have an inetd and a
> ping as well?
inetd is in inetutils, ping is in the Hurd currently (but there will
be one in inetutils, too).
> And I guess portmap and rpc can be removed from Depends:
> eventually too, so aren't too important. ifupdown should be mostly
> trivial to port.
Yes, however, see above. Only one interface, and up and down isn't
striclty hurdish, where services are run on demand. But I can hack
something up to make it explicit as well (it's really only one command).
> /etc/init.d/networking might need an `if <linux>; then' around some stuff,
> and some corresponding stuff for hurd (or to be binary-any and have the
> script preprocessed or whatever), but should otherwise work pretty well
> as is.
Agreed, I will have to look at what it does, and then we can see.
I would suggest that you make some early snapshot available to me,
and I come back with comments then.
Thanks,
Marcus
Reply to: