View Full Version : Migration guide for linux newbie wanted
I just managed to get kissdx 13.10a up and running, but wouldnt mind upgrading right away to the new beta release. Why not ?
My main problem is that I know very little about linux and the various commands, that are undoubtedly more basic than basic for most of the readers here.
I am requesting a migration guide for dummies.
Following the official migration guide I have the following questions :
@1. Make a backup copy of kissdx.conf.
How ? What do I write exactly after telnetting(putty) into my slug ?
@2. how do I install to the same directory. What do I write where ?
@5. How do I run in verbose mode ? What do I write where ?
@6. Launch script ? huh ? What is that ? Example ? what do I write where ?
As you can see I know zilch, and understand just a tiny little bit more than zilch. Anyway could be great if you could help me out :D
Vit and Hi-jack are the obvious ones(as always), but others are welcome to help out too.
P.S. By the way.. I havent programmed since I took a course in comal-80 back in the beginning of the 80´ies.
Where do I start if I would like to learn something about Linux ?
Something relevant concerning my slug and kiss player.
Any good books or sites here on the net ?
Would be great if I didnt have to write all those stupid questions :)
Thanks
In a first think, i would like to recomend not to play with beta if you do not understand a little your inux envir due to the name 'beta'.
.....
Thanks Bluediver
Always encouraging with a cold shoulder. I thought Linux was all about "open core". Guess I was wrong.
Hehe, Bluediver is on the kissdx team and probably doesn't want any more bug reports ;-)
Seriously, if you install from the NSLU ipkg package* of 0.14 beta, many things will just happen automatically. It will replace the existing 0.13 installation, and it will ask if you want to overwrite kissdx.conf.
You should let it replace kissdx.conf because there are many new and changed settings in this release.
That's where the backup comes in. If you are ok with configuring it from scratch again (at least setting the three media paths and persistentstoragepath), then you don't need a backup.
Quick replies to your questions:
@1: cp /opt/etc/kissdx.conf /opt/etc/kissdx.conf.bak
@2: This happens automatically with ipkg install *
@5: /opt/etc/kissdx -v
@6: /opt/etc/init.d/S83kissdx is the launch script. It starts kissdx when the NSLU2 is turned on.
*) ipkg install is best done with this command:
ipkg install http://kissdx.vidartysse.net/kissdx_0.14.0.b1a-1_armeb.ipk
Then just edit /opt/etc/kissdx.conf like before.
I recommend nano as a nice editor:
ipkg install nano
Then you can
nano /opt/etc/kissdx.conf
hi,
sorry if my response was a little bit "Cold shoulder", it was with a sense of humour that belongs to me exclusively ;-)
you are welcomed, but be carefull to try it only on a non production system.
The verbose mode generates a lot of log, then only use it for a reduce of time not to explode your free space on disk (if you redirect it to a file)
i fully agree with Vit, just a ipkg install and editing .conf is enough for testing
Once again, you are welcome and linux is not complex, just a little bit command line oriented.
See you
Bluediver
Very impressive Vidar, thanks.
Im busy the next couple of days. I will probably upgrade friday. Thanks again :)
I wil love this in nordisk VIT
Hi,
I've used kissdx for a while and I love it :bb: :sor:
I've just tried to upgrade my Synology CS-406:
Klods> ipkg install http://kissdx.vidartysse.net/kissdx_0.14.0.b1a-1_powerpc.ipk
Downloading http://kissdx.vidartysse.net/kissdx_0.14.0.b1a-1_powerpc.ipk
Upgrading kissdx on root from 0.13-10a-2 to 0.14.0.b1a-1...
package kissdx suggests installing gconv-modules
Segmentation fault (core dumped)
Klods>
My Kiss reports however, that I've got an 0.14 version (!) So this is good ;)
Now it doesn't auto start, and I'm not sure how to fix it... You two wouldn't btw have a quick solution :?: :oops:
regards
Søren
Edit=and btw I installed gconv-modules with ipkg (but what is it?) :?
Edit2=OK, found out - something about character conversion. Maybe, the danish characters display properly??? No big deal, but nice if they would... :)
Auto-starting is done by the /opt/etc/init.d/S83kissdx file.
This is what that file should contain on your system:
#!/bin/sh
OPTWARE_TARGET=ds101g
if [ -n "`pidof kissdx`" ]; then
killall kissdx 2>/dev/null
fi
/opt/bin/kissdx -d >/dev/null 2>&1
Hope that gets it running automatically.
Since the install terminated prematurely, you may not have the latest /opt/etc/kissdx.conf either. Check the migration guide (http://www.famille-kahn.com/kissdxmanual/Kissdx_user_manual:_Migration_Guide#Migrate_from_k issdx_0.13-10a_to_kissdx_0.14).
Hi,
Thanks for getting back to me! However, my s83kissdx-file contains excactly those lines.
And my conf-file is renewed (and better - good work :D)
I didn't stop kissdx the first time I tried the upgrade. Could that be a problem?
I've read the guide but I can't seem to find my specific prob...
Hmm, when I start kissdx with 'kissdx' in the telnet promt, I can't return to the telnet promt. Maybe something is incomplete ?!
I may have to uninstall or erase kissdx, but at this time I'm not confident that I could find out to do that by my self :oops:
regards
Søren[/i]
1. You are not returned to the telnet prompt when starting kissdx, that is normal behaviour. To start kissdx in the background, add the -d option:
/opt/bin/kissdx -d
2. Still not auto-starting, that's strange if it starts running when you start it in telnet. Do you have a kissdx.conf in your home directory or in the current directory when starting kissdx in telnet? When started automatically, it should read /opt/etc/kissdx.conf (unless there is a /root/.kissdx file). You can specify the config file using -c on the command line:
/opt/bin/kissdx -d -c /opt/etc/kissdx.conf
Does that produce an error message? If yes, the cause must be fixed, and you should also remove all other config files to avoid confusion later.
3. Not stopping kissdx before upgrading may have caused the install to fail. I am not sure. Easiest way to stop kissdx:
killall kissdx
4. You asked about Danish national characters. I successfully display Norwegian national characters with these settings in kissdx.conf:
server_character_set = CP850
client_character_set = ISO-8859-1
This is combined with client code page = 850 in /etc/samba/smb.conf and copying files to the NSLU2 from a Windows PC using the network file system (i.e. using Samba).
/opt/bin/kissdx -d
Thanks, works gooood :)
/opt/bin/kissdx -d -c /opt/etc/kissdx.conf
Produces no errors. I've had no errors in use with VR558 as long as I telnet to kissdx on NAS and start it.
killall, ok.. I've only tried 'kill'
Tried that, and again ipkg inst...url
Same error :( But kissdx working fine after manual start
ad 4
smb.conf consist of this:
PID Uid VmSize Stat Command
1 root 316 S init
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
17 root SW< [kblockd/0]
41 root SW [pdflush]
42 root SW [pdflush]
44 root SW< [aio/0]
43 root SW [kswapd0]
115 root SW< [ata/0]
117 root SW< [scsi_eh_0]
118 root SW< [scsi_eh_1]
125 root SW< [scsi_eh_2]
126 root SW< [scsi_eh_3]
144 root SW [mtdblockd]
164 root SW< [md0_raid1]
166 root SW< [md1_raid1]
168 root SW< [md2_raid5]
Maybe it's because I've got a CS-406?
I've altered the kissdx.conf to cp850 and iso8859-1 (by removing ##'s)
Thanks
Søren
> Maybe it's because I've got a CS-406?
Yes, maybe. But that's a weird smb.conf at any rate. See if you can find the real smb.conf somewhere else.
About the autostart issue: Do any of the S* files in /opt/etc/init.d/ start up automatically? Maybe it's a generic problem.
And try removing the -d when checking for errors:
/opt/bin/kissdx -c /opt/etc/kissdx.conf
The -d causes kissdx output to go to the syslog instead of the telnet window, sorry to mislead you there...
My ipkg status is:
Package: kissdx
Version: 0.13-10a-2
Depends: libdvdread, l
Suggests: gconv-module
Status: install user i
Architecture: powerpc
Hmmm, odd 8O
My Kiss reports 0.14
Could it be possible, that it would be best to make a ipkg install kissdx?
Would that work?
The only thing I miss is the autostart - all else is superb :D
Regards
Søren
I just noticed in your earlier post:
> my s83kissdx-file contains excactly those lines
Is there really a lower case "s" at the start of that filename on your system? It must be upper case: S83kissdx
I just noticed in your earlier post:
> my s83kissdx-file contains excactly those lines
Is there really a lower case "s" at the start of that filename on your system? It must be upper case: S83kissdx
Oh, it's only a typo.. :oops:
Sorry!
Well, now it got worse:
I removed kissdx and tried to make a new install:
Klods> ipkg install http://kissdx.vidartysse.net/kissdx_0.14.0.b1a-1_powerpc.ipk
Downloading http://kissdx.vidartysse.net/kissdx_0.14.0.b1a-1_powerpc.ipk
Installing kissdx (0.14.0.b1a-1) to root...
Segmentation fault (core dumped)
Now I can't install neither 0.14 nor 0.13 :(
What could that 'segmentation fault' be?
Regards
Søren
A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to access a memory location in a way that is not allowed (for example, attempting to write to a read-only location, or to overwrite part of the operating system). (Wikipedia)
It might have something to do with a firmware upgrade I recently made.
This upgrade could have restricted access to places where kissdx want to write(?)
With
ipkg install kissdx -V 3
(...)
Replacing pre-existing file /opt/bin/kissdx owned by package kissdx
Replacing pre-existing file /opt/man/man1/kissdx.1 owned by package kissdx
installing maintainer scripts
installing data files
extracting data files to /
Calling pkg_write_filelist from install_data_files
creating kissdx.list file
creating //opt/lib/ipkg/info/kissdx.list file for pkg kissdx
resolving conf files
Segmentation fault (core dumped)
All these files are present:
/opt/lib/ipkg/info/kissdx.list
/opt/etc/init.d/S83kissdx
/opt/bin/kissdx
/opt/etc/kissdx.conf
/opt/man/man1/kissdx.1
If I start kissdx:
Klods> kissdx
starting kissdx...
bind: Address already in use
:?:
Regards
Søren
> bind: Address already in use
That means that kissdx is already running, or another program is using one of the network ports that kissdx wants to use. Try using the -v option to get more info about which port is being opened when it fails:
/opt/bin/kissdx -d
It seems you have kissdx installed. The segmentation fault may be a general problem with ipkg on your new firmware. Can you install other packages without problems?
Yes, I installed gconv-modules without problems.
I'll try it out this evening :)
Maybe - if all other fails - I should remove the files manually, because it might be some sort of write protection that generates the fault.
r.
Søren
Klods> kissdx -v
[ 2946] 2007-12-21 00:24:29 Using config file /opt/etc/kissdx.conf
[ 2946] 2007-12-21 00:24:29 kissdx v0.13-10a, 2007-01-30 is now using the following configuration:
[ 2946] 2007-12-21 00:24:29 audiopath = /media/audio
[ 2946] 2007-12-21 00:24:29 videopath = /media/video
[ 2946] 2007-12-21 00:24:29 picturepath = /media/picture
[ 2946] 2007-12-21 00:24:29 persistentstoragepath =
[ 2946] 2007-12-21 00:24:29 kmlurl = http://tinystocks.com/k/kiss.php
[ 2946] 2007-12-21 00:24:29 pretrigger =
[ 2946] 2007-12-21 00:24:29 posttrigger =
[ 2946] 2007-12-21 00:24:29 audiofileextensions = mp3,ogg,wma,wav
[ 2946] 2007-12-21 00:24:29 videofileextensions = mpg,mpeg,vob,avi,wmv,ts,mp4
[ 2946] 2007-12-21 00:24:29 picturefileextensions = jpg,jpeg,png,bmp
[ 2946] 2007-12-21 00:24:29 isofileextensions = iso,img
[ 2946] 2007-12-21 00:24:29 max_recent_files = 30
[ 2946] 2007-12-21 00:24:29 server_character_set =
[ 2946] 2007-12-21 00:24:29 client_character_set =
[ 2946] 2007-12-21 00:24:29 subtitle_catchall_pattern = {name}*.*
[ 2946] 2007-12-21 00:24:29 picturetargetwidth = 1280
[ 2946] 2007-12-21 00:24:29 picturetargetheight = 720
[ 2946] 2007-12-21 00:24:29 picturemaxzoompercent = 20
[ 2946] 2007-12-21 00:24:29 picturecachesize = -1
[ 2946] 2007-12-21 00:24:29 picturecachetrimminginterval = 5
[ 2946] 2007-12-21 00:24:29 networktimeoutinterval = 0
[ 2946] 2007-12-21 00:24:29 enablehiddenfilestext = Toggle all files status
[ 2946] 2007-12-21 00:24:29 enablehiddenfilesminutes = 1
[ 2946] 2007-12-21 00:24:29 starting kissdx...
[ 2946] 2007-12-21 00:24:29 bind: Address already in use
Klods> ipkg remove kissdx
No packages removed.
Nothing to be done
Successfully terminated.
Klods>
It seems that I have to make a hardware reset and/or delete the kissdx file manually with rm...
I couldn't possibly find any reason that the address should suddenly be in use. And it is more strange that I can start the server and then afterwards get the message that server doesn't exist 8O
r.
Søren
I think I'll try to delete the kissdx files manually first - then try to reinstall.
Are these the files from the installation:
/opt/lib/ipkg/info/kissdx.list
/opt/etc/init.d/S83kissdx
/opt/bin/kissdx
/opt/etc/kissdx.conf
/opt/man/man1/kissdx.1
r. Søren
Ah, I forgot you are on v0.13-10a. That version does not display verbose info when opening ports, sorry.
The files you listed are the complete list of files installed. BTW what does ipkg files kissdx tell you? It is supposed to list the same files if kissdx is still installed.
I don't know the firmware you are using, but this command is worth a try to find which program is using port 8000:
netstat --inet -anp | grep :8000
After removing of the files, I installed 0.14.
It ended with Segmentation fault, but worked with kissdx -d :)
I might still have problems with the autostart ability :(
In spite of all errors the kissdx was apparently installed with ipkg.
It was only 0.14 that couldn't do that properly.
I'll have to look into how CS-406 / Debian autostarts programs when rebooted. This feature _would_ be nice because I turn the NAS off at night.
r.
Søren
vit,
Don't waste any more time on me in this tread. If I've got any more questions, I'll post them in http://www.mpcclub.com/modules.php?name=Forums&file=viewforum&f=142
Thanks a lot for all help!! :sor:
:)
Søren
Edit:
Just to wrap it up here...
/usr/syno/etc.defaults/rc.d/ contains startup scripts and I didn't find S83kissdx there. Then I copied it to the dir and gave it the extension sh. Let's see how it works! Cant test it right now because wife and kids are using the server.
cp /opt/etc/init.d/S83kissdx /usr/syno/etc.defaults/rc.d/S83kissdx.sh
Edit2:
Didn't work. I figure it's not a good idea to add 'sh' as extension without some other work?
vBulletin® v3.8.4, Copyright ©2000-2010, Jelsoft Enterprises Ltd.