Migrate links to new site and system

git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@4063 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Rudolf Marek committed 2006-07-02 19:50:05 +00:00
1 parent d3fa65e9f6
commit 7e1836636c
14 files changed
+55 -86

No files matched your search

+1 -1
View File
@@ -1,6 +1,6 @@
Except for many unimplemented things (listed in the TODO file), there may be
true bugs too. If you experience any problems not listed here,
do not hesitate to mail us (see http://secure.netroedge.com/~lm78/author.html).
do not hesitate to mail us (see http://www.lm-sensors.org/wiki/FeedbackAndSupport).
But read this file and doc/FAQ first, please!
============================================================================
+1 -1
View File
@@ -1,6 +1,6 @@
This package could not have been created without the help of many, many people.
The most notable contributors are listed below. You are probably best off
to use the mailing list (see http://secure.netroedge.com/~lm78/author.html)
to use the mailing list (see http://www.lm-sensors.org/wiki/AuthorsAndContributors)
if you have questions, suggestions or problems.
* Alexander Larsson <alla@lysator.liu.se>
+5 -5
View File
@@ -43,7 +43,7 @@ but is not API compatible to i2c releases 2.8.0 - 2.8.8
due to struct changes. Versions 2.8.x of i2c are considered deprecated.
See the lm_sensors download page for further guidance:
http://secure.netroedge.com/~lm78/download.html
http://www.lm-sensors.org/wiki/Download
WARNING! If you downloaded this package through our CVS archive, you walk
@@ -114,7 +114,7 @@ We also support some miscellaneous chips:
The list above may be out of date;
see our New Drivers page http://www.lm-sensors.nu/~lm78/newdrivers.html
see our New Drivers page at http://www.lm-sensors.org/wiki/NewDrivers
for the latest information on supported devices.
You may also refer to doc/chips/SUMMARY for details on what each chip
can monitor.
@@ -167,14 +167,14 @@ On the other hand, we provide a program called 'sensors-detect' which
tries to figure out what hardware is available on your system.
The developers of this package can be reached through a mailing-list
(see http://secure.netroedge.com/~lm78/author.html). Do not hesitate
(see http://www.lm-sensors.org/wiki/AuthorsAndContributors). Do not hesitate
to mail us if you have questions, suggestions, problems, want to
contribute, or just want to report it works for you. But please try to
read the documentation and FAQ before you ask any questions!
The latest version of this package can always be found on our homepage:
http://secure.netroedge.com/~lm78/. Pre-release versions can be retrieved
through anonymous CVS; see doc/cvs for more information.
http://www.lm-sensors.org. Pre-release versions can be retrieved
through anonymous SVN; see doc/svn for details.
This package may be distributed according to the GNU General Public
License (GPL), as included in the file COPYING.
+2 -2
View File
@@ -1131,7 +1131,7 @@ are running the `sensors' program it installed and not some older
* (Linux 2.6) Make sure you are using one of the recommended
kernel/lm_sensors combination
(http://secure.netroedge.com/~lm78/kernel26.html).
(http://www.lm-sensors.org/wiki/Kernel2.6).
* You have a `libsensors'/`sensors' mismatch. `sensors' is unable to
get a data entry from `libsensors'. You probably have an old
@@ -1272,7 +1272,7 @@ Post your question to our discussion list
individual authors, unless you have something private to say.
Instead of using email, you can also use the web-based support area,
at `http://secure.netroedge.com/~lm78/support.html'. You will be helped
at `http://www.lm-sensors.org/wiki/FeedbackAndSupport'. You will be helped
just as fast, and others may profit from the answer too. You will be
emailed automatically when your question has been answered.
+1 -1
View File
@@ -48,7 +48,7 @@ Note: kernel versions later than 2.4.18 not tested.
If anyone owns a board with those chips AND is willing to risk crashing &
burning an otherwise well-behaved kernel in the name of progress... please
contact me at <amalysh@web.de> or via the project's mailing list: see
http://secure.netroedge.com/~lm78/author.html. Please send bug reports
http://www.lm-sensors.org/wiki/AuthorsAndContributors. Please send bug reports
and/or success stories as well.
+1 -1
View File
@@ -56,7 +56,7 @@ as well: 635, and 635T.
If anyone owns a board with those chips AND is willing to risk crashing &
burning an otherwise well-behaved kernel in the name of progress... please
contact me at <mhoffman@lightlink.com> or via the project's mailing list:
see http://secure.netroedge.com/~lm78/author.html. Please send bug reports
see http://www.lm-sensors.org/wiki/AuthorsAndContributors. Please send bug reports
and/or success stories as well.
+1 -1
View File
@@ -9,7 +9,7 @@ directory.
To determine what chips you have in your system, run 'sensors-detect'.
If your sensor chip is not detected by sensors-detect, please contact us
(see http://secure.netroedge.com/~lm78/author.html). Only contact us
(see http://www.lm-sensors.org/wiki/AuthorsAndContributors). Only contact us
if you know for sure that your system includes a sensor chip (for
example if you have technical documentation mentioning it, or if the
BIOS setup screen presents monitoring values, or if you can get
-63
View File
@@ -1,63 +0,0 @@
Using the lm_sensors2 and i2c CVS archives
------------------------------------------
(This is based on mails from Philip and William, and edited by Frodo)
Anybody can now use CVS to access the code archive. CVS allows you to get
the latest and greatest version of lm_sensors, or any older version.
You need the rcs and cvs package, which can be retrieved from any GNU
mirror site (prep.ai.mit.edu is the master site).
1) Go to the directory where you want the lm_sensors2 (or i2c or lm_sensors)
directory to reside with the project source code. A good choice is
your home directory.
2) Assuming you have cvs installed (many distributions do include it).
Type:
cvs -d :pserver:anon@penn.netroedge.com:/home/cvs login
And type in "anonymous" at the password prompt.
3) Then to check out a project (in this case 'lm_sensors2'), type:
cvs -d :pserver:anon@penn.netroedge.com:/home/cvs checkout lm_sensors2
Use "lm_sensors2" for the 2.x tree; use "i2c" for the i2c tree.
If you _really_ want the ancient lm_sensors (1.x) tree, use "lm_sensors"
(although nobody is making changes to this tree).
4) Now you have a directory named "lm_sensors2" with all
the files in it. In a day or two when there have been some changes to
some of the files, you can do something like this to update your files
to the CVS archive's (be sure to be inside the lm_sensors2 directory for
this to work):
cvs update
If you want to be able to commit changes yourself, you need a real login
(as opposed to the anon login used above). Run the script
doc/developers/genpasswd.pl and follow the instructions to
get a login.
Some often-used CVS commands:
(-z3 is for compression, which speeds things up on slow links)
* login again (usually not needed)
cvs -z3 login
* get the most recent versions of the sources
cvs -z3 update
* commit your changes
cvs -z3 commit
When you commit, it will bring up an editor (probably vi) and ask you to
summarize your changes. Be verbose! we've also set things up so that everybody
gets an email whenever somebody checks in some changes which tells them the
names of the changed files and also the log message; we can turn this off for
you if you find it annoying.
It might be a good idea to browse the CVS documentation; you can do lots of
neat stuff like set watches on files. Also if you encounter conflicts you'll
need to know what to do. There is a short manpage, and a rather extensive
info manual (try 'info cvs').
Be warned that the CVS archive is not always stable or safe, or will even
compile. Review the CHANGES document in CVS for issues that may affect you.
Sometimes files are committed with known bugs. This is usually reported in
the commit logs or on our mailing list; non-developers will receive neither
(though you can ask cvs to show the logs, even if you only have a anon
acount).
+3 -3
View File
@@ -136,10 +136,10 @@ steps apply.
* If you want to have your driver integrated to Linux 2.6, you have to
port your driver to the new sysfs interface. Once done and preferably
after testing, submit a patch to our mailing list: see
http://secure.netroedge.com/~lm78/author.html
http://www.lm-sensors.org/wiki/AuthorsAndContributors
Make sure to check the current status for your driver first:
http://secure.netroedge.com/~lm78/kernel26.html
http://secure.netroedge.com/~lm78/newdrivers.html
http://www.lm-sensors.org/wiki/Kernel2.6
http://www.lm-sensors.org/wiki/NewDrivers
---------------------------------------------------------------------
Checklist for us to do on the webpage:
+1 -1
View File
@@ -12,7 +12,7 @@ so hardware which isn't directly related to the development of a hardware
monitoring driver, but can be used to build test systems, is welcome too.
If you would like to make a donation, please contact us. See
http://secure.netroedge.com/~lm78/author.html. Thanks!
http://www.lm-sensors.org/wiki/AuthorsAndContributors. Thanks!
Donations are listed in chronological order. Note that the person mentioned
+3 -2
View File
@@ -1612,7 +1612,7 @@ Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
<ul>
<li>(Linux 2.6) Make sure you are using one of the
<a href="http://secure.netroedge.com/~lm78/kernel26.html">recommended kernel/lm_sensors combination</a>.
<a href="http://www.lm-sensors.org/wiki/Kernel2.6">recommended kernel/lm_sensors combination</a>.
<li>You have a <span class="file">libsensors</span>/<span class="command">sensors</span> mismatch.
<span class="command">sensors</span> is unable to
get a data entry from <span class="file">libsensors</span>. You probably have an
@@ -1807,7 +1807,8 @@ and not the individual authors,
unless you have something private to say.
<p>Instead of using email, you can also use the web-based support
area, at <a href="http://secure.netroedge.com/~lm78/support.html">http://secure.netroedge.com/~lm78/support.html</a>. You will be helped
area, at <a href="http://www.lm-sensors.org/wiki/FeedbackAndSupport">
http://www.lm-sensors.org/wiki/FeedbackAndSupport</a>. You will be helped
just as fast, and others may profit from the answer too. You will be
emailed automatically when your question has been answered.
+2 -2
View File
@@ -1167,7 +1167,7 @@ and not some older @command{sensors}.
@itemize
@item (Linux 2.6) Make sure you are using one of the
@uref{http://secure.netroedge.com/~lm78/kernel26.html,
@uref{http://www.lm-sensors.org/wiki/Kernel2.6,
recommended kernel/lm_sensors combination}.
@item You have a @file{libsensors}/@command{sensors} mismatch.
@command{sensors} is unable to
@@ -1315,7 +1315,7 @@ and not the individual authors,
unless you have something private to say.
Instead of using email, you can also use the web-based support
area, at @uref{http://secure.netroedge.com/~lm78/support.html}. You will be helped
area, at @uref{http://www.lm-sensors.org/wiki/FeedbackAndSupport}. You will be helped
just as fast, and others may profit from the answer too. You will be
emailed automatically when your question has been answered.
+31
View File
@@ -0,0 +1,31 @@
Subversion Repository
Anonymous access to our Subversion repository (SVN) is available. This means
that users can have direct access to up-to-the-minute code.
(http://subversion.tigris.org/)
Driver development for 2.6 kernels is taking place directly in the kernel
using GIT. Do not use the drivers from our SVN repository for 2.6 kernels, it
will not work. The user-space tools will work though.
We presume that you have Subversion installed on your machine. To check out a
working copy of the code for this project use the following commands:
svn checkout http://lm-sensors.org/svn/i2c/trunk i2c
svn checkout http://lm-sensors.org/svn/lm-sensors/trunk lm-sensors
To update the code, do a svn update from within the i2c or lm-sensors
directories. Please read the README and INSTALL files of your working copy
for how to build the code. Also read the related files in the 'doc' directory
for info regarding the different bus and chip drivers. Lastly, you can use
the regular svn commands on the files (like cvs log [filename]) to see the
comments made by the developers as changes were made.
If you're not familiar with the use of Subversion we recommend the excellent
Subversion book which is a valuable resource.
(http://svnbook.red-bean.com/)
Commits to the repositories are notified on the lm-sensors-notify
mailing-list. Feel free to subscribe if you want to be informed of the
changes made to the i2c and lm-sensors repositories.
(http://lists.lm-sensors.org/mailman/listinfo/lm-sensors-notify)
+3 -3
View File
@@ -2356,7 +2356,7 @@ sub adapter_pci_detection
$device->{bus},$device->{slot},$device->{func},$try->{procid};
if ($try->{driver} eq "to-be-tested") {
print "\nWe are currently looking for testers for this adapter!\n".
"Please see http://secure.netroedge.com/~lm78/newdrivers.html\n".
"Please see http://www.lm-sensors.org/wiki/NewDrivers\n".
"and/or contact us if you want to help.\n\n";
print "Continue... ";
<STDIN>;
@@ -5190,7 +5190,7 @@ sub generate_modprobes
#check return value from modprobe in case modprobe -l isn't supported
if((($? >> 8) == 0) && ! $modulefound) {
$modprobes .= "# Warning: the required module $chip->{driver} is not currently installed on your system.\n";
$modprobes .= "# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html\n";
$modprobes .= "# For status of 2.6 kernel ports see http://www.lm-sensors.org/wiki/SupportedDevices\n";
$modprobes .= "# If driver is built-in to the kernel, or unavailable, comment out the following line.\n";
}
$modprobes .= "modprobe $chip->{driver}\n";
@@ -5421,7 +5421,7 @@ sub main
" http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html\n",
" (FAQ #4.24.3) for further information.\n",
" If you find out what chips are on your board, see\n",
" http://secure.netroedge.com/~lm78/newdrivers.html for driver status.\n";
" http://www.lm-sensors.org/wiki/NewDrivers for driver status.\n";
exit;
}