The boundaries of the Hyde Shuttle of Seattle for
the Northeast Seattle
neighborhood
- Seattle North to 145th
- South to the Ship Canal
- East to Lake Washington
- And West to I-5
We do make some exceptions:
- Northgate and adjacent medical facilities.
The boundaries of the Hyde Shuttle of Seattle for
the Northeast Seattle
neighborhood
We do make some exceptions:
#!/bin/bash -x | |
# Session duration | |
# DURATION=43200 | |
DURATION=3600 | |
unset AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_SESSION_TOKEN | |
if ! sts=( $( | |
aws sts assume-role \ |
for keyfile in /etc/apt/keyrings/*.asc; do echo "$keyfile"; cat "$keyfile" | gpg --with-colons --import-options show-only --import | awk -F: '$1 == "fpr" {print $10}' | xargs --verbose -L 1 apt-key del; done |
#!/bin/bash | |
if [ -z "$1" -o "$1" = "mount" ]; then | |
action=mount | |
elif [ "$1" = "umount" ]; then | |
action=umount | |
elif [ "$1" = "wait" ]; then | |
action=wait | |
else | |
echo "missing action" |
If you're running the linuxserver.io dockerized Unifi Network Application / Unifi Controller and you've SSH'd into the Unifi AP and set the inform URL as described in the README by running
set-inform http://$address:8080/inform
and when you run the info
command to see the result you see the message
#!/bin/bash | |
if [ -z "$1" -o "$1" = "mount" ]; then | |
action=mount | |
elif [ "$1" = "umount" ]; then | |
action=umount | |
else | |
echo "missing action" | |
exit 1 | |
fi |
I went to update the Storage Component on my Dell PowerEdge VRTX from 23.13.16.0017
23.14.06.0013_A08
.
I uploaded the Dell Shared PERC8 firmware for Dell PowerEdge VRTX-Fault Tolerant version 23.14.06.0013_A08 (filename VRTX_SAS-RAID_Firmware_THVJ9_WN64_23.14.06.0013_A08.EXE ). The upload completed successfully.
I applied the update. The UI showed that the update was "in-progress" for the next 8 hours. After 8 hours I gave up and powered off the Chassis from the CMC.
I powered the Chassis back on and the storage firmware showed as still being 23.13.16.0017
I uploaded the same file again and again initiated an update and this time it worked in fairly short order.
BEGIN:VCALENDAR | |
PRODID:-//Google Inc//Google Calendar 70.9054//EN | |
VERSION:2.0 | |
CALSCALE:GREGORIAN | |
METHOD:PUBLISH | |
X-WR-CALNAME:Temp | |
X-WR-TIMEZONE:America/Los_Angeles | |
BEGIN:VTIMEZONE | |
TZID:America/Los_Angeles | |
X-LIC-LOCATION:America/Los_Angeles |