corepup
Hi wanderer/all,
I now have weX audio, video, webcam, and screencast gtkdialog-based program working on my dCore-xenial system. Audio and video playback was already fine, but it is a much trickier matter to get audio and video recording subsystem going, and weX a good test of that:
http://www.murga-linux.com/puppy/viewtopic.php?t=107905
However, for some reason webcam audio/video synchronisation is perfect on XenialDog (debian-live type system) but not on Puppy's XenialPup or on dCore-xenial. I doubt if it the ffmpeg version, but might be, so I'll experiment further before releasing install details (including special dCore weX package).
Audio recording and X11 screencast (without webcam) works perfectly on dCore-xenial (and Puppy XenialPup) via weX now anyway. But I also want perfect webcam embedding facility (as on Fred's XenialDog).
William
I now have weX audio, video, webcam, and screencast gtkdialog-based program working on my dCore-xenial system. Audio and video playback was already fine, but it is a much trickier matter to get audio and video recording subsystem going, and weX a good test of that:
http://www.murga-linux.com/puppy/viewtopic.php?t=107905
However, for some reason webcam audio/video synchronisation is perfect on XenialDog (debian-live type system) but not on Puppy's XenialPup or on dCore-xenial. I doubt if it the ffmpeg version, but might be, so I'll experiment further before releasing install details (including special dCore weX package).
Audio recording and X11 screencast (without webcam) works perfectly on dCore-xenial (and Puppy XenialPup) via weX now anyway. But I also want perfect webcam embedding facility (as on Fred's XenialDog).
William
github mcewanw
Hi wanderer/anyone_interested,
I have now detailed how to Puppify tinycore/dCore in terms of making bash the default shell, adding gtkdialog and a couple of complex Puppy-type bash-gtkdialog apps (weX screencast recorder and weav commandline gui frontend) in steps 24 to 31 of my dCore-xenial HowTo project here:
http://murga-linux.com/puppy/viewtopic. ... 639#946639
(EDIT:) It can be a bit complicated to get Puppy utils running on other distributions, particularly since most Puppy utils require bash as the default shell (and it being not enough to simply start such apps from within a bash terminal). Unfortunately a lot of such Puppy utils were only designed to work with user root - weX and weav are among the exceptions to that limitation. ffconvert would be another good/useful candidate for converting for use with tinycore/dCore.
weX is the (superior) replacement for Precord (and also includes all pAVrecord functionality, and more, and provides screencast quality equal or similar to SSR but with additional ability to embed a webcam image stream in the screencast if so selected). I also included gifenc utility (code found by fredx181 - very useful) so that weX has a button to produce animated gifs of any created screencasts/videos.
William
I have now detailed how to Puppify tinycore/dCore in terms of making bash the default shell, adding gtkdialog and a couple of complex Puppy-type bash-gtkdialog apps (weX screencast recorder and weav commandline gui frontend) in steps 24 to 31 of my dCore-xenial HowTo project here:
http://murga-linux.com/puppy/viewtopic. ... 639#946639
(EDIT:) It can be a bit complicated to get Puppy utils running on other distributions, particularly since most Puppy utils require bash as the default shell (and it being not enough to simply start such apps from within a bash terminal). Unfortunately a lot of such Puppy utils were only designed to work with user root - weX and weav are among the exceptions to that limitation. ffconvert would be another good/useful candidate for converting for use with tinycore/dCore.
weX is the (superior) replacement for Precord (and also includes all pAVrecord functionality, and more, and provides screencast quality equal or similar to SSR but with additional ability to embed a webcam image stream in the screencast if so selected). I also included gifenc utility (code found by fredx181 - very useful) so that weX has a button to produce animated gifs of any created screencasts/videos.
William
github mcewanw
Though not a big deal, but as a matter of interest regarding my dCore-xenial installation:
When newly booted and only running Top utility in a uxterm, Top says:
used RAM = just under 30 MBytes.
CPU Idle = between 99.8 and 100% (i.e. 0 to 0.2% CPU being used!).
My other small Linux distributions report around 80MB or more RAM and 4 to 5% CPU or more (no conky) for similar onboot load.
The amazing dCore stats are probably due to just relying on simple tinycore mount tool (which I rather like actually) with no desktop icons (other than those on wbar) and no drive mount icons, and the efficient fltk_topside window manager: a few less running background services...
The above is on my HP Elitebook machine running with cpufreq governor ondemad at unstressed 800MHz (on load goes up to 2.13GHz).
Of course, all these stats, for all these small Linux systems (with efficient window managers), are very low anyway, so comes down to matter of taste/user-friendliness really.
I find myself comfortable using either. With dCore-xenial running my machine certainly runs comfortably cool in temperature (when Firefox 52.0 browser running, but just idling as I read page, the CPU still just using less than 0.5%)!
William
EDIT: I do dislike Firefox ver 52.0 though - not only does it force me to use pulseaudio (which is fine) but it doesn't like logging in to websites (such as murga-forum) using unencrypted passwords (covers up the boxes whilst I'm trying to type in username/password - works but tricky...). I expect there will be an about::config option to turn that 'feature' off...maybe
EDIT2: Yeah... here: https://support.mozilla.org/t5/Firefox/ ... -p/1374278
When newly booted and only running Top utility in a uxterm, Top says:
used RAM = just under 30 MBytes.
CPU Idle = between 99.8 and 100% (i.e. 0 to 0.2% CPU being used!).
My other small Linux distributions report around 80MB or more RAM and 4 to 5% CPU or more (no conky) for similar onboot load.
The amazing dCore stats are probably due to just relying on simple tinycore mount tool (which I rather like actually) with no desktop icons (other than those on wbar) and no drive mount icons, and the efficient fltk_topside window manager: a few less running background services...
The above is on my HP Elitebook machine running with cpufreq governor ondemad at unstressed 800MHz (on load goes up to 2.13GHz).
Of course, all these stats, for all these small Linux systems (with efficient window managers), are very low anyway, so comes down to matter of taste/user-friendliness really.
I find myself comfortable using either. With dCore-xenial running my machine certainly runs comfortably cool in temperature (when Firefox 52.0 browser running, but just idling as I read page, the CPU still just using less than 0.5%)!
William
EDIT: I do dislike Firefox ver 52.0 though - not only does it force me to use pulseaudio (which is fine) but it doesn't like logging in to websites (such as murga-forum) using unencrypted passwords (covers up the boxes whilst I'm trying to type in username/password - works but tricky...). I expect there will be an about::config option to turn that 'feature' off...maybe
EDIT2: Yeah... here: https://support.mozilla.org/t5/Firefox/ ... -p/1374278
github mcewanw
hi all
this is an update of what i am working on
corepup consists of
the base isos coreplus 6.4.1 and dcoreplus-jessie
mods to the boot menu - done
mods to the boot functions - done
the base corepup tcz which will contain
the backgrounds - done
hacked minimal jwm - done
the master utility program written in c - which i am writing now
the master utility program written in busybox ash - which i am writing now
in the spirit of minimalism and modularity
these master programs
are only written in c and ash
no gui toolkit
they have a small main function file
that calls all the other functions
which are contained in include files
some corepup functions are
scripts to make the linked directory system
a script to make the linked root directory
scripts to make the menu the core and tcz
a script to recompile jwm
a script to call/recompile the libc editor
a script to independently mount and link tcz
etc
a work in progress
when i am satisfied that this is usable
i will post the corepup base tcz
see you soon
wanderer
this is an update of what i am working on
corepup consists of
the base isos coreplus 6.4.1 and dcoreplus-jessie
mods to the boot menu - done
mods to the boot functions - done
the base corepup tcz which will contain
the backgrounds - done
hacked minimal jwm - done
the master utility program written in c - which i am writing now
the master utility program written in busybox ash - which i am writing now
in the spirit of minimalism and modularity
these master programs
are only written in c and ash
no gui toolkit
they have a small main function file
that calls all the other functions
which are contained in include files
some corepup functions are
scripts to make the linked directory system
a script to make the linked root directory
scripts to make the menu the core and tcz
a script to recompile jwm
a script to call/recompile the libc editor
a script to independently mount and link tcz
etc
a work in progress
when i am satisfied that this is usable
i will post the corepup base tcz
see you soon
wanderer
hi all
since mcewanw has started his own thread
to develop dcoredog
i would advise anyone interested
in using tinycore/dcore as a base
to direct their attention to his project
since he is doing the advanced work in this area
i will be following his thread as best i can
and if i feel there is something i can contribute
i will post it there
i will continue to work on my project
which has far more limited aims and expertise
and will post corepup specific stuff here
see you there
wanderer
since mcewanw has started his own thread
to develop dcoredog
i would advise anyone interested
in using tinycore/dcore as a base
to direct their attention to his project
since he is doing the advanced work in this area
i will be following his thread as best i can
and if i feel there is something i can contribute
i will post it there
i will continue to work on my project
which has far more limited aims and expertise
and will post corepup specific stuff here
see you there
wanderer
Hi wanderer,wanderer wrote:... will post corepup specific stuff here
wanderer
Yes, I won't be publishing anything related to the core product, only dcore, so nice to have both being covered without duplication since we can share a lot of ideas and some will be useful to both projects. I'm keen to see your corepup developments once you are ready to release it since some if not all of that could be useful in dCoreDog too.
William
github mcewanw
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I usually replace the CFLAGS optimizations (not the -I/* and -D* stuff) with:Keef wrote:I'd run 'strip' on the jwm binary - you'll get a big reduction. The 1.2 version drops from over 400 k to 112 k.
The 1.2 version has a configure script, I haven't tried anything older yet.
Goingnuts and technosaurus could no doubt give you some good advice on a minimal JWM.
-g0 -Os -s -fvisibility=hidden -fomit-frame-pointer -ffunction-sections -fdata-sections -fno-asynchronous-unwind-tables -fno-ident
and LDFLAGS (except -l and -L stuff) with:
-Wl,--sort-common,--gc-sections,--print-gc-sections,--as-needed,-s
The --print-gc-sections isn't needed but I like to see exactly what is being removed (in case it shouldn't be) and not removed (if I think it should be) so I can maybe help clean up the code. Also -fno-ident doesn't save much code, but it prevents people from easily detecting what compiler was used so they can exploit security issues... you may want to leave it off if you think you might need that info later.
There are a few more that I use regularly, but jwm doesn't do much floating point, so they'll have very little effect.
Edit: My build of my fork of jwm with stb_image and nanosvg statically compiled in (replaces libpng, libjpeg, libcairo+glib and librsvg and adds support for gif, bmp and pnm images) ... compiled to 209kb.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
if goingnuts or technosaurus (or anyone ) reads this
i would like to know your opinion
on statically compiling the old gtk1-dillo
so that i could have gtkedit emelfm and gtk-1dillo
all gtk1 apps
as a base tcz for corepup
i am going to try to get it to work with its old libraries
which it did fine in the older puppies
any thoughts
wanderer
i would like to know your opinion
on statically compiling the old gtk1-dillo
so that i could have gtkedit emelfm and gtk-1dillo
all gtk1 apps
as a base tcz for corepup
i am going to try to get it to work with its old libraries
which it did fine in the older puppies
any thoughts
wanderer
hi all
just an update to annoy everyone
and remind all that i continue to work on this little project
i have decided that i will make a corepup tcz
that has everything needed to build corepup from a base tc iso
it will include
1 the corepup howto
2 the corepup-jwm
3 some corepup backgrounds
4 the corepup syslinux.cfg to mod the boot menu
5 the corepup tc-config to mod the boot functions
6 other corepup stuff as decided
then anyone can download the base iso
add the corepup tcz
read the howto and mod what they want
and they will have a corepup iso
there are a great many mods and additional functions
that can be added to tc
to make a unique corepup version
and i am working on all this now
will post again soon
have a nice life
wanderer
just an update to annoy everyone
and remind all that i continue to work on this little project
i have decided that i will make a corepup tcz
that has everything needed to build corepup from a base tc iso
it will include
1 the corepup howto
2 the corepup-jwm
3 some corepup backgrounds
4 the corepup syslinux.cfg to mod the boot menu
5 the corepup tc-config to mod the boot functions
6 other corepup stuff as decided
then anyone can download the base iso
add the corepup tcz
read the howto and mod what they want
and they will have a corepup iso
there are a great many mods and additional functions
that can be added to tc
to make a unique corepup version
and i am working on all this now
will post again soon
have a nice life
wanderer
Hello, sounds like an interesting project. If you have anything working you should link to it in the first post so people don't have to skim through the whole thread to find the latest version but perhaps it isn't ready for release yet. I don't know, I haven't found it and I haven't tried it.wanderer wrote:hi all
just an update to annoy everyone
and remind all that i continue to work on this little project
i have decided that i will make a corepup tcz
that has everything needed to build corepup from a base tc iso
it will include
1 the corepup howto
2 the corepup-jwm
3 some corepup backgrounds
4 the corepup syslinux.cfg to mod the boot menu
5 the corepup tc-config to mod the boot functions
6 other corepup stuff as decided
then anyone can download the base iso
add the corepup tcz
read the howto and mod what they want
and they will have a corepup iso
there are a great many mods and additional functions
that can be added to tc
to make a unique corepup version
and i am working on all this now
will post again soon
have a nice life
wanderer
hi guys
thank you cisbear for your support
and s243a for your interest
i apologize
i have been a very poor project manager
but i beg forgiveness
i have been playing with things in corepup
and not posting
and i have demands from my job
i have tried to explain that looking at the tinycore system
is really the key
i am just adding things to expand its functions
and make it more useful to the puppy community
if you download the tc isos and play with them
everything i am doing will become clear
this project is just intended to provide an answer
to the perennial questions on the forum
for a minimal modular system and community project
mcewanw has done a great job
and his system is more powerful
since it accesses the debian repositories
so looking at what he has done may be more useful
i will post the corepup tcz when time allows
and i will put it on the first post so people can find it easily
thanks all
wanderer
thank you cisbear for your support
and s243a for your interest
i apologize
i have been a very poor project manager
but i beg forgiveness
i have been playing with things in corepup
and not posting
and i have demands from my job
i have tried to explain that looking at the tinycore system
is really the key
i am just adding things to expand its functions
and make it more useful to the puppy community
if you download the tc isos and play with them
everything i am doing will become clear
this project is just intended to provide an answer
to the perennial questions on the forum
for a minimal modular system and community project
mcewanw has done a great job
and his system is more powerful
since it accesses the debian repositories
so looking at what he has done may be more useful
i will post the corepup tcz when time allows
and i will put it on the first post so people can find it easily
thanks all
wanderer
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
hi all
i continue to play with corepup
which is an attempt to combine the advantages of
puppy and tinycore
one way to do this is to make puppy sfs files into tinycore tcz files
the best choice would be a browser
firefox or chrome or one of their derivatives
does anyone have a suggestion for what puppy sfs would be a good candidate ?
wanderer
i continue to play with corepup
which is an attempt to combine the advantages of
puppy and tinycore
one way to do this is to make puppy sfs files into tinycore tcz files
the best choice would be a browser
firefox or chrome or one of their derivatives
does anyone have a suggestion for what puppy sfs would be a good candidate ?
wanderer
HI wanderer.
Good to see you back.
I'm not sure I understand your post above:
a puppy.sfs is a complete OS, as is tinycore. If you offer a Puppy.sfs in tinycore,
the two OS's will conflict, yes?
If you just want to put a browser in an sfs and convert it to tcz, I'd offer the extremes:
links2 and vivaldi
potentially the smallest browser and potentially the largest browser,
just to get people talking!
BFN.
Good to see you back.
I'm not sure I understand your post above:
a puppy.sfs is a complete OS, as is tinycore. If you offer a Puppy.sfs in tinycore,
the two OS's will conflict, yes?
If you just want to put a browser in an sfs and convert it to tcz, I'd offer the extremes:
links2 and vivaldi
potentially the smallest browser and potentially the largest browser,
just to get people talking!
BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)