**** BEGIN LOGGING AT Sun Aug 02 02:59:57 2009 Aug 02 11:39:23 hi Aug 02 11:40:14 I have this issue with SlugOS 5.3. I need someone who has beyond 'basic linux skills' to take a look at it if possible :) Aug 02 11:40:34 is anyone fitting that description in the house? Aug 02 11:40:45 the issue is explained here: http://www.nslu2-linux.org/wiki/SlugOS/Twonkymediaserver5#slugos53issues Aug 02 11:41:25 'basic linux skills' is almost as specific as 'basic computer skills' :p Aug 02 11:46:07 well I know my way around linux cli Aug 02 11:46:25 but I do not have much understanding of what stuff like glibc libraries are actually used for Aug 02 11:46:44 and what the fact that SlugOS 5.3 uses EABI practically means Aug 02 11:47:15 in relation to trying to run binaries compiled for linux ARM slibc architecture Aug 02 11:47:24 correction glibc Aug 02 11:47:58 I just know that twonkymedia does not work on slugos 5.3 Aug 02 11:48:19 and I'd like to find out why those needed GLIBC ABIs are missing, and if there's a workaround possible Aug 02 11:50:33 I'm hesitant to go to the developers channel, as I don't have enough knowledge to fit the 'developer' description Aug 02 14:12:45 hey i am having trouble adding a user to my nslu2 unslung os install Aug 02 14:13:10 i created a user using the linksys admin interface Aug 02 14:16:47 and have created the home directory Aug 02 14:16:57 but still can't ssh in Aug 02 14:17:02 as that user Aug 02 14:17:08 any ideas ? Aug 02 14:18:13 what's the user's line in the passwd file look like? Does the user have a shell? Aug 02 14:40:00 hey mwester, do you have any idea about my problem? Aug 02 14:41:33 FrankL_, I read your comments, but I don't see any problem. Aug 02 14:43:39 Perhaps you can rephrase your issue? Aug 02 14:43:46 What is it that doesn't work for you? Aug 02 14:45:44 twonkymedia server won Aug 02 14:45:50 twonkymedia server won't run in slugos 5.3 Aug 02 14:46:18 it makes GLIBC_2.0, GLIBC2.1 and GLIBC2.1.3 ABI calls Aug 02 14:46:34 those are not supported by libc6.so in slugos 5.3 (why?) Aug 02 14:46:50 It does not have to do with glibc. Aug 02 14:46:58 I've explained it into a bit more detail on http://www.nslu2-linux.org/wiki/SlugOS/Twonkymediaserver5#slugos53issues Aug 02 14:47:45 do you have any idea why those ABIs are missing in SlugOS 5.3? Aug 02 14:48:44 Prior to SlugOS 5.3, we used the old, obsolete OABI convention for calling functions (the ABI defines what registers hold which arguments, and where the return value is). With SlugOS 5.3, we switched to the new, more efficient EABI. Applications using the OABI function calling technique cannot call libraries expecting the new EABI technique. It has nothing to do with missing ABIs. Aug 02 14:49:12 So with SlugOS 5.3, you merely need to recompile the app -- no changes at all are necessary, just a recompile. Aug 02 14:49:39 ah Aug 02 14:49:44 For some apps, this will actually result in a significant, noticable performance gain. Aug 02 14:50:06 so twonkymedia needs to recompile the twonkymedia server with EABI support Aug 02 14:50:11 Yes. Aug 02 14:50:33 I'll let them know Aug 02 14:50:39 thanks Aug 02 14:51:41 The only other alternative is horribly ugly, and requires great persistence and some Linux expertise -- basically, you install an OABI-compiled set of all the libraries need by Twonky, and point Twonky to them using chroot or other techniques. Aug 02 14:53:13 a sort of sandbox? Aug 02 14:53:31 Yep. Aug 02 14:53:57 I was thinking about something like that. But I'd rather explore the option of Twonkymedia compiling with arch support for ARM glibc EABI big endian first :) Aug 02 14:53:59 I think the kernel itself is built to accept OABI calls. Aug 02 14:54:45 But you would need either an entirely-static Twonky, or all the dynamic libs it calls would have to be available in that sandbox as old-style OABI libs. Aug 02 14:56:34 I'll keep that in mind when I fail to persuade twonkymedia into providing an additional platform build Aug 02 14:57:02 oh, and is it technically possible to run uclibc compiled binaries in a sandbox too? Aug 02 14:57:21 I mean _if I fail_ , not _when I fail_ Aug 02 14:57:33 (hopefully) ;) Aug 02 14:58:06 Pointless, but it should be possible. Aug 02 15:00:25 well it would increase compatibility with different binaries Aug 02 15:03:27 anyway, thanks for your answers Aug 02 15:03:42 exactly what I was looking for, since quite a few weeks too :) Aug 02 15:09:25 eps:scIPDVtzLqtHo:2000:501:::/home/user/eps:/bin/sh Aug 02 15:09:44 thats my line from the /etc/passwd file Aug 02 15:11:52 eps, and you have checked that /home/user/eps exists, and has correct permissions? Aug 02 15:12:42 # ls -al /home/user/eps/ Aug 02 15:12:43 drwxrwxrwx 2 eps root 4096 Jun 13 11:42 . Aug 02 15:12:44 drwx------ 4 root root 4096 Jun 13 11:42 .. Aug 02 15:12:53 i chmodded it to 777 Aug 02 15:14:11 And what is the error message you get when you log in via ssh? And what is logged by the NSLU2 in its logfiles (in /var/log/*, IIRC) Aug 02 15:17:08 Permission denied, please try again. Aug 02 15:18:32 which log file ?, can't see anything relevant in messages Aug 02 15:20:43 Please cut and paste the login session and messages -- use a pastebin service, please. Aug 02 15:22:00 http://pastebin.com/mda03c52 Aug 02 15:26:36 Actually, upon closer inspection, your passwd entry seems to be borked. Aug 02 15:26:52 The format should be this: Aug 02 15:27:16 id:password:UID:GID:comments-which-can-be-blank:homedir:shell Aug 02 15:27:26 I think you have a few too many ":" in it? Aug 02 15:27:33 ok, i will give that a go Aug 02 15:27:41 do i have to give the user a GID ? Aug 02 15:27:48 Yes Aug 02 15:28:00 501 is fine Aug 02 15:28:20 Actually the correct UID and GID should have been assigned by the Linksys GUI. Aug 02 15:28:33 ah yes, it is now working# Aug 02 15:28:39 thanks for your help **** ENDING LOGGING AT Mon Aug 03 02:59:57 2009