public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Devan Franchini" <twitch153@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: tools-hardened/desktop/
Date: Thu, 11 Dec 2014 23:20:33 +0000 (UTC)	[thread overview]
Message-ID: <1418340026.8453184f38fa317f973adefa3120640106b039e8.twitch153@gentoo> (raw)

commit:     8453184f38fa317f973adefa3120640106b039e8
Author:     Devan Franchini <twitch153 <AT> gentoo <DOT> org>
AuthorDate: Thu Dec 11 23:20:26 2014 +0000
Commit:     Devan Franchini <twitch153 <AT> gentoo <DOT> org>
CommitDate: Thu Dec 11 23:20:26 2014 +0000
URL:        http://sources.gentoo.org/gitweb/?p=proj/releng.git;a=commit;h=8453184f

tools-hardened/desktop: Updates README to include information about the stage3 tarball

---
 tools-hardened/desktop/README | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/tools-hardened/desktop/README b/tools-hardened/desktop/README
index fa8526f..139124a 100644
--- a/tools-hardened/desktop/README
+++ b/tools-hardened/desktop/README
@@ -19,10 +19,21 @@ Then apply the patch:
 * rm -f drivers/block/loop.c include/linux/loop.h
 * patch -p1 < loop-AES-kernel.patch
 
+Stage 3 tarball:
+================
+TinHat relies on a stage 3 tarball as it's seed to begin the chroot.
+By default, it expects to see the tarball in:
+"/var/tmp/catalyst/builds/hardened/amd64/stage3-amd64-hardened-latest.tar.bz2"
+You can however inform TinHat of your own location of choice by passing it
+as an environment variable: "STAGE3".
+
 To run:
 =======
+ex.) STAGE3="/ministry/of/silly/walks/evil-rabbit.tar.bz2" ./<DM>-run.sh
+
+or without the STAGE3 environment variable.
 
-Execute ./<DM>-run.sh
+ex.) ./<DM-run.sh
 
 Where <DM> is a desktop manager of three flavors of choice:
 


             reply	other threads:[~2014-12-11 23:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 23:20 Devan Franchini [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-16 22:15 [gentoo-commits] proj/releng:master commit in: tools-hardened/desktop/ Devan Franchini
2015-06-16 22:09 Devan Franchini
2015-06-16 22:02 Devan Franchini
2015-06-16 22:02 Devan Franchini
2015-06-16 21:17 Devan Franchini
2015-06-16 21:04 Devan Franchini
2015-06-13 17:50 Devan Franchini
2015-03-24  2:19 Devan Franchini
2015-03-19 21:12 Devan Franchini
2015-03-15 19:22 Devan Franchini
2015-03-15 19:15 Devan Franchini
2015-03-15 19:12 Devan Franchini
2015-03-12  2:28 Devan Franchini
2015-03-12  2:23 Devan Franchini
2015-03-11 21:26 Devan Franchini
2015-02-15 19:56 Devan Franchini
2015-02-15 19:37 Devan Franchini
2015-02-14  4:13 Devan Franchini
2015-02-11 20:25 Devan Franchini
2015-02-10  3:28 Devan Franchini
2015-01-02  4:45 Devan Franchini
2014-12-18  5:34 Devan Franchini
2014-12-15 20:33 Devan Franchini
2014-12-11 22:29 Devan Franchini
2014-12-09  2:42 Devan Franchini
2014-10-23 14:47 Devan Franchini
2014-10-09 20:38 Devan Franchini
2014-10-09 20:38 Devan Franchini
2014-10-09 20:38 Devan Franchini
2014-08-18 21:59 Robin H. Johnson
2014-07-23  3:31 Devan Franchini
2014-05-06 19:32 Devan Franchini
2014-04-26  3:01 Devan Franchini
2014-04-08 19:59 Devan Franchini

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=1418340026.8453184f38fa317f973adefa3120640106b039e8.twitch153@gentoo \
    --to=twitch153@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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