Monday, March 2, 2020
Library - in a Temperature Controlled Storage Unit
Black Earth, Wisconsin 53515.
I go by twice a day on my way to and from work, so it is extremely easy to pick up or drop off a book. There is 24-hour a day access, and I am able to park right next to the door for easy loading and unloading. There is a gas station right next door, so it is also conveniently when I have to fill-up my car. I should have thought of this a long time ago.
I am able to rotate books from storage to my home book shelves depending on my projects and the season. It is almost time for me to rotate gardening and travel books back home to prepare for spring.
Wednesday, January 17, 2018
macOS High Sierra remote reboot encrypted drive
When you reboot a macOS computer with an encrypted drive, you must login to unlock the volume before the boot process can complete. This creates a problem if you are working remotely.
The solution is to add a key temporarily in memory to make it through the reboot process.
Is FileVault on? If off, you don’t have to do any of this.
$ sudo fdesetup status
FileVault is On.
Does your hardware support authrestart? If not, this doesn’t help.
$ fdesetup supportsauthrestart
true
Turn on authrestart, but don’t reboot yet.
$ sudo fdesetup authrestart -delayminutes -1
The old prompt wants a recover key or an admin password? confusing question. This was changed in the current OS to ask for a username of a user who is authorized to unlock the drive.
Enter a password for '/', or the recovery key: # enter the admin password, or the internal drive key
The new version asks for a username and then a password
$ sudo fdesetup authrestart -delayminutes -1
Password:
Enter the user name:support
Enter the password for user 'support':
other useful commands
list of users who are able to unlock a FileVault volume.
$ sudo fdesetup list
Wednesday, November 22, 2017
Friday, May 10, 2013
MarsEdit Blogger Software for OS X
Testing MarsEdit to see if it will make it easier to post to this blog.
Monday, August 1, 2011
OSX Lion
Instructions to change this behavior
http://gregferro.com/osx-lion-library-folder-not-visible/
Open the Terminal and type:
chflags nohidden /Users/[username]/Library/
Wednesday, July 6, 2011
gitosis
http://sitaramc.github.com/gitolite/doc/1-INSTALL.html
back on the gitolite track
as root do the following:
root method
On your workstation:
copy your ~/.ssh/id_rsa.pub file to /tmp/YourName.pub on the server
On your server, as root:
git clone git://github.com/sitaramc/gitolite
cd gitolite
src/gl-system-install
# defaults to being the same as:
# src/gl-system-install /usr/local/bin /usr/local/share/gitolite/conf /usr/local/share/gitolite/hooks
# to upgrade gitolite, repeat the above commands. Make sure you use the
# same arguments for the last command each time.
# create your "hosting user" if not already created
useradd git
su - git
# (now as git)
gl-setup /tmp/YourName.pub
On your workstation:
git clone git@server:gitolite-admin
Note: things to look for:
The git user has to have ssh login ability, you may have to turn that on in the GUI, system preferences --> Sharing remote access
had to add a file for the git user:
.bashrc
containing:
$ cat .bashrc
export PATH=:/usr/bin:/usr/local/bin:$PATH:
#export PATH=$(git --exec-path):$PATH
export GIT_EXEC_PATH=/usr/libexec/git-core
# get the path with $ git --exec-path
6July2011
needed help from this source too
http://www.justlogged.com/Question/1/5041067/4e549dc7aa65302b9e71c9941b815058/show
ran the following command (running google's binary install of git:
$ git --exec-path
/usr/libexec/git-core
my .bashrc file now looks like this
$ cat .bashrc
export PATH=:/usr/bin:/usr/local/bin:$PATH:
#export PATH=$(git --exec-path):$PATH
export GIT_EXEC_PATH=/usr/libexec/git-core
also important, I used the GUI in Snow Leopard 10.6.8 to create the git user. The git user is not an administrator, therefore they were blocked from ssh, I had to manually add them to the users who could ssh in system preferences sharing.
instructions that worked from this source
http://lukhnos.org/blog/en/archives/162
- create in system preferences a user git, make the user an admin for a short while, undo this later
- create a group git, and add the user to the group
- for convenience, I also created a gitosisadmin admin user. (why? was this needed? perhaps to avoid making the git user admin and then removing it requiring a reboot.)
login as the gitosisadmin user and download gitosis.
ssh -l gitosisadmin localhost
$ which python
/usr/bin/python
$ which git
/usr/bin/git
$ pwd
/Users/gitosisadmin
$ git clone git://eagain.net/gitosis.git
$ cd gitosis/
$ sudo python setup.py install
create key if you don't have one
ssh-keygen -t rsa
copy key to a temp location so git user can read it
cp ~/.ssh/id_rsa.pub /tmp/my_key.pub
$ sudo -H -u git gitosis-init < /tmp/eabolden.pub Initialized empty Git repository in /Users/git/repositories/gitosis-admin.git/ Reinitialized existing Git repository in /Users/git/repositories/gitosis-admin.git/
may need this:
make sure post update hook is executable.
sudo chmod 755 /Users/git/repositories/gitosis-admin.git/hookspost-update
from a different account clone the admin repository
$ git clone git@your.server.com:gitosis-admin.git
Cloning into gitosis-admin...
bash: gitosis-serve: command not found
fatal: The remote end hung up unexpectedly
tried reinstalling...
saw this error:
Searching for setuptools==0.6c12dev-r85381
Reading http://pypi.python.org/simple/setuptools/
Reading http://peak.telecommunity.com/snapshots/
No local packages or download links found for setuptools==0.6c12dev-r85381
error: Could not find suitable distribution for Requirement.parse('setuptools==0.6c12dev-r85381')
used solution from: http://www.errorhelp.com/search/details/74034/importerror-no-module-named-setuptools
wget http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c11.tar.gz
$ tar xfvz setuptools-0.6c11.tar.gz
$ cd setuptools-0.6c11
python setup.py build
sudo python setup.py install
Notes
The following can be done with the osx gui
list users and uid
$ sudo dscl . list /Users kid
list groups and group id
$ sudo dscl . list groups did
delete user username
$ sudo dscl . -delete /Users/username
delete group groupname
$ sudo dscl . -delete /groups/groupname
manually create group commandline
sudo dscl . create groups/git
sudo dscl . create groups/git did 401
manually create user commandline
sudo dscl . create users/git
sudo dscl . create users/git uid 401
sudo dscl . create users/git NFSHomeDirectory /Users/git
sudo dscl . create users/git gid 401
sudo dscl . create users/git UserShell /bin/bash
sudo dscl . create users/git Password '*'
create home directory
sudo mkdir /Users/git
sudo chown git /Users/git
sudo chgrp git /Users/git
********************
not sure if this next part is necessary
$ cat .bashrc
#export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin:$PATH
export PATH=/usr/local/bin:/usr/local/git/bin:$PATH
wget http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c8.tar.gz#md5=0e9bbe1466f3ee29588cc09d3211a010 tar xfvz setuptools-0.6c8.tar.gz cd setuptools-0.6c8 python setup.py build sudo python setup.py install
OLD Tries side note, gitolite next try use from here: https://github.com/sitaramc/gitolite/blob/pu/doc/1-INSTALL.mkd sudo /usr/bin/python setup.py install had the following error: ImportError: No module named setup tools used solution from: http://www.errorhelp.com/search/details/74034/importerror-no-module-named-setuptools wget wget http://pypi.python.org/packages/source/s/setuptools/setuptools-0.6c8.tar.gz#md5=0e9bbe1466f3ee29588cc09d3211a010 tar xfvz setuptools-0.6c8.tar.gz cd setuptools-0.6c8 python setup.py build sudo python setup.py install
Notes The following can be done with the osx gui list users and uid $ sudo dscl . list /Users kid list groups and group id $ sudo dscl . list groups did delete user username $ sudo dscl . -delete /Users/username delete group groupname $ sudo dscl . -delete /groups/groupname manually create group commandline sudo dscl . create groups/git sudo dscl . create groups/git did 401 manually create user commandline sudo dscl . create users/git sudo dscl . create users/git uid 401 sudo dscl . create users/git NFSHomeDirectory /Users/git sudo dscl . create users/git gid 401 sudo dscl . create users/git UserShell /bin/bash sudo dscl . create users/git Password '*' create home directory sudo mkdir /Users/git sudo chown git /Users/git sudo chgrp git /Users/git
installing Chilliproject offshoot of Redmine
https://www.chiliproject.org/projects/chiliproject/wiki/Installation
needed to update to a specific version of rails
$ sudo gem update rails --version='2.3.12'
get a copy of ChiliProject
git clone git://github.com/chiliproject/chiliproject.git
cd chiliproject
git checkout stable
After getting the code, needed to install supporting gems using the following, after installing postgressql83 with macports, could have avoided some of this, by specifying I was not using postgressql.
$ sudo port install postgresql83
$ env ARCHFLAGS="-arch x86_64" bundle install
other notes:
$ sudo port install postgresql83
http://www.icoretech.org/2009/08/how-to-install-pg-postgresql-gem-on-snow-leopard-64-bit/
Install PostgreSQL from source/port for this, does not currently build against binary package.
PATH should be /usr/local/pgsql.
export PATH=/usr/local/pgsql/bin:${PATH}
env ARCHFLAGS="-arch x86_64" gem install pg
Or if you are using macports:
export PATH=/opt/local/lib/postgresql83/bin:${PATH}
env ARCHFLAGS="-arch x86_64" gem install pg
$ sudo gem install rmagick
Password:
Fetching: rmagick-2.13.1.gem (100%)
Building native extensions. This could take a while...
Successfully installed rmagick-2.13.1
1 gem installed
Installing ri documentation for rmagick-2.13.1...
Installing RDoc documentation for rmagick-2.13.1...
~ $ irb -rubygems -r RMagick
>> puts Magick::Long_version
This is RMagick 2.13.1 ($Date: 2009/12/20 02:33:33 $) Copyright (C) 2009 by Timothy P. Hunter
Built with ImageMagick 6.6.9-1 2011-05-07 Q16 http://www.imagemagick.org
Built for ruby 1.8.7
Web page: http://rmagick.rubyforge.org
Email: rmagick@rubyforge.org
$ rake db:migrate RAILS_ENV="production"
fix for generate session store problem.
$ rake generate_session_store