Cannot mount linprocfs by unresolving sysvs?m symbols

Jung-uk Kim jkim at
Fri Apr 6 21:51:28 UTC 2007

On Friday 06 April 2007 05:20 pm, Dag-Erling Smørgrav wrote:
> Jung-uk Kim <jkim at> writes:
> > On Friday 06 April 2007 01:43 pm, Roman Divacky wrote:
> > > I dont like this, I would prefer some dynamic determining
> > > whether sysv symbols are present and if not just fill
> > > in "safe" values.
> >
> > You know I have used sysctlbyname before but it was shot down by
> > des. :-(
> I didn't shoot anything down.  If you read my email again, you'll
> see that I pointed out that it was slow, but that we didn't really
> have a choice precisely because sysv{msg,sem} were not guaranteed
> to be present.
> Dropping sysctlbyname() was *your* choice.  I agreed with the
> revised patch because you pointed out that linprocfs depends on
> linux, which depends on sysv{msg,sem}, so we *could* rely on their
> presence.

It was a bad choice of words.


Jung-uk Kim

More information about the freebsd-current mailing list