Re: "kickstart" for debian needed
On Mon, Apr 02, 2001 at 05:55:41PM +0200, I. Forbes wrote: > The problems: > > "apt-get --deslect-upgrade" is painfully slow - particularly on slow > hardware. And you have to sit and watch and answer "y/n" stuff 'till > it is finished. (Can't wait for debconf to be working on a useful > level). You missed the "-y" option for apt-get :)
Re: "kickstart" for debian needed
On Mon, Apr 02, 2001 at 05:55:41PM +0200, I. Forbes wrote: > The problems: > > "apt-get --deslect-upgrade" is painfully slow - particularly on slow > hardware. And you have to sit and watch and answer "y/n" stuff 'till > it is finished. (Can't wait for debconf to be working on a useful > level). You missed the "-y" option for apt-get :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Hello Duane On 27 Mar 2001, at 21:58, Duane Powers wrote: > I don't know if anyone has the details on redhat's kickstart > program, and whether that is something that could be ported to > debian... Any suggestions? At the moment we do the following: - base install (3 floppies + base.tgz from nfs drive). - break the installation when "dselect" starts - download a "configs.tgz" from the network. This contains customized versions of debian "config" files in /etc as well as other utilities in /usr/local/ and /var/www/. This configures /etc/apt/sources etc. It also contains a file "/etc/deblist" which was generated using "atp-get --set-selections". - run apt --get-selections < /etc/deblist - run apt-get --deselect-update - manually edit /etc/... to suite the particular install. This is flexible, when we change something on the network, we change in the master "configs.tgz" and all subsequent installs get it. The process is not broken when there is an upstream update - because of debian policy for "configuration" files. We have a script which backs up each machine and creates a personalized "config.tgz" file. If we have to reload a machine, we just use that one instead. (It will get upgraded to the latest "stable" stuff during the re-install process.) The problems: "apt-get --deslect-upgrade" is painfully slow - particularly on slow hardware. And you have to sit and watch and answer "y/n" stuff 'till it is finished. (Can't wait for debconf to be working on a useful level). The personalisation of the config files is slow. I think we could do with a script which runs after the config.tgz has been extracted and asks things like domain names and user names. I tried using a customized "base.tgz" that installed everything in one go. But it was too inflexible and introduced too many bugs, so we went back to the old procedure as outlined above. Regards Ian - Ian Forbes ZSD http://www.zsd.co.za Office: +27 +21 683-1388 Fax: +27 +21 64-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa -
Re: "kickstart" for debian needed
Hello Duane On 27 Mar 2001, at 21:58, Duane Powers wrote: > I don't know if anyone has the details on redhat's kickstart > program, and whether that is something that could be ported to > debian... Any suggestions? At the moment we do the following: - base install (3 floppies + base.tgz from nfs drive). - break the installation when "dselect" starts - download a "configs.tgz" from the network. This contains customized versions of debian "config" files in /etc as well as other utilities in /usr/local/ and /var/www/. This configures /etc/apt/sources etc. It also contains a file "/etc/deblist" which was generated using "atp-get --set-selections". - run apt --get-selections < /etc/deblist - run apt-get --deselect-update - manually edit /etc/... to suite the particular install. This is flexible, when we change something on the network, we change in the master "configs.tgz" and all subsequent installs get it. The process is not broken when there is an upstream update - because of debian policy for "configuration" files. We have a script which backs up each machine and creates a personalized "config.tgz" file. If we have to reload a machine, we just use that one instead. (It will get upgraded to the latest "stable" stuff during the re-install process.) The problems: "apt-get --deslect-upgrade" is painfully slow - particularly on slow hardware. And you have to sit and watch and answer "y/n" stuff 'till it is finished. (Can't wait for debconf to be working on a useful level). The personalisation of the config files is slow. I think we could do with a script which runs after the config.tgz has been extracted and asks things like domain names and user names. I tried using a customized "base.tgz" that installed everything in one go. But it was too inflexible and introduced too many bugs, so we went back to the old procedure as outlined above. Regards Ian - Ian Forbes ZSD http://www.zsd.co.za Office: +27 +21 683-1388 Fax: +27 +21 64-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
On Wed, Mar 28, 2001 at 09:52:49AM +0200, Michelle Konzack wrote: > newmachine:# dpkg --set-selections myselection.txt > > now use dselect to install it. Easier to run: 'apt-get dselect-upgrade' instead of running dselect. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz [EMAIL PROTECTED] Linux geek /) "Níl aon tinteán mar do thinteán féin." beekeeper -8|||} --Dorothy \)
Re: "kickstart" for debian needed
On Wed, Mar 28, 2001 at 09:52:49AM +0200, Michelle Konzack wrote: > dpkg --get-selections >myselection.txt You should really use: dpkg --get-selections '*' > myselection.txt Difference is the '*' gives you a list of installed, removed and purged packages. Without it you get only a list of installed packages. So you won't get a true mirror other machine. The * in inside single quotes to protect it from the shell. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz [EMAIL PROTECTED] Linux geek /) "Níl aon tinteán mar do thinteán féin." beekeeper -8|||} --Dorothy \)
Re: "kickstart" for debian needed
Hello, you need only the Base-Installation then install all programms needed and after ths make a dpkg --get-selections >myselection.txt Now you can install on other machines the Base-Installation and at the end quiet it withot any selections. Login as root and make newmachine:# dpkg --set-selections myselection.txt now use dselect to install it. Michelle Am 21:58 27.03.2001 -0800 hat Duane Powers geschrieben: > >Ok all, > >I've talked upper management into rolling out linux as the primary >OS/workstation for the members of our NOC (we're a major ISP). Now I'm >faced with installing >30+ similar machines with debian, life sucks, eh? :o) >I'm considering dd as one alternative, but that's kinda bulky 'cuz it >requires physically removing each hard drive installing in "parent" and >imaging... I've looked at things like >ghost, but that doesn't seem to be an option... I know we've had this >discussion on the list before... I don't know if anyone has the details >on redhat's kickstart program, >and whether that is something that could be ported to debian... Any >suggestions? > >A couple of the parameters I need to consider, > >Most (of our) engineers are not linux-compliant. >Need centralized login, (can't use NIS+, we've already got a NIS+ system >for Solaris... don't wanna confuse the issue,) >May need to be reinstalled occassionally due to high tech network >engineers hosing >various applications (these are going to be workstations, not servers... >accessed frequently by different users... stuff will get broken) > > >Any helpful hints, or experience will be appreciated very much. > >Duane Powers >Senior Systems Engineer II > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > ## Get the Power of Debian/GNU-Linux ##
Re: "kickstart" for debian needed
On Wed, Mar 28, 2001 at 09:52:49AM +0200, Michelle Konzack wrote: > newmachine:# dpkg --set-selections myselection.txt > > now use dselect to install it. Easier to run: 'apt-get dselect-upgrade' instead of running dselect. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz [EMAIL PROTECTED] Linux geek /) "Níl aon tinteán mar do thinteán féin." beekeeper -8|||} --Dorothy \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
On Wed, Mar 28, 2001 at 09:52:49AM +0200, Michelle Konzack wrote: > dpkg --get-selections >myselection.txt You should really use: dpkg --get-selections '*' > myselection.txt Difference is the '*' gives you a list of installed, removed and purged packages. Without it you get only a list of installed packages. So you won't get a true mirror other machine. The * in inside single quotes to protect it from the shell. bob -- bob billsonemail: [EMAIL PROTECTED] ham: kc2wz [EMAIL PROTECTED] Linux geek /) "Níl aon tinteán mar do thinteán féin." beekeeper -8|||} --Dorothy \) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Hello, you need only the Base-Installation then install all programms needed and after ths make a dpkg --get-selections >myselection.txt Now you can install on other machines the Base-Installation and at the end quiet it withot any selections. Login as root and make newmachine:# dpkg --set-selections myselection.txt now use dselect to install it. Michelle Am 21:58 27.03.2001 -0800 hat Duane Powers geschrieben: > >Ok all, > >I've talked upper management into rolling out linux as the primary >OS/workstation for the members of our NOC (we're a major ISP). Now I'm >faced with installing >30+ similar machines with debian, life sucks, eh? :o) >I'm considering dd as one alternative, but that's kinda bulky 'cuz it >requires physically removing each hard drive installing in "parent" and >imaging... I've looked at things like >ghost, but that doesn't seem to be an option... I know we've had this >discussion on the list before... I don't know if anyone has the details >on redhat's kickstart program, >and whether that is something that could be ported to debian... Any >suggestions? > >A couple of the parameters I need to consider, > >Most (of our) engineers are not linux-compliant. >Need centralized login, (can't use NIS+, we've already got a NIS+ system >for Solaris... don't wanna confuse the issue,) >May need to be reinstalled occassionally due to high tech network >engineers hosing >various applications (these are going to be workstations, not servers... >accessed frequently by different users... stuff will get broken) > > >Any helpful hints, or experience will be appreciated very much. > >Duane Powers >Senior Systems Engineer II > > >-- >To UNSUBSCRIBE, email to [EMAIL PROTECTED] >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > ## Get the Power of Debian/GNU-Linux ## -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
DI Peter Burgstaller wrote: > Hi there, > > > > Most (of our) engineers are not linux-compliant. > > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > > for Solaris... don't wanna confuse the issue,) > > > > You might like to look into using LDAP for this. Another alternitive is > > using an SQL database. This issue is pretty flexiable considering there > > are many PAM modules and quite a few Name Service (libnss) modules. > > I fail to see why you can't use NIS!? You can bind to different domains so > just run your 30 debians under their own NIS domain and you can cross exist > no problem. If you even maybe host the NIS Servers on the same machine I could > think of some very nice perl scripts to cross import data between them if you > need same userids but different services for ex. We had a similar setting > at the university of salzburg which worked very well. > Specifically because as a NOC, if NIS+ goes down, we may be unable to access our tools to troubleshoot the issue. ~duane > > - Just my 0.02, Peter > /--\ > | Dipl.-Ing. Peter Burgstaller | > | Technical Assistant and System Administrator | > | @ all information network & services gmbh| > | email: [EMAIL PROTECTED] | > | phone: +43 662 452335| > | fax : +43 662 452335 90 | > \--/ > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
DI Peter Burgstaller wrote: > Hi there, > > > > Most (of our) engineers are not linux-compliant. > > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > > for Solaris... don't wanna confuse the issue,) > > > > You might like to look into using LDAP for this. Another alternitive is > > using an SQL database. This issue is pretty flexiable considering there > > are many PAM modules and quite a few Name Service (libnss) modules. > > I fail to see why you can't use NIS!? You can bind to different domains so > just run your 30 debians under their own NIS domain and you can cross exist > no problem. If you even maybe host the NIS Servers on the same machine I could > think of some very nice perl scripts to cross import data between them if you > need same userids but different services for ex. We had a similar setting > at the university of salzburg which worked very well. > Specifically because as a NOC, if NIS+ goes down, we may be unable to access our tools to troubleshoot the issue. ~duane > > - Just my 0.02, Peter > /--\ > | Dipl.-Ing. Peter Burgstaller | > | Technical Assistant and System Administrator | > | @ all information network & services gmbh| > | email: [EMAIL PROTECTED] | > | phone: +43 662 452335| > | fax : +43 662 452335 90 | > \--/ > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Hi there, > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > You might like to look into using LDAP for this. Another alternitive is > using an SQL database. This issue is pretty flexiable considering there > are many PAM modules and quite a few Name Service (libnss) modules. I fail to see why you can't use NIS!? You can bind to different domains so just run your 30 debians under their own NIS domain and you can cross exist no problem. If you even maybe host the NIS Servers on the same machine I could think of some very nice perl scripts to cross import data between them if you need same userids but different services for ex. We had a similar setting at the university of salzburg which worked very well. - Just my 0.02, Peter /--\ | Dipl.-Ing. Peter Burgstaller | | Technical Assistant and System Administrator | | @ all information network & services gmbh| | email: [EMAIL PROTECTED] | | phone: +43 662 452335| | fax : +43 662 452335 90 | \--/
Re: "kickstart" for debian needed
Dexter wrote: > What about VA System Imager (systemimager.sourceforge.net) ? We use it here > for all our base installs - we adapt the servers with apt-get next. RSync > shall also be useful - rsync -e ssh if you're on a hostile environment (and i > believe we always are ...) Thanks, I'll look into systemimager... I've had no experience with it. ~duane > > > On Wednesday 28 March 2001 07:58, Duane Powers wrote: > > Ok all, > > > > I've talked upper management into rolling out linux as the primary > > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > > faced with installing > > 30+ similar machines with debian, life sucks, eh? :o) > > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > > requires physically removing each hard drive installing in "parent" and > > imaging... I've looked at things like > > ghost, but that doesn't seem to be an option... I know we've had this > > discussion on the list before... I don't know if anyone has the details > > on redhat's kickstart program, > > and whether that is something that could be ported to debian... Any > > suggestions? > > > > A couple of the parameters I need to consider, > > > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > May need to be reinstalled occassionally due to high tech network > > engineers hosing > > various applications (these are going to be workstations, not servers... > > accessed frequently by different users... stuff will get broken) > > > > > > Any helpful hints, or experience will be appreciated very much. > > > > Duane Powers > > Senior Systems Engineer II > > -- > Knowledge-sharing and open-source content : another way to gain eternity. > Dexter - Linux system administrator > http://lab.dexter.be - mailto : [EMAIL PROTECTED] - keep zen. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Jeremy Lunn wrote: > On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers wrote: > > 30+ similar machines with debian, life sucks, eh? :o) > > discussion on the list before... I don't know if anyone has the details > > on redhat's kickstart program, > > and whether that is something that could be ported to debian... Any > > suggestions? > > I am not sure how much of the base install could be automated. But have > you thought of making a task package? That way you can keep the > packages that are installed on each machine consistant. I'm not sure > how task packages work or how you can make them, but I think it's as > simple as depending on all the packages you need. Yes, I'm hoping to build a task-package, though I haven't had much experience with them either. > > > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > You might like to look into using LDAP for this. Another alternitive is > using an SQL database. This issue is pretty flexiable considering there > are many PAM modules and quite a few Name Service (libnss) modules. > Any suggestions on where I could learn more about using LDAP as an authentication tool? we use it for customer authentication, but I personally am not _very_ well versed... > > > May need to be reinstalled occassionally due to high tech network > > engineers hosing > > You mean they'll have root access? If that is the case there is not > much they can do. If that is the case though maybe they should be > given machines with nothing on them to start with. Or ones that can be > mucked up. If they don't have root access then I don't see it as a > problem. > no, they won't have root. but as your typical computer enthusiasts, they'll likely try to get it. :o) > > > various applications (these are going to be workstations, not servers... > > accessed frequently by different users... stuff will get broken) > > You might be able to update your task packages and either come up with a > system to start upgrading of all machines or schedule them to run > apt-get update && apt-get -y dist-upgrade every 24 hours or so. I am not > sure how debconf can handle with sitewides defaults yet either, but I do > recall something being considered for this. > This is quite a good idea, I will need to become more versed in holding packages back, and the like, we'll be running X4.02 (or .03) and apt-get upgrade's off potato like to overwrite with X3.3, so I'll want to hold that back, stuff like that. > > -- > Jeremy Lunn > Melbourne, Australia > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Duane Powers Systems Engineer II
Re: "kickstart" for debian needed
Duane, On Tue, 27 Mar 2001, Duane Powers wrote: > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) I modified the NetBSD boot floppy so it automatically uses the defaults (answers "yes"), uses DHCP (by default) and uses a local FTP server. (Right now it is two floppies, but after I remove some junk and reduce the kernel size it may fit on one.) Maybe you can modify a Linux boot floppy to do the same. > Most (of our) engineers are not linux-compliant. All that needs to be done with my boot is: 1) DHCP server setup for location; 2) DNS setup to provide correct info for the installs; 3) local ftp server setup with the base files; 4) one floppy put into machine, turn on, replace floppy when prompted and then press "Y" and enter to begin auto install; 5) repeat step three for each system. Putting the floppies into 30 computers will take about thirty minutes. The complete installation for all 30 computers will take 30 minutes (each) -- so all 30 computers will be installed within one hour. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) The base files on the FTP server can be modified for your particular needs -- so by default they can use some type of centralized authentication. Maybe there are some login (or PAM) routines that can use RADIUS or someother external authentication. Or maybe you can use a different NIS server for these? > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) If complete reinstall is needed, then simply put the auto-install disks in again. If just need to update an update (and using Debian), try using dpkg with the "--set-selections" option to set the package selections based on a prepared list. (Or point your apt sources.list to your own local Debian packages list and collection.) Jeremy C. Reed ... ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/
Re: "kickstart" for debian needed
Hi there, > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > You might like to look into using LDAP for this. Another alternitive is > using an SQL database. This issue is pretty flexiable considering there > are many PAM modules and quite a few Name Service (libnss) modules. I fail to see why you can't use NIS!? You can bind to different domains so just run your 30 debians under their own NIS domain and you can cross exist no problem. If you even maybe host the NIS Servers on the same machine I could think of some very nice perl scripts to cross import data between them if you need same userids but different services for ex. We had a similar setting at the university of salzburg which worked very well. - Just my 0.02, Peter /--\ | Dipl.-Ing. Peter Burgstaller | | Technical Assistant and System Administrator | | @ all information network & services gmbh| | email: [EMAIL PROTECTED] | | phone: +43 662 452335| | fax : +43 662 452335 90 | \--/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Dexter wrote: > What about VA System Imager (systemimager.sourceforge.net) ? We use it here > for all our base installs - we adapt the servers with apt-get next. RSync > shall also be useful - rsync -e ssh if you're on a hostile environment (and i > believe we always are ...) Thanks, I'll look into systemimager... I've had no experience with it. ~duane > > > On Wednesday 28 March 2001 07:58, Duane Powers wrote: > > Ok all, > > > > I've talked upper management into rolling out linux as the primary > > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > > faced with installing > > 30+ similar machines with debian, life sucks, eh? :o) > > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > > requires physically removing each hard drive installing in "parent" and > > imaging... I've looked at things like > > ghost, but that doesn't seem to be an option... I know we've had this > > discussion on the list before... I don't know if anyone has the details > > on redhat's kickstart program, > > and whether that is something that could be ported to debian... Any > > suggestions? > > > > A couple of the parameters I need to consider, > > > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > May need to be reinstalled occassionally due to high tech network > > engineers hosing > > various applications (these are going to be workstations, not servers... > > accessed frequently by different users... stuff will get broken) > > > > > > Any helpful hints, or experience will be appreciated very much. > > > > Duane Powers > > Senior Systems Engineer II > > -- > Knowledge-sharing and open-source content : another way to gain eternity. > Dexter - Linux system administrator > http://lab.dexter.be - mailto : [EMAIL PROTECTED] - keep zen. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Jeremy Lunn wrote: > On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers wrote: > > 30+ similar machines with debian, life sucks, eh? :o) > > discussion on the list before... I don't know if anyone has the details > > on redhat's kickstart program, > > and whether that is something that could be ported to debian... Any > > suggestions? > > I am not sure how much of the base install could be automated. But have > you thought of making a task package? That way you can keep the > packages that are installed on each machine consistant. I'm not sure > how task packages work or how you can make them, but I think it's as > simple as depending on all the packages you need. Yes, I'm hoping to build a task-package, though I haven't had much experience with them either. > > > > Most (of our) engineers are not linux-compliant. > > Need centralized login, (can't use NIS+, we've already got a NIS+ system > > for Solaris... don't wanna confuse the issue,) > > You might like to look into using LDAP for this. Another alternitive is > using an SQL database. This issue is pretty flexiable considering there > are many PAM modules and quite a few Name Service (libnss) modules. > Any suggestions on where I could learn more about using LDAP as an authentication tool? we use it for customer authentication, but I personally am not _very_ well versed... > > > May need to be reinstalled occassionally due to high tech network > > engineers hosing > > You mean they'll have root access? If that is the case there is not > much they can do. If that is the case though maybe they should be > given machines with nothing on them to start with. Or ones that can be > mucked up. If they don't have root access then I don't see it as a > problem. > no, they won't have root. but as your typical computer enthusiasts, they'll likely try to get it. :o) > > > various applications (these are going to be workstations, not servers... > > accessed frequently by different users... stuff will get broken) > > You might be able to update your task packages and either come up with a > system to start upgrading of all machines or schedule them to run > apt-get update && apt-get -y dist-upgrade every 24 hours or so. I am not > sure how debconf can handle with sitewides defaults yet either, but I do > recall something being considered for this. > This is quite a good idea, I will need to become more versed in holding packages back, and the like, we'll be running X4.02 (or .03) and apt-get upgrade's off potato like to overwrite with X3.3, so I'll want to hold that back, stuff like that. > > -- > Jeremy Lunn > Melbourne, Australia > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Duane Powers Systems Engineer II -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
Duane, On Tue, 27 Mar 2001, Duane Powers wrote: > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) I modified the NetBSD boot floppy so it automatically uses the defaults (answers "yes"), uses DHCP (by default) and uses a local FTP server. (Right now it is two floppies, but after I remove some junk and reduce the kernel size it may fit on one.) Maybe you can modify a Linux boot floppy to do the same. > Most (of our) engineers are not linux-compliant. All that needs to be done with my boot is: 1) DHCP server setup for location; 2) DNS setup to provide correct info for the installs; 3) local ftp server setup with the base files; 4) one floppy put into machine, turn on, replace floppy when prompted and then press "Y" and enter to begin auto install; 5) repeat step three for each system. Putting the floppies into 30 computers will take about thirty minutes. The complete installation for all 30 computers will take 30 minutes (each) -- so all 30 computers will be installed within one hour. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) The base files on the FTP server can be modified for your particular needs -- so by default they can use some type of centralized authentication. Maybe there are some login (or PAM) routines that can use RADIUS or someother external authentication. Or maybe you can use a different NIS server for these? > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) If complete reinstall is needed, then simply put the auto-install disks in again. If just need to update an update (and using Debian), try using dpkg with the "--set-selections" option to set the package selections based on a prepared list. (Or point your apt sources.list to your own local Debian packages list and collection.) Jeremy C. Reed ... ISP-FAQ.com -- find answers to your questions http://www.isp-faq.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
What about VA System Imager (systemimager.sourceforge.net) ? We use it here for all our base installs - we adapt the servers with apt-get next. RSync shall also be useful - rsync -e ssh if you're on a hostile environment (and i believe we always are ...) On Wednesday 28 March 2001 07:58, Duane Powers wrote: > Ok all, > > I've talked upper management into rolling out linux as the primary > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? > > A couple of the parameters I need to consider, > > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) > > > Any helpful hints, or experience will be appreciated very much. > > Duane Powers > Senior Systems Engineer II -- Knowledge-sharing and open-source content : another way to gain eternity. Dexter - Linux system administrator http://lab.dexter.be - mailto : [EMAIL PROTECTED] - keep zen.
Re: "kickstart" for debian needed
On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers said: > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? I just got an UGLY idea... what about making a HUGE rpm with a complete Debian-install, with the configuration either as commands in the Deian-package (as little interactivity as possible) or as postinst-commands in the RPM-package or in the postinst-section of kickstart, and then install this debian-2.2.i386.rpm (etc) vai kickstart. Yes, this IS ugly, and I don't know if it will work. But it's dfinitely a dirty hack :) I have been working quite a lot with kickstart recently and it's a nice tool. The mkkickstart-command that comes with RH 6.2 is however useless and with lots of errors. Read the HOWTO instead. > Most (of our) engineers are not linux-compliant. Kickstart is not very easy to tweak, since the doc is poor, but if you understand the basics it's easy. Once it's set up, it requires no knowledge to use for installation and rather little knowledge to add packages etc. > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) Either don't give them root on their boxes - they and install on their homedirectories - or make sure they ONLY install stuff on /usr/local or something. Or reinstall every week, our reinstallation takes some 7 minutes (via NFS on a fast LAN) and requires one floppy (the green one). But those hints on kickstart are rather RedHat-specific. I wouldn't recommend someone porting kickstart to Debian. It sucks, some fighting makes it suck less, but it's still ugly. But Debian really needs something similar. For me Debian is my choice when it comes to my desktop PC or a single server, but when installing more than one server that should be identical, I need a kickstart tool and since Debian doesn't have it and RedHat does...well. Requirements: - simple and liberal configfile (i.e. no strict, or at least non-logical, requirements about the order in the config file) - installation methods: ftp, http, NFS (or doesn't Debian support that at all?), CD - network config: dhcp, static - no interactivity required, all info must/can be given in the configfile If someone are interested in making such a thing or if someone are actually working on it now, I'd be happy to know and maybe contribute (I don't program, but I think I may have some skills on other areas anyway :)) -- Magni Onsøien Initio IT-løsninger AS [EMAIL PROTECTED] http://www.initio.no/ Tlf. 73 83 71 71/928 10 269
Re: "kickstart" for debian needed
On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers wrote: > 30+ similar machines with debian, life sucks, eh? :o) > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? I am not sure how much of the base install could be automated. But have you thought of making a task package? That way you can keep the packages that are installed on each machine consistant. I'm not sure how task packages work or how you can make them, but I think it's as simple as depending on all the packages you need. > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) You might like to look into using LDAP for this. Another alternitive is using an SQL database. This issue is pretty flexiable considering there are many PAM modules and quite a few Name Service (libnss) modules. > May need to be reinstalled occassionally due to high tech network > engineers hosing You mean they'll have root access? If that is the case there is not much they can do. If that is the case though maybe they should be given machines with nothing on them to start with. Or ones that can be mucked up. If they don't have root access then I don't see it as a problem. > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) You might be able to update your task packages and either come up with a system to start upgrading of all machines or schedule them to run apt-get update && apt-get -y dist-upgrade every 24 hours or so. I am not sure how debconf can handle with sitewides defaults yet either, but I do recall something being considered for this. -- Jeremy Lunn Melbourne, Australia
Re: "kickstart" for debian needed
I agree that something like this is needed badly in Debian. However... considering there has been so much hassle over the boot floppies alone, i doubt there will be much chance a kickstart-like proggie will make it in. - Original Message - From: "Duane Powers" <[EMAIL PROTECTED]> To: Cc: <[EMAIL PROTECTED]> Sent: Wednesday, 28 March, 2001 1:58 PM Subject: "kickstart" for debian needed > Ok all, > > I've talked upper management into rolling out linux as the primary > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? > > A couple of the parameters I need to consider, > > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) > > > Any helpful hints, or experience will be appreciated very much. > > Duane Powers > Senior Systems Engineer II > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: "kickstart" for debian needed
What about VA System Imager (systemimager.sourceforge.net) ? We use it here for all our base installs - we adapt the servers with apt-get next. RSync shall also be useful - rsync -e ssh if you're on a hostile environment (and i believe we always are ...) On Wednesday 28 March 2001 07:58, Duane Powers wrote: > Ok all, > > I've talked upper management into rolling out linux as the primary > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? > > A couple of the parameters I need to consider, > > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) > > > Any helpful hints, or experience will be appreciated very much. > > Duane Powers > Senior Systems Engineer II -- Knowledge-sharing and open-source content : another way to gain eternity. Dexter - Linux system administrator http://lab.dexter.be - mailto : [EMAIL PROTECTED] - keep zen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers said: > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? I just got an UGLY idea... what about making a HUGE rpm with a complete Debian-install, with the configuration either as commands in the Deian-package (as little interactivity as possible) or as postinst-commands in the RPM-package or in the postinst-section of kickstart, and then install this debian-2.2.i386.rpm (etc) vai kickstart. Yes, this IS ugly, and I don't know if it will work. But it's dfinitely a dirty hack :) I have been working quite a lot with kickstart recently and it's a nice tool. The mkkickstart-command that comes with RH 6.2 is however useless and with lots of errors. Read the HOWTO instead. > Most (of our) engineers are not linux-compliant. Kickstart is not very easy to tweak, since the doc is poor, but if you understand the basics it's easy. Once it's set up, it requires no knowledge to use for installation and rather little knowledge to add packages etc. > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) Either don't give them root on their boxes - they and install on their homedirectories - or make sure they ONLY install stuff on /usr/local or something. Or reinstall every week, our reinstallation takes some 7 minutes (via NFS on a fast LAN) and requires one floppy (the green one). But those hints on kickstart are rather RedHat-specific. I wouldn't recommend someone porting kickstart to Debian. It sucks, some fighting makes it suck less, but it's still ugly. But Debian really needs something similar. For me Debian is my choice when it comes to my desktop PC or a single server, but when installing more than one server that should be identical, I need a kickstart tool and since Debian doesn't have it and RedHat does...well. Requirements: - simple and liberal configfile (i.e. no strict, or at least non-logical, requirements about the order in the config file) - installation methods: ftp, http, NFS (or doesn't Debian support that at all?), CD - network config: dhcp, static - no interactivity required, all info must/can be given in the configfile If someone are interested in making such a thing or if someone are actually working on it now, I'd be happy to know and maybe contribute (I don't program, but I think I may have some skills on other areas anyway :)) -- Magni Onsøien Initio IT-løsninger AS [EMAIL PROTECTED] http://www.initio.no/ Tlf. 73 83 71 71/928 10 269 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
On Tue, Mar 27, 2001 at 09:58:27PM -0800, Duane Powers wrote: > 30+ similar machines with debian, life sucks, eh? :o) > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? I am not sure how much of the base install could be automated. But have you thought of making a task package? That way you can keep the packages that are installed on each machine consistant. I'm not sure how task packages work or how you can make them, but I think it's as simple as depending on all the packages you need. > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) You might like to look into using LDAP for this. Another alternitive is using an SQL database. This issue is pretty flexiable considering there are many PAM modules and quite a few Name Service (libnss) modules. > May need to be reinstalled occassionally due to high tech network > engineers hosing You mean they'll have root access? If that is the case there is not much they can do. If that is the case though maybe they should be given machines with nothing on them to start with. Or ones that can be mucked up. If they don't have root access then I don't see it as a problem. > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) You might be able to update your task packages and either come up with a system to start upgrading of all machines or schedule them to run apt-get update && apt-get -y dist-upgrade every 24 hours or so. I am not sure how debconf can handle with sitewides defaults yet either, but I do recall something being considered for this. -- Jeremy Lunn Melbourne, Australia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "kickstart" for debian needed
I agree that something like this is needed badly in Debian. However... considering there has been so much hassle over the boot floppies alone, i doubt there will be much chance a kickstart-like proggie will make it in. - Original Message - From: "Duane Powers" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, 28 March, 2001 1:58 PM Subject: "kickstart" for debian needed > Ok all, > > I've talked upper management into rolling out linux as the primary > OS/workstation for the members of our NOC (we're a major ISP). Now I'm > faced with installing > 30+ similar machines with debian, life sucks, eh? :o) > I'm considering dd as one alternative, but that's kinda bulky 'cuz it > requires physically removing each hard drive installing in "parent" and > imaging... I've looked at things like > ghost, but that doesn't seem to be an option... I know we've had this > discussion on the list before... I don't know if anyone has the details > on redhat's kickstart program, > and whether that is something that could be ported to debian... Any > suggestions? > > A couple of the parameters I need to consider, > > Most (of our) engineers are not linux-compliant. > Need centralized login, (can't use NIS+, we've already got a NIS+ system > for Solaris... don't wanna confuse the issue,) > May need to be reinstalled occassionally due to high tech network > engineers hosing > various applications (these are going to be workstations, not servers... > accessed frequently by different users... stuff will get broken) > > > Any helpful hints, or experience will be appreciated very much. > > Duane Powers > Senior Systems Engineer II > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"kickstart" for debian needed
Ok all, I've talked upper management into rolling out linux as the primary OS/workstation for the members of our NOC (we're a major ISP). Now I'm faced with installing 30+ similar machines with debian, life sucks, eh? :o) I'm considering dd as one alternative, but that's kinda bulky 'cuz it requires physically removing each hard drive installing in "parent" and imaging... I've looked at things like ghost, but that doesn't seem to be an option... I know we've had this discussion on the list before... I don't know if anyone has the details on redhat's kickstart program, and whether that is something that could be ported to debian... Any suggestions? A couple of the parameters I need to consider, Most (of our) engineers are not linux-compliant. Need centralized login, (can't use NIS+, we've already got a NIS+ system for Solaris... don't wanna confuse the issue,) May need to be reinstalled occassionally due to high tech network engineers hosing various applications (these are going to be workstations, not servers... accessed frequently by different users... stuff will get broken) Any helpful hints, or experience will be appreciated very much. Duane Powers Senior Systems Engineer II
"kickstart" for debian needed
Ok all, I've talked upper management into rolling out linux as the primary OS/workstation for the members of our NOC (we're a major ISP). Now I'm faced with installing 30+ similar machines with debian, life sucks, eh? :o) I'm considering dd as one alternative, but that's kinda bulky 'cuz it requires physically removing each hard drive installing in "parent" and imaging... I've looked at things like ghost, but that doesn't seem to be an option... I know we've had this discussion on the list before... I don't know if anyone has the details on redhat's kickstart program, and whether that is something that could be ported to debian... Any suggestions? A couple of the parameters I need to consider, Most (of our) engineers are not linux-compliant. Need centralized login, (can't use NIS+, we've already got a NIS+ system for Solaris... don't wanna confuse the issue,) May need to be reinstalled occassionally due to high tech network engineers hosing various applications (these are going to be workstations, not servers... accessed frequently by different users... stuff will get broken) Any helpful hints, or experience will be appreciated very much. Duane Powers Senior Systems Engineer II -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
