hi mike,

remember this discussion.  Have a look at b9 and see what you think, in the conf dir.

cheers

Miles

Looks good! Very promising for a tidier ts.conf.

I tried to add lprng as a test to see PRINTER_0 stuff getting added to ts.conf.sample - and nothing happened! That confused me a bit untill I realized that this particular package has a bug...! Build actually reports this too, but I didn't notice. Typical to pick the buggy package for the first test

Good work!

Mike


 

Miles Roper wrote:
> been thinking about your idea, no it hasn't taken me 6 days to come up
> with a response, just busy :o)
>
> I can see merit in what your suggesting :o) actually not a bad idea ;o)
> now that I've taken time to read it and stop saying "butbutbutbut"
>
> ok, how does this sound.....
>
> ts/conf/*.conf.example files, these are all copies of
>
> ts/packages/xxx/build/conf/.....
>
> when I do a build for a upload, I'll script it so it automatically takes
> a copy of the files and places them in ts/conf, that way there will only
> one set being maintained.
>
> now, how does your suggestion work in regards to getting the
> *.conf.example files into the buildtime file.  will a person go through
> and add what example files he wants into a buildtime file?  thoughts?
>
> Mike Eriksen wrote:
>> On Tue, 10 Jan 2006, Miles Roper wrote:
>>
>>> spell checked version :o)
>>>
>>> was having a think about this on the way to work.
>>>
>>> what about as you suggested a two pass solution.
>>>
>>> ie
>>>
>>> person does a build, at end of which user is told they can import a
>>> buildtime file by copying and modifying the sample file if they wish,
>>> and then running
>>>
>>> ./addbuildtime
>>>
>>> which is a script which adds the file to the image (default being
>>> thinstation.conf.buildtime, you can specify file name).
>>>
>>> all the script does is call the build script with the correct
>>> parameters, much like TS-O-Matic
>>
>>
>> Ehm, nah - don't really see the advantage of this. Then I think the
>> current system is at least as good. The idea of my previous suggestion
>> was to automatically get the user selected defaults into the image. If
>> the user has to be involved twice anyway, we might as well keep the
>> current system and not bother people with more changes.
>>
>> However, I do wonder why you are so reluctant to the buildtime idea.
>> It's really just a matter to add ts.conf.network into the image.
>> Ofcourse a ts.conf.network will still be needed for quick tests and
>> on-the-fly changes, but how often do they really occur once you the
>> your setup right? Never mind, I can get it as I like with the current
>> system and there hasn't exactly been an outcry in the community to
>> support me
>>
>> BTW - have I broken my beta 8 or doesn't ts.conf.sample contain any X
>> configuration?
>>
>> Mike
>>
>>
>>> mroper-kGM0oXzJM5p02iOg2JU2CQ@public.gmane.org wrote:
>>>
>>>> was having a think about this on the way to work.
>>>>
>>>> what about as you suggested a two pass solution.
>>>>
>>>> ie
>>>>
>>>> person does a build
>>>> at end of build user is told the can import a buildtime file by
>>>> copying and modifying the sample file if they wish, and then running
>>>>
>>>> ./addbuildtime
>>>>
>>>> which is a script which adds the file to the image (default   being
>>>> thinstation.conf.buildtime, you can specify file name).
>>>>
>>>> all the script is all the build script with the correct parameters.
>>>>
>>>>> From: Mike Eriksen < kme3-SQEBM9gbwNBknbxzx/v8hQ@public.gmane.org>
>>>>> Date: 2006/01/09 Mon AM 08:07:50 GMT+13:00
>>>>> To: Miles Roper <mroper-kGM0oXzJM5r/PtFMR13I2A@public.gmane.orgz >
>>>>> CC: thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>>> Subject: Re: [Thinstation-developer] beta 8
>>>>>
>>>>> On Mon, 9 Jan 2006, Miles Roper wrote:
>>>>>
>>>>>
>>>>>> hold on, just a question first,  why are you saying the person
>>>>>> needs to modify or even know the file in
>>>>>> x-common/build/conf/other/x-common even exists.  the entire point
>>>>>> was they don't need to have anything to do with these files, they
>>>>>> are included in thinstation.conf.sample  the only difficulty is
>>>>>> the buildtime file, but I have a solution for TS-O-Matic for this,
>>>>>> still thinking on TS general release.
>>>>>>
>>>>>> thoughts?
>>>>>
>>>>>
>>>>> Agreed - it's really all about the buildtime file. As you may have
>>>>> guessed I feel strongly about that one Without a buildtime you
>>>>> can't start a beta 8 at all without a tftpd. It hangs looking for
>>>>> one during boot! This applies both if you don't want/need a tftpd
>>>>> (say, a CD boot) or your tftpd fails for some reason or an other.
>>>>> This is one of the most typical newbie problems.
>>>>>
>>>>> And that's why I ask for safe defaults and at the same time to get
>>>>> a nice and clean access to the config files.
>>>>>
>>>>> The user will have to adapt ts.conf.sample anyway, so why not take
>>>>> advantage of the choises made and put those into buildtime?
>>>>>
>>>>> I hope the TS-O-Matic twist will work with a stand-alone TS. It
>>>>> looks as an elegant solution to the two-pass problem.
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>>
>>>>>> Mike Eriksen wrote:
>>>>>>
>>>>>>> On Sun, 8 Jan 2006, Miles Roper wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Mike Eriksen wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Just realized beta 8 is missing a "display" or "x" file in
>>>>>>>>> conf/ to setup the display.
>>>>>>>>>
>>>>>>>>> Mike
>>>>>>>>
>>>>>>>>
>>>>>>>> works for me.  is in x-common/build/conf/other.  does it not
>>>>>>>> work for you?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hmm - I somehow failed to spot it there. Which is probably a
>>>>>>> point by itself...
>>>>>>>
>>>>>>> It's really inhuman to ask people to edit configs *that* deep in
>>>>>>> the directory structure
>>>>>>> (packages/x-common/build/conf/other/x-common isn't exactly
>>>>>>> obvious - not to me at least!)
>>>>>>>
>>>>>>> I think we have some interesting possibilities right now with
>>>>>>> 2.2. In my opinion the two "worst" parts about TS has been the
>>>>>>> complexity of the config file and the lack of a sane default config.
>>>>>>>
>>>>>>> I see a couple of possiblities with 2.2, but I know that Miles
>>>>>>> won't necessarily be happy about the ideas.
>>>>>>>
>>>>>>> I like the idea of the conf/ directory with broken-down config
>>>>>>> files. It's *much* simpler just to edit one category (network, X,
>>>>>>> whatever) in stand-alone files. Good. But it should be the
>>>>>>> standard for any package. I understand Miles' wish to keep
>>>>>>> packages "modular" (everything belonging to a package in it's own
>>>>>>> directory and nothing else). However, a plain sym link from conf/
>>>>>>> to, say, packages/x-common/build/conf/other/x-common hardly
>>>>>>> breaks modularity.
>>>>>>>
>>>>>>> One may argue that it really doesn't matter much what
>>>>>>> packages/x-common/build/conf/other/x-common says, as it is
>>>>>>> overwritten by a local ts.conf anyway. However, what is in
>>>>>>> (packages/.../x-common is the fall-back defaults, so is DOES
>>>>>>> matter. And a lot IMHO. Well defined defaults is very important
>>>>>>> especially to newcomers. I would still like a telnet session if
>>>>>>> even the buildtime session_0 is missing.
>>>>>>>
>>>>>>> Here is what I suggest to consider:
>>>>>>> 1) The package config (and its icons) resides in
>>>>>>> packages/<package>/<whatever>
>>>>>>> 2) Each conf file exists in duplicate: <package> and
>>>>>>> <package>.example. The <package> file gets edited by the user,
>>>>>>> the <package>.example stays original and can be used to revert to
>>>>>>> defaults once the user screws up.
>>>>>>> 3) A sym link is a part of the package from conf/<package> to
>>>>>>> packages/<package>/<whatever>. I honestly don't think this sym
>>>>>>> link breaks the modularity. A normal user will only have to edit
>>>>>>> stuff in conf/ and *not* have to travese the entire packages/
>>>>>>> directory structure for configs.
>>>>>>> 4) The build script generates a ts.conf.sample and use this one
>>>>>>> as a ts.conf.buildtime as well. This step isn't trivial and may
>>>>>>> call for a two-pass build procedure, but I really don't see any
>>>>>>> way around this unless you go for a two-pass user interaction
>>>>>>> (one build to create ts.conf.sample, then copy it to buildtime
>>>>>>> and rebuild). The latter solution is very bad, IMHO.
>>>>>>>
>>>>>>> I realize this is a fairly drastical request, but if we want to
>>>>>>> address the two weakest point in TS (e.g. getting simpler
>>>>>>> configuration and sane defaults) I believe this is a possility.
>>>>>>>
>>>>>>> Whau, long post. Sorry.
>>>>>>>
>>>>>>> Mike
>>>>>>
>>>>>>
>>>>>>
>>>>> --
>>>>> Thinstation FAQ maintainer
>>>>> http://thinstation.sourceforge.net
>>>>> - a light, full featured linux based thin client OS
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through
>>>>> log files
>>>>> for problems?  Stop!  Download the new AJAX search engine that makes
>>>>> searching your log files as easy as surfing the  web.  DOWNLOAD
>>>>> SPLUNK!
>>>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>>>>> _______________________________________________
>>>>> Thinstation-developer mailing list
>>>>> Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-developer
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through
>>>> log files
>>>> for problems?  Stop!  Download the new AJAX search engine that makes
>>>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>>>> _______________________________________________
>>>> Thinstation-developer mailing list
>>>> Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>>> https://lists.sourceforge.net/lists/listinfo/thinstation-developer
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.net email is sponsored by: Splunk Inc. Do you grep through
>>> log files
>>> for problems?  Stop!  Download the new AJAX search engine that makes
>>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>>> _______________________________________________
>>> Thinstation-developer mailing list
>>> Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>>> https://lists.sourceforge.net/lists/listinfo/thinstation-developer
>>>
>>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Thinstation-developer mailing list
> Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/thinstation-developer
>



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Thinstation-developer mailing list
Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-developer

HI.

 

Tried to install new beta9 to Slovenian TS-O-MATIC site and run into troubles:

 

1. Build with tarantella gives this error:

 

21:42:16 (19.62 MB/s) - `wget_tmp/tnci3li.tar' saved [3225600/3225600]

 

cp: cannot stat `./wget_tmp/ttwebtop/ttwebtop': No such file or directory
strip: './packages/tarantella/bin/ttwebtop': No such file

 

Error has occured while installing package
Build Aborted

 

2. Build with nx client returns this error:

 

           => `wget_tmp/nxclient-1.5.0-135.i386.tar.gz'
Connecting to 64.34.161.181:80... connected.
HTTP request sent, awaiting response... 404 Not Found
21:45:41 ERROR 404: Not Found.

 

Error has occured downloading file
Build Aborted

3. Running beta9 on www.b2-net.com/tom produces an error on STEP 2:

 

Warning: file_get_contents(files/TSB_193.95.248.123/conf/master): failed to open stream: No such file or directory in /web/b2-net/html/tom/index.php on line 1127

Warning: file_get_contents(files/TSB_193.95.248.123/conf/network): failed to open stream: No such file or directory in /web/b2-net/html/tom/index.php on line 1137

Warning: file_get_contents(files/TSB_193.95.248.123/conf/storage): failed to open stream: No such file or directory in /web/b2-net/html/tom/index.php on line 1138

Warning: file_get_contents(files/TSB_193.95.248.123/conf/hdupdate): failed to open stream: No such file or directory in /web/b2-net/html/tom/index.php on line 1139

 

 

Can you guys take a look, because I'm out of time at the moment.

 

Best regards

 

Bostjan