On Sun, 19 Mar 2000, Pete wrote:
> It does not have to be that hands on.
...
> I hacked PicoBSD to do this so it works from one floppy. You can
> either name the file install.cfg in which case it is run automatically
> or give it a ../stand/my_script.cfg to grab the build file you wish
> from s
It does not have to be that hands on.
Brian Dean wrote:
>
> Daniel C. Sobral wrote:
> > Brian Dean wrote:
> > >
> > > Forrest Aldrich wrote:
> > > > Someone mentioned that sysinstall could be scripted... is this the way to
> > > > go, then?
> > >
> > > I use scripted sysinstalls here. It's real
Daniel C. Sobral wrote:
> Brian Dean wrote:
> >
> > Forrest Aldrich wrote:
> > > Someone mentioned that sysinstall could be scripted... is this the way to
> > > go, then?
> >
> > I use scripted sysinstalls here. It's really easy, however, you still
> > have to interact with a few dialogs, namel
Brian Dean wrote:
>
> Forrest Aldrich wrote:
> > Someone mentioned that sysinstall could be scripted... is this the way to
> > go, then?
>
> I use scripted sysinstalls here. It's really easy, however, you still
> have to interact with a few dialogs, namely:
>
> 1) of course, you have t
This wouldn't work in our situation, where we are needing to modify data...
so if there were a power outage, imagine the hassle. Good idea, though.
Most of our systems have 64 - 128mb of ram. They are doing distributed
status monitoring and secondary DNS. So, there would be a bit of changes
* Jonathan Smith <[EMAIL PROTECTED]> [000317 08:48] wrote:
>
>
>
> On Fri, 17 Mar 2000, Forrest Aldrich wrote:
>
> > Another issue here, at least in our application of it, is about adding
> > users and setting passwords.With well over 100 machines, we want to
> > also have installed user
On Fri, 17 Mar 2000, Forrest Aldrich wrote:
> I was also curious about what people do to keep a fleet of FreeBSD
> machines up-to-date with CVSup and buildworld. I can't imagine
> manually going to more than 100 machines and doing the same thing
> manually... how time consuming.
Have a master c
On Fri, 17 Mar 2000, Forrest Aldrich wrote:
> I was also curious about what people do to keep a fleet of FreeBSD machines
> up-to-date with CVSup and buildworld. I can't imagine manually going to
> more than 100 machines and doing the same thing manually... how time consuming.
>
> To summariz
As far as keeping them "up to date", this is what we do:
- Have a local cvsup-mirror server
- All FreeBSD workstations and servers cvsup (just ports) off of it
nightly.
- Our central build server (which doubles as an insanely overpowered SMP
dns server), builds -STABLE, and all kernels nightly
On Fri, 17 Mar 2000, Forrest Aldrich wrote:
> Another issue here, at least in our application of it, is about adding
> users and setting passwords.With well over 100 machines, we want to
> also have installed user accounts for our engineers. Again, nightmareish
> to consider doing man
Another issue here, at least in our application of it, is about adding
users and setting passwords.With well over 100 machines, we want to
also have installed user accounts for our engineers. Again, nightmareish
to consider doing manually.
Such a script used at startup could contain also
Yes, making this process easier with Sysinstall would be a Good
Thing(tm). Especially I see the need here due to the widespread use of
FreeBSD in enterprise environments. This topic will certainly come up
again and again.
What I would like to see is a customized boot disk that, after loading
Forrest Aldrich wrote:
> Someone mentioned that sysinstall could be scripted... is this the way to
> go, then?
I use scripted sysinstalls here. It's really easy, however, you still
have to interact with a few dialogs, namely:
1) of course, you have to specify your config file from
On Fri, Mar 17, 2000 at 07:51:28AM -0500, Forrest Aldrich wrote:
> Someone mentioned that sysinstall could be scripted... is this the way
> to go, then?
It's one way to go, although it's not as good as Solaris' JumpStart
(although that has faults of it's own...). For a quick example look in
/usr
There was mentioned that someone was "appointed" (perhaps unwillingly :) to
look into this one... who?
I was also curious about what people do to keep a fleet of FreeBSD machines
up-to-date with CVSup and buildworld. I can't imagine manually going to
more than 100 machines and doing the same
Nik Clayton wrote:
>
> On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote:
> > I'm wondering if there might not be a way to streamline this install
> > process, such that a boot floopy and script could be created to take a
> > minimum amount of information, and then "do the right thi
On Fri, Feb 25, 2000 at 10:23:37AM -0500, Forrest Aldrich wrote:
> I'm wondering if there might not be a way to streamline this install
> process, such that a boot floopy and script could be created to take a
> minimum amount of information, and then "do the right thing" as for the
> install.
> In article <[EMAIL PROTECTED]>, Rodney W. Grimes
> <[EMAIL PROTECTED]> wrote:
>
> > A much faster way to do this is to just dd the first few megabytes
> > of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use
> > dump | restore to populate the disk.
>
> Do you run newfs on the re
In article <[EMAIL PROTECTED]>, Rodney W. Grimes
<[EMAIL PROTECTED]> wrote:
> A much faster way to do this is to just dd the first few megabytes
> of the disk (dd if=foo of=/dev/rXXd bs=32768 count=1024). Then use
> dump | restore to populate the disk.
Do you run newfs on the receiving disk bef
> Perhaps this would be of interest in CURRENT issues:
>
>
> We have several servers that we plan on deploying across the US. Their
> purpose in life is network status and monitoring. The hardware profiles
> are exactly the same...
>
> Currently, we're using DD to mirror a disk image onto
In message <[EMAIL PROTECTED]>, Forrest Aldrich writes
:
>Perhaps this would be of interest in CURRENT issues:
>
>
>We have several servers that we plan on deploying across the US. Their
>purpose in life is network status and monitoring. The hardware profiles
>are exactly the same...
>
>Curre
Perhaps this would be of interest in CURRENT issues:
We have several servers that we plan on deploying across the US. Their
purpose in life is network status and monitoring. The hardware profiles
are exactly the same...
Currently, we're using DD to mirror a disk image onto a new installati
22 matches
Mail list logo
