![]() |
Optware.Packages HistoryHide minor edits - Show changes to markup February 24, 2011, at 10:54 AM
by -- LLMP for Plug Computers.
Changed line 105 from:
to:
December 20, 2010, at 03:09 AM
by --
Changed lines 33-34 from:
The oPTWARE package repositorIES can be found at http://ipkg.nslu2-linux.org/feeds/ to:
The Optware package repositories can be found at http://ipkg.nslu2-linux.org/feeds/ December 20, 2010, at 03:08 AM
by --
Changed lines 20-27 from:
You can update your ipkg database on the slug with To check out a list of available packages, use To see the packages you already have installed, use To install a new package, use to:
Changed lines 33-41 from:
The Unslung package repository can be found at http://ipkg.nslu2-linux.org/feeds/unslung To find ipkgs that have already been made : http://ipkgfind.nslu2-linux.org Cross-complied package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/cross/Packages Natively compiled package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages These packages require you to be running the Unslung firmware. to:
The oPTWARE package repositorIES can be found at http://ipkg.nslu2-linux.org/feeds/ Changed lines 44-45 from:
You can contribute it yourself (to learn more, see AddAPackageToOptware). Or you can add it to the PackageWishList and hope that someone else provides it. to:
December 20, 2010, at 02:47 AM
by --
Deleted lines 10-13:
Preamble for UnslungIf you are using Unslung, before attempting to run ipkg, install or use a package, or update the list of packages, make sure that you have installed a hard drive or memory stick and "unslung" to it. Failure to do so may fill your NSLU2's internal Flash RAM with too much data and not allow it to reboot. To recover, follow the Recover From A Bad Flash process. Changed lines 13-32 from:
In general, packages are commonly-available software programs that we have simply ported to the NSLU2. The effort to do this work is provided by the volunteer NSLU2 Linux community. If you have a question on how to use a particular package, please use Google or something to search for the general documentation about the package before asking questions that are not specific to the NSLU2 port of the package. For example, Google "man tar" for information on how to use the "tar" application. When using Unslung, look under /opt for the corresponding files for a particular package. First Steps
If you're having problems at this stage connecting with ipkg, see this troubleshooting FAQ. to:
In general, packages are commonly-available software programs that we have simply ported to the Optware environment. The effort to do this work is provided by the volunteer Optware community. If you have a question on how to use a particular package, please use Google or something to search for the general documentation about the package before asking questions that are not specific to the platform's port of the package. For example, Google "man tar" for information on how to use the "tar" application. December 20, 2010, at 02:45 AM
by --
Changed lines 1-4 from:
Preamble for OptWareThe OptWare package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms, however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. to:
Optware IntroductionFor a detailed description of Optware's history and current state, see the Optware Home Page. For information on installing Optware on the NSLU2, see the Slug Install page. Note about the OptWare documentationMuch of the documentation hasn't been updated to remove NSLU2 references, so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. Don't panic. November 24, 2010, at 12:54 AM
by -- ddclient
Added line 101:
December 29, 2009, at 07:01 AM
by -- Add wikilink for vsftpd-FTP to vsftpd entry.
Changed line 183 from:
to:
December 28, 2009, at 06:03 AM
by -- Add entry and wikilink for SWAT, Samba Web Administration Tool
Added line 162:
August 09, 2008, at 03:04 PM
by -- Fixed entry for Hplip to an Optware package page
Changed line 117 from:
to:
August 08, 2008, at 04:21 PM
by -- References HPLIP on Unslung scanning
Added line 117:
August 08, 2008, at 03:10 PM
by -- added `TorrentFlux
Changed lines 174-175 from:
to:
May 10, 2008, at 05:32 PM
by -- add clutch howto link
Added line 95:
April 01, 2008, at 10:30 PM
by -- added mimms
Added line 129:
March 19, 2008, at 07:45 PM
by --
Changed line 85 from:
to:
March 19, 2008, at 07:44 PM
by -- fixing link
Changed line 85 from:
to:
March 19, 2008, at 07:42 PM
by -- Adding BD
Added line 85:
November 15, 2007, at 09:12 AM
by -- layout
Added line 59:
November 15, 2007, at 09:12 AM
by -- Added list of mirrors
Added lines 56-60:
Mirrorsnslu2-linux, US (main) OSUOSL, US October 19, 2007, at 10:14 PM
by -- Added dstat
Changed lines 97-98 from:
nfsstat, and ifstat to:
October 19, 2007, at 10:13 PM
by -- Added dstat
Added lines 97-98:
nfsstat, and ifstat September 21, 2007, at 06:56 PM
by -- Added castget
Changed line 84 from:
to:
September 21, 2007, at 06:56 PM
by -- added castget
Added line 84:
September 15, 2007, at 02:11 AM
by -- added a couple of wiki implementations
Added line 170:
September 15, 2007, at 02:10 AM
by -- added yawk
Added line 173:
September 07, 2007, at 03:08 AM
by -- link to Optware.Haserl
Changed line 105 from:
to:
September 06, 2007, at 09:54 PM
by -- added haserl
Added line 105:
September 05, 2007, at 10:49 PM
by --
Changed line 81 from:
to:
September 05, 2007, at 10:38 PM
by --
Changed line 81 from:
to:
September 02, 2007, at 10:06 PM
by -- added ipcalc and sipcalc
Added line 105:
Changed line 108 from:
to:
September 02, 2007, at 09:58 PM
by -- added btpd, and nickle
Changed lines 80-81 from:
to:
Added line 83:
Changed line 133 from:
to:
August 29, 2007, at 08:02 PM
by -- added a few Smalltalk ports
Added line 150:
June 21, 2007, at 04:41 PM
by -- added jove to emacs clone list
Changed line 95 from:
to:
June 11, 2007, at 02:40 PM
by -- emacs clones
Changed line 95 from:
to:
June 11, 2007, at 05:28 AM
by -- added git & mercurial
Added line 100:
Added line 115:
June 11, 2007, at 05:18 AM
by -- added erlang, cvm
Changed lines 95-96 from:
to:
Added line 134:
June 11, 2007, at 05:14 AM
by -- added cherokee, lighttpd & nginx
Added line 84:
Added line 106:
Added line 128:
June 11, 2007, at 05:11 AM
by -- added mldonkey & emacs
Added lines 94-95:
Deleted line 96:
Added line 111:
June 11, 2007, at 05:07 AM
by -- added rtorrent
Added line 133:
June 11, 2007, at 05:06 AM
by -- added screen
Deleted line 134:
Added lines 136-137:
June 11, 2007, at 05:05 AM
by -- added slrn & slsc
Added lines 137-138:
June 11, 2007, at 05:04 AM
by -- added tin
Added line 142:
June 11, 2007, at 05:03 AM
by -- added vim
Added line 148:
June 01, 2007, at 06:47 AM
by -- ccollect added
Added line 82:
May 30, 2007, at 07:03 PM
by -- minor spelling fix
Changed lines 29-30 from:
If you're having problems at this stage connecting with ipkg, see this troubshooting FAQ. to:
If you're having problems at this stage connecting with ipkg, see this troubleshooting FAQ. February 10, 2007, at 03:55 PM
by -- Added memtest
Added line 108:
February 08, 2007, at 11:48 AM
by --
Changed lines 33-34 from:
You can update your ipkg database on the slug with to:
You can update your ipkg database on the slug with February 08, 2007, at 05:16 AM
by -- added nanoblogger
Added line 114:
January 18, 2007, at 04:35 PM
by -- Added entry for syslog-ng
Added line 135:
January 17, 2007, at 09:42 PM
by -- Added Logrotate link
Added line 103:
January 12, 2007, at 04:55 PM
by -- changed package list URL
Changed lines 41-42 from:
The complete package list is also available here. to:
The complete package list is also browsable here. January 08, 2007, at 10:12 PM
by -- Added gnokii
Added line 97:
January 07, 2007, at 09:20 AM
by -- amule
Added line 78:
December 21, 2006, at 09:51 AM
by -- Transmission
Added line 135:
December 18, 2006, at 10:04 PM
by -- Avoid WikiWord KiSS
Changed line 99 from:
to:
December 18, 2006, at 09:22 PM
by -- Add kissdx to list of packages
Added line 99:
December 07, 2006, at 09:44 PM
by -- Added atop
Added line 77:
November 16, 2006, at 04:30 PM
by -- fixed external links
Changed line 121 from:
to:
Changed line 123 from:
to:
Changed lines 142-143 from:
to:
November 16, 2006, at 01:59 AM
by -- reorganizing information about Optware packages
Changed lines 59-60 from:
You can contribute it yourself (to learn more, see AddAPackageToUnslung). Or you can add it to the PackageWishList and hope that someone else provides it. to:
You can contribute it yourself (to learn more, see AddAPackageToOptware). Or you can add it to the PackageWishList and hope that someone else provides it. November 16, 2006, at 01:12 AM
by -- reorganizing information about Optware packages
Changed lines 29-30 from:
If you're having problems at this stage connecting with ipkg, see this troubshooting FAQ. to:
If you're having problems at this stage connecting with ipkg, see this troubshooting FAQ. Changed lines 59-60 from:
You can contribute it yourself (to learn more, see AddAPackageToUnslung?). Or you can add it to the PackageWishList and hope that someone else provides it. to:
You can contribute it yourself (to learn more, see AddAPackageToUnslung). Or you can add it to the PackageWishList and hope that someone else provides it. November 16, 2006, at 01:10 AM
by -- reorganizing information about Optware packages
Changed lines 3-4 from:
The OptWare package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms as listed at http://www.nslu2-linux.org/wiki/Unslung/OptwarePlatforms however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. to:
The OptWare package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms, however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. Changed line 134 from:
to:
October 20, 2006, at 12:23 PM
by --
Changed lines 65-66 from:
Please search the wiki? to see if your problem is a known problem with a workaround. to:
Please search the wiki to see if your problem is a known problem with a workaround. September 25, 2006, at 04:59 PM
by -- Corrected link
Changed line 134 from:
to:
September 25, 2006, at 11:43 AM
by --
Changed lines 41-42 from:
The complete package list is also available here. (THIS LINK IS BROKEN) to:
The complete package list is also available here. September 10, 2006, at 06:55 AM
by -- Added working link for ushare
Changed line 135 from:
to:
September 04, 2006, at 12:05 AM
by --
Changed lines 63-64 from:
If you find any problems with the packages, please report them to NSLU2-Linux SlugBug. to:
If you find any problems with the packages, please report them to the nslu2-linux mailinglist. August 26, 2006, at 07:03 PM
by -- Added www to gphoto so that it is in the approved list?
Changed line 94 from:
to:
August 26, 2006, at 06:57 PM
by -- Added gphoto2
Added line 94:
August 25, 2006, at 08:33 PM
by -- Added link to zip
Changed lines 141-142 from:
to:
August 23, 2006, at 03:30 PM
by -- added irssi
Added line 95:
July 09, 2006, at 02:46 PM
by -- added extract-xiso
Added line 92:
July 05, 2006, at 07:17 AM
by -- add torrent
Added line 129:
June 12, 2006, at 03:04 AM
by -- Added reference do Enhanced CTorrent
Added line 90:
May 28, 2006, at 09:38 PM
by --
Changed lines 21-22 from:
to:
May 28, 2006, at 09:35 PM
by --
Added lines 21-22:
May 27, 2006, at 01:42 PM
by -- Added zip
Changed lines 135-136 from:
to:
May 22, 2006, at 10:35 PM
by -- Added nbench-byte
Added line 103:
May 18, 2006, at 11:31 PM
by -- This is a list of packeges in slug native format. If you realy want this make it a ipkg package!!!
Deleted line 130:
May 18, 2006, at 10:40 PM
by -- Restoring wizd; it is a package, just an older version
Added line 131:
May 18, 2006, at 08:11 PM
by -- Moved wizd to package wish list (build instructions != package)
Deleted line 130:
May 18, 2006, at 08:08 PM
by -- Corrected link
Changed lines 138-139 from:
Link Broken --> NOTE: The complete package list is available here. to:
NOTE: The complete package list is available at http://ipkg.nslu2-linux.org/feeds/optware/nslu2/. May 18, 2006, at 02:27 AM
by -- Add link to a wizd compiling notes page
Changed line 131 from:
to:
May 13, 2006, at 07:49 PM
by -- Added ntfsprogs
Added line 109:
May 08, 2006, at 03:30 AM
by --
Changed line 126 from:
to:
May 08, 2006, at 03:28 AM
by -- add ushare
Added line 126:
May 01, 2006, at 03:11 PM
by -- noted broken link
Changed lines 39-40 from:
The complete package list is also available here. to:
The complete package list is also available here. (THIS LINK IS BROKEN) April 03, 2006, at 10:20 PM
by -- Don\'t make OptWare a link
Changed lines 1-4 from:
Preamble for OptWare?The OptWare? package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms as listed at http://www.nslu2-linux.org/wiki/Unslung/OptwarePlatforms however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. to:
Preamble for OptWareThe OptWare package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms as listed at http://www.nslu2-linux.org/wiki/Unslung/OptwarePlatforms however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. April 03, 2006, at 10:17 PM
by -- Explain that Optware is now multi-platform
Added lines 1-4:
Preamble for OptWare?The OptWare? package system was originally created to accompany the Unslung firmware for the NSLU2 (originally the packages were also called Unslung packages). It has since been expanded to cover a variety of other platforms as listed at http://www.nslu2-linux.org/wiki/Unslung/OptwarePlatforms however much of the documentation hasn't been updated so you may still see references to Unslung and the NSLU2 when the information also applies to other platforms. March 05, 2006, at 12:26 PM
by --
Changed line 92 from:
to:
March 04, 2006, at 01:18 PM
by --
Changed line 92 from:
to:
March 04, 2006, at 01:06 PM
by -- mt-daapd problem note
Changed line 92 from:
to:
December 24, 2005, at 11:51 PM
by -- CTorrent redefinition
Changed line 77 from:
to:
December 11, 2005, at 02:07 AM
by -- adding link to relevant FAQ page
Added lines 23-24:
If you're having problems at this stage connecting with ipkg, see this troubshooting FAQ. November 23, 2005, at 02:13 PM
by -- Added digitemp
Added line 78:
November 20, 2005, at 03:55 PM
by -- Added nagios plugins and nrpe
Added line 92:
Added line 99:
September 24, 2005, at 12:03 AM
by -- Link to complete list of packages broken
Changed lines 126-127 from:
NOTE: The complete package list is available here. to:
Link Broken --> NOTE: The complete package list is available here. September 15, 2005, at 08:52 PM
by -- Changed location of upslug2
Added line 115:
Deleted line 117:
September 15, 2005, at 08:43 PM
by -- Added upslug2
Added line 117:
September 15, 2005, at 08:37 PM
by -- Added tftp-hpa
Added line 113:
September 12, 2005, at 08:56 PM
by -- Added netio
Added lines 95-97:
Deleted lines 99-100:
September 12, 2005, at 08:51 PM
by --
Changed line 80 from:
to:
September 12, 2005, at 08:50 PM
by -- Added dovecot
Added line 80:
Changed line 113 from:
to:
September 10, 2005, at 08:08 AM
by --
Added line 112:
August 08, 2005, at 07:17 PM
by -- Added net-snmp
Added line 97:
August 08, 2005, at 01:16 PM
by --
Changed lines 39-40 from:
The Unslung package repository can be found at http://ipkg.nslu2-linux.org/ipkg to:
The Unslung package repository can be found at http://ipkg.nslu2-linux.org/feeds/unslung Changed lines 43-47 from:
Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages Natively compiled (unslung-feeds) package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). to:
Cross-complied package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/cross/Packages Natively compiled package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages These packages require you to be running the Unslung firmware. August 07, 2005, at 09:27 PM
by -- Renamed ncftp for link
Changed line 93 from:
to:
July 25, 2005, at 03:39 AM
by -- add qemu
Added line 103:
June 19, 2005, at 08:47 PM
by --
Changed lines 3-4 from:
If you are using Unslung, before attempting to run ipkg, install or use a package, or update the list of packages, make sure that you have installed a hard drive or memory stick and "unslung" to it. Failure to do so may fill your NSLU2's internal Flash RAM with too much data and not allow it to reboot. To recover, follow the Recover From A Bad Flash process. to:
If you are using Unslung, before attempting to run ipkg, install or use a package, or update the list of packages, make sure that you have installed a hard drive or memory stick and "unslung" to it. Failure to do so may fill your NSLU2's internal Flash RAM with too much data and not allow it to reboot. To recover, follow the Recover From A Bad Flash process. Changed lines 57-60 from:
Please search the wiki? to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. You can also Browse the IRC Logs. to:
Please search the wiki? to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. You can also Browse the IRC Logs. Changed line 112 from:
to:
Changed lines 119-120 from:
NOTE: The complete package list is available here. to:
NOTE: The complete package list is available here. June 10, 2005, at 08:19 AM
by -- Added command to install a new package
Added lines 31-32:
To install a new package, use May 30, 2005, at 08:20 PM
by -- added asterisk
Added line 66:
May 29, 2005, at 10:35 AM
by --
Changed lines 33-34 from:
The package format is compatible between the Unslung firmware and the OpenSlug firmware (when it is ready). to:
The package format is compatible between the all versions of the Unslung firmware. Some packages have also been ported to the Asus WL-series of wireless routers. May 29, 2005, at 10:34 AM
by -- Deprecated unfs3, and added recommendation for nfs-utils
Changed line 91 from:
to:
Changed line 106 from:
to:
May 24, 2005, at 04:14 PM
by --
Changed lines 13-23 from:
Package Sources and LocationsThe Unslung package repository can be found at http://ipkg.nslu2-linux.org/ipkg To find ipkgs that have already been made : http://ipkgfind.nslu2-linux.org Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages Natively compiled (unslung-feeds) package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). to:
First Steps
Added lines 35-45:
Package Sources and LocationsThe Unslung package repository can be found at http://ipkg.nslu2-linux.org/ipkg To find ipkgs that have already been made : http://ipkgfind.nslu2-linux.org Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages Natively compiled (unslung-feeds) package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). May 23, 2005, at 07:27 AM
by -- linking this package
Added line 90:
May 17, 2005, at 02:55 AM
by -- Fix wizd link
Changed line 98 from:
to:
May 15, 2005, at 02:51 PM
by -- Added - wizd
Added line 97:
May 06, 2005, at 02:26 PM
by --
Changed lines 1-2 from:
Preable for Unslungto:
Preamble for UnslungMay 06, 2005, at 02:19 PM
by --
Added lines 1-14:
Preable for UnslungIf you are using Unslung, before attempting to run ipkg, install or use a package, or update the list of packages, make sure that you have installed a hard drive or memory stick and "unslung" to it. Failure to do so may fill your NSLU2's internal Flash RAM with too much data and not allow it to reboot. To recover, follow the Recover From A Bad Flash process. What are Packages?In general, packages are commonly-available software programs that we have simply ported to the NSLU2. The effort to do this work is provided by the volunteer NSLU2 Linux community. If you have a question on how to use a particular package, please use Google or something to search for the general documentation about the package before asking questions that are not specific to the NSLU2 port of the package. For example, Google "man tar" for information on how to use the "tar" application. When using Unslung, look under /opt for the corresponding files for a particular package. Package Sources and LocationsChanged lines 22-25 from:
These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). You can update your ipkg database on the slug with In general, these are commonly-available software packages that we have simply ported to the NSLU2, and installed under /opt. So you should look on the internet for the general documentation about the package before asking questions that are not specific to the NSLU2 port of the package. Look under /opt for the corresponding files in an Unslung installation. to:
These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). How To Use ipkgYou can update your ipkg database on the slug with To check out a list of available packages, use To see the packages you already have installed, use The complete package list is also available here. Added lines 36-37:
Can't Find A Package You Want?Changed lines 41-53 from:
More details are here for: to:
Found A Bug?If you find any problems with the packages, please report them to NSLU2-Linux SlugBug. Please search the wiki? to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. You can also Browse the IRC Logs. The easiest way to find a maintainer is to look at the cvs log - "cvs log make/foo.mk" - for package foo. This will tell you who originally checked in the package and who has modified it since. The usernames in the cvs log are @users.sourceforge.net addresses. Specific Package DetailsMore details are available for the following packages: Deleted line 104:
If you find any problems with the packages, please report them to NSLU2-Linux SlugBug. Please search the wiki? to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. The easiest way to find a maintainer is to look at the cvs log - "cvs log make/foo.mk" - for package foo. This will tell you who originally checked in the package and who has modified it since. The usernames in the cvs log are @users.sourceforge.net addresses. April 28, 2005, at 12:19 AM
by --
Added lines 3-4:
To find ipkgs that have already been made : http://ipkgfind.nslu2-linux.org April 25, 2005, at 07:32 PM
by --
Changed lines 35-36 from:
to:
Changed line 38 from:
to:
April 24, 2005, at 11:48 PM
by -- added bittorrent and mutt
Added line 19:
Added line 38:
April 24, 2005, at 11:00 AM
by -- link to mc docu
Changed line 34 from:
to:
April 19, 2005, at 11:11 AM
by --
Changed lines 6-7 from:
These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from http://sourceforge.net/project/showfiles.php?group_id=116564 if you want to help with the beta testing). You can update your ipkg database on the slug with to:
These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from the NSLU2 SourceForge project area if you want to help with the beta testing). You can update your ipkg database on the slug with April 19, 2005, at 11:09 AM
by --
Changed line 16 from:
to:
Changed line 18 from:
to:
Changed lines 21-23 from:
to:
Changed lines 25-29 from:
to:
Changed lines 31-33 from:
to:
Changed line 37 from:
to:
Changed line 39 from:
to:
Changed line 41 from:
to:
Changed lines 44-48 from:
to:
Changed lines 50-51 from:
to:
Changed lines 53-59 from:
to:
Changed line 64 from:
If you find any problems with the packages, please report them to NSLU2-Linux SlugBug. Please search the wiki to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. The easiest way to find a maintainer is to look at the cvs log - "cvs log make/foo.mk" - for package foo. This will tell you who originally checked in the package and who has modified it since. The usernames in the cvs log are @users.sourceforge.net addresses. to:
If you find any problems with the packages, please report them to NSLU2-Linux SlugBug. Please search the wiki? to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. The easiest way to find a maintainer is to look at the cvs log - "cvs log make/foo.mk" - for package foo. This will tell you who originally checked in the package and who has modified it since. The usernames in the cvs log are @users.sourceforge.net addresses. April 19, 2005, at 12:13 AM
by -- add mediawiki link
Added line 35:
April 17, 2005, at 04:11 PM
by -- unbork package uri
Changed line 3 from:
Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages\\ to:
Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages April 04, 2005, at 12:02 AM
by --
Added line 56:
March 31, 2005, at 01:37 AM
by --
Added line 47:
March 30, 2005, at 04:29 AM
by --
Added line 44:
Added line 46:
February 23, 2005, at 08:48 AM
by --
Changed lines 12-17 from:
The source for packages is added to the Unslung CVS repository, and built and uploaded from there. All packages must be able to be rebuilt from source from the CVS repository. We do not accept binary-only packages in the official Unslung package repository (however, we are happy to point to other third-party repositories). See AddAPackageToUnslung? for details on how to add a new package to the repository, and see the PackagingBestPractices for our packaging policies. If you are unable to provide a new package you might want to add it to the PackageWishList and hope that someone else provides it. Here is a list of RequiredSoftware? for building Unslung Packages to:
If there is a package you would like that is not part of unslung already, you have two options: You can contribute it yourself (to learn more, see AddAPackageToUnslung?). Or you can add it to the PackageWishList and hope that someone else provides it. February 20, 2005, at 08:39 AM
by --
Added line 20:
February 15, 2005, at 01:30 PM
by --
Added line 26:
February 08, 2005, at 01:04 AM
by --
Changed line 58 from:
NOTE: The complete package list is available http://ipkg.nslu2-linux.org/ipkg/Packages here to:
NOTE: The complete package list is available http://ipkg.nslu2-linux.org/ipkg/Packages here. Changed line 60 from:
If you find any problems with the packages, please report them to http://slugbug.nslu2-linux.org to:
If you find any problems with the packages, please report them to http://slugbug.nslu2-linux.org NSLU2-Linux SlugBug. Please http://www.nslu2-linux.org/wiki/Main/SearchWiki search the wiki to see if your problem is a known problem with a workaround. In the chance that the problem might be fixed with the help of the package maintainer, come to the IRC channel and politely ask for help. The easiest way to find a maintainer is to look at the cvs log - "cvs log make/foo.mk" - for package foo. This will tell you who originally checked in the package and who has modified it since. The usernames in the cvs log are @users.sourceforge.net addresses. February 07, 2005, at 04:38 PM
by --
Added line 44:
February 06, 2005, at 07:46 PM
by --
Added line 52:
February 05, 2005, at 07:43 AM
by --
Changed line 15 from:
for details on how to add a new package to the repository. If you are unable to provide a new package you might want to add it to the PackageWishList and hope that someone else provides it. to:
for details on how to add a new package to the repository, and see the PackagingBestPractices for our packaging policies. If you are unable to provide a new package you might want to add it to the PackageWishList and hope that someone else provides it. February 04, 2005, at 04:24 PM
by --
Added line 40:
February 03, 2005, at 07:35 PM
by --
Added line 50:
February 03, 2005, at 05:42 PM
by --
Added line 43:
February 02, 2005, at 06:24 PM
by --
Added line 45:
February 01, 2005, at 04:34 AM
by --
Changed line 3 from:
Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages to:
Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages\\ February 01, 2005, at 04:33 AM
by --
Added line 4:
Natively compiled (unslung-feeds) package descriptions are at http://ipkg.nslu2-linux.org/feeds/unslung/native/Packages January 27, 2005, at 07:00 PM
by --
Added line 43:
January 26, 2005, at 10:54 AM
by --
Added line 24:
January 20, 2005, at 10:50 PM
by --
Changed lines 1-50 from:
Describe {{Packages}} here. to:
The Unslung package repository can be found at http://ipkg.nslu2-linux.org/ipkg Package descriptions are at http://ipkg.nslu2-linux.org/ipkg/Packages These packages require you to be running the Unslung firmware (which is currently in beta testing, and can be built from source, or downloaded from http://sourceforge.net/project/showfiles.php?group_id=116564 if you want to help with the beta testing). You can update your ipkg database on the slug with In general, these are commonly-available software packages that we have simply ported to the NSLU2, and installed under /opt. So you should look on the internet for the general documentation about the package before asking questions that are not specific to the NSLU2 port of the package. Look under /opt for the corresponding files in an Unslung installation. The package format is compatible between the Unslung firmware and the OpenSlug firmware (when it is ready). The source for packages is added to the Unslung CVS repository, and built and uploaded from there. All packages must be able to be rebuilt from source from the CVS repository. We do not accept binary-only packages in the official Unslung package repository (however, we are happy to point to other third-party repositories). See AddAPackageToUnslung? for details on how to add a new package to the repository. If you are unable to provide a new package you might want to add it to the PackageWishList and hope that someone else provides it. Here is a list of RequiredSoftware? for building Unslung Packages More details are here for:
Todo: please add details of other packages NOTE: The complete package list is available http://ipkg.nslu2-linux.org/ipkg/Packages here If you find any problems with the packages, please report them to http://slugbug.nslu2-linux.org
view ·
edit ·
print ·
history ·
Last edited by OddballHero.
Based on work by rboatright, OddballHero, Jim DeLaHunt, Marcelo Vianna, fcarolo, Darek Sliwa, axm, eiffel, bdguru, anonymous, marceln, BrianZhou, HN, oleo, allen, coward, anonymous coward, Humpda, vidar, rwhitby, Zack45668, JJ, repvik, bzhou, japher, HenrikB, Eddie, Peter Enzerink, gshier, Adam Baker, andreas, GAPi, niel, John McCabe, ingeba, jp30, tman, Richard Folwell, cdoban, barrym, J, FlipFlop, George Sherwood, ka6sox, ChrisE, kaste, paulhar, shenson, ByronT, bobtm, jsilence, jharuska, and RickardDahlstrand. Originally by tman. Page last modified on February 24, 2011, at 10:54 AM
|