| 1 |
I think I ort to make myself a little clearer. |
| 2 |
|
| 3 |
it's not about auto detection / auto configuration. it's about information |
| 4 |
gathering and resources, sure auto configuration is an option at a much later |
| 5 |
stage but I'd much prefere a system that provides information to the usrs as |
| 6 |
a primary goal. |
| 7 |
|
| 8 |
The most important part is creating/generating unique id's for hardware that |
| 9 |
you can match the information up to. then if the system gets it wrong or |
| 10 |
dosn't have any information allowing the users to input new data (subject to |
| 11 |
review) which can then be used to expand and revise the information. |
| 12 |
|
| 13 |
-- DoctorMO -- |
| 14 |
|
| 15 |
On Friday 16 Jul 2004 20:39, Jason Rhinelander wrote: |
| 16 |
> Martin Owens wrote: |
| 17 |
> > This is probably not a new idea, but I've had the idea of creating a |
| 18 |
> > driver portage system that contains information firstly, detection |
| 19 |
> > secondly and |
| 20 |
> |
| 21 |
> In other words, what lspci/pciutils does? |
| 22 |
> |
| 23 |
> > configuration scripts and tools thirdly. |
| 24 |
> |
| 25 |
> This is (sort of) what Redhat's kudzu is meant to do - detect new |
| 26 |
> hardware and automatically configure it for you, more or less like what |
| 27 |
> MS Windows does. |
| 28 |
> |
| 29 |
> > the idea is to enable admins and users to quickly learn if their device |
| 30 |
> > is suported, find out what device they actualy have and maybe get the |
| 31 |
> > right configuration, kernel modules and scripts installed. |
| 32 |
> |
| 33 |
> Again, basically what Kudzu does. To be honest, way back when I used |
| 34 |
> Redhat and/or Mandrake, I found the automatic hardware detection |
| 35 |
> terribly annoying. |
| 36 |
> |
| 37 |
> > I just know someone has to be working on this, because it seems like such |
| 38 |
> > a worthwhile project to enable Linux to escape the hardware headache |
| 39 |
> > monica it has too readly acuired. |
| 40 |
> |
| 41 |
> I suspect Redhat's automatic detection programs annoyed more experienced |
| 42 |
> linux users (i.e. admins) than it helped; most admins are able to run |
| 43 |
> lspci in order to see what kernel configuration/modules they'll need. |
| 44 |
> |
| 45 |
> |
| 46 |
> If you really want to do something to help the "hardware headache" (I'm |
| 47 |
> not sure what 'monica' means - I couldn't find it in any dictionary) - |
| 48 |
> help the linux kernel developers to actually support more hardware more |
| 49 |
> stably (like Serial ATA, ACPI suspend-to-ram, etc.) The "hardware |
| 50 |
> headache" doesn't come from having trouble identifying cards, it comes |
| 51 |
> from having to be nearly on the bleeding edge of kernel development for |
| 52 |
> support of any hardware less than a year old. |
| 53 |
> |
| 54 |
> |
| 55 |
> -- |
| 56 |
> -- Jason Rhinelander |
| 57 |
> -- Gossamer Threads, Inc. |
| 58 |
> |
| 59 |
> |
| 60 |
> -- |
| 61 |
> gentoo-dev@g.o mailing list |
| 62 |
|
| 63 |
-- |
| 64 |
Bibliotech Ltd. |
| 65 |
|
| 66 |
|
| 67 |
|
| 68 |
-- |
| 69 |
gentoo-dev@g.o mailing list |
Archives