Date: Thu, 23 Jan 2025 10:06:03 +0100 From: Bertrand Petit <freebsd-hackers@phoe.frmug.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Daniel Lovasko <daniel.lovasko@gmail.com>, freebsd-hackers@freebsd.org Subject: Re: wg ifconfing control Message-ID: <20250123090603.GC1358@memo2.memo.frmug.org> In-Reply-To: <202501230824.50N8O8hx008288@critter.freebsd.dk> References: <CA%2BcSnN1UYpecBV145FAkdySM9otr%2BOPTfaWL6PUfj14VEinGVQ@mail.gmail.com> <202501230824.50N8O8hx008288@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 23, 2025 at 08:24:08AM +0000, Poul-Henning Kamp wrote: > > Isn't that program already horrible and complex enough, in terms > of source code, manual page and command line options ? And buggy, see [1]. Reported Oct. 2021 and still present. I'm not against ifconfig per se, I even like the interface it exposes to the user, a unified interface. Having dozens of commands, each configuring a protocol or even parts of a protocol, each with its own command line paradigm and idiosyncrasies is daunting and taxing on human memory. I like ifconfig however, its source code is a mess---a mess similar to what a cat makes when playing with balls of knitting yarn. [1] <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259003>; -- %!PS -- Bertrand Petit /D{def}def/E{exch}D/G{get}D/I{2 div}D/U{dup}D/L{roll}D/Y{setgray}D/N{newpath}D /O{N 0 0 moveto}D/P{pop}D/T{translate}D currentpagedevice/PageSize G U 0 G/w E D 1 G /h E D w I h I T 0 Y 1 setlinewidth 0 1 2 { P 120 rotate 2 4 w U mul h U mul add sqrt I 50 add {N 50 0 3 2 L 0 360 arc stroke}for}for/s{O true charpath pathbbox exch 4 -1 L E sub I 3 1 L sub I} D /l(bp)D 0.94 Y /Helvetica findfont 22 scalefont setfont l s P(x)s exch P T O l show showpage
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250123090603.GC1358>