uumenu packages conf files

A lot of these conf files seem to be pointing to a server that no longer has the binaries being requested, such as libxml2, ntfs, pciutils, php, smartmontools, infozip, etc.

 

Are there new conf files somewhere, or a different server to pick up binaries referenced?

 

Thanks.

 

--Bill

A lot of these conf files seem to be pointing to a server that no longer has the binaries being requested, such as libxml2, ntfs, pciutils, php, smartmontools, infozip, etc.

 

Are there new conf files somewhere, or a different server to pick up binaries referenced?

 

Thanks.

 

--Bill

I always used this site: http://packages.slackware.it/ as a starting point.  You MUST choose Slackware 12.2, then navigate to a site near you, then download the file (or right-hand-click on the link to the file to get the URL) . 

 

There might even be a newer version of the same package as was originally in the package .conf file.  In the same way, the MD5 Checksum will not be the same if you download a newer version... It too will need to be updated in the .conf file.  You can type:

md5sum package_name.tgz

to get the new MD5 value.

For many, you can change the path from slackware-current to slackware-12.2  (or slackware 12.1) as shown below

#PACKAGE_URL http://slackware.cs.utah.edu/pub/slackware/slackware-current/slackware/a/file-4.21-i486-1.tgz   <-- OLD

PACKAGE_URL http://slackware.cs.utah.edu/pub/slackware/slackware-12.2/slackware/a/file-4.21-i486-1.tgz       <-- NEW

You can use the "Config View/Edit" link built into unMENU to edit the .conf file.

 

Thanks Joe.

 

Changing the distribution to 12.2 from current did the trick for everything except ntfs-3g.  In checking the http://packages.slackware.it/ it does not show any matches for ntfs-3g-2009-3.8 as is spec'd in the .conf file. But in Slackware-13 there was ntfs-3g-2009.4.4-i486-1.txz which would seem to be newer, but is a txz file.  I believe I read somewhere here that those should not be used with installpkg -- is that true?  If so, where else might I find the .tgz version.

 

Sorry if these are noob questions...

 

--Bill

Thanks Joe.

 

Changing the distribution to 12.2 from current did the trick for everything except ntfs-3g.  In checking the http://packages.slackware.it/ it does not show any matches for ntfs-3g-2009-3.8 as is spec'd in the .conf file. But in Slackware-13 there was ntfs-3g-2009.4.4-i486-1.txz which would seem to be newer, but is a txz file.  I believe I read somewhere here that those should not be used with installpkg -- is that true?  If so, where else might I find the .tgz version.

 

Sorry if these are noob questions...

 

--Bill

It is not that the .tgx fils should not be used, it is that they use a different compression tool that does not yet exist in the slackware version used in unRAID.

 

This link is valid for an older version of ntfs-3g http://slackware.cs.utah.edu/pub/slackware/slackware-12.2/slackware/a/ntfs-3g-1.5130-i486-1.tgz

with a md5 checksum of 7076810b8ff4c4f148c311f10dcbb163

 

It should get you going... 

 

You can always install the "xz" package (download from this link http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/xz-4.999.8beta-i486-1.tgz)

and then install it with

installpkg xz-4.999.8beta-i486-1.tgz

 

Then, as described in this thread: http://lime-technology.com/forum/index.php?topic=3915.0, un-compress the .txz, and re-compress into a .tgz.

 

Download http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/ntfs-3g-2009.4.4-i486-1.txz

 

Then this might do it...

xz -dc ntfs-3g-2009.4.4-i486-1.txz | gzip -c > ntfs-3g-2009.4.4-i486-1.tgz

followed by

installpkg ntfs-3g-2009.4.4-i486-1.tgz

 

 

Seemed to work for me...  I'll try to put together a .conf file for it later today.

It is not that the .tgx fils should not be used, it is that they use a different compression tool that does not yet exist in the slackware version used in unRAID.

 

This link is valid for an older version of ntfs-3g http://slackware.cs.utah.edu/pub/slackware/slackware-12.2/slackware/a/ntfs-3g-1.5130-i486-1.tgz

with a md5 checksum of 7076810b8ff4c4f148c311f10dcbb163

 

It should get you going...   

 

You can always install the "xz" package (download from this link http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/xz-4.999.8beta-i486-1.tgz)

and then install it with

installpkg xz-4.999.8beta-i486-1.tgz

 

Then, as described in this thread: http://lime-technology.com/forum/index.php?topic=3915.0, un-compress the .txz, and re-compress into a .tgz.

 

Download http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/ntfs-3g-2009.4.4-i486-1.txz

 

Then this might do it...

xz -dc ntfs-3g-2009.4.4-i486-1.txz | gzip -c > ntfs-3g-2009.4.4-i486-1.tgz

followed by

installpkg ntfs-3g-2009.4.4-i486-1.tgz

 

 

Seemed to work for me...   I'll try to put together a .conf file for it later today.

Yep, it works perfectly!  Thanks so much, it's all making some sense now.  I've worked with several Unix's but never Linux so it's another learning curve.

 

--Bill

 

You can use the "Config View/Edit" link built into unMENU to edit the .conf file.[/b]

 

 

Forgive the noob question, just where is this link located?  I think I'm on the latest version.  Here's from the About link:

 

unmenu.awk: Version 1.1 Joe L.... with modifications as suggested by bjp999Plug-in-modules

07-unmenu-mymain.awk: 1.0 - contributed by bjp999

10-unmenu-links.awk: 1.1

16-unmenu-syslog.awk: Version: .8  - modified by Joe L. to use a pattern file.

17-unmenu-syslog.awk: Version: .8  - modified by Joe L. to use a pattern file.

20-unmenu-usage.awk: 1.0

25-unmenu-dupe_files.awk: 1.1

29-unmenu-sysinfo.awk: 1.3 - modified to better deal with utilities not yet installed Joe L.

30-unmenu-file_browser.awk: 1.1.3 added unmenu_local.conf file - by Joe L.

50-unmenu-user_scripts.cgi: .2 - Added unmenu_local.conf file

99-unmenu-utility.awk: 1.0 - contributed by bjp999

990-unmenu-wget.awk: 1.2 Changed pattern expected to match package .conf files to not need leading number, suggested by jarodtufts

999-unmenu-unraid_main.awk: 1.1 Joe L. -- Added parse of "ps" to check for non-standard emhttp port.

 

 

You can use the "Config View/Edit" link built into unMENU to edit the .conf file.[/b]

 

 

Forgive the noob question, just where is this link located?  I think I'm on the latest version.  Here's from the About link:

 

unmenu.awk: Version 1.1 Joe L.... with modifications as suggested by bjp999Plug-in-modules

07-unmenu-mymain.awk: 1.0 - contributed by bjp999

10-unmenu-links.awk: 1.1

16-unmenu-syslog.awk: Version: .8  - modified by Joe L. to use a pattern file.

17-unmenu-syslog.awk: Version: .8  - modified by Joe L. to use a pattern file.

20-unmenu-usage.awk: 1.0

25-unmenu-dupe_files.awk: 1.1

29-unmenu-sysinfo.awk: 1.3 - modified to better deal with utilities not yet installed Joe L.

30-unmenu-file_browser.awk: 1.1.3 added unmenu_local.conf file - by Joe L.

50-unmenu-user_scripts.cgi: .2 - Added unmenu_local.conf file

99-unmenu-utility.awk: 1.0 - contributed by bjp999

990-unmenu-wget.awk: 1.2 Changed pattern expected to match package .conf files to not need leading number, suggested by jarodtufts

999-unmenu-unraid_main.awk: 1.1 Joe L. -- Added parse of "ps" to check for non-standard emhttp port.

 

Oops... i thought it was in the last release....

 

My apologies...  It is here: http://lime-technology.com/forum/index.php?topic=2951.msg24387#msg24387

 

Looks like I need to get everything packaged together once more.... to make it easier.  I did not realize the editor was not part of the last set of release .zip files I had made.  It is time to make a new set of files....  (perhaps this weekend if I get a chance)

 

I think you will like the config file editor....

 

You'll need to stop and re-start the unMENU program to get it to see the new plug-in. 

 

Joe L.

Thanks for the quick reply.  Worked like a champ.

You can always install the "xz" package (download from this link http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/xz-4.999.8beta-i486-1.tgz)

and then install it with

installpkg xz-4.999.8beta-i486-1.tgz

 

Seemed to work for me...   I'll try to put together a .conf file for it later today.

 

An additional option is in your go script is to install "xz", followed by an upgrade of package utils themselves [ie: ftp://slackware.mirrors.tds.net/pub/slackware/slackware-13.0/slackware/a/pkgtools-13.0-noarch-3.tgz ]. In the future you wont have to deal with converting the .txz files to .tgz anymore.

You can always install the "xz" package (download from this link http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/xz-4.999.8beta-i486-1.tgz)

and then install it with

installpkg xz-4.999.8beta-i486-1.tgz

 

Seemed to work for me...   I'll try to put together a .conf file for it later today.

 

An additional option is in your go script is to install "xz", followed by an upgrade of package utils themselves [ie: ftp://slackware.mirrors.tds.net/pub/slackware/slackware-13.0/slackware/a/pkgtools-13.0-noarch-3.tgz ]. In the future you wont have to deal with converting the .txz files to .tgz anymore.

 

I've put this sequence in my go file for now.  Hopefully the build used for unRAID 4.5 will have this stuff built in.

 

--Bill

You can always install the "xz" package (download from this link http://slackware.cs.utah.edu/pub/slackware/slackware-13.0/slackware/a/xz-4.999.8beta-i486-1.tgz)

and then install it with

installpkg xz-4.999.8beta-i486-1.tgz

 

Seemed to work for me...   I'll try to put together a .conf file for it later today.

 

An additional option is in your go script is to install "xz", followed by an upgrade of package utils themselves [ie: ftp://slackware.mirrors.tds.net/pub/slackware/slackware-13.0/slackware/a/pkgtools-13.0-noarch-3.tgz ]. In the future you wont have to deal with converting the .txz files to .tgz anymore.

 

I've put this sequence in my go file for now.  Hopefully the build used for unRAID 4.5 will have this stuff built in.

 

--Bill

The "xz" program will probably not be part of the standard unRAID until it migrates to Slackware 13.  4.5 will probably still be based on Slackware 12.2

 

Perhaps the 5.0 version will include it... We'll just have to wait and see.  In the interim, it is easy to add.

 

Joe L.