Page 15 of 20

Posted: Sat 02 Mar 2013, 11:53
by 01micko
.

Re: Failure to access a LAN resource using 541RC

Posted: Sat 02 Mar 2013, 11:57
by 01micko
gcmartin wrote:On a Pristine boot immediately after FirstRUN and Frisbee setup, I tried to mount my NAS and got an error.

Code: Select all

# /mnt/NAS2
# mount -o username=root,password=woofwoof //192.168.1.207/NASunit /mnt/NAS2
mount: wrong fs type, bad option, bad superblock on  //192.168.1.207/NASunit
       missing codepage or helper program, or other error
       (for several filesystems (e.g. nfs, cifs) you might
       need a /sbin/mount.<type> helper program)
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
Anyone noticed the same.

Hadn't notice this problem in earlier release.
Edit: I used YASSM ..Search and was about to attach the NAS.
SMB?

try mount.cifs

or at least mount -t cifs

Posted: Sat 02 Mar 2013, 12:07
by gcmartin
Already tried -t cifs....but, mount.cifs. yields

Code: Select all

# mount.cifs -o username=root,password=woofwoof //192.168.1.207/NASunit /mnt/NAS2 

Mounting the DFS root for domain not implemented yet
No ip address specified and hostname not found
(This is remarkably similar to what happened in FATDOG6+ when it 1st came out. @JamesBond/@Kirk addressed it in the release of 610.)

Posted: Sat 02 Mar 2013, 12:15
by Billtoo
01micko wrote: In other news, try the new hardinfo, and Billtoo, this one should open the report.
Yes, it works now,thanks.

Posted: Sat 02 Mar 2013, 12:23
by gcmartin
In asn earlier post, it should have read that YASSM has no problem accessing the NAS for me.

Posted: Sat 02 Mar 2013, 12:32
by 01micko
gcmartin wrote:In asn earlier post, it should have read that YASSM has no problem accessing the NAS for me.
Ok, neither should the network roxapp. I just tried this:

# mount.cifs //192.168.1.6/homeshare /mnt/share
Password:
#

Got on... maybe try that.

Posted: Sat 02 Mar 2013, 12:33
by rcrsn51
gcmartin wrote:Already tried -t cifs....but, mount.cifs. yields

Code: Select all

# mount.cifs -o username=root,password=woofwoof //192.168.1.207/NASunit /mnt/NAS2 

Mounting the DFS root for domain not implemented yet
No ip address specified and hostname not found
(This is remarkably similar to what happened in FATDOG6+ when it 1st came out. @JamesBond/@Kirk addressed it in the release of 610.)
The mount.cifs command always requires that the options list be at the end.

[Edit] I also tried "mount -t cifs". It worked correctly both with the options list at the front and the back of the command.

Posted: Sat 02 Mar 2013, 12:49
by gcmartin
Thanks, both suggestions work.

Been using mount for about 10 years and had grown accustomed to having it around. I'll appeal to @JamesBond to find out what they did to get mount to work again. (@Rcrsn51 was that you that helped them with that?)

Thanks again to get me this far.

Posted: Sat 02 Mar 2013, 12:51
by rcrsn51
See my edit above. The mount command still works correctly for me.

[Edit] I also tried it with just "mount -o ....." and it worked too.

I would try a fresh install, WITHOUT using Frisbee.

Slacko Patches

Posted: Sat 02 Mar 2013, 12:57
by tlchost
Hmmmm....pidgin does not show up....I updated the PPM...still doesn;t show up. What have I done wrong?

Re: Slacko Patches

Posted: Sat 02 Mar 2013, 13:12
by 01micko
tlchost wrote:Hmmmm....pidgin does not show up....I updated the PPM...still doesn;t show up. What have I done wrong?
Dunno.. but I know where my truck is... c u on irc

Posted: Sat 02 Mar 2013, 20:44
by artsown
Micko, concerning the optical media freeze bug, I found a post of
mine on Dec 2, 2012 that mentions the problem in connection with
testing Barry's Precise 5.4.2. I don't recall exactly when I first noticed
the problem.

I did as you requested, and posted on Barry's Precise 5.5 Beta thread
concering the bug.

Art

Posted: Sat 02 Mar 2013, 20:49
by 01micko
Hi Art

So.. what you observe is that boot goes normally until it gets to ::

Code: Select all

Recognising media devices... optical
then it hangs, Right?

Posted: Sat 02 Mar 2013, 20:53
by artsown
Yes, Micko, that's right. I can spot a freeze immediately since the
cursor is static (not blinking).

Art

udev-175

Posted: Sat 02 Mar 2013, 20:59
by mavrothal
Hi Mick,
5.4.0.5 looks really nice. :D

I was disappointed that was not playing well in the XOs so I took another stub on udev-175 using the debian-patched source and moving udevd to /sbin, and it works!
So I can have a proper SlaXO_14 :lol:

In case anyone needs the full udev-175 with extras for Slacko 14, find them here (md5sum: 0424dbad23f07f9278397d43c3cd3a7f)
The tarball has the udev-175-i486 exe, dev and doc pets.

Re: udev-175

Posted: Sat 02 Mar 2013, 21:34
by 01micko
mavrothal wrote:
In case anyone needs the full udev-175 with extras for Slacko 14, find them here (md5sum: 0424dbad23f07f9278397d43c3cd3a7f)
The tarball has the udev-175-i486 exe, dev and doc pets.
I gather that is committed to pox-git?

ipinfo

Posted: Sat 02 Mar 2013, 21:47
by SFR
Well, it's not a bug actually, just another "aesthetic" thing, but quite annoying:
I have noticed that ipinfo has been, inter alia, i18l'ed recently (which is good), but at the same time --geometry=600x400 & <vbox scrollable=\"true\">...</vbox> have been removed as well, what very often (when more than ~10 connections) causes enormously stretched window in vertical direction - even twice as my screen height...and the bottom half is simply empty.
Has anyone else noticed this too?

IDK what was the reason to set it up this way, but in case I'm not the only one who prefer the old way, I recreated things as they were originally designed by Vovchik (script attached).
_________

BTW: What happened to YAD? Haven't seen it since 5.4. :cry: :wink:

Greetings!

Posted: Sat 02 Mar 2013, 22:09
by 01micko
SFR

Thanks for latest ipinfo script, yeah I forgot to patch it :oops: :oops: , it's impossible on a small eee pc the old way!

As for yad, I should put it in PPM, I have an older version, is that ok?

Posted: Sat 02 Mar 2013, 22:21
by SFR
01micko wrote:As for yad, I should put it in PPM, I have an older version, is that ok?
It's not a big deal actually, I was just curious what happened. 8)
But what is the version you have, btw?
I just checked in the repo (using 'find') and there's yad-0.17.1.1, but I have yad-0.19.1 installed (and I can't recall from where it is..? :shock: ).

Greetings!

Posted: Sat 02 Mar 2013, 22:27
by 01micko
I remember removing yad because no stock slacko app was using it, I guess I can compile the latest, only takes a minute or 2.