From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Cc: <news@sea.gmane.org>
Subject: RE: [gentoo-user] Re: rsync internal mirror configuration
Date: Tue, 12 Jul 2005 15:47:14 -0400 [thread overview]
Message-ID: <006601c5871a$809c6600$5f01010a@jnetlab.lcl> (raw)
In-Reply-To: <loom.20050712T211413-492@post.gmane.org>
> Thanks for the scripts and help!
That's what we're here for ;-)
> When I roll out a new TCP/IP based data-logger
> (hopefully this fall) it'll take sensor inputs and control a few outputs.
> No humans will use the devices for anything other than interfacing
> sensors and collecting data.
As with most other embedded devices, wouldn't these remain fairly static at
the OS level? I mean, would you really want to try to debug why (all of a
sudden) the remote devices stopped functioning because of an errant package
emerge?
As for learning gentoo at a deeper level, we encourage that. I would
suggest, only because it really made things clear for me, that you look at
Linux from Scratch http://www.linuxfromscratch.org. It will make the entire
process for how to custom build a linux box a lot clearer.
> The experience I gain form helping kids/adults use Gentoo, will help me
> manage thousands of dataloggers across public and private networks.
> Besides if I screw it up, no big deal. They can always use a winblows
> box until I get it fixed. Strict user control semantics will be
> used to limit what they can screw up.
>From an administrative point of view, however, I think you'd be better
served by having one system working, freeze it and then clone it to the
other systems. Skip updates as much as possible.
Basically you'd be taking the same route as other embedded linux products.
My linksys routers, all linux based, have the ability to handle new firmware
(linux distribution) but they do not auto-update themselves.
> I'm also using jffnms to update and manage all sorts of routers and
> industrial contols embedded devices. After some
> time, I'm sure I'll roll my own solution, but for now, managing Gentoo
> user systems and customizing JFFNMS for router and other snmp devices
> is enough of to keep me busy.
Exactly my point - why introduce even more administrative headaches to have
thousands of gentoo systems automatically emerging packages on their own?
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-12 19:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 18:18 [gentoo-user] rsync internal mirror configuration James
2005-07-11 18:37 ` Dave Nebinger
2005-07-12 2:42 ` [gentoo-user] " James
2005-07-12 6:51 ` A. Khattri
2005-07-12 15:16 ` James
2005-07-12 13:06 ` Dave Nebinger
2005-07-12 15:03 ` James
2005-07-12 15:29 ` Dave Nebinger
2005-07-12 16:03 ` James
2005-07-12 16:36 ` Dave Nebinger
2005-07-12 19:24 ` James
2005-07-12 19:47 ` Dave Nebinger [this message]
2005-07-13 14:35 ` James
2005-07-13 14:55 ` Dave Nebinger
2005-07-13 16:03 ` James
2005-07-13 14:51 ` James
2005-07-13 15:12 ` Dave Nebinger
2005-07-13 16:16 ` James
2005-07-13 17:54 ` A. Khattri
2005-07-13 20:35 ` James
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 13:09 Dave Nebinger
2005-07-12 15:04 ` James
2005-07-12 15:36 ` Dave Nebinger
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='006601c5871a$809c6600$5f01010a@jnetlab.lcl' \
--to=dnebinger@joat.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=news@sea.gmane.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