TC64: User feedback.

[labeas]

Is this forum like M$ gmail: can't login to send without js enabled?
Is it known that often:
  mount <device> <mount point>
fails, until the mountTool first tries and also fails?

With WiFi, mc & gpm [chrooted strangely to 32bit], links' textOnly
facility is very efficient in extracting the info from html
fluff/garbage. But further efficiency needs wily, and I don't want to
have to compile it so I fetched:
   wily_0.13.41-7.2_amd64.deb   and
  " * Quick hack to convert Debian packages." from the forum.

But I get "./Deb2TC: line 56: mksquashfs: not found" problems;
and there's no mksquashfs* in my recent listing of <TC64>.tcz

Is it true that <Debian to TC> is not approved of ?

BTW I just plugged in my mobile to a spare USB, which caused
the mouse: doing:
  chroot /mnt/P15 /usr/sbin/gpm -m /dev/psaux -t ps2
to an old IDE, via a USB-to-IDE adaptor to "lose" /dev/sdd15.

`fdisk -l`  showed that the IDE had become sde15 which when
remounted was again able to chroot-32bit-gpm on this TC64.

I must have wily on TC, to avoid the need to reboot to Debian
to handle the text of the *.html that TC:links fetches so well.

I can advise other users about the brilliant but never popular
wily's quirks, if you want to fly instead of crawling.

Pity that I must now reboot to M$ [TC forum needs js?] to post this ?

[polikuo]

Is this forum like M$ gmail: can't login to send without js enabled?

Dillo does not support JS but one can login to the forum just fine.

Is it known that often:
  mount <device> <mount point>
fails, until the mountTool first tries and also fails?

What do you mean?
What file system does your partition have ?
You might need some extensions to mount it.

With WiFi, mc & gpm [chrooted strangely to 32bit], links' textOnly
facility is very efficient in extracting the info from html
fluff/garbage. But further efficiency needs wily, and I don't want to
have to compile it so I fetched:
   wily_0.13.41-7.2_amd64.deb   and
  " * Quick hack to convert Debian packages." from the forum.

But I get "./Deb2TC: line 56: mksquashfs: not found" problems;
and there's no mksquashfs* in my recent listing of <TC64>.tcz

Is it true that <Debian to TC> is not approved of ?

mksquashfs is in squashfs-tools.tcz
<Debian to TC> is not recommended for standard port, try dCore if you really need it.

[labeas]

]]Is it known that often:
]]  mount <device> <mount point>
]]fails, until the mountTool first tries and also fails?

]What do you mean?

mount <device> <mountPoint> = FAIL
Try mountTool = FAIL
retry: mount <device> <mountPoint> = success

]What file system does your partition have ?
]You might need some extensions to mount it.

No! but I forgot to ask: Why is my TC:USBstik FATFS, whith all kinds
of complications like permission and sym-links?
In the confusion of 32/64bit & M$ new <UEFI> to keep linux out,
did I mistakenly skip re-formatting the TC partition?

[polikuo]

mount <device> <mountPoint> = FAIL
Try mountTool = FAIL
retry: mount <device> <mountPoint> = success

What's inside your /etc/fstab ?
While mounting, it's always best to run with sudo.

No! but I forgot to ask: Why is my TC:USBstik FATFS, whith all kinds
of complications like permission and sym-links?
In the confusion of 32/64bit & M$ new <UEFI> to keep linux out,
did I mistakenly skip re-formatting the TC partition?

You might want to take a look at this.
http://forum.tinycorelinux.net/index.php/topic,19364.msg119228.html

[polikuo]

You can do it manually.

Code: [Select]

busybox ar xv wily_0.13.41-7.2_amd64.deb
mkdir tmp
tar zxf data.tar.gz -C tmp
rm -fr data.tar.gz debian-binary control.tar.gz
sudo chown -R root:root tmp
tce-load -w squashfs-tools
tce-load -i squashfs-tools
mksquashfs tmp wily.tcz
echo libXt.tcz > wily.tcz.dep
mv wily.tcz wily.tcz.dep /etc/sysconfig/tcedir/optional


[labeas]

] mksquashfs is in squashfs-tools.tcz
] <Debian to TC> is not recommended for standard port,
] try dCore if you really need it.

Yes, and the [Search Button} led there too;
but they seem to NOT have 64-bit.

[polikuo]

Yes, and the [Search Button} led there too;
but they seem to NOT have 64-bit.

Yes,there is.
Which version of TC are you using ?

[labeas]

**
Posts: 65
View Profile
 Email
 Personal Message (Online)
 




 

Re: TC64: User feedback.

« Reply #4 on: Today at 11:03:38 PM »


Quote
You can do it manually.

Code: [Select]

busybox ar xv wily_0.13.41-7.2_amd64.deb
mkdir tmp
tar zxf data.tar.gz -C tmp
rm -fr data.tar.gz debian-binary control.tar.gz
......etc...........

Thanks, I'll study that; but I forgot to mention:
apparently Ubuntu has taken the name "wily' for some other package.

The 1990s based wily is from the BIG-BOYS who designed unix & C and
then went on to make the even better Plan9 and then ....

This 'wily' is versatile like emacs, but much smaller, and VISUAL:
mouse driven, so you don't need to look away from [the possibly
multiple text frames on] the screen to find the F7-key.

[Juanito]

wily posted to corepure64 repo

[labeas]

Thanks for the script. I gave it a good work-out, but eventually got lost. Interestingly, wily
is superb for <executing your actual notes/text eg. email>. Here's some logs:-- .......
tce-load -w squashfs-tools
tce-load -i squashfs-tools
=> needs nonROOT : must do in X == OK installed !!

mksquashfs tmp wily.tcz
-> mksquashfs tmp wily.tcz ==
Parallel mksquashfs: Using 2 processors .....

echo libXt.tcz > wily.tcz.dep
-> echo libXt.tcz > wily.tcz.dep

mv wily.tcz wily.tcz.dep /etc/sysconfig/tcedir/optional
-> mv wily.tcz wily.tcz.dep /etc/sysconfig/tcedir/optional

==> ? Install: Try:
-> tce-load -i /etc/sysconfig/tcedir/optional/wily.tcz
== Don't run this as root
......
-> which wily == /usr/bin/wily
=> go back to X to test ?!
==> copy to $PATH

->ls -l `which wily` == looks good
-rwxr-xr-x    1 root  root  145992 Mar  3 10:50 /usr/local/bin/wily

=> Examaine bytes with mc: .ELF...../lib64/ld-linux-x86-64.so.2...
== looks OK

=> mc: <wily64>.deb  shows: /usr/X11R6/lib/X11/wily/ prop.9.font , fixed.9.font
   Have the libraries been installed ?
-> ldd /usr/local/bin/wily ==
        linux-vdso.so.1 (0x00007fffbb7ec000)
        libXt.so.6 => /usr/local/lib/libXt.so.6 (0x00007fb1f8831000)
        libX11.so.6 => /usr/local/lib/libX11.so.6 (0x00007fb1f8515000)
        libc.so.6 => /lib/libc.so.6 (0x00007fb1f81a7000)
        libSM.so.6 => /usr/local/lib/libSM.so.6 (0x00007fb1f7fa0000)
        libuuid.so.1 => /lib/libuuid.so.1 (0x00007fb1f7d9d000)
        libICE.so.6 => /usr/local/lib/libICE.so.6 (0x00007fb1f7b84000)
        libxcb.so.1 => /usr/local/lib/libxcb.so.1 (0x00007fb1f7962000)
        libXau.so.6 => /usr/local/lib/libXau.so.6 (0x00007fb1f7760000)
        libXdmcp.so.6 => /usr/local/lib/libXdmcp.so.6 (0x00007fb1f755a000)
        libdl.so.2 => /lib/libdl.so.2 (0x00007fb1f7356000)
        /lib64/ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x000055916e154000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fb1f7144000)
..bla bla.. <-->'ve been through all of that. AFAIR it's only
   linux-vdso.so.1  that was missing..
================> I've now returned to TC64, after other jobs, and am annoyed that
<the installed wily has gone> ! TC quirks get some getting used to ?
I strongly believe in: Test/confirm stage1,....Test/confirm stageN; rather than: DoA, DoB...
Also I want to save my fetched files in case I loses my inet here.
== How should I proceed ?
     

[Juanito]

=> Examaine bytes with mc: .ELF...../lib64/ld-linux-x86-64.so.2...
== looks OK

corepure64 expects to find the loader in /lib and not in /lib64.

..but anyway, there is now a wily extension in the corepure64 repo, so you don't need to mess around with the debian version of wily.

================> I've now returned to TC64, after other jobs, and am annoyed that
<the installed wily has gone> ! TC quirks get some getting used to ?
I strongly believe in: Test/confirm stage1,....Test/confirm stageN; rather than: DoA, DoB...
Also I want to save my fetched files in case I loses my inet here.
== How should I proceed ?

read the book 

[Misalf]

Hi labeas

[...]
=> Examaine bytes with mc: .ELF...../lib64/ld-linux-x86-64.so.2...
== looks OK
[...]
================> [...]
== How should I proceed ?

I'd start by <stopping> to use random formatting and random ==> characters on your [KEYBOARD] to emphasize what you're saying (because the result is the opposite) but use traditional methods like code / quote tags instead, so that people don't have such a hard time reading your posts. You would certainly get more replies that way.

[labeas]

> there is now a wily extension in the corepure64 repo
Which runs BEAUTIFULLY, also with good size font, and IMO white on black is better.
That it covers the whole screen, disabling access to DesktopControls, we'll fix later;
besides I've got a dozen `sudo su` VTs @ Ctrl/Alt/F1; like I'm using now.
I made a big log of my first use/test of wily, which is natural, since YOU EXECUTE THE
CODE ANYWHERE YOU SEE IT ON THE SCREEN, IN ANY OF THE MULTIPLE WINDOWS.
But I'm with-holding pasting it here, for fear of agrevating readers, by being
over-the-top.
== Thanks for TC. I think I'm using ver 7 of 64-bit.

[Juanito]

I think I'm using ver 7 of 64-bit.

You can find out like this:

Code: [Select]

$ version
$ uname -a

[labeas]

 uname -a
Linux box 4.2.9-tinycore64 #1999 SMP Mon Jan 18 19:59:34 UTC 2016 x86_64 GNU/Linux
root@box:/home/tc# version
7.2
------
A mere 28314bytes is dvtm_0.6-1_amd64.deb; which gives window-tiling,
so the user can in VT or X: have 2 or more windows open on the same
screen to eg. be able to read from one file and paste to another and
test in a 3rd...............

I failed to <Deb to TC> dvtm.  But gpm is now good.

== Thanks for TC.