From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] blocks to fix
Date: Thu, 30 Oct 2008 11:05:34 -0700 [thread overview]
Message-ID: <5bdc1c8b0810301105u1f7601b2m3d48013612bb9ca3@mail.gmail.com> (raw)
In-Reply-To: <20081030172419.48c66bc7@zaphod.digimed.co.uk>
On Thu, Oct 30, 2008 at 10:24 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 30 Oct 2008 06:46:30 +0100, Momesso Andrea wrote:
>
>> > It's a bit late now, but installing a second distro, or a bare stage 3
>> > gentoo, as a dual boot so you can still access the machoine if it
>> > breaks. As an alternative, send the user a GRML CD and get them to
>> > boot that if things go wrong.
>
>> There is no need to drive there or to send a cd. Even with no com_err
>> and no wget, you can still ssh into the machine, so scp should work too.
>
> On this occasion, yes. But as a general CYA policy, as long as the user
> is capable of making a selection from a boot menu, a fallback distro
> would be useful in this situation.
>
>
> --
> Neil Bothwick
Yes, it would be helpful. In my case it would need to be configured
for full ssh/noip support, and probably shouldn't be Gentoo based as
this selection wouldn't likely get updated very often and the now far
more restrictive policies on how often Gentoo has to be updated
probably aren't appropriate for this task.
None the less maybe a good thing for me to do would be to do an
install of something like this remotely, test it, and then deal with
system updates later.
Also, as long as ssh isn't harmed I can pretty much scp any package to
the machine and get it working again, albeit with some extra work.
Normally I already do a --fetchonly any time I'm planning on an emerge
-DuN world but if I forgot usually you can still make it work somehow.
Take care,
Mark
next prev parent reply other threads:[~2008-10-30 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 2:34 [gentoo-user] blocks to fix Mark Knecht
2008-10-29 2:43 ` James Homuth
2008-10-29 3:11 ` Allan Gottlieb
2008-10-29 16:24 ` Andrew MacKenzie
2008-10-29 18:00 ` Mark Knecht
2008-10-29 20:49 ` Neil Bothwick
2008-10-29 21:46 ` Mark Knecht
2008-10-30 20:44 ` Alex Schuster
2008-10-30 21:51 ` Neil Bothwick
2008-10-30 21:57 ` Paul Hartman
2008-10-30 22:12 ` BRM
2008-10-30 22:58 ` Mark Knecht
2008-10-29 22:08 ` [gentoo-user] " »Q«
2008-10-30 5:46 ` [gentoo-user] " Momesso Andrea
2008-10-30 17:24 ` Neil Bothwick
2008-10-30 18:05 ` Mark Knecht [this message]
2008-10-30 11:18 ` KH
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=5bdc1c8b0810301105u1f7601b2m3d48013612bb9ca3@mail.gmail.com \
--to=markknecht@gmail.com \
--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