← Back to team overview

c4c-dev team mailing list archive

"Byte-Sized" Actions

 

Guys,

I know it took me an hour to upload the huge 1404-2.zip (2.1 GB) file to the shared C4C Folder in Dropbox, so it's probably going to take triple that for anyone to download via DSL, or satellite. So, I've uploaded "byte-size" chunks of it too, tar-gz files, split by where it ends up (but, still in the same order as the bullet lists). Israel; this may also help explain why there are a ton of binary files. The list below is also a text file called TAR-GZ-FILES. Oh, and the big one is still up there too if you've got a fast connection and/or just want everything at once.

ADD BIBLES, COMMENTARIES, MAPS, BOOKMARKS & FILE SETTINGS
dot-jsword.tar.gz [15.3MB] expands to dot-jsword, the contents of which go into ~/.jsword dot-mozilla.tar.gz [3.4MB] expands to dot-mozilla, the contents of which go into ~/.mozilla dot-sword.tar.gz [144.8MB] expands to dot-sword, the contents of which go into ~/.sword dot-xiphos.tar.gz [2.7KiB] expands to dot-xiphos, the contents of which go into ~/.xiphos etc-gnome.tar.gz [1.7KiB] expands to etc-gnome, the contents of which (defaults.list) go into/etc/gnome etc-xdg-lubuntu-applications.tar.gz [1.7KiB] expands to etc-xdg-lubuntu-applications, the contents of which (defaults.list) go into/etc/xdg/lubuntu/applications

ADD C4C SPECIFIC STUFF
dot-config.tar.gz [19.2KiB] expands to dot-config, the contents of which go into ~/.conf share.tar.gz [3.7KiB] expands to share, the contents of which go into ~/.local/share christian-12-apostles.tar.gz [592KiB] expands to 12-apostles, which goes into /usr/share/christian christian-audio-bible.tar.gz [16KiB] expands to audio-bible, which goes into /usr/share/christian christian-believe.tar.gz [3.3MB] expands to believe, which goes into /usr/share/christian christian-bkgs.tar.gz [8.2MB] expands to bkgs, which goes into /usr/share/christian christian-bvmq.tar.gz [528KiB] expands to bvmq, which goes into /usr/share/christian christian-christian-music.tar.gz [296.8MB] expands to christian-music, which goes into /usr/share/christian christian-christian-videos.tar.gz [16KiB] expands to christian-videos, which goes into /usr/share/christian christian-disciple.tar.gz [2MB] expands to disciple, which goes into /usr/share/christian christian-fbgs.tar.gz [7.8MB] expands to fbgs, which goes into /usr/share/christian christian-icons.tar.gz [176KiB] expands to icons, which goes into /usr/share/christian christian-john-123.tar.gz [644.6MB] expands to john-123, which goes into /usr/share/christian christian-new-testament.tar.gz [158.2MB] expands to new-testament, which goes into /usr/share/christian christian-ogg-video.tar.gz [54.2MB] expands to ogg-video, which goes into /usr/share/christian christian-old-testament.tar.gz [591.5MB] expands to old-testament, which goes into /usr/share/christian christian-swf-video.tar.gz [24.6MB] expands to swf-video, which goes into /usr/share/christian doc.tar.gz [816KiB] expands to doc, the contents of which go into /usr/share/doc lubuntu.tar.gz [21.8MB] expands to lubuntu, the contents of which go into /usr/share/lubuntu themes.tar.gz [32KiB] expands to themes, the contents of which go into /lib/plymouth/themes/ applications.tar.gz [16KiB] expands to applications, the contents of which go into /usr/share/applications

Eric

On 05/17/2015 08:23 AM, KI7MT wrote:
Hi Eric,

Nice work!

I've only browsed through each section briefly, but I think most, if not
all could be done with a single shell script, at least, when building a
box locally. Doing all this from the command line would make things a
bit easier also.

Now we need to look at each action and determine if is a system wide
task or user specific task then determine the best way accomplish the
task programatically. A good could be, after the box is configured the
way you like, create a new user and determine what needs doing.


best regards

Greg












On 05/16/2015 09:57 PM, Eric Bradshaw wrote:
Guys,

I've installed the C4C ReSpin of 14.04.2 on a 64-bit machine and made
both a High Level Action List called "Bullet-Points" and one with more
detail called "Bullet-List-Expanded" (sorry - couldn't help it) attached
to this email and uploaded to the C4C shared folder. I've also uploaded
a zipped 1404-2 folder with all the files I used and reference in the
Bullet-List-Expanded text file.

I release now why Greg was confused about why I was un-installing apps.
It was because I never could get what I wanted to start with by
installing the Lubuntu-base - I always started with Lubuntu Desktop.
Plus everything on my home network has a static IP, so it's easier to
set the Internet connection from a Desktop ISO to do the initial install.

Anyway - I hope I'm helping.

Eric

On 05/16/2015 01:09 PM, KI7MT wrote:
Hi Eric,

Just a suggestion; I would recommend using a .txt document rather than
.odt files for your high level doc. Text formatting is a bit of an art,
but when done properly, is reansferable to almost anything, likst
text2html for example.

Most developers prefer .txt docs for Emails as well as procedures, as it
is much easier to read / edit / and merge.

It can take a while to get used too, but in the long run, allot of
documentation for things in Linux are written in plain-txt: How-To's,
README, INSTALL, all that stuff is always in plain-txt. It also makes
copy & past work much better :-)

best regards,

Greg.






Follow ups

References