Install JDK/OpenJDK and Avahi?

[yldouright]

I'm in the middle of composing the 3rd and largest part of my installation tutorial found here. One of the packages that I'm considering including is studioware found here. The pre-installation seems to indicate that JDK/OpenJDK and avahi are required for Slackware 14.2 (ie: Porteus 3.2.x). OpenJDK is my choice and USM shows several versions of it and I have some questions about these pre-installation recommendations:

1. Do I need to install the base OpenJDK package openjdk6-6b41-x86_64-3_slonly.txz before any other version?
2. Do I need to install each upgrade step in sequence or can I upgrade directly to the latest versin?
3. How do the 'zulu' packages differ from the plain openjdk packages and will they install over them?
4. What does studioware use avahi for and can I turn it off later if its only use is to facilitate the install script?

[ncmprhnsbl]

1. Do I need to install the base OpenJDK package openjdk6-6b41-x86_64-3_slonly.txz before any other version?
2. Do I need to install each upgrade step in sequence or can I upgrade directly to the latest versin?

pick a version and use that.. i'd use what looks like the latest..

3. How do the 'zulu' packages differ from the plain openjdk packages and will they install over them?

4. What does studioware use avahi for and can I turn it off later if its only use is to facilitate the install script?

presumably the studioware package manager(sepkg) users it to browse the server..

you realise that studioware is just a repository of (multimedia) packages? which can be got directly from http://slackware.uk/studioware/14.2/packages/
sepkg might be helpful with dependency resolution or quite possibly not(since it is aimed at a full slackware install)

[yldouright]

@ncmprhnsbl
Thanks for your attention. In USM the 'zulu' version of java shows up. The website describes it here. The avahi application in USM gives me a LIBS.TXT error when I try to install it. Can I get it from the terminal with su update install avahi ?

[Ed_P]

In USM the 'zulu' version of java shows up. The website describes it here.

For Java I use the java builder module shown here: Tip: Build your own Java Oracle module with a script of which part is:

Code: Select all

echo
echo "1. Download the current non-RPM Linux file. "
#firefox "http://www.java.com/en/download/linux_manual.jsp" 
firefox "http://www.java.com/en/download/linux_manual.jsp" > /dev/null 2>&1 &
# Results in the download being in the /root/downloads folder rather than the guest one.
echo "   Close Firefox when done. "
echo " "
echo "2. Invoke [Menu > Admin] Java Builder "
echo " "
echo "3. Point it at the jre-*.tar.gz file in the /root/Downloads/ folder "
echo "   and run it. It takes a moment to start and several to end. "
echo " "
echo "4. When it ends copy the jre-*.xzm file to the "
echo "   $MODULES folder."

Note: I run the script as root which is why the download is in the /root/downloads/ folder rather than the guest one.

The avahi application in USM gives me a LIBS.TXT error when I try to install it.

Did you get the LIBS.TXT error recently? There was a problem with SourceForge up until a few days ago that caused that type of problem. So worth retrying.

[yldouright]

I just tried again today, same LIBS.TXT failure.

[Ed_P]

Try sesm.sh.

[yldouright]

Thanks Ed_P, just for the record, do those mirror scripts work with Porteus 3.1?

[Ed_P]

Thanks Ed_P, just for the record, do those mirror scripts work with Porteus 3.1?

I've never tried them with 3.1 so I can't say. Should be easy enough for you to test and find out, just backup the /etc/usm/*.txt files before you run the script so if there are problems you can restore the files.

I don't see why the scripts wouldn't work though.

Ref your avahi LIBS.TXT problem. I just tried and it ran ok.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -s avahi

avahi-0.6.32-x86_64-1dj.txz was found in salix [not installed]
avahi-0.6.32-x86_64-1_slonly.txz was found in slackonly [not installed]
Packages found:   2 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download

root@porteus:/home/guest# usm -g avahi

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) avahi-0.6.32-x86_64-1_slonly.txz
2) avahi-0.6.32-x86_64-1dj.txz
#? 1

 The following packages are required. 
avahi-0.6.32-x86_64-1_slonly.txz [420K] [not installed]

Total size: 420 KB
 Would you like to install the package/s? (custom paths are supported) [y/n]

 Press [r] to remove packages, [q] to quit, or enter to start downloading.

 Updates are available. 
 Program update:   not required 
 Database update:  available 
 Please run:  usm -u all  and/or  usm -u usm 
 This message can be disabled in /etc/usm/usm.conf
 ############################### 
Downloading: avahi-0.6.32-x86_64-1_slonly.txz  DONE

 Commencing package conversion ... 
Verifying package avahi-0.6.32-x86_64-1_slonly.txz.
Installing package avahi-0.6.32-x86_64-1_slonly.txz:
PACKAGE DESCRIPTION:
# avahi (service discovery aka zeroconf)
#
# Avahi is an Implementation the DNS Service Discovery and Multicast
# DNS specifications for Zeroconf Computing. It uses D-BUS for
# communication between user applications and a system daemon. The
# daemon is used to coordinate application efforts in caching replies,
# necessary to minimize the traffic imposed on networks. This kind of
# technology  is already found  in  Apple MacOS X (branded Rendezvous
# Bonjour and sometimes Zeroconf) and is very convenient.
#
Executing install script for avahi-0.6.32-x86_64-1_slonly.txz.
Package avahi-0.6.32-x86_64-1_slonly.txz installed.

Creating /tmp/usm/avahi-0.6.32-x86_64-1_slonly.xzm

 Enter a custom path to install packages to or press enter to install to the system: 
>
Installing to system

+==============================================================================
| Installing new package /tmp/usm/avahi-0.6.32-x86_64-1_slonly.txz
+==============================================================================

Verifying package avahi-0.6.32-x86_64-1_slonly.txz.
Installing package avahi-0.6.32-x86_64-1_slonly.txz:
PACKAGE DESCRIPTION:
# avahi (service discovery aka zeroconf)
#
# Avahi is an Implementation the DNS Service Discovery and Multicast
# DNS specifications for Zeroconf Computing. It uses D-BUS for
# communication between user applications and a system daemon. The
# daemon is used to coordinate application efforts in caching replies,
# necessary to minimize the traffic imposed on networks. This kind of
# technology  is already found  in  Apple MacOS X (branded Rendezvous
# Bonjour and sometimes Zeroconf) and is very convenient.
#
Executing install script for avahi-0.6.32-x86_64-1_slonly.txz.
Reloading system message bus configuration...
Package avahi-0.6.32-x86_64-1_slonly.txz installed.

root@porteus:/home/guest# 

[yldouright]

Ed_P
I ran the sesm.sh scripts twice and still can't get a good salix database and that seems to be where avahi resides. Would you please post me your active links for salix and slonly? By the way, when I run the scripts from Pluma (Mate), I get no feedback or terminal displaying execution. Is this normal?

For the record:

Code: Select all

root@porteus:/home/guest# usm -s avahi

awk: fatal: cannot open file `/var/usm/sbo/SLACKBUILDS.TXT' for reading (No such file or directory)
Nothing found for avahi

is what I get when I run usm -s avahi. When I usm -u all the terminal always hangs on "salix".

[Ed_P]

Would you please post me your active links for salix and slonly?

salix: http://mirror.its.dal.ca/salix
slonly: http://packages.slackonly.com/pub/packages (it's the only option)

By the way, when I run the scripts from Pluma (Mate), I get no feedback or terminal displaying execution. Is this normal?

For Cinnamon x64, no. For Mate, I don't know, I don't use it, but I would suspect not.



-update-

Pluma a file manager? So you are executing sesm.sh via the file manager? Try opening a terminal and running the scripts manually. If they are running or have errors you will be able to see them.

[yldouright]

@Ed_P
As I understand it, Pluma is a script editor and engine. Mate integrates it into the Caja file manager as a "Scripts" sub-menu. I put the trio of scripts in that directory and they are always available in Caja without having to open a terminal.I manually edited the Config list to use your salix repo and that fixed everything.

[Ed_P]

You need to run them from a terminal to see what they are doing, or not and why.

This is what you are missing doing it your way.

Code: Select all

root@porteus:/home/guest# USM/sesm.sh
Argument usage:		all	[<Toggle Debug: 0/1>]	[ URL .. ]
URL .. Optional Exclusion Mirror List on Command Line
Optional Exclusion File of URLs: .usm/badmirrors.txt (following format of 'mirrors-<repo>,txt')
root@porteus:/home/guest# 

[yldouright]

@Ed_p
When I run it from the terminal I get the following:

Code: Select all

guest@porteus:~$ sh usm/sesm.sh
usm/sesm.sh: line 12: $'\r': command not found
usm/sesm.sh: line 20: $'\r': command not found
usm/sesm.sh: line 24: $'\r': command not found
usm/sesm.sh: line 29: syntax error near unexpected token `$'\r''
'sm/sesm.sh: line 29: `kpv ()
guest@porteus:~$ 

I think I may have originally saved the scripts on a Windows box as a text file. Maybe there was an ASCII encoding dispartiy. Would you copy the error lines from your sesm.sh script and post them here to compare?

[Ed_P]

Yup. Been there, done that with the Windows updating of a script. Re: [INFO & SCRIPT] Slackware Mirror Settings for USM (Post by Ed_P #56135)
Recopy and paste it using Porteus and you will be fine.