extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-11-24 00:23:28 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add a link in the download page. Improve readability of the LEAF/Bering bullet

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@9854 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2009-04-12 17:13:37 +00:00
parent 665cce0f20
commit 69c99bae2c
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
web/download.htm
View File

@ -150,7 +150,8 @@ it from the Arch Linux site</a>. </p>
<li> <li>
<p style="margin-bottom: 0in;">If you run a <b>SUSE,</b> <b>Linux <p style="margin-bottom: 0in;">If you run a <b>SUSE,</b> <b>Linux
PPC</b>, <b>Trustix</b> or <b>TurboLinux</b> distribution with a 2.4 PPC</b>, <b>Trustix</b> or <b>TurboLinux</b> distribution with a 2.4
or 2.6 kernel, you can use the standard RPM version (note: the RPM or 2.6 kernel, you can use the <a href="#Sites">standard RPM version</a>
(note: the RPM
should also work with other distributions that store init scripts in should also work with other distributions that store init scripts in
/etc/init.d and that include chkconfig or insserv). If you find that it /etc/init.d and that include chkconfig or insserv). If you find that it
works in other cases, let <a href="mailto:teastep@shorewall.net">me</a> works in other cases, let <a href="mailto:teastep@shorewall.net">me</a>
@ -184,7 +185,10 @@ Hardy Heron</a>.<br>
or one if it's or one if it's
derivatives, you can download a .lrp file from the Leaf site.<br> derivatives, you can download a .lrp file from the Leaf site.<br>
<br> <br>
From the LEAF Bering-uClibc Team: We try to provide the latest stable From the LEAF Bering-uClibc Team: <br>
<br>
</p>
<div style="margin-left: 40px;">We try to provide the latest stable
version shortly after release, but we also want to do some internal version shortly after release, but we also want to do some internal
tests before making it available. So we may be behind sometimes. But tests before making it available. So we may be behind sometimes. But
better be sure that the new version is running on LEAF, than being too better be sure that the new version is running on LEAF, than being too
@ -200,9 +204,9 @@ shorewall.lrp is part of the packages page:<br>
which itself links to cvs:<br> which itself links to cvs:<br>
<br> <br>
<a <a
href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/bering-uclibc/packages/shorwall.lrp?rev=HEAD&amp;content-type=application/octet-stream">http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/bering-uclibc/packages/shorwall.lrp?rev=HEAD&amp;content-type=application/octet-stream<br> href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/bering-uclibc/packages/shorwall.lrp?rev=HEAD&amp;content-type=application/octet-stream">http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/leaf/bin/bering-uclibc/packages/shorwall.lrp?rev=HEAD&amp;content-type=application/octet-stream</a><br>
<br> <br>
</a></p> </div>
</li> </li>
<li>Shorewall packages for <a target="_top" <li>Shorewall packages for <a target="_top"
href="http://www.slackware.com/"><span style="font-weight: bold;">Slackware</span></a> href="http://www.slackware.com/"><span style="font-weight: bold;">Slackware</span></a>