[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: No intend to package vbox


Sorry for the late reply.

Paul Slootman (paul@wau.mis.ah.nl),
"Re: No intend to package vbox":
> On Sat 23 Jan 1999, Craig Sanders wrote:
> > On Wed, Jan 20, 1999 at 11:36:23AM +0100, Paul Slootman wrote:
> > 
> > > isdnutils      contains the basic isdnctrl, ipppd stuff needed for networking
> > > isdnmonitoring isdnlog, imon, xisdnload, ... that sort of thing
> > > isdndocs       the faqs and other docs
> > > isdnvbox       vbox

Thinking of rawip stuff and small disks, I'd change this to

isdnutils      contains the basic stuff: hisaxctrl, isdnctrl, iprofd
ipppd          contains ipppd

Uhmm, at least I'm voting for seperate init.d scripts for device setup,
ipppd, isdnlog, iprofd, ... Those ipppd and device scripts should use *one*
shared configfile for all devices. The current sheme is incapable of coping
with mppp setup in an elegant way and it makes it so damned hard
to keep the overview over several different setups.

I have alternative scripts, but they aren't that perfect yet. In addition
there are scripts in in ip-{up,down} which reuse the shared configfile to
reset interfaces to the desired settings.

Oh, and my packetfilter is going to use this configfile, too.

Hmm, how about splitting vbox into vbox-{client,server}, too?


KeyID=58341901 fingerprint=A5 57 04 B3 69 88 A1 FB  78 1D B5 64 E0 BF 72 EB

Attachment: pgp9MpQN_baT1.pgp
Description: PGP signature

Reply to: