You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: dann f. <da...@hp...> - 2004-03-29 18:17:08
|
On Mon, Mar 29, 2004 at 11:41:45AM -0600, Brian Elliott Finley wrote: > Cool! > > I think we should do a branch, and have a /stable manual that > auto-builds from the stable branch and an /unstable manual that > auto-builds from head. > > What think you? when we do a devel branch, yeah. right now, the manual is built from head. -- --------------------------- dann frazier Hewlett-Packard Linux and Open Source Lab da...@hp... (970) 898-0800 |
From: Brian E. F. <fi...@mc...> - 2004-03-29 17:41:49
|
Cool! I think we should do a branch, and have a /stable manual that auto-builds from the stable branch and an /unstable manual that auto-builds from head. What think you? Thus spake Dann Frazier (da...@hp...): >fyi, i've move the automatic manual generation code to a new machine and updated it >for version 3.2. > >Commit triggered builds of the documentation are published here: > http://www.systemimager.org/doc/html/ > http://www.systemimager.org/doc/systemimager-manual.pdf > >With a timestamped build log here: > http://www.systemimager.org/doc/build.log > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Sisuite-users mailing list >Sis...@li... >https://lists.sourceforge.net/lists/listinfo/sisuite-users > -- --------------------------------------------------------- Brian Elliott Finley Argonne, MCS Division Phone: 630.631.6621 http://thefinleys.com gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52 --------------------------------------------------------- |
From: dann f. <da...@hp...> - 2004-03-29 05:32:31
|
fyi, i've move the automatic manual generation code to a new machine and updated it for version 3.2. Commit triggered builds of the documentation are published here: http://www.systemimager.org/doc/html/ http://www.systemimager.org/doc/systemimager-manual.pdf With a timestamped build log here: http://www.systemimager.org/doc/build.log |
From: WALTERS,DENISE (HP-FtCollins,ex1) <den...@hp...> - 2003-07-28 20:34:25
|
Dann, Let me know when you have text so I can edit. Thanks, Denise > -----Original Message----- > From: dann frazier [mailto:da...@hp...] > Sent: Sunday, July 27, 2003 9:37 PM > To: WALTERS,DENISE (HP-FtCollins,ex1) > Cc: 'Brian Elliott Finley'; sis...@li...; Anton > Smith; SISuite Users > Subject: Re: [Sisuite-docs] Re: [Sisuite-users] Re: getting an image > throu gh SSH > > > On Fri, Jul 25, 2003 at 11:17:53AM -0400, WALTERS,DENISE > (HP-FtCollins,ex1) wrote: > > Brian and Dann, > > > > What timeframe are you looking at for incorporating > > the info in the manual so I can plan for time? > > well - i took a look at adding this stuff on the plane. problem is, > i've never set this up before, so i think someone else will need to > write this section. brian: if you can do it, that'd be cool. > if a user > wants to fill in the text, i'll volunteer to do the sgml conversion. > > i did do the stub, so i'll commit that as a placeholder. > |
From: dann f. <da...@hp...> - 2003-07-28 20:22:12
|
On Fri, Jul 25, 2003 at 10:10:52AM -0500, Brian Elliott Finley wrote: > This was a clever way to figure out how to do this, and I wonder if the > hosts allow and hosts deny options are something we should consider > adding to prepareclient. > > Dann, what do you think? prepareclient --server HOSTNAME (option to > add the host allow/deny params)? having an option that adds restriction options to the generated rsyncd.conf would make sense to me. |
From: dann f. <da...@hp...> - 2003-07-28 20:22:10
|
On Fri, Jul 25, 2003 at 11:17:53AM -0400, WALTERS,DENISE (HP-FtCollins,ex1) wrote: > Brian and Dann, > > What timeframe are you looking at for incorporating > the info in the manual so I can plan for time? well - i took a look at adding this stuff on the plane. problem is, i've never set this up before, so i think someone else will need to write this section. brian: if you can do it, that'd be cool. if a user wants to fill in the text, i'll volunteer to do the sgml conversion. i did do the stub, so i'll commit that as a placeholder. |
From: dann f. <da...@da...> - 2003-07-27 23:16:22
|
i've added sisuite-docs to the cc list - doc discussion at the end. On Wed, Jul 23, 2003 at 07:29:00AM -0700, Steve G wrote: ... > I've reached an uneasy truce with systemimager. I've had to > hack the install scripts because parted does not work for > me. My server is an athlon system and the target machines > are pentium based. Some how...some way, it pulls athlon > libraries across the network. The pentium machines croak. systemimager links the binaries it builds against libraries reduced from your building system. if your server has libaries optimized for a specific subarch, then your boel won't run on conflicting subarches. i build releases on debian, where this shouldn't be a problem. > So what I've done is create a bootable parted disk which > runs the parted commands and then I use another disk to do > the systemimager install. The next problem I run into is > that systemimager does not setup grub on the boot > partition. To get around this I use the following patch: ... make sure you're running the latest systemconfigurator. i know that the last couple releases have had plenty of grub fixes. > *Documentation > 1) no sample local.cfg. Book says its in /usr/share/doc. > Maybe the name in the book is wrong? the install_docs rule wasn't installing it - i've fixed it in my tree, so the debs will begin including it. the spec file will need to be updated too. > 2) Subjects need better organization. > 2.a)Chapter 2 should cover installation. For some reason > chapter 3 starts off by covering installation again, > even > though chapter 2 did this. Take the xtra words in > chapter 3 & put it in chapter 2. can you be more specific? i see that chapter 3 refers to chapter 2 in the intro, but otherwise describes the imaging processes. > 2.b) Chapter 3 would be better if its outline were this: > 3.0 Checking out your system after installation - go > over rsync, dhcp, tcp_wrappers, firewall, etc. > 3.1 Creating a golden image > 3.2 creating an autoinstall boot disk > 3.3 creating an autoinstall cd-rom > 3.4 setting up a Pxe based install > 3.5 loading an image onto target machine - this goes > over the steps to get it going for all 3 ways. > 3.6 updating a golden image > 3.7 client side initiated update > 3.8 server side initiated update > 3.9 removing or renaming images > 3.10 Building your own image - its in faq, but should > be in the main documentation right now, chapter 3 mostly consists of a step-by-step process, assuming a linear progression through the steps. switching to a more "goal-oriented" (as bdale would say) set of steps, which happen to be in a workable order, sounds like a better way of organizing it, and looks like what you are suggesting, at a high level. currently, i think we are lacking a reference quality. Denise: what do you think? |
From: WALTERS,DENISE (HP-FtCollins,ex1) <den...@hp...> - 2003-07-25 15:18:05
|
Brian and Dann, What timeframe are you looking at for incorporating the info in the manual so I can plan for time? Thanks, Denise > -----Original Message----- > From: Brian Elliott Finley [mailto:br...@bg...] > Sent: Friday, July 25, 2003 9:11 AM > To: dann frazier > Cc: sis...@li...; br...@bg...; Anton Smith; > SISuite Users > Subject: [Sisuite-docs] Re: [Sisuite-users] Re: getting an > image through > SSH > > > Thus spake dann frazier (da...@de...): > > There is definitely a lacking of ssh information in the manual, so > > how about I add this in the Usage chapter, in its own section? > > Yes, yes, yes! > > I really like going in the direction similar to the Flamethrower > chapter. Something like "HOWTO Use SSH for Secure Installs". > > > Brian: is what Anton describes currently the recommended procedure? > > > > On Thu, Jul 17, 2003 at 11:22:41PM +1200, Anton Smith wrote: > > > Solved this for myself, and thought I'd post it here for > everyone else. > > > > > > (just a reminder, this is for pulling images across to > your server via ssh). > > > > > > 1) run prepareclient on your goldenclient as you usually do. > > Yes. > > > > Immediately after it starts, ps -ef | grep for rsync and > kill the daemon it started. Take note of the config file it > used, most likely it will be in /tmp. > > > 2) edit the rsync config file from above, and under > [root], change it so it looks like this: > > > > > > auth users root > > > path = / > > > hosts allow = clientsiphere > > > hosts deny = * > > > > > > This locks it down so that only root can log in and so > that the only host that can connect is the client itself (we > will be ssh tunneling so the packets will appear to come from > the client itself, which is why this works). > > > > > > 3) run "rsync --daemon --config-file > /tmp/rsyncd.conf.xxxxx". Tail /var/log/syslog to make sure > the daemon came up okay and didn't complain about any of your > new config changes (if it ignores any of your security lines > then it will be listening for any host, which is a bad [tm] thing). > > This is not the intended use, but certainly you could do it this way. > It is assumed that the client is firewalling everything but ssh to > itself. Running the rsync daemon wide open is ok in this > case, assuming > that there are no malicious local users on the golden client. > > When you rung getimage, use the --ssh-user option, and the > image will be > retrieved using rsync over ssh. > > > > All of the following is on your image server: > > > > > > 4) Bring up the ssh tunnel: ssh -C -L > localport:goldenclients_ip:873 root@goldenclients_ip and > enter the root password. > > > 5) Switch to another terminal on your imageserver (make > sure you leave the ssh session you opened in step 4 open), > and run getimage -golden-client localhost:localport -image > imagename (make sure you use the same value for localport > here as you did in step 4. It can be any port but ideally > should be an ephemereal and not already in use. As an example > I use 15000 but you could use whatever you like). > > > 6) From here, it should be just like a normal getimage. > When its all finished you can log out of your ssh > session/tunnel, and you can also kill the rsync daemon on > your golden client. > > All of the above is handled for you by getimage if you use the > --ssh-user option. Also look at the details at the bottom of the > local.cfg file for autoinstall related details. > > Anton, > > This was a clever way to figure out how to do this, and I > wonder if the > hosts allow and hosts deny options are something we should consider > adding to prepareclient. > > Dann, what do you think? prepareclient --server HOSTNAME (option to > add the host allow/deny params)? > > Also, Anton, can we put you down as an OFFICIAL_TESTER? And > have you do > the ssh testing when we do new releases? > > Cheers, -Brian > > > > > > > > Voila :) > > > > > > Regards, > > > Anton > > > > > > > > -- > --------------------------------------------------------- > Brian Elliott Finley Phone: 630.803.8183 > GPG: 3FF8 D096 0E0C D3F3 29B7 6518 D20B 1931 10F8 EE52 > --------------------------------------------------------- > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet _072303_01/01 _______________________________________________ Sisuite-docs mailing list Sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-docs |
From: Brian E. F. <br...@bg...> - 2003-07-25 15:12:30
|
Thus spake dann frazier (da...@de...): > There is definitely a lacking of ssh information in the manual, so > how about I add this in the Usage chapter, in its own section? Yes, yes, yes! I really like going in the direction similar to the Flamethrower chapter. Something like "HOWTO Use SSH for Secure Installs". > Brian: is what Anton describes currently the recommended procedure? > > On Thu, Jul 17, 2003 at 11:22:41PM +1200, Anton Smith wrote: > > Solved this for myself, and thought I'd post it here for everyone else. > > > > (just a reminder, this is for pulling images across to your server via ssh). > > > > 1) run prepareclient on your goldenclient as you usually do. Yes. > Immediately after it starts, ps -ef | grep for rsync and kill the daemon it started. Take note of the config file it used, most likely it will be in /tmp. > > 2) edit the rsync config file from above, and under [root], change it so it looks like this: > > > > auth users root > > path = / > > hosts allow = clientsiphere > > hosts deny = * > > > > This locks it down so that only root can log in and so that the only host that can connect is the client itself (we will be ssh tunneling so the packets will appear to come from the client itself, which is why this works). > > > > 3) run "rsync --daemon --config-file /tmp/rsyncd.conf.xxxxx". Tail /var/log/syslog to make sure the daemon came up okay and didn't complain about any of your new config changes (if it ignores any of your security lines then it will be listening for any host, which is a bad [tm] thing). This is not the intended use, but certainly you could do it this way. It is assumed that the client is firewalling everything but ssh to itself. Running the rsync daemon wide open is ok in this case, assuming that there are no malicious local users on the golden client. When you rung getimage, use the --ssh-user option, and the image will be retrieved using rsync over ssh. > > All of the following is on your image server: > > > > 4) Bring up the ssh tunnel: ssh -C -L localport:goldenclients_ip:873 root@goldenclients_ip and enter the root password. > > 5) Switch to another terminal on your imageserver (make sure you leave the ssh session you opened in step 4 open), and run getimage -golden-client localhost:localport -image imagename (make sure you use the same value for localport here as you did in step 4. It can be any port but ideally should be an ephemereal and not already in use. As an example I use 15000 but you could use whatever you like). > > 6) From here, it should be just like a normal getimage. When its all finished you can log out of your ssh session/tunnel, and you can also kill the rsync daemon on your golden client. All of the above is handled for you by getimage if you use the --ssh-user option. Also look at the details at the bottom of the local.cfg file for autoinstall related details. Anton, This was a clever way to figure out how to do this, and I wonder if the hosts allow and hosts deny options are something we should consider adding to prepareclient. Dann, what do you think? prepareclient --server HOSTNAME (option to add the host allow/deny params)? Also, Anton, can we put you down as an OFFICIAL_TESTER? And have you do the ssh testing when we do new releases? Cheers, -Brian > > > > Voila :) > > > > Regards, > > Anton > > > > -- --------------------------------------------------------- Brian Elliott Finley Phone: 630.803.8183 GPG: 3FF8 D096 0E0C D3F3 29B7 6518 D20B 1931 10F8 EE52 --------------------------------------------------------- |
From: dann f. <da...@de...> - 2003-07-20 22:10:50
|
There is definitely a lacking of ssh information in the manual, so how about I add this in the Usage chapter, in its own section? Brian: is what Anton describes currently the recommended procedure? On Thu, Jul 17, 2003 at 11:22:41PM +1200, Anton Smith wrote: > Solved this for myself, and thought I'd post it here for everyone else. > > (just a reminder, this is for pulling images across to your server via ssh). > > 1) run prepareclient on your goldenclient as you usually do. Immediately after it starts, ps -ef | grep for rsync and kill the daemon it started. Take note of the config file it used, most likely it will be in /tmp. > 2) edit the rsync config file from above, and under [root], change it so it looks like this: > > auth users root > path = / > hosts allow = clientsiphere > hosts deny = * > > This locks it down so that only root can log in and so that the only host that can connect is the client itself (we will be ssh tunneling so the packets will appear to come from the client itself, which is why this works). > > 3) run "rsync --daemon --config-file /tmp/rsyncd.conf.xxxxx". Tail /var/log/syslog to make sure the daemon came up okay and didn't complain about any of your new config changes (if it ignores any of your security lines then it will be listening for any host, which is a bad [tm] thing). > > All of the following is on your image server: > > 4) Bring up the ssh tunnel: ssh -C -L localport:goldenclients_ip:873 root@goldenclients_ip and enter the root password. > 5) Switch to another terminal on your imageserver (make sure you leave the ssh session you opened in step 4 open), and run getimage -golden-client localhost:localport -image imagename (make sure you use the same value for localport here as you did in step 4. It can be any port but ideally should be an ephemereal and not already in use. As an example I use 15000 but you could use whatever you like). > 6) From here, it should be just like a normal getimage. When its all finished you can log out of your ssh session/tunnel, and you can also kill the rsync daemon on your golden client. > > Voila :) > > Regards, > Anton > > |
From: <da...@da...> - 2003-02-11 23:40:24
|
at long last we now have the systemimager manual autopublished to the web from cvs (on commit). i'm going to wait a few days before asking brian to switch over the link on the website, to work out any robustness issues. http://www.systemimager.org/doc/html/ http://www.systemimager.org/doc/systemimager-manual.pdf you can visit http://www.systemimager.org/doc/build.log to see a log of the build/upload process. |
From: <da...@ld...> - 2002-06-26 14:13:28
|
[i removed si-devel from the cc list since it will hit most people twice] it work fine. more detail: i have a fake user subscribed to the cvs commits list. when it recieves a message, it triggers a cvs update & a make. if the commit had nothing to do with the docs, the make should do nothing. it also does some simplistic locking to prevent a new commit from screwing with a in-process make. On Tue, Jun 25, 2002 at 07:34:11PM -0500, Brian Finley wrote: > Ok, > > So in 3 words or less, how does your system work? > > -Brian > > > > On Tue, 2002-06-25 at 13:39, dann frazier wrote: > > this would be rather difficult, sense the sf machines don't have > > the proper build-dependencies. we could have a cron job that just > > mirrors the bits from another machine, or just links directly to > > another machine. > > > > On Mon, Jun 24, 2002 at 03:23:06PM -0500, Brian Finley wrote: > > > I like this idea, Dann. What does it take for you to get this up and > > > running in http://systemimager.org/manual/html/ ? > > > > > > -Brian > > > > > > > > > > > > On Sun, 2002-06-23 at 23:20, dann frazier wrote: > > > > hey, > > > > i've implemented a system to autobuild the manual upon commit. > > > > i'd like to suggest that we have at least 2 manuals online at any > > > > given time - one for the top of the stable branch, and one for the > > > > top of branch for the next stable series. the manual is a more > > > > fluid document then the code of a release, and it's content is > > > > often driven by issues that occur after release. > > > > > > > > This can allow changes to the manual to be immediately viewable by > > > > users, and will hopefully reduce a number of FAQs. > > > > > > > > Right now, I'm just auto-updating html & pdfs for the manual in the > > > > unstable-2_1_x branch. > > > > > > > > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/html/ > > > > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/systemimager-manual.pdf > > > > > > > > -- > > > > da...@da... > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: Jabber Inc. > > Don't miss the IM event of the season | Special offer for OSDN members! > > JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn > > _______________________________________________ > > SystemImager-devel mailing list > > Sys...@li... > > https://lists.sourceforge.net/lists/listinfo/systemimager-devel > > > -- > --------------------------------------------------- > Brian Elliott Finley http://baldguysoftware.com/ > phone: 214.280.8188 http://systemimager.org/ > --------------------------------------------------- > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber Inc. > Don't miss the IM event of the season | Special offer for OSDN members! > JabConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn > _______________________________________________ > Sisuite-docs mailing list > Sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-docs -- --------------------------- dann frazier Hewlett-Packard Linux Development Lab da...@ld... (970) 898-0800 |
From: <da...@da...> - 2002-06-25 18:39:11
|
this would be rather difficult, sense the sf machines don't have the proper build-dependencies. we could have a cron job that just mirrors the bits from another machine, or just links directly to another machine. On Mon, Jun 24, 2002 at 03:23:06PM -0500, Brian Finley wrote: > I like this idea, Dann. What does it take for you to get this up and > running in http://systemimager.org/manual/html/ ? > > -Brian > > > > On Sun, 2002-06-23 at 23:20, dann frazier wrote: > > hey, > > i've implemented a system to autobuild the manual upon commit. > > i'd like to suggest that we have at least 2 manuals online at any > > given time - one for the top of the stable branch, and one for the > > top of branch for the next stable series. the manual is a more > > fluid document then the code of a release, and it's content is > > often driven by issues that occur after release. > > > > This can allow changes to the manual to be immediately viewable by > > users, and will hopefully reduce a number of FAQs. > > > > Right now, I'm just auto-updating html & pdfs for the manual in the > > unstable-2_1_x branch. > > > > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/html/ > > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/systemimager-manual.pdf > > -- da...@da... |
From: Brian F. <bri...@ba...> - 2002-06-24 20:22:42
|
I like this idea, Dann. What does it take for you to get this up and running in http://systemimager.org/manual/html/ ? -Brian On Sun, 2002-06-23 at 23:20, dann frazier wrote: > hey, > i've implemented a system to autobuild the manual upon commit. > i'd like to suggest that we have at least 2 manuals online at any > given time - one for the top of the stable branch, and one for the > top of branch for the next stable series. the manual is a more > fluid document then the code of a release, and it's content is > often driven by issues that occur after release. > > This can allow changes to the manual to be immediately viewable by > users, and will hopefully reduce a number of FAQs. > > Right now, I'm just auto-updating html & pdfs for the manual in the > unstable-2_1_x branch. > > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/html/ > http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/systemimager-manual.pdf > > -- > > da...@da... > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > SystemImager-devel mailing list > Sys...@li... > https://lists.sourceforge.net/lists/listinfo/systemimager-devel > -- --------------------------------------------------- Brian Elliott Finley http://baldguysoftware.com/ phone: 214.280.8188 http://systemimager.org/ --------------------------------------------------- |
From: <da...@da...> - 2002-06-24 04:20:36
|
hey, i've implemented a system to autobuild the manual upon commit. i'd like to suggest that we have at least 2 manuals online at any given time - one for the top of the stable branch, and one for the top of branch for the next stable series. the manual is a more fluid document then the code of a release, and it's content is often driven by issues that occur after release. This can allow changes to the manual to be immediately viewable by users, and will hopefully reduce a number of FAQs. Right now, I'm just auto-updating html & pdfs for the manual in the unstable-2_1_x branch. http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/html/ http://home.dannf.org/~dannf/si-doc-autobuild/manual_source/systemimager-manual.pdf -- da...@da... |
From: <da...@da...> - 2002-04-26 23:42:16
|
hey, I committed Denise's latest changes after our meeting yesterday. Please take the time to review the document (I also need to read through it). Denise has asked that any changes to the first few chapters go through her. The FAQ/Troubleshooting sections are more technical in nature, so committing changes directly is ok. Denise is subscribed to the sisuite-docs list, so this is a good place for comments / additions to be sent. Thanks Denise! On Fri, Apr 26, 2002 at 05:00:35PM -0500, Brian Finley wrote: > Thanks, man. > > > On Thu, 2002-04-25 at 14:58, dann wrote: > > Denise has already gone through a few revisions. > > I'm meeting with her this afternoon, in fact, to discuss it - I'll update you > > then. > > > > On Thu, Apr 25, 2002 at 10:15:54AM -0500, Brian Finley wrote: > > > Dann, > > > > > > What is the ETA for having the new documentation in standard HOWTO > > > format? I'd like to start answering some of the questions we're getting > > > by updating the FAQ section, and pointing the users there. > > > > > > -Brian > > > > > > > > > > > -- da...@da... |