• Download
  • Dream page
  • [STYLE]
  • Do we get to the other side?

    *cough* *cough* *cough*

    We are experiencing troubles with|in a|the tube(s). Please help us diagnosis this issue by verifying https://dave.thehorners.com/ is responding and displaying properly for you on your device. At this time, the main host is still

    OPERATIONAL,

    https cert is NOT locked on either http(s)! disturbance in the force. USE AT YOUR OWN RISK!

    it should work but lock may not show green and secure; that is expected. If you can't get to secure sites, please use http://dave.thehorners.com/. If your ISP has restrictions to certain sites, consider another provider or another VPN. Life is too short and precious to be controlled and manipulated. I pray for ALL those people who are endure under censor and control; This is the Land of the Free and the Home of The Brave....the always on always connected multi-verse Internet right?! What's your locale like? I hope it's not oppressive. See here, a beautiful view from satellite(s) below. God Speed; and Good Luck.

    .

    Ppl of the Internet. Right now, dave.thehorners.com is unavailable on the *[LTE AT&T network] (outage has been persistent for a long while; last personal report to ATT with no response 11/11/2018)

    I don' t know if it is an outage or what; but please do a tracert from your device and request access to dave.thehorners.com if it doesn't route from your ISP (at this time I only KNOW that LTE ATT is affected if you find otherwise, please post proof in deepdream. I was told 24 hours; but that was days and days ago. I would be interested in the help...frustrating figuring out a routing|sensor|censor problem. I will remove this message from my site when LTE is routing again from my phone. [DOWN NETWORK QUICK ACCESS NOTES] AT&T LTE - Customer service: 1 (800) 331-0500
    Pardon|Thank you|Merci|Gracias


    My current preferred deep dream site(s) are: fibFile dave.thehorners.com My last 3 deep dreams were:(b0caa;5141d;bcab1) the current time is 11/17/2018 at 01:56
    https://q4j2g5j9.stackpathcdn.com/ddg-dream/a9f99e2f09d974fdfc36e91384e18e453e9b0caa.jpg - AT&T
    https://q4j2g5j9.stackpathcdn.com/ddg-dream/01cce5bee4c316e5ae8e1a4f53957b527525141d.jpg
    https://q4j2g5j9.stackpathcdn.com/ddg-dream/70cebfdbcdeb8c09a0d9076a5c669d735cbbcab1.jpg


    If you are reading these bytes and you didn't have to hop around N+1 nodes to anon and make things confusing.....CONGRATULATIONS you're blessed to be free. Thank|Pardon|Garcias someone. It didn't happen by itself.
    and now back to the strange loop perspective of just another.

    Dave Horner's Website - Yet another perspective on things...
    Home Tech Talk Programming CVS - adminstration and usage
    76 guests
    Rough Hits : 3551972
    moon and stars
    how did u find my site?





     
    consciousness survives death of brain?



     
    RIF [Reading is Fun-duh-mental] but TLDR [Too long; didn't read]
    1=0.999...

    CVS - adminstration and usage

    Saturday, 26 March 2005 11:46
    CVS

    To start a repository, a suitable directory on the server machine must be initiated. To initiate, run:
    #cvs -d /var/cvs init
    This will create a directory CVSROOT under /var/cvs.


    By default, CVS adds new files to the repository under the default group of the user performing the addition. But in multi-group repositories, this leads to CVS additions that are not readable by other developers. Fortunately CVS makes it easy to automate associating the new file with the proper group for the project. Edit the file /var/cvs/CVSROOT/loginfo:

    Add the following lines to the bottom of the file:
    module  (chgrp -Rf groupname $CVSROOT/module)
    module  (chmod -Rf u+rw,g+rw,o= $CVSROOT/module)
    Save the file and exit.
    This will make sure any additions to the CVS repository will be automatically associated with the project's default group and permissions of user & group read/write, other with no perms.

    Often what I do is add the following in one line:
    modulename (somecmds;chgrp -Rf groupname $CVSROOT/modulename;chmod -Rf u+rw,g+rw,o-rwx $CVSROOT/modulename;)
    This runs somecmds and then changes the group and read permissions for the whole tree.

    When you setup a repository, you will want to control access by group (add a group for all the developers and remove writable/readable by others).  When users do checkins and checkouts, do a newgrp to change the effective group.  This will make sure that all new files created will be accessable to the other developers in the cvs group. To find out what groups you have membership to run groups.

    Another thing you might want to do is: umask 007  (this will replace any existing umask). This will make all new files with user and group read/write but others have no permission.

    To tag the current module use the following:
    cvs tag -cR TAGNAME
    This tells cvs to tag the module, making sure that working files are unmodified from the repository, and recursively down the tree.

    To pull a tagged release use the following:
    cvs update -r TAGNAME


    When adding binary files under CVS use the cvs admin -kb to set the binary flag.
    This issue is transparent unless you checkout to a windows machine.

    Keyword List
    ============
    This is a list of the keywords:
    `$Author$' - The login name of the user who checked in the revision.
     `$Date$' - The date and time (UTC) the revision was checked in.
    `$Header$' -  A standard head
    `$Id$' -  Same as `$Header$', except that the RCS filename is without a path.
     `$Name$' -  Tag name used to check out this file. The keyword is expanded only if one checks out with an explicit tag name.
    `$Locker$' - The login name of the user who locked the revision.
    `$Log$' -  The log message supplied during commit, preceded by a header containing the RCS filename, the revision number, the author, and  the date (UTC).
     `$RCSfile$' -  The name of the RCS file without a path.
     `$Revision$' -  The revision number assigned to the revision.
     `$Source$' -  The full pathname of the RCS file.

    The file commitinfo contains a list of pre-commit programs.
    The file loginfo file contains a list of post-commit programs.
    When you want your pre/post commit programs to reside in the CVSROOT folder, you need to add them in the checkoutlist file.

    You can setup email notifications when commits are done using the wonderful program CVSSPAM
    A good article on CVS automation: Pragmatic CVS
    Multi-Group CVS Administration HOWTO


    < Prev  Next >
    Last Updated on Friday, 04 July 2014 15:43