Menu
▾
▴
devil-linux-develop
|
From: Diego T. <dt...@co...> - 2003-09-16 23:38:45
|
this patches could be useful (at least, there are *very* useful for me) http://secure.netroedge.com/~lm78/index.html http://secure.netroedge.com/~lm78/archive/i2c-2.8.0.tar.gz patches for i2c/lmsensors. don't work for kernels 2.5/2.6. it gives lots of drivers for hardware sensors (cpu temp, cpu fan speed, etc...) available on today motherboards. http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.0.tar.gz userspace applications for installing & configuring the sensors. http://pcmcia-cs.sourceforge.net/ as always, getting the latest pcmcia-cs drivers is a must. don't even think in enabling pcmcia in-kernel support. http://www.sistina.com/products_lvm.htm http://tldp.org/HOWTO/LVM-HOWTO/ of course, if someone wants to do serious raid across several disks/partitions, he will probably use the device mapper patches + lvm2 patches to kernel. ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz user space tools ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz kernel patches for 2.4.21. http://sourceforge.net/projects/acpi useful with newer or modern pcs, mainly because 2.4.21 is obsolete in acpi terms... -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Heiko Z. <he...@zu...> - 2003-09-20 14:20:21
|
Diego Torres wrote: > this patches could be useful (at least, there are *very* useful for me) > > http://secure.netroedge.com/~lm78/index.html > > http://secure.netroedge.com/~lm78/archive/i2c-2.8.0.tar.gz > patches for i2c/lmsensors. don't work for kernels 2.5/2.6. it gives lots of drivers for hardware sensors (cpu temp, cpu fan speed, etc...) available on today motherboards. > > http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.0.tar.gz > userspace applications for installing & configuring the sensors. I would vote for including those. > http://pcmcia-cs.sourceforge.net/ > as always, getting the latest pcmcia-cs drivers is a must. don't even think in enabling pcmcia in-kernel support. > > http://www.sistina.com/products_lvm.htm > http://tldp.org/HOWTO/LVM-HOWTO/ > of course, if someone wants to do serious raid across several disks/partitions, he will probably use the device mapper patches + lvm2 patches to kernel. > > ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz > user space tools > > ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz > kernel patches for 2.4.21. Should we switch to LVM2 ? How stable is it? > http://sourceforge.net/projects/acpi > useful with newer or modern pcs, mainly because 2.4.21 is obsolete in acpi terms... True. Add some point we have to support it, the question is do we want to do it in the next release. cya Heiko |
|
From: Dean N. <di...@ti...> - 2003-09-20 21:03:06
|
>Diego Torres wrote: >> this patches could be useful (at least, there are *very* useful for me) >> >> http://secure.netroedge.com/~lm78/index.html >> >> http://secure.netroedge.com/~lm78/archive/i2c-2.8.0.tar.gz >> patches for i2c/lmsensors. don't work for kernels 2.5/2.6. it gives lots of drivers for hardware sensors (cpu temp, cpu fan speed, etc...) available on today motherboards. >> >> http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.0.tar.gz >> userspace applications for installing & configuring the sensors. > >I would vote for including those. Yes, -IF- we decided to run a monitor on one of the virtual consoles (maybe #9?), like we today with procinfo. >> >> http://www.sistina.com/products_lvm.htm >> http://tldp.org/HOWTO/LVM-HOWTO/ >> of course, if someone wants to do serious raid across several disks/partitions, he will probably use the device mapper patches + lvm2 patches to kernel. >> >> ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz >> user space tools >> >> ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz >> kernel patches for 2.4.21. > >Should we switch to LVM2 ? How stable is it? LVM2 was selected over EVMS to replace LVM for the 2.6 kernel. It probably shouldn't be considered stable at this point. In fact, they are still trying to trace down Raid induced file corruption in the 2.6 kernel series. >> http://sourceforge.net/projects/acpi >> useful with newer or modern pcs, mainly because 2.4.21 is obsolete in acpi terms... > >True. Add some point we have to support it, the question is do we want >to do it in the next release. I would vote to ship the V1.0 WITHOUT the ACPI enhancements, in order to actually SHIP V1.0! Now, I am as guilty of feature creap as anybody, but at somepoint we need to start looking at putting a stake in the ground with what we have, close up the bugs, and mark it V1.0. Just my thoughts.... Dean Nedelman TimeLord Consulting |
|
From: Heiko Z. <he...@zu...> - 2003-09-20 21:56:20
|
Dean Nedelman wrote: >>Diego Torres wrote: >> >>>this patches could be useful (at least, there are *very* useful for me) >>> >>>http://secure.netroedge.com/~lm78/index.html >>> >>> http://secure.netroedge.com/~lm78/archive/i2c-2.8.0.tar.gz >>> patches for i2c/lmsensors. don't work for kernels 2.5/2.6. it gives lots > > of drivers for hardware sensors (cpu temp, cpu fan speed, etc...) available > on today motherboards. > >>> http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.0.tar.gz >>> userspace applications for installing & configuring the sensors. >> >>I would vote for including those. > > > Yes, -IF- we decided to run a monitor on one of the virtual consoles (maybe > #9?), like we today with procinfo. I like that idea ! >>>http://www.sistina.com/products_lvm.htm >>>http://tldp.org/HOWTO/LVM-HOWTO/ >>> of course, if someone wants to do serious raid across several > > disks/partitions, he will probably use the device mapper patches + lvm2 > patches to kernel. > >>> ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz >>> user space tools >>> >>> ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz >>> kernel patches for 2.4.21. >> >>Should we switch to LVM2 ? How stable is it? > > > LVM2 was selected over EVMS to replace LVM for the 2.6 kernel. It probably > shouldn't be considered stable at this point. In fact, they are still > trying to trace down Raid induced file corruption in the 2.6 kernel series. OK, let's stick with LVM1. It works fine for me >>>http://sourceforge.net/projects/acpi >>> useful with newer or modern pcs, mainly because 2.4.21 is obsolete in > > acpi terms... > >>True. Add some point we have to support it, the question is do we want >>to do it in the next release. > > > I would vote to ship the V1.0 WITHOUT the ACPI enhancements, in order to > actually SHIP V1.0! Yes I agree. > Now, I am as guilty of feature creap as anybody, but at somepoint we need to > start looking at putting a stake in the ground with what we have, close up > the bugs, and mark it V1.0. I actually was working on closing most of the bugs. I updated my server at home to the latest CVS release and found quite a few problems (all fixed in CVS). cya Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-09-21 00:41:16
|
Heiko Zuerker wrote: > Dean Nedelman wrote: > >>> Diego Torres wrote: >>> >>>> this patches could be useful (at least, there are *very* useful for me) >>>> >>>> http://secure.netroedge.com/~lm78/index.html >>>> >>>> http://secure.netroedge.com/~lm78/archive/i2c-2.8.0.tar.gz >>>> patches for i2c/lmsensors. don't work for kernels 2.5/2.6. it gives >>>> lots >> >> >> of drivers for hardware sensors (cpu temp, cpu fan speed, etc...) >> available >> on today motherboards. >> >>>> http://secure.netroedge.com/~lm78/archive/lm_sensors-2.8.0.tar.gz >>>> userspace applications for installing & configuring the sensors. >>> >>> >>> I would vote for including those. >> >> >> >> Yes, -IF- we decided to run a monitor on one of the virtual consoles >> (maybe >> #9?), like we today with procinfo. > > > I like that idea ! The I2C and LM_SENSORS stuff is in CVS now. I have to start a clean compile and will provide a new testing release tomorrow when everything works. Then you guys can work on the console-status stuff. cya Heiko |
|
From: Diego T. <dt...@co...> - 2003-09-21 13:37:28
|
On Sat, Sep 20, 2003 at 08:38:27PM -0400, Heiko Zuerker wrote: > >I like that idea ! > > The I2C and LM_SENSORS stuff is in CVS now. > I have to start a clean compile and will provide a new testing release > tomorrow when everything works. > Then you guys can work on the console-status stuff. i'm going to use it (at least try it) on a vmware machine under win2k. hope it works :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-09-21 13:36:33
|
On Sat, Sep 20, 2003 at 02:02:26PM -0700, Dean Nedelman wrote: > >> ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz > >> kernel patches for 2.4.21. > > > >Should we switch to LVM2 ? How stable is it? > > LVM2 was selected over EVMS to replace LVM for the 2.6 kernel. It probably > shouldn't be considered stable at this point. In fact, they are still > trying to trace down Raid induced file corruption in the 2.6 kernel series. i don't think so. in 2.6 there is a device_mapper infraestructure, that enables you to use evms or lvm2 from userspace. There are 3 possibilities, md (the usual raid stuff), dm (devicemapper) -> lvm2 || evms. -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Dean N. <di...@ti...> - 2003-09-21 16:08:48
|
>> >> LVM2 was selected over EVMS to replace LVM for the 2.6 kernel. It probably >> shouldn't be considered stable at this point. In fact, they are still >> trying to trace down Raid induced file corruption in the 2.6 kernel series. > >i don't think so. in 2.6 there is a device_mapper infraestructure, that enables >you to use evms or lvm2 from userspace. There are 3 possibilities, md (the >usual raid stuff), dm (devicemapper) -> lvm2 || evms. There were two competing designs - lvm2 and evms. LVM2 used a device mapper (dm) to manage its core functionality and evms used a much more kernel intrusive approach. In the end it was decided to go with LVM2, at which point the EVMS group took a step back and completely rewrote their system so that it could be run on top of LVM2's device mapper system. But the entire device_mapper infrastructure -is- LVM2's. Dean Nedelman TimeLord Consulting |
|
From: Diego T. <dt...@co...> - 2003-09-21 13:34:46
|
On Sat, Sep 20, 2003 at 10:15:51AM -0400, Heiko Zuerker wrote: > > ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz > > user space tools > > > > ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz > > kernel patches for 2.4.21. > > Should we switch to LVM2 ? How stable is it? i've been using it for 1'5 years. never had a problem, but my configuration is pretty simple, 3 hds on a raid0 (stripped) configuration. > >http://sourceforge.net/projects/acpi > > useful with newer or modern pcs, mainly because 2.4.21 is obsolete in > > acpi terms... > > True. Add some point we have to support it, the question is do we want > to do it in the next release. maybe better if we wait to the next release, acpi is a strange thing :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
