1 |
Justin Vander Ziel wrote: |
2 |
|
3 |
> Hello folks. |
4 |
> |
5 |
> Some more questions for the eventual Gentoo/linux dev-newbies if nothing |
6 |
> else (and for myself, of course B) |
7 |
> |
8 |
> 1. I managed to revise the iptables-1.1.2.ebuild script to handle |
9 |
> iptables-1.2 -- and it worked! That is, except for one small problem: I |
10 |
> forgot to build a package list for ebuild and BTW, how do I do this? |
11 |
> |
12 |
> 2. the ebuild script chokes on versions such as in autofs-4.0.0-pre9.tar.bz2 |
13 |
> (with accompanying ebuild file) -- when I do |
14 |
> |
15 |
> # ebuild autofs-4.0.0-pre9.ebuild merge |
16 |
> |
17 |
> I get the message |
18 |
> |
19 |
> 4.0.0pre9 doesn't appear to be a version or rev string |
20 |
> !!! packagename is not a valid packagename |
21 |
> Exiting |
22 |
|
23 |
autofs-4.0.0_pre9.ebuild should work. Maybe Daniel can document the naming |
24 |
pattern |
25 |
somewhere on the net. |
26 |
|
27 |
> |
28 |
> |
29 |
> 3. iptables |
30 |
> when I do |
31 |
> |
32 |
> # modprobe ip6table_filter |
33 |
> # ip6tables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE |
34 |
> |
35 |
> (this is from from Rusty Russel's Linux 2.4 NAT HOWTO from |
36 |
> netfilter.kernelnotes.org) I get the error message |
37 |
> |
38 |
> iptables: v1.2: can't initialize iptables table 'nat': iptables who? (do |
39 |
> you need to insmod?) |
40 |
> Perhaps iptables or your kernel needs to be upgraded |
41 |
|
42 |
I think that is just a kernel-configuration issue. |
43 |
|
44 |
> |
45 |
> |
46 |
> (Yes, I upgraded to v1.2 (see number 1 above) thinking perhaps something was |
47 |
> missed and then I did a portage-unmerge of the original sys-apps/iptables... |
48 |
> but I get the exact same error message as I did with 1.1.2 ). |
49 |
> |
50 |
> 4. kernel confusion |
51 |
> On Sun, 7 Jan 2001 08:55:23 -0700, drobbins@g.o wrote: |
52 |
> > To: achim@g.o |
53 |
> > > Another question, what kernel do you use at the moment test12, |
54 |
> prerelease or |
55 |
> > > final ac1/2/3.? |
56 |
> > |
57 |
> > I'm using test12. |
58 |
> OK, could someone please clarify the *NEW* and bungled kernel naming system? |
59 |
> - Is there a match between 2.3.X and the 2.4.0-testX kernels? |
60 |
> - What does final ac1/2/3 refer to? |
61 |
> When all is said and done why not just go with 2.4.0 stable? |
62 |
|
63 |
2.4.0 does not work correct with reiserfs. Thats why I made packages for |
64 |
ac2/3/4. (2.4.0.2, 2.4.0.3 ...). |
65 |
I use 2.4.0.3-r1 at the moment here. 2.4.0.3 includes a buggy nfs-patch, this |
66 |
patch gets |
67 |
not applied in 2.4.0.3-r1. In 2.4.0.4 there where a few changes to LFS in the |
68 |
kernel and |
69 |
there is only a quick fix for that to work with reiserfs available at the |
70 |
moment, so |
71 |
2.4.0.3-r1 is the best choice at the moment but you can't use nfs with |
72 |
reiserfs. |
73 |
|
74 |
|
75 |
> |
76 |
> Ok, so I'm sure you get/will get suggestions until the cows come home and |
77 |
> then some. However, I did notice that you have a bootscripts alternative in |
78 |
> the package list that I did not find particularly impressive (Though I seem |
79 |
> to recall that it was mostly because nothing was written for it, yet or else |
80 |
> I can't remember why). Here is my suggested alternative - Linux Boot |
81 |
> Scripts. In fact, it seems such a good idea to me that I think it should be |
82 |
> THE init script. A full description is available here |
83 |
> (http://www.atnf.csiro.au/~rgooch/linux/boot-scripts/) but here are the |
84 |
> highlights IMHO: |
85 |
> * There is no master script which orchestrates everything. The mini scripts |
86 |
> are kept in /sbin/init.d and init(8) runs all of them, in random order |
87 |
> except where there is a script dependent on another. |
88 |
> * Each script runs any other scripts it depends on, using the need(8) |
89 |
> programme which ensures that a script is only run once. |
90 |
> * runlevels can be supported in one of two ways. The traditional method |
91 |
> would require that the script specified be a directory in which case all the |
92 |
> scripts in the directory would be run. This uses rc1.d etc. with symlinks |
93 |
> back to init.d |
94 |
> R Gooch says that a "more elegant solution is to have a script for each |
95 |
> runlevel, which would look something like this: |
96 |
> #! /bin/sh |
97 |
> # /sbin/init.d/runlevel.3 |
98 |
> case "$1" in |
99 |
> start) |
100 |
> need runlevel.2 |
101 |
> need portmap |
102 |
> mount -vat nfs |
103 |
> ;; |
104 |
> stop) |
105 |
> umount -vat nfs |
106 |
> ;; |
107 |
> esac |
108 |
> # End |
109 |
> which seems to be pretty elegant to me as well. Expert comments? |
110 |
|
111 |
Sounds interesting, more comments later. :-) |
112 |
|
113 |
> |
114 |
> |
115 |
> 8. cfengine (http://www.gnu.org/software/cfengine/cfengine.html) |
116 |
> This also seems to be the way to go from what I have heard (mostly from |
117 |
> Christopher Brown at http://vip.hpnc.com/~cbbrowne/linuxsysconfig.html. |
118 |
> However, the e-mail responses from him are all at work). Any thoughts on |
119 |
> this? |
120 |
> |
121 |
> 9. Nifty cd package label in ps if your interested. |
122 |
> I spent a little time in Photoshop LE (I don't have $600 smackers to pay for |
123 |
> the real thing!) and whipped this up. I think it's attractive but it's not |
124 |
> exactly 'production quality'. Anyways if you want a copy I'll send you a |
125 |
> postscript file with the cd label and jacket for gentoo 1.0 rc3 |
126 |
> |
127 |
> Justin (Just enough to be dangerous) Vander Ziel |
128 |
> mailto:zielot@××××××××××.com |
129 |
> |
130 |
> _______________________________________________ |
131 |
> gentoo-dev mailing list |
132 |
> gentoo-dev@g.o |
133 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |