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