public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: blockage
Date: Sat, 28 Mar 2015 14:44:54 +0100	[thread overview]
Message-ID: <87384pp76x.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <loom.20150323T213533-115@post.gmane.org> (James's message of "Mon, 23 Mar 2015 22:07:31 +0000 (UTC)")

James <wireless@tampabay.rr.com> writes:

> If we have some quick way to install, then systems could be setup,
> customized, used for testing and torn down again, all in a few hours? I'd
> focus on simple, minimized installs and it would give the user base a way to
> duplicate  systems for problem verification and resolution.

+1

Gentoo is really nice, and I too would like to see a way of installing a
minimal system in a faster way.  Now I need to boot the live DVD and
follow the manual to get a starting point, which takes a lot of time
which I don't have.


As to updating, it kinda turns into a PITA because you might run into
dependency problems, and you just /might/ be able to solve them --- or
not.  I can *not* have the servers in a /maybe/ operational state, so my
only choice is to *not* update them.  That, of course, isn't really a
choice either, and it leads to unreasonably long intervals between
updates, which in turn become even more difficult because more has
changed.

The same is true for my machine at home, and after the last update with
these dependency problems, I haven't had the time to compile the new
kernel that came with it --- and I probably won't because there will be
another one next time.  I didn't dare to even try to update the servers
at work after that, and I didn't dare to reboot at home.

What do you guys do?  Take the risk of having the machines down for
hours due to an update?


For those who might argue that I shouldn't put Gentoo on servers: ZFS is
required, and Gentoo appears to be the safest and easiest distribution
when you need ZFS.  Even when you don't need ZFS, there's still an awful
lack of alternatives nowadays.


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.


      reply	other threads:[~2015-03-28 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22  3:24 [gentoo-user] blockage lee
2015-03-22  5:21 ` [gentoo-user] blockage Jonathan Callen
2015-03-22 11:00   ` lee
2015-03-22  9:24 ` [gentoo-user] blockage Alan McKinnon
2015-03-22 10:45   ` lee
2015-03-22 11:31     ` Alan McKinnon
2015-03-22 12:09       ` Tom H
2015-03-22 13:04         ` lee
2015-03-22 15:02           ` [gentoo-user] blockage Jonathan Callen
2015-03-22 18:08             ` lee
2015-03-22 21:22               ` Alan McKinnon
2015-03-22 21:54                 ` Dale
2015-03-23  9:55                 ` Peter Humphrey
2015-03-23  9:59                   ` Alan McKinnon
2015-03-23 10:04                     ` Peter Humphrey
2015-03-23 22:07                     ` James
2015-03-28 13:44                       ` lee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87384pp76x.fsf@heimdali.yagibdah.de \
    --to=lee@yagibdah.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox