[Gbootroot-devel] Re: Necessary Devices -> Frame Buffer

[Jonathan R. <mtt...@ac...>]

On Tue, 22 Aug 2000, Cristian Ionescu-Idbohrn wrote:

> On Tue, 22 Aug 2000, Jonathan Rosenbaum wrote:
> 
> True. Let's put them devices in a list and test and (maybe) create them 
> one by one.

This sounds like a good idea.  /dev/MAKEDEV could be used.  We should give
the user the benefit of the doubt, maybe he wants to use a device for the
program which doesn't yet exist, but we should ask him first.  We don't
need all devices on the Boot disk.  We may consider asking him in one or
both of the ways mentioned below.
 
> > You mentioned:
> > 
> > > To make it work on my system, the way I want to, I had to add
> > > 
> > >  "video=matrox:vesa:402,depth:16 aic7xxx=verbose:0x39"
> > > 
> > > to the "append" option.
> > 
> > What I think needs to be done is to have gBootRoot bring up an interactive
> > text selection.  After a person makes the changes, gBootRoot will sense
> > the changes in the text and add the new devices as needed.  I think
> > advanced users will like this feature, otherwise gBootRoot will become an
> > installation program where the gBootRoot developers have to do all the
> > guessing about other people's systems.  gBootRoot should remain a tool. 
> > 
> > There may be better ways of doing this.  Tell me what you think?
> 
> "Another way of doing it" might be to show a new editable field with a
> default value for the append parameter.

On the other hand, maybe the person wants to enter a lot of different
things in brlilo, so it may not be a good idea to limit him to one
editable field.  We could provide both an editable field for simple needs
and the ability to edit brlilo() for complex needs.