Le 24/03/2019 à 00:41, Thor Lancelot Simon a écrit :
On Sun, Mar 17, 2019 at 05:41:18AM +0800, Paul Goyette wrote:
On Sat, 16 Mar 2019, Maxime Villard wrote:
Regarding COMPAT_OSF1: I'm not totally sure, but it seems that Alpha's
COMPAT_LINUX uses COMPAT_OSF1 as dependency (even if there is no
While looking into creating a new module for the tap pseudo-device, I
noticed that for tun(4) we create both an 'if_tun' module and another
'tun' module. The latter of these seems to have no purpose other than
to require the former.
Perhaps there was a time when the autoload code for network
On Sun, Mar 17, 2019 at 05:41:18AM +0800, Paul Goyette wrote:
> On Sat, 16 Mar 2019, Maxime Villard wrote:
>
> > Regarding COMPAT_OSF1: I'm not totally sure, but it seems that Alpha's
> > COMPAT_LINUX uses COMPAT_OSF1 as dependency (even if there is no proper
> > dependency in the module), because
Le 16/03/2019 à 22:41, Paul Goyette a écrit :
On Sat, 16 Mar 2019, Maxime Villard wrote:
Regarding COMPAT_OSF1: I'm not totally sure, but it seems that Alpha's
COMPAT_LINUX uses COMPAT_OSF1 as dependency (even if there is no proper
dependency in the module), because there are osf1_* calls. Some
