Tiny Core Base > TCB Q&A Forum
TinyCore from SCRATCH - NADA -ZILCH - ZIP - NULL - - - THE BIG BANG!!!
^thehatsrule^:
Okay then. I'll give one reminder: respect is paramount in communities.
Hints on starting rolling your own was given, and it was already explained that there was no build system, nor retrievable 'log'. And that busybox was used, scripts are plaintext, etc. I'll still say that I am not sure what you are trying to ask for (vague). To answer your previous question though, currently improvements are done by modifying the corresponding parts of the system.
Micon Frink:
Hats, I have the utmost respect for the community and for your lack of understanding. Thanks for your input - I really do appreciate it. Sorry I'm not communicating in your brand of English. I'll post a build script when I've got one I guess...
Looking at the unique parts I wonder if buildroot was have used to generate the base system. If this is true it would be helpful to have the buildroot config files. However, I don't find these in the source so perhaps the base file system was made by hand. Then again the init scripts are not in the src either. Hm... I'll be testing out this theory next week and post my results...
I noticed that most of the contents of /usr/bin/ are custom scripts and programs.
The following is a list of scripts unique to TinyCoreLinux:
desktop.sh, exitcheck.sh, filetool.sh, floppytool.sh, getTime.sh, menu.awk, mkcryptohome, mktclocal, search.sh, set_jwm_background.awk, showbootcodes, startx, tce2tcz.sh, tce-fetch.sh, tce-load, tc-terminal-server, tcz-unistall, text2lp0, wbar.sh, xsetup.sh
These scripts are not included in the TinyCoreLinux source directory so they will need to be copied from the current distro ISO directly. Ideally these should be placed in a tarball in the source tree. Perhaps I can create that tarball.
LEGALITY: Many of these scripts do not bear proper reference to copyright. Some of them don't seem to originate with TinyCoreLinux but have no reference information to their origination. Could it be that these are carry-over from DSL?
The following binaries are also included in the /usr/bin/ directory:
add2file, appbrowser, cpanel, datetool, exittc, fdtool, filetool, flrun, help, mnttool, mousetool, netcardconf, popask, popup, settheme, stats, swapfile, tcemirror, wallpaper, watcher
All of these are original work for TinyCoreLinux and their source resides in the fltk_projects/ directory of the source tree. There is however, one exception: watcher is in the base of the source tree. None of these apps have a Makefile but usually consist of three files <foo>.cxx, <foo>.h and <foo>.fl
LEGALITY: Some of these programs seem to have originated with DSL but there the references in source are incomplete. I'm not sure if there are any license issues with this as both distros use the same license.
SIDE NOTE: The source tree and releases have been removed from the tinycorelinux.com server and now reside on distro.ibiblio.org/pub/linux/distributions/tinycorelinux/
. This was not noted on the main site so I thought I'd mention it here. I was frustrated for a minutes trying to find the source. The link to the download directory on the tinycorelinux.com website has been changed to reflect this new location. Not a big deal just a minor frustration that takes up space here...
- FRINK
mikshaw:
There's an English expression (probably derive from an earlier source) "making mountains out of molehills". Much of what you have just mentioned has no real importance.
--- Quote ---Many of these scripts do not bear proper reference to copyright.
--- End quote ---
It's up to the author to decide whether copyright is necessarily included. If there is no copyright notice in these scripts, there never was one.
--- Quote ---Some of them don't seem to originate with TinyCoreLinux but have no reference information to their origination.
--- End quote ---
They originate with roberts and others who wrote for roberts.
--- Quote ---None of these scripts are included in the TinyCoreLinux source directory.
--- End quote ---
Scripts are already in source form.
--- Quote ---None of these apps have makefiles but usually consist of three files <foo>.cxx, <foo>.h and <foo>.fl.
--- End quote ---
Makefiles are not a requirement for building software.
--- Quote ---Some of these programs seem to have originated with DSL but there the references in source are incomplete.
--- End quote ---
As with the scripts, they were written by roberts and his minions. It is not necessary for an author to reference the origin of his own work.
--- Quote ---This should be noted prominently on the website but wasn't. However, the link to the download directory has been changed to reflect this new location.
--- End quote ---
What is the complaint here? The server changed, that's all. All the links are the same as they were; it's just as easy to access the source.
Doing things differently is not the same as doing things wrong.
roberts:
Yeah, your're right I don't always put a copywrite banner on every dinky plain text script that I write. And that most of Tiny Core consists of my custom stuff. So what.
Now this thread is turned into your personal blog area, where you are the critic down to the minutiae. I find your actions and attitude very curious. You seem to have nothing to contribute but only to complain about absolutely everything.
tobiaus:
--- Quote from: ^thehatsrule^ on December 25, 2008, 01:55:31 AM ---Okay then. I'll give one reminder: respect is paramount in communities.
Hints on starting rolling your own was given, and it was already explained that there was no build system, nor retrievable 'log'.
--- End quote ---
--- Quote from: roberts on December 26, 2008, 09:03:18 AM ---Yeah, your're right I don't always put a copywrite banner on every dinky plain text script that I write. And that most of Tiny Core consists of my custom stuff. So what.
Now this thread is turned into your personal blog area, where you are the critic down to the minutiae. I find your actions and attitude very curious. You seem to have nothing to contribute but only to complain about absolutely everything.
--- End quote ---
whoa whoa whoa! this is totally unnecessary... no one's said anything to make it necessary to come down on him like this. no one's being disrespectful. this same thing happened with puppy linux years ago... and i've always known dsl and roberts to be far less uptight about these things. in general, i've always counted on the dsl community to if nothing else, have a more professional image, or at least a more meticulous, less sloppy one.
as for "so what," i mean no disrespect either. only that in the open source world, it's expected that you be able to modify things, just as dsl was (THANKFULLY) modified by roberts, and thus made into the best dsl that dsl ever was. some people just take code and aren't careful with it. they mean well, and no one's being accused of anything. only sometimes people want to make a new distro, or adapt it to a new platform (that's the case here,) and they want to follow all the rules.
that means they have to ask where the stuff comes from. so if no one provided copyright information, that's not a problem for roberts, because roberts is the author.
it's only a problem for the original poster, who wants to respect roberts copyright and use it per a gpl license or something. he just wants to respect the rules. so unless roberts gives him formal permission (or writes copyright information on each script, or as a collection of scripts) then anyone trying to respect roberts (and the gpl) has to ask more than once.
please don't be mad at him for that. if anything, he should be applauded. and it is certainly not disrespectful.
--- Quote from: ^thehatsrule^ on December 18, 2008, 07:28:57 PM ---Please remember that this is a public forum, so interpreting messages 'lightly' in general would be helpful.
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version