Jump to content
Muxe Inc Forums
Sign in to follow this  
Guest JClu

ndn_3_00_0004_l64 doesn't start within tinycore 11.1

Recommended Posts

Garl    0

ascii art with single and double lines work fine for me

image.png.26f295ac06c78ad76315ba5f2c9bb3c5.png

Share this post


Link to post
Share on other sites
Guest JClu   
Guest JClu

Really? with the same version you provided me with? Wow!

  Well, I guess I'll have to deal with the terminal conf
     though i even put lxterminal, locales in UTF8 and some inernatl fonts...
     -sigh- gotta dig deeper i guess. not easy with limited time, age and skills :-)
     but were would the fun be? it the reason why i chose TinyCore :
      to have the bare minimum and DIY + enjoy the CPU spare from the bloat of other distros (ubu* being just another wdoz)

  thank you for giving it the possibility to blossom in linux,
    plus you give me a nice alternative to my current only choices :
    mc for TUI and dcmd on GUI (BTW, dcmd is also devd in Pascal and russian... is it a coincidence?  :-)
JClu
PS: what the mention inconvenience i mentionned earlier : about the letters assigned to ALL mount points?
       I mean, to avoid the loop devices, unless explicitly asked. possible? cpacibo. dobri dien.

Share this post


Link to post
Share on other sites
Garl    0
15 hours ago, Guest JClu said:

PS: what the mention inconvenience i mentionned earlier : about the letters assigned to ALL mount points?

Options->configurations->intreface ->drive info -> [x] Hide Pseudo FS

http://ndn.muxe.com/download/file/nightly_l64.zip

 

p.s.

i'll try use TinyCore 

 

 

Share this post


Link to post
Share on other sites
Guest JClu   
Guest JClu

Hi Garl,
  Yes! now it really gets usable to switch "drives" with 'alt+F1' or 'alt+F1'
   (though 'alt+left' and 'alt+right' are not responding the expected way :
     there's a 'dir change history' popup showing current dir but nothing changes) or even usingthe mouse : Thank you!

  As for the lines drawing, the way i see it, the ball is on my side and i got to figure out how to handle all I/O on terminals solving any key (combinations) inputs and charsets display problems. If i want to

  tinycore(TCL)? if you are already using a distro and are happy with it...keep using it! It's not to prevent you to come to the dark side but rather to make sure you put your energy into ndn rather than disco

   Now, before you put your mind into it i'm going to tell the + and - i see in it (my experience/opinion) :
  i've got acquainted with slackware  when in its v2 (about 20 floppies to install!) ...fast-forward
  After tasting live linux in the form of demolinux (made @ PVI university along side DNX demo on a floppy)
  a soon later puppylinux... i could not go back installing distros anymore. Knoppix and many other came : HUGE!
  FFward again to nowadays and only a few distros respect the meaning of the word lightweight
    for x86_64 archi in decreasing size of main branch of the general purpose distro :
     GRML (<300+~700+MB), slax|porteus (<300MB),
     puppy (<200MB), alpine (<150MB),
     slitaz (<60MB), tinycore (<20MB)
  there are some specialized distros out there that could join :
    in VoIP astlinux (a semi-live distro with asterisk <100MB)

  now, why did i end up with tcl?
  the "+"
    size (easy/fast boot on haedware and in qemu(run in tcl :-)),
    extensions (thus the problem of the 'loop devices') like the modules from slax = "live (un-)mount the whole app pkg",
    and their repo has most i need (bbox, tmux, mc, elinks...)
  the "-"
    well since the community isn't big, you can find yourself on your own when trying to solve problems that are too specific :
    i asked to have LXC pkg (and kernel ready) available back in version 3+... not done yet in 11.1
    i like its poweroff backup(persistence), and sleep2ram is easy... but hibernation isn't there (of course own scripts and...)

  maybe you'd like slitaz and it's web configuration+pakg managmt but its persistence system is not as efficient as in tcl

  the others... their weigth (though alpine musl nased adds security, a rich pkg base...)

  well, so the choice depends much on :
    you goal, your current skills and the resources available (time&money included).

  however, thank you for mentionning it as it really shows how dedicated you are as a dev.
  as for ndn i've known it when its grand-pa dn prior to v1.51 was coming out of Rit-labs(and their email cli:-)
  so, seing it under linux (even with its too fast tetris) touchde me with nostalgia (no sudoku yet?)

  i have a lot of suggestions but prefer to focus in having it running correctly so
    i can use it instead of mc (to many script configured to drop it easily).

thank you again,
  as soon as i get it correctly running i report here with the findings (or if i meet some unexpected roadblock)

JClu

 

Share this post


Link to post
Share on other sites
Garl    0
On 23.10.2020 at 0:07 PM, Guest JClu said:

Yes! now it really gets usable to switch "drives" with 'alt+F1' or 'alt+F1'

image.png.afd257900ae3e9bc831a396b98002395.png

image.png.1067ffa1938eec7198895655c46762ee.png

is NDN run on your TinyCore?

 

Share this post


Link to post
Share on other sites
Guest JClu   
Guest JClu

Hello Garl,
  as for ruuning ndn on TCL... well that's my only OS for about 2 years so yes else i would have not been able to perform the previous tests.
  here the screen ib text mode (easier for copy/paste an lighter :
 

[20201025 7 07:53:56]{tc@bsrv:/mnt/sda2/data/Downloads/-- ndn/ndn_lin/nightly_l64}
$ uname -a
Linux bsrv 4.19.10-tinycore64 #1999 SMP Tue Dec 18 15:18:54 UTC 2018 x86_64 GNU/Linux
[]
$ # did you make sure you're running ndn65 on tcl64?
[]
$ ./ndn
Messagebox():
/mnt/sda2/data/Downloads/-- ndn/ndn_lin/nightly_l64/lib/locale.so: cannot open shared object file: No su

Necromancer's Dos Navigator v3.00.0005f/LINUX64.
Based on Dos Navigator by Ritlabs...
[DEFINES/CPUX64/LINUX/FREEPASCAL]
* Linux (v4.19) detected
* TTY: /dev/tty18 (rxvt)
* Process ID = 7407 ...
* PCRE Version 8.44 2020-02-12
* Berkeley (BSD) socket API for Unix/Linux

When running binaries on wrong platform the binary type gets wrongly identified as shell script by default by the shell itself (since it will accept the fact it is executable). but we both know it is not so... leading to failure of execution.
Thus use the binaries you gave me (ndn64) on a 64bits version of tcl and, unless some libs are missing it should start smoothly.
the way i proceed later if missing libs is :
   ask the bin what is missing :

$ ldd ndn
        statically linked

but since you compile ndn with all its dependencies that should be no worries.

if after that you make it display things nicely and get rid of the locale msg ... that will be huge thank you

JClu

Share this post


Link to post
Share on other sites
Guest JClu   
Guest JClu

OK,
  after conflicting with myself i prefer to include this (should be self explanatory):

 

(i thought the image was insert at text position... well just attached)
JClu, thanks

ndn-202010257-02.png

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoticons maximum are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×