Tiny Core Base > Release Candidate Testing
tinycore_v2.11rc3
maro:
Thank you to the Core team for now including VI editing mode in BusyBox. I now need to get used to the fact that it's available.
I did some more of my "poking around" with this RC and I'd like to raise a few other points. As typical for me I was booting from a "plain" ISO file, no persistence and without any backup (i.e. "cloud mode"):
(1) In addition to 'fgconsole' there are a couple of other BusyBox applets that don't appear to have a symbolic link:
--- Code: ---tc@box:~$ busybox | sed '1,/functions:$/d' \
> | tr -d ' \t\n' | tr ',' '\n' | while read F ; do
> L=$(which $F)
> T=$(ls -l $L 2> /dev/null | sed -e 's#.* -> ##' -e 's#.*/##')
> [ -z "$L" ] && echo "no softlink for $F"
> [ -n "$L" ] && [ "$T" != "busybox" ] && echo "$L not using busybox"
> done
no softlink for chrt
no softlink for dnsdomainname
no softlink for dumpleases
no softlink for fgconsole
no softlink for linuxrc
--- End code ---
I wonder if those are intended to be "hidden", or to which degree their appearance is a bug of the BusyBox build process.
(2) There are still cases of applications that are not getting represented in '~/.wmx/Applications' (e.g. 'midori', 'shiretoko', ...). Looking a bit closer into it lead me to '/usr/bin/flwm_topside_makemenu' where I changed writeFLWMitem "$FREEDESK" to writeFLWMitem "${FREEDESK}/${1}.desktop" This seem to have fixed it for me.
(3) The issue with "% options from freedesktop Exec elements" has also an impact on files in '~/.wmx/Applications'. I guess applying the change done for '/usr/bin/wbar_icon_upd.sh' to '/usr/bin/flwm_topside_makemenu' should fix it.
roberts:
Thanks for the feedback! Corrected for 2.11 final.
bmarkus:
Small Appbrowser cosmetics;
Trying to install extension already downloaded with more than one dot in the name like graphics-2.6.29.1-tinycore.tcz status message is
graphics-2 is already downloaded!
instead of
graphics-2.6.29.1-tinycore is already downloaded!
curaga:
Linuxrc shouldn't have a symlink (it just calls init anyway), but the others should.
jur:
I am confused... I can't lsusb, it reports lsusb not found... I'm sure I used this before?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version