how to avoid setting time/date when auto-net-installing?

how to avoid setting time/date when auto-net-installing?

Post by HWank » Sun, 30 Jan 1994 11:30:08



I've setup a completely automatic network installation server, and was able
to install a client by using "boot net - install" from the prom monitor.
All went well, but I was unable to avoid the need to manually confirm that
the time and date were actually correct.  In all cases the time and date
were correct, and even if they were not, I don't care -- I want the
automatic installation to continue without the need for manual intervention.

I figured that the program which prompts for time/date is /usr/sbin/sysidsys
(right?), but I don't have source to modify it.  The man page did not reveal
any way to override this need.  Does anyone know how to perform a "more"
automatic installation than what currently is available?

Thanks,
Erez Zadok.
Central Research Facilities.
Columbia University Department of Computer Science.
---

 after midnight."                     | Usenet: ...!rutgers!columbia!cs!ezk


 
 
 

how to avoid setting time/date when auto-net-installing?

Post by Casper H.S. D » Sun, 30 Jan 1994 20:52:24



Quote:}I've setup a completely automatic network installation server, and was able
}to install a client by using "boot net - install" from the prom monitor.
}All went well, but I was unable to avoid the need to manually confirm that
}the time and date were actually correct.  In all cases the time and date
}were correct, and even if they were not, I don't care -- I want the
}automatic installation to continue without the need for manual intervention.

This is actually documented:  you need a timehost alias in your NIS/NIS+
host maps and you need a timezone map/table  (format is Timezone Domainname)

Casper

 
 
 

how to avoid setting time/date when auto-net-installing?

Post by David P. Ke » Mon, 31 Jan 1994 10:42:26




Quote:>I've setup a completely automatic network installation server, and was able
>to install a client by using "boot net - install" from the prom monitor.
>All went well, but I was unable to avoid the need to manually confirm that
>the time and date were actually correct.

I had this problem doing net installs - the machine would ask for netmasks,
timezone, and date/time.  The problem (for us) was NIS+ permissions.
Since install clients are completely unauthenticated during an install,
any information they need from NIS+ must have read permission for "nobody".

The following need to be readable:
  netmasks entry for your domain
  timezone entry for your domain (one per host is not necessary)
  timehost entry in the hosts table (or the whole host table if you
                       don't mind allowing everybody to read it)
  services table  (since rdate needs tcp service to get the time)

Since you weren't getting prompted for netmask and timezone, I suspect
your NIS+ is set up with level 0 (minimum) security, but you are missing a
timehost alias.  Add that, and you should be able to install without
typing a thing.

--

-----------------------------------------------------------------------------
"If it doesn't have an analogy, it isn't Usenet (tm)"

 
 
 

how to avoid setting time/date when auto-net-installing?

Post by Wolfram Wagn » Thu, 03 Feb 1994 00:24:19




> }I've setup a completely automatic network installation server, and was able
> }to install a client by using "boot net - install" from the prom monitor.
> }All went well, but I was unable to avoid the need to manually confirm that
> }the time and date were actually correct.  In all cases the time and date
> }were correct, and even if they were not, I don't care -- I want the
> }automatic installation to continue without the need for manual intervention.

> This is actually documented:  you need a timehost alias in your NIS/NIS+
> host maps and you need a timezone map/table  (format is Timezone Domainname)

> Casper

I actually tried to get around this by creating the timezone yp-map and aliasing
a central computer timehost. In my case, this brought a lot of work but no
change to the mentioned problem.

I fixed it by the following workaround: in the file that gets mounted as
/sbin/sysconfig ( in my case:
/export/install/export/exec/kvm/sparc.sun4X.Solaris_2.3/sbin/sysconfig)
the line calling sysidsys is commented out. By this, the Timezone is not set at
all (not exactly what you wish). I postpone this until the finish script is
running, where I put in some lines saying:

==============================start example===============================
# set timezone
cp /a/etc/default/init /a/etc/default/init.bak
sed </a/etc/default/init.bak -e"/TZ=/d" >/a/etc/default/init
ypcat timezone.byname | grep "[         ]$DOMAINNAME" |\
      sed -e"s/[        ].*//" -e"s/^/TZ=/" >>/a/etc/default/init
===============================end example================================

[     ] contains a blank and a tab every time, DOMAINNAME is set before.

This works just fine for me (finally).


Max-Planck-Institut fuer Informatik     Tel.:  +49-681/302-5403
Im Stadtwald                            Fax:   +49-681/302-5417
66123 Saarbruecken GERMANY

 
 
 

1. Auto install asks for date & time

I'm running Solaris 2.3 on SPARCstations.
I have set up my server as an install server.
I want to use the auto install stuff to install Solaris on a client.
I used the host manager in admintool to add the client, which
added lines to /etc/{hosts,bootparams,ethers,timezone}.
I created /export/install_info/{rules,class,finish} as the
auto install scripts.
On the client I did "boot net - install".
But it stops to prompt the client's console for the date and time.
After I manually enter the date and time, it keeps going automatically
through everything else.
The server's /etc/timezone looks like this:
        US/Arizona      mipl.ece
        US/Arizona      birdie
[mipl.ece is the domain name; birdie is the client's name]
Am I supposed to put something in the "class" script to set
the date and time?

--
Jeff Rodriguez


The University of Arizona               Tel: (602) 621-8732 or 8963
Tucson, AZ 85721                        FAX: (602) 621-8076

2. tv tuner help

3. date/time of a file compare with current date/time

4. Cable-Modem configuration with Cog├ęco ISP

5. run time date and syslog date/time conflict

6. IPv6 multiple routing tables

7. Auto system date & Time

8. DHCPcd prior to 1.3.22-p12 are vunerable

9. Solaris 2.5 Auto-Net-Install Problems.

10. Up to date: Net-2 or Net-3?

11. how to set correct date and time on my linux box

12. How to set Date/Time zone on Linux?

13. unable to set date/time - why?