[Thincrust-devel] ec2-creator merge into appliance-tools
Joey Boggs
jboggs at redhat.com
Tue Sep 2 14:55:15 UTC 2008
Bryan Kearney wrote:
> Joey Boggs wrote:
>> Bryan Kearney wrote:
>>> Joey Boggs wrote:
>>>> Bryan Kearney wrote:
>>>>> Nice work joey. Couple of comments:
>>>>>
>>>>> - Can you add a -n attribute so I can name it what I want?
>>>> Yep can add that in easily
>>>
>>> Great!
>> I'll work on that today
>>>
>>>>> - is there any way to autodetect the inputtype based on the
>>>>> imagefile?
>>>> I'm thinking there is based on using the output of "file
>>>> $filename" I'm playing around with glade/pygtk and perhaps adding
>>>> in a options simple gui interface in shouldn't be too hard.
>>>
>>> Dont worry about GUI yet. Lets focus on more commmand line features
>>> and the whitelisting.
>> After spending so much time working on the blacklist/whitelist items,
>> it's gonna be much simpler just to put the list in a file. Based on
>> comments from dlutterkort, the interpreter would most likely need to
>> be written C, as well as passing those directory variables around can
>> be trouble. There are a few C interpreter/compilers framework types
>> out that that can work in our case but it just alot of overhead we
>> would need to add to the image, as well as providing the source that
>> wouldn't be able to compile correctly on gcc etc... The best and most
>> manageable route is to put the list inside of $nameAppliance rpm in a
>> predetermined filename then just run: /path/to/minimizer $filename
>> The file containing the listing can still contain drop/keep
>> commands. Its much cleaner, simpler and easier to keep track of
>> should the list get very granular, and without filling up the
>> kickstart file.
>
> What exactly is the issue? I looked at a simple python program (since
> we require python to be there) and it seems like the contents of the
> post section are written to to a file, and that file is passed in as
> sys.argv[1]. So.. a simple python program could be used to open it,
> read it, and apply the necessary rules.
>
> -- bk
It's the way the program is being called. If you specify an interpreter
it's just running it like a bash script being called. All of the
commands should understood inside the script by the shell/interpreter.
If you specify /usr/bin/python or some other variant for an interpreter
it has to be a real interpreter, since the rest of the file contains
DROP commands. It's effectively just copy/pasting the contents on a
console and DROP is not a command.
%post --interpreter=/myinterpreter
DROP /dir1
DROP /dir2
At the above point ^^ the DROP commands are not sys arguments they are
commands/keywords
>
> _______________________________________________
> Thincrust-devel mailing list
> Thincrust-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/thincrust-devel
More information about the Thincrust-devel
mailing list