WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
TCE Corepure64 / Re: Building TCZ extensions for Corepure64
« Last post by Rich on February 16, 2019, 12:45:07 PM »
Hi coreplayer2
...   unset command should be as per variable assignment as I understand,  ...
I suspected as much, especially when I saw the syntax of all the other  unset  commands. :)
22
TCE Corepure64 / Re: Building TCZ extensions for Corepure64
« Last post by coreplayer2 on February 16, 2019, 11:46:05 AM »
Hi andyj
Code: [Select]
/usr/local/bin/submitqc: unset: line 834: ./usr/local/sbin/suexec: bad variable name
At which point the script dies and leaves an unpacked tcz directory.

Looking at line 834 it reads:
Code: [Select]
unset $BINI believe it should read:
Code: [Select]
unset BINTry replacing the link   /usr/local/bin/submitqc  with a copy of the file  /tmp/tcloop/submitqc/usr/local/bin/submitqc  and editing
out the extra  $  sign to confirm it fixes the problem. I see a similar issue on line  657  that reads:
Code: [Select]
unset $FOUND

Thanks for spotting that,    unset command should be as per variable assignment as I understand,  I'll fix that and update

thanks
23
TCE Talk / Re: Bluefish editor menu icons are missing
« Last post by TomyTurbos on February 16, 2019, 11:41:49 AM »
@ rich: libffi5 caused it to crash immediately.  BTW, Thank you very, very, very much for the 'script' hint!

@juanito:  All up-to-date.
24
Off-Topic - Tiny Core Lounge / Re: virtual machines
« Last post by vinceASPECT on February 16, 2019, 11:23:13 AM »
i am guessing Juanto that this "virtualhere" Linux client is a simple excercise to run in TCL

it says it runs on any Linux, self contained executable, no deps....exists in userland...etc ...etc.

https://virtualhere.com/usb_server_software
https://virtualhere.com/usb_client_software
V
25
Raspberry Pi / Spotify connect (librespot) on piCore
« Last post by Gerrelt on February 16, 2019, 11:06:48 AM »
Hi all,

I've got Spotify connect with librespot working on piCore, and I wanted to share how I did it.
With librespot running, your raspbery pi will show up in the Spotify app under "devices available".
When selected, the song will be played on your raspberry instead of your phone.
(NOTE: I believe this does not work with a free spotify account)

Librespot uses "libportaudio2" which wasn't available on piCore, so I compiled it, and made a .tcz package for it.
To get it all running, execute these commands:

Code: [Select]
mkdir librespot
cd librespot
# libportaudio2 compiled and packaged by me, and source downloaded from:
#     http://www.portaudio.com/download.html
wget http://www.gerrelt.nl/RaspberryPi/libportaudio2.tcz -P /mnt/mmcblk0p2/tce/optional
sudo echo "libportaudio2.tcz" >> /mnt/mmcblk0p2/tce/onboot.lst
# librespot compiled by me, and source downloaded from:
#     https://github.com/librespot-org/librespot
wget http://www.gerrelt.nl/RaspberryPi/SpotifyRadio/librespot.tar.gz
tar -xvzf librespot.tar.gz
sudo mv librespot /mnt/mmcblk0p2/tce
chmod u+x /mnt/mmcblk0p2/tce/librespot

To start it at boot, you will have to choose a soundcard first.
Execute:
Code: [Select]
aplay -lor
Code: [Select]
cat /proc/asound/cards
And see wich soundcard number and device number you want to use.

Open bootlocal.sh:
Code: [Select]
sudo nano -\$\icwS /opt/bootlocal.sh
And add this line to the end:
Code: [Select]
/mnt/mmcblk0p2/tce/librespot --name YourSpotifyConnectDevicename --cache /tmp --bitrate 320 --initial-volume 100 --backend alsa --device hw:0,0 > /dev/null 2>&1 &
Now, change "--device hw:0,0" to the choosen soundcard and device number, this example uses soundcard 0 and device 0.

Also check if you want to set the initial volume to 100%. If you adjust volume by a physical volume knob, you probably want it set to 100. If you use a software "volume knob", you probaly want to set it to something a lot lower.  ;D
See option "--initial-volume 100" to change it.

You will also want to change "--name YourSpotifyConnectDevicename" to give your device a recognizable name.

Exit nano with CTRL-X, save the file, and make all your changes persistent by executing:
Code: [Select]
filetool.sh -b
Reboot your raspberry pi, and when booted, it should appear under "devices available".

Enjoy! 8)


26
Final Releases / Re: Tiny Core v10.0
« Last post by Ted Clayton on February 16, 2019, 09:54:09 AM »
The exchange with 'drunk' is of interest.  My time on Ubuntu has been dominated by surfing the repo with Synaptic, and I've seen so many under-the-radar little programs.  Installed 1,000 (but had a hard time finding or managing).

Genealogy (GEDCOM): we are getting DNA tests, and I need a more competent browser for the secure User pages.  There are special-purpose GEDCOM-database editors and HTML Tree makers, etc.  LifeLines!  Dad started with 3-ring binders, graduated to TRS-80, MS-DOS and Windows.  And we continue.

Many other amateur radio codes; NEC, minNEC propagation, grayline ... and great utilities that are not marked as Ham/Amateur!  Smith Charts!

GIS/GPS, DEM, cartography.  A true love.  And a true story, I self-rescued from the off-trail Olympics with my old Magellan 310.  After RTDM and figuring out how to change the Datum to match my topo.

Can I really make Extensions for Tiny Core?  I compile from source, on Ubuntu, though I'm no way a compiler-user.  But I surfed into nitram's 2015 extension-creation post http://forum.tinycorelinux.net/index.php?topic=18682.0 and it looks kinda gnarly.  But that is old, strongly-condensed, and not labeled Official.

I had not looked at the Wiki yet.  dCore!  Direct access to Debian and Ubuntu repos!  Wow!

But again, is this really for me?  dCore is not visible from the sidewalk, and there may well be good reason.

Plus ... are dCore SCEs the same thing as TCEs?  Or are these like the easier 'personal' Extensions in TC ... and not useful to the Project? 

I'm a good technician (and code-tinker), but I'm not a real Engineer (or programmer).  BaCon?  I can do BaCon alright ... and some ASM, on CPM.

Thanks!
27
TCE Corepure64 / Re: Building TCZ extensions for Corepure64
« Last post by Rich on February 16, 2019, 08:50:08 AM »
I checked the TC9 x86 version of  submitqc. I suspect the same version is used in TC9 and TC10 for x86 and x86_64.
And possibly  piCore  too.
28
TCE Corepure64 / Re: Building TCZ extensions for Corepure64
« Last post by Rich on February 16, 2019, 08:43:59 AM »
Hi andyj
Code: [Select]
/usr/local/bin/submitqc: unset: line 834: ./usr/local/sbin/suexec: bad variable name
At which point the script dies and leaves an unpacked tcz directory.

Looking at line 834 it reads:
Code: [Select]
unset $BINI believe it should read:
Code: [Select]
unset BINTry replacing the link   /usr/local/bin/submitqc  with a copy of the file  /tmp/tcloop/submitqc/usr/local/bin/submitqc  and editing
out the extra  $  sign to confirm it fixes the problem. I see a similar issue on line  657  that reads:
Code: [Select]
unset $FOUND
29
TCE Corepure64 / Re: Building TCZ extensions for Corepure64
« Last post by andyj on February 16, 2019, 08:15:22 AM »
I'm getting an error in submitqc when checking apache2.4:

Code: [Select]
submitqc: apache2.4.tcz binaries have been stripped? /
Some binaries have not been stripped:
usr/local/sbin/suexec
This may be intentional. Else to strip, use --strip.
You have warnings.
/usr/local/bin/submitqc: unset: line 834: ./usr/local/sbin/suexec: bad variable name

At which point the script dies and leaves an unpacked tcz directory.
30
Off-Topic - Tiny Core Lounge / Re: virtual machines
« Last post by Juanito on February 16, 2019, 04:16:03 AM »
affirmative
Pages: 1 2 [3] 4 5 ... 10