1 |
> > and both systems contain bash, that interprets the script, why the |
2 |
> > difference on syntax? |
3 |
> > |
4 |
> |
5 |
> Can you attach to bash script you are running and the exact error |
6 |
> messages? It is hard to say (at least for me) without seeing it; bash |
7 |
> to bash portability issues are something I have never heard of. As a |
8 |
> guess there are a variety of options you can change while running in |
9 |
> the interpreter with the "set" command that can also be set in |
10 |
> configuration files or the command line. Also possible is that the |
11 |
> install CD contains a gimped version of bash, but typically then it's |
12 |
> not called bash. It could also be running it with "set -o posix" for |
13 |
> some reason. |
14 |
|
15 |
The script itself is of not interest -- it is just particulars -- that |
16 |
i can change even right on the target machine, though it is hard to do |
17 |
for many lines and w/o mcedit at least, not to say graphical editor -- |
18 |
w/ the everywhere existing nano! :o) |
19 |
|
20 |
I simply wonder the phenomena. And having not found the answer myself, |
21 |
would ask more experienced users of "Gentoo". |
22 |
|
23 |
> The installation process at its core involves preparing the disks and |
24 |
> then extracting the stage 3 to them. Disk preparation can be |
25 |
> exceedingly complicated and making an automated installer that |
26 |
> supports all possible setups is pretty hard, only fairly recently have |
27 |
> distributions like Debian been able to offer automatic setup of |
28 |
> encrypted LVM volume groups. Some possible configurations (per PV |
29 |
> keys) still aren't supported. |
30 |
|
31 |
It is not always required. So, this part could be done manually still |
32 |
whereas the rest -- automated, like usual installer does. |
33 |
|
34 |
> The other part is creating a kernel. For that there is genkernel, but |
35 |
> it just compiles everything in. I'm not sure that counts as |
36 |
> configuration but it is automatic. |
37 |
|
38 |
Again, nothing keeps us from using several commands to compile |
39 |
customized kernel, starting w/ |
40 |
|
41 |
/usr/bin/make menuconfig |
42 |
|
43 |
> I do think the handbook leaves far too many things out that normal |
44 |
> users would need. I'm trying to compile a list of useful x86/PC |
45 |
> related things to add to the handbook at some point, like useful |
46 |
> default make.conf and portage options. There's also a lot of |
47 |
> configuration files to sort through, documenting files of interest (if |
48 |
> not providing some default configuration for them) is probably a good |
49 |
> idea. |
50 |
|
51 |
Of course! Best practical knowledge should be accumulated in the |
52 |
documentation and included as default presets for the installation or |
53 |
later system administration. |
54 |
|
55 |
You remember, i did rise here question on profile customization? -- So, |
56 |
i thought out that base profiled is too "thick" to be called base or |
57 |
default. I think, only working kernel, package manager and network |
58 |
-- speaking of installed and self booted system -- should be installed |
59 |
and called base/default and from that base all other profiles grow. |
60 |
Also, all those other profiles should not to be as next step to |
61 |
develop and grow the installation, but checklists of packages |
62 |
w/ corresponding checklists of the packages dependencies -- just like |
63 |
"Debian" does for its compiled packages w/ that differences, that |
64 |
choosing process will be followed not downloading and installation |
65 |
only, but compilation also. -- These i call "all about choice", so that |
66 |
user/admin had not to fight w/ the profiles that are totally |
67 |
unnecessary at wide angle of view, but rather add some automation for |
68 |
the lazy -- like client wants KDE suite -- alright, get it -- and so |
69 |
forth. But for the concerned, are those checklists of packages -- when |
70 |
everyone can choose what is desired likewise USE, CFLAGS -- all through |
71 |
checklists, so that the user will not search the web for the well known |
72 |
stuff, but right in the system configuration might see all that is |
73 |
available w/ comments on what and why it does, as well as pros and cons |
74 |
that follow the choices. |
75 |
|
76 |
All this simplifies the process of installation and farther support of |
77 |
systems. Nobody likes to wade through the oceans of routine but rather |
78 |
make something fast, reliable, new, etc. But routine just scares away. |
79 |
|
80 |
|
81 |
Sthu. |