I am thinking of doing another re-spin of the car2-v3alpha11 .upgrade file (the player software distro).

There would be no changes to the player s/w itself of course (it is now frozen in time). But there could be some useful changes to the packaging of it and a certain number of "essential" add-ons.

This has been done before, for the "big disk" images I created.
The idea is to take those, and add certain other recent things.

But what? Thus far, I have:

• Hijack kernel, for big mem/drive support and other stuff
• the improved Vu Meter visual with rivets
• updated timezone info
• run set_empeg_max_fid on the player executable
• run fidsift.sh on the music filesystem(s)
• enable swap by default
• empeg web lite stylesheet and supporting files

That's a good start. But what other stuff is there that many of us might want by default?

???

Hi Mark-
I haven't done much reading about the config.ini file (and haven't done any editing, either), but I always wondered if it would be possible to update it from the empeg, instead of elsewhere.
Sort of a 'save this configuration as new default' option.

Like I said- I don't really know how it all works, so if I'm out of bounds please don't mind me.

I think this is a great idea, Mark.

I'd even go so far as to say this could be done to the 2.0 images as well.

Sounds like a fantastic idea. I'd be happy to test.

Yes 2.0 as well please

v3 eats my lunch

I've always liked having telnetd on my player for various things which requires the binary, the /dev entries and the hijack entry (although I'm not sure how easy that last one is to add to an existing config.ini with the installer.

v3 is good for me. I only ever use it these days. It's stable enough for me.

Hi Mark,

Those are the items I have to redo by hand so that would be a brilliant time saver. I did try to modify my setup using your upgrader/splitter apps but had enough issues each time that I reverted.

Excellent stuff.

Yeah, just having the files there and available would be useful, even if it still required some action to "enable" it in Hijack.

Can you bundle up everything that is needed (plus GPL sources), and a short note of instruction for me? I'll put it in the queue with the rest.

Thanks

I use netcat, dmesg and telnetd from Trevor's Excellent Homepage (yes, the source is there too).

Peachy. If you want any of those in the build, I would ask that you package them up for me, with instructions for where to put things etc..

Yes, I can figure it all out myself, and it is easy.. but it's even easier to just ignore things that I don't need here myself. Unless somebody goes to the effort of making it more effortless here.

Cheers

I guess we could add ifconfig, and ntpdate and/or rdate to that list.

-ml

I'll put a package together for you Mark, but it will have to be tomorrow when I have my Empeg handy for reference.

rsync?

I'm quite happy to do that for telnetd (and if I think of anything else) for you Mark, but I'm not sure how much more you want than isn't on that page sein linked to. There's a binary and source archive and description to install.

Put the binary somewhere, run the script to create the /dev entries and put an entry in hijack to start it.

Good one!

What about emphatic and/or all the Third party software found on the Empeg Wiki (excluding the replacement player software)?

I'd be less interested in this. The ones above I'd find useful, but the majority of the 3rd party software is fun-n-games stuff that I don't need, or want installed, let alone by default with this other, more useful* stuff.

*edit: by "useful", I mean small utilities for services commonly found in linux distros.

Here is a small archive.

• Pim's cool rsync 2.6.0 with --empeg-progress option
• Some of Trevor's handy utils
  • Telnet Daemon
  • Netcat
  • Dmesg
• Mark's Smartctl

This is all handy stuff which I think most people would like to see included as a start. runonce/devs has to be run once to create the magic to make the telnet daemon work, all that should be rolled in so it works out of the box I guess. A Hijack menu entry for the telnet daemon would be useful.

Perhaps an text editor of some description?

Not something I use that often though I admit, since there really is only one text file config.ini and that has other edit methods.

Another great suggestion. I think a stripped vim (or maybe elvis) would be perfect.

While I would personally prefer a vi, nano might make more sense for those not previously familiar with vi.

ROFL !!!!

Then die gasping for air...

That one got printed and went on my cubicle wall the day it went online.

Along with this one.

I have now pulled down a local copy of the source and binary archives of the Debian Potato Linux distro for ARM. This is apparently the recommended starting point for empeg add-ons, so I figured having my own permanent copy of it might be handy someday.

So this means we've now got a pretty large pool of potential empeg add-ons that could be included in the re-spin.

Note that this re-spin isn't going to happen today (or tomorrow), but rather some time between now and the 10th Birthday Party weekend.

Cheers

Another thing for the list:

Include the bigdisk-builder functionality, so that a special builder image is no longer needed when just adding a second drive.

-ml

One more:

Fix the rwm script to use the nocheck flag.

-ml