Jeremy Huntwork wrote:
> lists wrote:
>> right now I have three completely different machines that I test the cd on.
>> 1) AMD AM2 3800+ 64bit machine, 1 GB ram, 250 GB Sata drive, dual layer
>> DVD-RW, asus graphics gard using NVidia chipset. never seem to run into
>> any problems with this one.
>>
>> 2) AMD Athlon 2200+ 768MB ram 80 GB ide drive + 34 GB ide, 54x cdrw and
>> a dual layer dvdrw, ati powered graphics card, sis900 chipset nic.  The
>> chipset wasn't supported in the cd, until I mentioned it on the list.
>>
>> 3) Dell Inspiron 3000 [ intel pentium-mmx @ 266 MHz ] 128 MB ram 3.2 GB
>> hd, 24x cdr, wireless nic. [ test new cd when it's posted for support of
>> the wireless nic. ] 2 pcmcia cardbus ports. This is the beast that is a
>> battle to boot any current distro, not just the livecd. the hardware
>> clock is damaged, as even bypassing tsc clocksource with boot parameters
>> I get tsc clocksource unstable errors whenever using time functions,
>> such as using mc to copy the sources to the hard disk, or wrapping a
>> build sequence in time  { configure [options] && make && make install }
>> I'm waiting until 6.3 is released to actually put an OS on this laptop,
>> right now it's "bare metal"
> 
> Thanks Jacqui. (That's the right name, right?) 
well you put an extra letter in it. :) Jaqui, no "c", but that's a
common typo on my name.

This is, in part, the
> type of info we need. Perhaps we can create a form online that allows 
> users to fill in specs and comments about various CDs, which ones worked 
> and what didn't, etc?
> 
> Any PHP gurus up to the task?
maybe ask linux counter for thier machine specs code?
it has most of the data fields already, with a few extra for os [ change
to cd version ] only need to enhance the machine specs for including
chipsets and peripherals [ if desired ]

or, customise a bugzilla install to track the hardware used with each
version of the cd.


I think the linux counter code would be a good option, then a report on
a specific cd version could reference that listing of hardware, rather
than having the hardware get listed every single time a version is
tested. saves on db scale in the long run.

Jaqui


-- 
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to