1 |
I am in the process of trying to develop something along these lines. I |
2 |
havent gotten very far because I am trying to develop a list of features |
3 |
to be implemented. In the near term the busybox discussion that you are |
4 |
mentioning wont be implemented. There is too much work to get a usable |
5 |
system based on that. I know for a fact that much of the regular |
6 |
expression stuff will break because of that. Who knows how much else |
7 |
will be broken. |
8 |
|
9 |
For what you are doing however you could use cow files to make things |
10 |
more secure. If you feel you have been hacked you can stop the instance |
11 |
and remove the cow file and restart and you are back to the point when |
12 |
you first started the instance. I am not sure if this is what you are |
13 |
after but it could help. |
14 |
|
15 |
Basically what is left to add to catalyst is a new target that will take |
16 |
a seed stage and copy it into a loop back filesystem. COde needs to be |
17 |
added to choose the size and name of the initial backing file. What |
18 |
type of filesystem should be formatted to it etc. Most of the other |
19 |
heavy lifting is already in place. |
20 |
|
21 |
When catalyst 2 comes out you can take the stage4 target which makes it |
22 |
possible to make a system that is stored in a tarball and take some |
23 |
scripts and migrate it into the uml loop back files. This may be what |
24 |
you are looking for. Otherwise at somepoint catalyst may have these |
25 |
features built in but it depends on the time constraints. |
26 |
|
27 |
I hope this helps. |
28 |
Rocket |
29 |
|
30 |
On 17:28 Wed 29 Jun , Chris Gianelloni wrote: |
31 |
> On Wed, 2005-06-29 at 17:04 -0400, Victor Condino wrote: |
32 |
> > Also, I was wondering how realistic it is to replace bash, grep, sed, |
33 |
> > awk, tail, procps, psutil, etc. with busybox. I know that the |
34 |
> > initscripts in baselayout rely on these various text- and shell-utils |
35 |
> > and obviously on bash... is it possible to get them to run using busybox |
36 |
> > and its builtin applets? if so that would cut down on the root-fs size |
37 |
> > and complexity, not to mention my build time, by alot. |
38 |
> |
39 |
> The embedded stuff uses baselayout-lite, I believe. Otherwise, |
40 |
> replacing the baselayout stuff will be a serious pain and will probably |
41 |
> take you quite a few man-hours. |
42 |
> |
43 |
> > I know catalyst is designed to do this sort of thing, and from what I |
44 |
> > gather, the embedded target, although meant for real (as in hw) embedded |
45 |
> > systems, is pretty close to what I need, but when it comes to python, i |
46 |
> > know very little, so examining the source in /usr/lib/catalyst/modules/ |
47 |
> > hasn't been too helpful. Which target is closest to what I'm looking |
48 |
> > for, and if the embedded target is it, where can I find some good info |
49 |
> > and an example .spec for it? I found this link: |
50 |
> > [http://dev.gentoo.org/~mutex/catalyst-doc], but at the end there's |
51 |
> > nothing after the line, "Links to sample spec files:" ;) |
52 |
> |
53 |
> I would think it would be the embedded target. Very little work has |
54 |
> really been done in this area by me, so I couldn't tell you how it |
55 |
> works. |
56 |
> |
57 |
> > I'm willing to take the plunge and learn python if nescessary to do some |
58 |
> > hacking on one of the existing target modules to get it to do what i |
59 |
> > need. Basically just wondering if anyone else is interested in automated |
60 |
> > building of this kind of system, and if anyone can suggest where to |
61 |
> > start and what might need to be done in order to get catalyst to do |
62 |
> > this. I don't mean to pester the developers; this is not intended as a |
63 |
> > "feature request" or a "how do I ..." help-desk call ;) |
64 |
> |
65 |
> I'm sure rocket will pipe in once I quit harassing him for changes for |
66 |
> the release. He's been poking around with both UML and Xen, so he would |
67 |
> probably be one of the best resources on this. |
68 |
> |
69 |
> -- |
70 |
> Chris Gianelloni |
71 |
> Release Engineering - Strategic Lead/QA Manager |
72 |
> Games - Developer |
73 |
> Gentoo Linux |