Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 09 Mar 2013 23:53:11 +0100
From:      =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        emulation@freebsd.org
Subject:   Re: [cfr] patch to clean up old Linux ports
Message-ID:  <513BBD57.20307@freebsd.org>
In-Reply-To: <20130309233148.00004ad1@unknown>
References:  <513A0C04.8090907@freebsd.org> <20130309121625.00004279@unknown> <513BA4AE.4000802@freebsd.org> <20130309233148.00004ad1@unknown>

next in thread | previous in thread | raw e-mail | index | archive | help
On 09-03-2013 23:31, Alexander Leidinger wrote:
> On Sat, 09 Mar 2013 22:07:58 +0100
> René Ladan <rene@freebsd.org> wrote:
>
>> On 09-03-2013 12:16, Alexander Leidinger wrote:
>>> On Fri, 08 Mar 2013 17:04:20 +0100
>>> René Ladan <rene@freebsd.org> wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Hi,
>>>>
>>>> I have made a patch to clean up the old Linux ports (those that
>>>> expired together with FreeBSD 7) at [1]
>>>>
>>>> Besides removing expired ports, it:
>>>> - - de-orbits support for Linux 2.4.2 (is that still available in
>>>> the kernel?)
>>> Yes, we can still switch to 2.4.2-emulation in the kernel.
>> Time to de-orbit that too?
> It doesn't seem to hurt, and you can run an old program how it was
> meant to run. Nothing prevents someone to put an old linux FS into
> FreeBSD and use it there. We just do not want to distribute an old and
> unsupported by upstream linux_base port. If you use a trusted
> environment for a specific purpose, it's still possible with FreeBSD
> to run this e.g. in a jail (and as such have a lightweight
> virtualization without the need to have driver support inside the old
> linux version which is used inside).
That should indeed still be possible, there is indeed just no userland
support from FreeBSD for it any longer.
>>>> [emulators/linux_base-c6]
>>>> - - remove the unsupported Linux 2.4.2 case
>>>> - - new Makefile header
>>>> - - portlint fixes
>>> I think the "-p" for makedir was placed there on purpose... can't
>>> remember what the error-case was which triggered this.
>> If you remember, could you write it down in the Makefile? The -p flag
>> is the default for ${MKDIR} (see Mk/bsd.commands.mk)
> Hmmm... I would rather say let's forget about it, what you do in the
> patch is supposed to work correctly.
OK.

I'll send the patch of to portmgr for an exp-run in the next few days, I
think the following can be resolved later:
- cleanup direct commands in pkg-install files
- make sure the alternative (centos, gentoo) base ports work
- propose some warning for 7.X users (preferably on freebsd-ports)

Rene



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?513BBD57.20307>