| 1 |
Grant Edwards <grant.b.edwards <at> gmail.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > I don't get why any distro leaves this out, why anyone wouldn't like to |
| 5 |
> > automatically notice while booting any announcement that something failed, |
| 6 |
> > especially someone who has just gotten a new installation up for the first |
| 7 |
> > times. Why isn't --noclear set by default? |
| 8 |
|
| 9 |
+1 |
| 10 |
|
| 11 |
> Yep, I find it infuriating that by default all distros seem to go to |
| 12 |
> great effort to hide as much information about the boot/startup |
| 13 |
> process as possible. WTF? Do they think that stuff is top secret or |
| 14 |
> something? Are they afraid they'll lose their jobs if that info gets |
| 15 |
> out? |
| 16 |
|
| 17 |
++1 |
| 18 |
|
| 19 |
|
| 20 |
It's even worse than you guys have stated. There is code often referred to |
| 21 |
as "netconsol":: |
| 22 |
|
| 23 |
I was/is wonderful for streaming concurrent detail about a system |
| 24 |
during install, as soon as the ethernet interface is set:: |
| 25 |
|
| 26 |
https://www.kernel.org/doc/Documentation/networking/netconsole.txt |
| 27 |
|
| 28 |
|
| 29 |
I'm not sure why it's not part of most installation semenatics:: |
| 30 |
I have posted numerous times to numerous forums about it and |
| 31 |
nothing ever happens. So now I have just decided to develop my own gentoo |
| 32 |
installation semantics. |
| 33 |
|
| 34 |
Dont misunderstand my position:: I think all those folks that have |
| 35 |
writen/removed coded from the kernel and the distros are well intentioned |
| 36 |
and honest folks. But, when you add up the entire ecosystem of what's |
| 37 |
going on (insert your favorite conspiracy theories, as you like) the |
| 38 |
days of average users being able to efficiently use open source |
| 39 |
*nix technologies is fading fast. So like Alan has said (and many others) |
| 40 |
there is *no we* in nix unless your or I step up. |
| 41 |
|
| 42 |
|
| 43 |
Fair enough! :: |
| 44 |
|
| 45 |
git clone --bare https://gitweb.gentoo.org/proj/gli.gitCloning into bare |
| 46 |
repository 'gli.git'... |
| 47 |
fatal: repository 'https://gitweb.gentoo.org/proj/gli.git/' not found |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
It'd be wonderfully appreciated if somebody (anybody) has those old |
| 52 |
installer sources anywhere I can replicate them for tweaking. |
| 53 |
|
| 54 |
|
| 55 |
Note:: I intend to work on a variety of install semantics. ALL are welcome |
| 56 |
to help, guide, critisize and encourage me on this journey! |
| 57 |
|
| 58 |
Beware:: I'm old, crotchitee, dumb, dense etc etc, and those are my |
| 59 |
better qualities. My intentions are well intentioned. |
| 60 |
|
| 61 |
(off to hoop_it_up to relieve some stress!) |
| 62 |
|
| 63 |
If/when we get an installer(s) working for the commoners, we should |
| 64 |
start a gentoo-install reflector so as to not hassle the gentoo_user |
| 65 |
experts that do not believe in automated gentoo installs. These 'experts' |
| 66 |
are really wonderful folks that have answered thosands of questions over the |
| 67 |
years for folks:: and I thank them for that. |
| 68 |
|
| 69 |
But supporting the noob installers is more a job for the |
| 70 |
post_noob_installers who just maybe are able to present a |
| 71 |
kinder_gentler_mo_practical face on automated installation support. |
| 72 |
|
| 73 |
|
| 74 |
PEACE, |
| 75 |
James |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
sincerely, |
| 81 |
James |
Archives