In trying to build "make release" today, I discovered that the
"vn" driver is required now to build the boot floppies.
I would suggest that this driver be added to "GENERIC". For
what it's worth, I added the driver to my kernel, rebooted, and
completed the make release.
Thanks all.
Kent
To Un
I had earlier written (to deafening silence) that I had
been unable to build a release from current. Buildworlds
worked OK, but make release didn't.
I have since figured out what was not working, but
this leads to another question. On my particular box,
I don't have a whole lot of room on /us
> In trying to build "make release" today, I discovered that the
> "vn" driver is required now to build the boot floppies.
You make it sound like a new thing - the release process has required
the vn device for years.
> I would suggest that this driver be added to "GENERIC". For
It's already dy
>> In trying to build "make release" today, I discovered that the
>> "vn" driver is required now to build the boot floppies.
>
>You make it sound like a new thing - the release process has required
>the vn device for years.
Jordan,
Thanks for your time. I guess I need to rephrase my comment
I'v
In message <[EMAIL PROTECTED]>, Mike Smith writes:
>>
>> In trying to build "make release" today, I discovered that the
>> "vn" driver is required now to build the boot floppies.
>
>What do you mean "now"? It's _always_ been required.
I actually think you could still do it with real floppies up
>
> In trying to build "make release" today, I discovered that the
> "vn" driver is required now to build the boot floppies.
What do you mean "now"? It's _always_ been required.
> I would suggest that this driver be added to "GENERIC". For
> what it's worth, I added the driver to my kernel, re
In <[EMAIL PROTECTED]> Mike Smith <[EMAIL PROTECTED]> wrote:
>>
>> In trying to build "make release" today, I discovered that the
>> "vn" driver is required now to build the boot floppies.
>
> What do you mean "now"? It's _always_ been required.
>
>> I would suggest that this driver be added t
Curious.
I've done several (say a dozen) make release builds in the last 4 months
of 4.0-CURRENT & 5.0-CURRENT. The previous one was about 2 weeks ago.
I've never had "vn" in my kernel, nor had a problem. Maybe something
in the latest "loadable kernel modules" synchronization/version control
cha
