Welcome to thatlinuxbox.com Saturday, November 02 2024 @ 03:26 PM UTC
Pine Mountain Trail Race 2020 - Ultramarathon Race Report
- Thursday, January 07 2021 @ 07:00 PM UTC
- Contributed by: Dan Stoner
- Views: 1,477
I feel like my training went well this year... 2020 was good for my running. With most races cancelled due to COVID-19, I had a long steady gradual multi-month fitness buildup. I had many weeks over 50 miles, four weeks over 60 miles, and one 70 mile week. I was lucky and able to work remotely for my job during the pandemic and this gave me extra time each day to get my run in or just to sleep longer for recovery. At some point I asked myself what I was going to do with all of this fitness? So I started looking for trail races and found that the PMTR was going to be held this year with pandemic protocols in-place.
The first time I considered (but did not run) the PMTR was when I was 40 years old, and I think at that time the race was actually 40 miles (give or take). Things didn't work out when I was 40, but now I am 46 years old and the race is now 46 miles long. This seemed very fateful. I have been to F. D. Roosevelt State Park a few times and did some trail running on the Pine Mountain Trail before, so I felt pretty good about knowing the type of trail and some parts of the course. I knew how chunky and rocky it is! This was helpful in figuring out where to train and what kind of shoes to wear.
To train I spent time on the Conquistador trail in San Felasco Hammock Preserve State Park near my home in Florida. I also took a special vacation training trip to Tennessee and north Georgia a few weeks before the race, spending time at Frozen Head State Park and on Lookout Mountain. I wore all of the clothing and shoes and tested my planned nutrition during these long trail runs. I generally run in the morning without any breakfast, but for training I practiced eating before and during these runs. I even experienced one "bad" training day where I had to walk a lot and decide whether to quit and head back to the car or just keep moving. This turned out to be good practice and helped solidify my confidence that no matter what happened I would be able to finish an Ultra, even if I had to walk it in.
For the race, I camped at the state park, which meant I could walk over to pickup my packet the afternoon before the race, and just jog over to the starting line on the day of the race. It was quite cold! Low temperatures were in the 30s so my tent was a bit chilly! I did have an electric heater with me which definitely helped. One thing that didn't work out according to plan is that I had trouble getting my campfire started. Frustration and lots of squatting and blowing later, I eventually was able to cook my dinner... a nice big steak! I think the firewood I bought at the camp store must have still been wet or something (the green moss was a hint) and spending so much time on dinner prep meant I got to bed a little later than I had planned and was chilled longer than expected. When I finally got into my tent for the night, I laid out all of my clothes so I could throw everything on quickly in the morning. The race day weather forecast made clothing choice a challenge. It was very cold in the morning but I definitely didn't want to get hot during the day and the temperature was supposed to get up in to the mid-to-high 50s and maybe be sunny.
One thing I didn't expect was the sound of Christmas carols in the distance playing well into the evening. I think the music must have been coming from nearby Callaway Gardens. I didn't have much trouble falling asleep though, and didn't have any pre-race jitters keeping me awake.
I managed a good solid chunk of sleep until around 2:30am. Then I woke up (maybe I was cold?) and just dozed until my alarm went off at 4:45am. I got up and heated some water on my camp stove to make coffee and oatmeal. I also ate a banana.
I put my Garmin Instinct into GPS Ultratrac mode to make sure the battery would last thru the race. I put my phone in airplane mode so I wouldn't have any distractions but could still access all of the images of maps I had stored locally on it. I wore shorts, an underjacket, and a lightweight shell on top. I wore Injinji socks to help prevent blisters on my toes and a compression undershirt to reduce chafing around my arms and from my vest. I added Skin Strong Slather on my toes, inside thighs, private parts, nipples, and anywhere else that might chafe. (Tip: Slather does not solidify in the cold like some products) For gear and hydration I used my Salomon S-Lab Sense Ultra Set paired with a Nathan Peak hydration belt. This combo keeps both my hands free and helps prevent the fatigue in my shoulders that develops if I carry a handheld. I planned to wear hat and gloves at the start and change to a cap after getting to my drop bag. And finally, I chose the Topo Terraventure 2 shoes because I wanted some protection from all those chunky rocks. For a headlamp I used a Black Diamond Iota, which was one of the smallest, lightest, and cheapest usb-rechargeable lights I could find (it worked great).
My drop bag contained lots of water (I brought a bunch of "local" water with me to reduce chance of stomach distress), hat, sunglasses, dry socks, calories of various sorts, and an extra set of Salomon soft flasks filled with water.
I jogged my drop bag over to the picnic shelter, huddled by one of the heaters for a little bit, and jogged back to use the bathroom one last time. Pretty soon it was time to start! I jogged back to the dam road where the runners were gathering. After a few words from the RD, we were off!
I now realize I have zero pictures of myself from the race or even just a picture of my Ultra kit! Not even a selfie. Oh well!
- read more (1,878 words)
- Comments (0)
Altra Vanish-R Racing Flat
- Friday, November 20 2020 @ 07:06 PM UTC
- Contributed by: Dan Stoner
- Views: 1,300
Getting a shoe this light seems to guarantee that there are some compromises and tradeoffs.
These shoes remind me a lot of the Mizuno Wave Universe 3 from (many) years ago...
Both are lightweight. So extremely light! Both have a plate-like thing inside. Both have only a small amount of foam and very little cushion. Both have a very similar amount of ground feel. Neither are particularly comfortable. Neither are my favorite shoe.
The Inov-8 Bare-X Lite 150 are still my favorite racing shoes.
But since the Wave Universe and the Bare-X Lite 150 are no longer available for purchase, the Vanish-R could be a good option.
It is nice to see Altra adding some more minimalist shoes to their lineup. Another Altra that I am interested in checking out is the Escalante Racer (not to be confused with the Escalante). On paper, it looks like it is just a little bit more shoe and could be the sweet spot like another one of my favorite shoes, the ST series from Topo Athletic.
- Comments (0)
Annotate PDF files on Linux with Xournal
- Tuesday, July 07 2020 @ 05:31 PM UTC
- Contributed by: Dan Stoner
- Views: 2,203
I use this tool only infrequently and have trouble remembering its name so I am making this blog post for it.
I use Xournal fill out PDF forms on Linux when the PDF document has no actual form fields (basically annotating over the empty blanks) so I can type on a computer instead of having to print a form, fill it out, and then scan it. This also makes the form much more legible than if I were writing on paper.
I have also used Xournal with a Wacom stylus in order to "hand write" / sign my name. Tip: Have your Wacom plugged into the computer before starting Xournal.
On Ubuntu, the package name is "xournal" in the Universe section and you start annotating a PDF by selecting from the menu File -> Annotate PDF
Forms with the little boxes for individual letters are a little challenging, but usually there is a font that comes close to the proper spacing.
You can save your work in-progress as a Xournal file (.xoj). To get the results into a final PDF for submissions, select from the menu File -> Export to PDF.
- Comments (0)
Laptop Screen Height and Remote Work
- Wednesday, March 25 2020 @ 12:31 AM UTC
- Contributed by: Dan Stoner
- Views: 2,988
I know some people who stand up at a table or breakfast bar and use their laptops, but that is a terrible neck angle for long periods of time.
If your laptop will open to 180 degrees, then the following configuration with an external keyboard and mouse may help the screen position considerably:
Otherwise, I suggest a laptop stand such as this one from 1home:
https://www.amazon.com/gp/product/B077JZSBS2
which works very well compared to some others I have tried.
Here I am using it in combination with my Ergotron WorkFit sit-stand workstation:
- Comments (0)
Access Docker After Install Without Logout or Reboot
- Tuesday, March 24 2020 @ 06:48 PM UTC
- Contributed by: Dan Stoner
- Views: 4,044
By default, after installing docker on Ubuntu, normal user accounts cannot connect to the docker daemon.
$ sudo apt install docker.io
$ docker ps
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock
After adding one's user account to the "docker" group, a full logout and login is typically needed for the user account to receive the new group membership. And in fact, on Ubuntu running the default desktop environment, one may need to actually reboot or run an extra command such as:
$ loginctl terminate-user $USERNAME
because systemd seems to preserve a user context even after logout.
Starting a new bash login shell inside an existing terminal is definitely insufficient:
$ bash --login -i
Terminating a desktop session can be fairly inconvenient, depending on the amount of Work In Progress and document editors and browser tabs, etc.
On Ubuntu 18.04, here are steps to allow a normal user account to immediately access docker without having to log out first:
$ groups # note that "docker" will not be in list of groups
$ sudo gpasswd -a $USERNAME docker # add your specific username to the "docker" group
$ sudo grpck # verify that your group file has no syntax errors, and only the expected differences exist
[sudo] password for dan:
'dan' is a member of the 'docker' group in /etc/group but not in /etc/gshadow
$ sudo grpconv # syncs group and gshadow aka the magic command that prevents "newgrp" from generating the error: 'failed to crypt password with previous salt'
$ newgrp docker # log in to new group (starts a subshell with the new group membership attached, environment preserved)
$ groups # note that "docker" will now appear in list of groups for the user
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
$ docker run docker/whalesay cowsay "No Logout Needed!"
___________________
< No Logout Needed! >
-------------------
\
\
\
## .
## ## ## ==
## ## ## ## ===
/""""""""""""""""___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\______/
Thanks to the following articles which provided reference for this blog post:
https://askubuntu.com/questions/477551/how-can-i-use-docker-without-sudo
https://www.geeksforgeeks.org/grpconv-command-in-linux-with-examples/
https://askubuntu.com/questions/1045993/after-adding-a-group-logoutlogin-is-not-enough-in-18-04
- Comments (0)
Thermal Issues on Dell Latitude with Microsoft Teams for Linux
- Friday, March 20 2020 @ 06:26 PM UTC
- Contributed by: Dan Stoner
- Views: 3,423
With work from home orders due to COVID-19, I am now working remotely fulltime.
My company is relying on Microsoft Teams for chat and video conferencing. Thankfully, Microsoft released a native Linux client. Not really, it appears to be an electron app. But at least it doesn't need to run in a browser tab somewhere. And it actually works... audio, video, and screen sharing. And after using a variety of video conferencing solutions over the years, I can say that video and audio quality of Teams is quite good. Unfortunately, as of Microsoft Teams Version 1.3.00.958 (64-bit), the app is a CPU hog and causes my Ubuntu laptop to heat up. When the laptop heats up, the fan winds up like a small jet engine. This is especially noticeable in a quiet home office environment.
I spent a lot of time with i8kutils and cpufrequtils to no avail. On Linux, the Dell Latitude 5501 seems to have only three fan speeds: off, low, and high. There is no medium speed. It is possible to tweak the temperature at which those fan transitions happen, but it is not possible adjust the fan RPMs. On "low", the temperature will just continue to rise while Teams is running and eventually the fan has to kick into high (or the laptop overheat and crash).
The most significant change I was able to make to resolve the heat issue was to turn off TurboBoost. Whereas my temps were shooting up to over 90 degrees C if I tried to run the fan on "low", with TurboBoost disabled the temperature rarely goes about 50 degrees C. I disabled both Hyperthreading and TurboBoost in the system BIOS. This is disappointing to say the least, but this laptop still has 6 cores running at 1.4 GHz, which has been fine for all of the types of work I have been doing.
After disabling TurboBoost, the cpufreq-info tool shows:
- read more (138 words)
- Comments (0)