> On Apr 20, 2019, at 9:44 AM, John Baldwin <j...@freebsd.org> wrote:
>
> On 4/20/19 6:23 AM, Justin Hibbits wrote:
>> On Sat, Apr 20, 2019, 08:21 Alan Somers <asom...@freebsd.org> wrote:
>>
>>> On Sat, Apr 20, 2019 at 6:58 AM Justin Hibbits <chmeeed...@gmail.com>
>>> wrote:
>>>>
>>>>
>>>>
>>>> On Sat, Apr 20, 2019, 07:51 Alan Somers <asom...@freebsd.org> wrote:
>>>>>
>>>>> Author: asomers
>>>>> Date: Sat Apr 20 12:51:05 2019
>>>>> New Revision: 346441
>>>>> URL: https://svnweb.freebsd.org/changeset/base/346441
>>>>>
>>>>> Log:
>>>>> Use symlinks for kernel modules rather than hardlinks
>>>>>
>>>>> When aliasing a kernel module to a different name (ie if_igb for
>>> if_em),
>>>>> it's better to use symlinks than hard links. kldxref will omit
>>> entries for
>>>>> the links, ensuring that the loaded module has the correct name.
>>>>>
>>>>>
>>>>
>>>>
>>>> Thanks! This should fix installkernel on my POWER9.
>>>>
>>>> - Justin
>>>
>>> What's the problem with your POWER9? Is that one of those msdosfs
>>> /boot systems? If so, I don't think this will fix it. msdosfs
>>> doesn't support either symlinks or hardlinks. Or is there some other
>>> problem?
>>> -Alan
>>>
>>
>> Yes it is. Well that's a bummer then. I thought we faked symlinks on
>> msdosfs, but on second thought not sure how well would do that.
>
> You could just use cp instead of a link?
*eyes `install -l`*:
-l linkflags
Instead of copying the file make a link to the source. The type
of the link is determined by the linkflags argument. Valid
linkflags are: a (absolute), r (relative), h (hard), s
(symbolic), m (mixed). Absolute and relative have effect only
for symbolic links. Mixed links are hard links for files on the
same filesystem, symbolic otherwise.
Cheers,
-Enji
_______________________________________________
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"