can this be done in a way that makes the next update a 'just drop the
new drive in' way.
what I mean is something automated, or that just uses the code as is.
making updates much easier.
Just a thought.
On Tue, Mar 18, 2003 at 01:22:46PM -0600, Randy Couey wrote:
I am currently negotiating
Whether or not an update occurs, I would suggest that patches have a
place on the grub ftp site, as the official releases will always fall
behind the newest hardware. An unsupported patches directory, with a
use-at-your-own-risk policy, would be a useful source for adminstrators
At Fri, 14 Mar 2003 23:57:21 +,
James Scott wrote:
I enclose a patch which adds e1000 support to grub 0.93, using code from
the etherboot sources.
Thanks, but I prefer updating all drivers to just adding one driver.
If nobody wants to do that, I would have to do that myself. Ummh.
Okuji
Yoshinori K. Okuji wrote:
At Fri, 14 Mar 2003 23:57:21 +,
James Scott wrote:
I enclose a patch which adds e1000 support to grub 0.93, using code from
the etherboot sources.
Thanks, but I prefer updating all drivers to just adding one driver.
If nobody wants to do that, I would have to do
Of course, a full update would be a very good thing, and I hope Randy
gets the go-ahead to do one.
Whether or not an update occurs, I would suggest that patches have a
place on the grub ftp site, as the official releases will always fall
behind the newest hardware. An unsupported patches
At Tue, 18 Mar 2003 22:52:40 +,
James Scott wrote:
Of course, a full update would be a very good thing, and I hope Randy
gets the go-ahead to do one.
Me, too.
Whether or not an update occurs, I would suggest that patches have a
place on the grub ftp site, as the official releases will
