From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo way of handling pre-built kernels
Date: Fri, 23 Feb 2007 05:26:31 -0600 [thread overview]
Message-ID: <200702230526.36247.bss03@volumehost.net> (raw)
In-Reply-To: <20070223111337.740b46d2@hactar.digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
On Friday 23 February 2007, Neil Bothwick <neil@digimed.co.uk> wrote
about 'Re: [gentoo-user] Gentoo way of handling pre-built kernels':
> On Fri, 23 Feb 2007 10:42:17 +0100, Robert Szentmihalyi wrote:
> > I have successfully deployed Gentoo on about 30 desktop PCs in a
> > corporate environment.
> > Now, as I need to update the kernel on those PCs, I wonder if there is
> > a standard Gentoo way (maybe a script or something), that people are
> > using to build and deploy binary kernel packages.
>
> Even better, if the
> machines are all networked, push the changes out with rsync then use
> tentakel (or a for loop) to reboot each box.
Or, push the kernel (with included initramfs) out via netboot, and after
mounting the root filesystem, copy the modules into place. If you have a
large number of modules (too big to fit inside the kernel image), push
them with rsync (or similar) to the client machines, either from within
the initramfs or with an initscript that starts before any others.
> You could also put this in an update script on each of the boxes then
> use tentakel to run it on some or all of them. tentakel (in portage) is
> a handy way of running the same command on a group of machines, and you
> can set up named groups and subgroups to make life even easier.
Never used tentakel, but IIRC there's another parallel-shell tools
available that works over rsh/rlogin/ssh called psh.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss03@volumehost.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.org/ \_/
New GPG Key! Old key expires 2007-03-25. Upgrade NOW!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-23 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 9:42 [gentoo-user] Gentoo way of handling pre-built kernels Robert Szentmihalyi
2007-02-23 11:13 ` Neil Bothwick
2007-02-23 11:26 ` Boyd Stephen Smith Jr. [this message]
2007-02-23 12:29 ` [gentoo-user] Wine and Cedega at the same time Gyuszk
2007-02-23 13:50 ` Peter Ruskin
2007-02-23 16:52 ` b.n.
2007-02-23 20:24 ` Gyuszk
2007-02-23 14:30 ` Bo Ørsted Andresen
2007-02-23 20:22 ` Gyuszk
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=200702230526.36247.bss03@volumehost.net \
--to=bss03@volumehost.net \
--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