Well, as always, you raise wonderful points......... Just got through working in my yard for the last 4 hours......attempting to rehydrate myself......but once that task it taken care of I may go ahead and type up the document. It is currently in the really, really rough.....written down on paper faze.
One question .......during my installation of flowscan and the other software compenent that were needed......I logged in as root for most of the software install (except for flowscan itself which warns NOT to do the ./configure make make install thing as root but rather and the user that is created to run the package) but later I found that I have to do the chown -R thingy on several directories and on some files so that the flowscan app could create logs, locks, etc as it needed. I pretty much used trial and error and came up with something that worked however, if there is an easier, better way then I would prefer to do it that way. What originally happened was that I tried to install all components as the "flowscan" user that I created but found that this user did not have sufficient rights to install things were they wanted to go....so I would become root but then later the flowscan user needed to update create or append to already created files but did not have sufficient rights to update the files and directories so I had to give the flowscan user ownership of those files, etc. This is an example of where "all the other documentation" is lacking....no mention is made of who should install what where.....ie. it is gear toward someone who knows what they are doing. Is it more correct to provide a group with rights to certain files and directories and then to add my flowscan user to that group? I definitely have one way to make this thing work......but I don't want my document to be giving bad habits to the readers. Especially, since one of the main points of this document is to provide a way for non-linux professionals with a way to get their feet wet and feel like they've accomplished something useful; rather than feeling discouraged and running back to the other environment. cha John Hebert wrote: >Good question. There should be a "SourceForge"-like >site for free documentation. > >I guess if it is in the same formats as the HOWTOs, >you could put it on tldp.org, but that means you would >have to do a little more work. You would learn a lot >about document formatting though. > >There must be plenty of places to put docs like this. >If anything, submit it as an article to a few Linux >news sites and see what they say. Or, at the least, >why not brlug.net? No insult intended, but I don't >think the traffic generated would break Dustin's >budget for hosting it. > >John Hebert > >--- Cleve Allison <[EMAIL PROTECTED]> wrote: > > >>I'm going to contact the guys whose instructions >>were most useful and >>hopefully enter into a light discussion about this >>topic but have a >>couple of questions and I'm interested in your >>opinions and input. >>The instructions that I used to set up Flowscan were >>very general and >>broad so as to be useful to as many different people >>and distributions >>as possible......a good thing IMHO, however the >>instructions that I want >>to write will be very specific. >>I will detail exactly which distribution/version I >>used for OS and all >>software packages. The reason I'm doing this is >>that my document is >>geered toward non-linux professionals that would >>like to use the tool >>but don't know how to get there. >>This being the case, I would like to put it on a >>website and leave it >>there......I have no problem with testing and >>updating the document for >>all major releases of the software and OS that I >>will be using as I will >>be testing the new platforms anyway....and the hard >>part is doing it the >>first time and writing the first document. Now, I >>have a domain already >>cleve.allison.name however I really don't want >>public stuff associated >>with a domain named for me. Are there domains that >>invite community >>contributed documents like this, where I could place >>this instruction >>manual? >> >>cha >> >>-- >>Insert really cool quote here. >> >> >>_______________________________________________ >>General mailing list >>[email protected] >>http://brlug.net/mailman/listinfo/general_brlug.net >> >> > > >__________________________________ >Do you Yahoo!? >Yahoo! Finance Tax Center - File online. File on time. >http://taxes.yahoo.com/filing.html > >_______________________________________________ >General mailing list >[email protected] >http://brlug.net/mailman/listinfo/general_brlug.net > > > -- When a distinguished but elderly scientist states that something is possible, he is almost certainly right. When he states that something is impossible, he is very probably wrong. Arthur C. Clarke, Profiles of the Future, 1962
