Date: Thu, 04 Feb 1999 00:24:22 +0100 From: Marcel Moolenaar <marcel@scc.nl> To: Mike Smith <mike@smith.net.au> Cc: emulation@FreeBSD.ORG Subject: Re: Linux collections (was: Linux devel doesn't work with glibc libs) Message-ID: <36B8DAA6.B5BF232E@scc.nl> References: <199902031906.LAA08199@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith wrote:
>
> > Currently I don't use the ports-collection. I've downloaded Red Hat 5.2
> > packages and installed them.
>
> This is exactly what I think the port should do. Ie., it should
> proceed as follows (in the case where nothing is already installed)
>
> - Ensure that the Linux emulator is already running.
Check.
> - Download and install the current RedHat RPM binaries.
I prefer the RPM port for the following reasons:
1. It is easier.
2. Releases and updates of RPM are independent of Red Hat releases.
3. We cannot satisfy any possible configuration with only a few prefab
collections; so we can expect users to want to install individual packages
too. A FreeBSD native rpm is more pleasant to use than an emulated one.
> - Download and install (using the just-installed RPM) the various RPMs
> that Linux applications these days are requiring.
This is the hard part. I think we're better off with more than two
collections, because that would scales better (especially for small
installations). We also benefit from the dependency information stored in the
port.
> The linux-devel port should have the linux-lib port as a prerequisite,
> and should again use the Linux RPM to install the development RPMs.
What about the following collections (as a start):
Linux: basic runtime environment (whatever we define it :-)
Linux-devel: basic development env. (needs Linux)
Linux-X11: X runtime environment (needs Linux)
Linux-X11-devel: X development env. (needs Linux-devel)
linux-ports: FreeBSD ports of linux-specific tools (such as ps(1)) (needs
linux)
> This really isn't too difficult - you're going to spend most of your
> time working out which two dozen or so RPMs you want installed, but
> that's about it.
True. I've already build a port to test things. It can almost be committed
:-)
> If you feel like you can undertake this, start small; just pick four or
> five RPMs and make the Makefile and packaging work. Get back to us/me
> here if you need any help.
Ok. Feedback time :-)
1. I'll start with the basic (bare minimum), and call it Linux (as to
preserve the current ports)...
2. I'm going to use the RPM port as the sole dependency...
3. linux.ko is loaded if necessary...
4. It is going to contain just enough packages to have a Linux bash
installed. To be precise:
setup-1.9.2-1.noarch.rpm
filesystem-1.3.2-3.noarch.rpm
basesystem-4.9-3.noarch.rpm
ld.so-1.9.5-8.i386.rpm
ldconfig-1.9.5-8.i386.rpm
glibc-2.0.7-29.i386.rpm
termcap-9.12.6-11.noarch.rpm
zlib-1.1.3-2.i386.rpm
mktemp-1.4-3.i386.rpm
libtermcap-2.0.8-10.i386.rpm
bash-1.14.7-13.i386.rpm
5. Other collections (to be defined) build upon the 'Linux' collection (see
my suggestion of other collections)...
marcel
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36B8DAA6.B5BF232E>