Date: Sun, 18 Nov 2001 10:50:13 -0800 From: Luigi Rizzo <rizzo@aciri.org> To: "Sam Leffler (at Usenix)" <sam@usenix.org> Cc: freebsd-small@FreeBSD.ORG Subject: Re: crunch.conf for picobsd+openssh Message-ID: <20011118105013.A5104@iguana.aciri.org> In-Reply-To: <052601c1705c$9844c370$a665a8c0@errno.com> References: <052601c1705c$9844c370$a665a8c0@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
have you had a look at the "bridge" picobsd configuration on
a receont (4.4/ RELENG_4) FreeBSD version ?
That one works, using a specially modified version of
ssh (not Openssh) which is in ports/picobsd.
The main problem with the "open"s{sh,cp,shd} is that they
bring in a huge amount of things, if i remember well it is
over 500KB _compressed_, which is unacceptable bloat for picobsd.
The second problem is that (both in the ssh in the ports, and I
think also in openssh, which is derived from the same code),
ssh, scp and sshd share a large number of source files, but you
cannot make a library out of them because those files reference
symbols in program-specific files (i.e. there are three different
functions named "foo" in ssh, sshd and scp).
And if you don't make a library, the code bloat is again unacceptable.
The ssh port in ports/picobsd is patched to avoid the above problem.
cheers
luigi
On Sun, Nov 18, 2001 at 10:12:27AM -0800, Sam Leffler (at Usenix) wrote:
> I took "theWall"'s picobsd configuration and tried to incorporate ssh, sshd,
> and scp but haven't been able to figure out the necessary crunchgen
> configuration glop to get things to work. I can make things work by editing
> the crunch1.mk file directly but I want something more maintainable. Has
> anyone done this and want to share their results? All this is with 4.4
> (-stable).
>
> For those that care there are three issues:
>
> 1. scp, ssh, and sshd are built by referencing libssh.a that's built in
> another directory, but never installed. I see no crunchgen mechanism for
> specifying a make target other than "prog". But since libssh.a isn't an
> executable and has no main entry point, prog isn't appropriate.
> 2. I don't see any way to specify that scp, ssh, and sshd should reference a
> libssh.a, if I can build it. Listing all the .o files with objs is
> problematic because they aren't in the same directory as the target so
> you're forced to also specify the objpath and even that leads to problems.
> 3. scp, ssh, and sshd aren't crunchgen-aware so you need to wack them to do
> the right thing when built with RELEASE_CRUNCH, etc. Not a big deal.
>
> I tried contacting the crunchgen author but perhaps there's someone
> currently maintaining it? I don't mind adding to crunchgen if there really
> is no way to do what I want.
>
> Sam
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-small" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011118105013.A5104>