User Tools

Site Tools


haas:status

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
haas:status [2018/03/06 16:51] wedgehaas:status [2022/08/28 16:15] (current) – [August 28th, 2022] wedge
Line 5: Line 5:
   * update grade not-z scripts to handle/be aware of winter terms   * update grade not-z scripts to handle/be aware of winter terms
   * update system page for (new)www   * update system page for (new)www
-    * include information on db server 
-  * upgrade mail VM to jessie/opensmtpd 
-  * upgrade LDAP VMs to jessie 
-  * create new router, using OpenBSD 5.7 
   * scripts to write:   * scripts to write:
     * user homedir backup pruning script     * user homedir backup pruning script
Line 85: Line 81:
     * http://www.askapache.com/linux/rxvt-xresources.html     * http://www.askapache.com/linux/rxvt-xresources.html
 ======Other Days====== ======Other Days======
 +
 +======August 28th, 2022======
 +=====updated dokuwiki=====
 +After enduring constant nags of available updates that I could never resolve, and despite an active semester underway, I committed to updating to the recent major release of dokuwiki (igor), and after wrestling with various file permission issues, was seemingly successful in performing the upgrade AND eliminating the annoying nag messages.
 +=====dokuwiki included pages no edit button (fixed)=====
 +I wanted a read-only base project page, with notes namespace-included content that users could edit.
 +
 +Unfortunately, that particular combination did not work, at least, not until I did some searching and found: https://github.com/dokufreaks/plugin-include/issues/132
 +
 +<code php>
 +function html_secedit($text,$show=true){
 +    global $INFO;
 +
 +    if((isset($INFO) && !$INFO['writable']) || !$show || (isset($INFO) && $INFO['rev'])){
 +        $include_SEC_EDIT_PATTERN = '#<!-- EDIT{(?!.*PLUGIN_INCLUDE).*?} -->#';
 +        return preg_replace($include_SEC_EDIT_PATTERN,'',$text);
 +    }
 +
 +    return preg_replace_callback(SEC_EDIT_PATTERN,
 +                'html_secedit_button', $text);
 +}
 +</code>
 +======March 12th, 2020======
 +
 +=====borked journal, maybe fix=====
 +
 +<code>
 +tune2sf -O ^has_journal /dev/<dev>
 +e2fsck -f /dev/<dev>
 +tune2sf -j /dev/<dev>
 +</code>
 +
 +Obtained from:
 +
 +  * https://www.linuxquestions.org/questions/linux-newbie-8/aborted-journal-and-volume-remounted-read-only-812216/
 +======November 21st, 2019======
 +=====pi4b dual head=====
 +Apparently I was missing something when building up from the lite version of raspbian. For when I popped in a new raspbian (the full desktop version) everything came up just fine.
 +
 +Oh well. At least things are now working as they should.
 +
 +======November 19th, 2019======
 +=====pi4b dual head issues=====
 +Attempting to set up a fresh raspbian install on the pi4b. Strangely, getting issues with dual head: it is only coming up in mirrored mode (or when I play with it, not at all).
 +
 +The only major variables that have changed:
 +
 +  * new raspbian release (I could test my old setup.. that is easy enough to verify)
 +  * no longer using HDMI monitors, but the DVI connections on the LAIR monitors.
 +    * further investigation suggests the pi may be seeing identical EDIDs and other monitor ID things, so it is defaulting to a mirroring mode.
 +    * **tvservice -l** consistently identifies two displays, so the hardware sees it, the software is not.
 +
 +Interestingly: my old raspbian setup IS working properly. So what is different between the two?
 +======March 15th, 2018======
 +Setting up the raspberry pi 3 for use in the comporg class. Named it **pi3b**, and will get the IP of 10.80.2.48; running the latest stable release of rasbian.
 +
 +Looking to get LDAP and autofs going, then installing packages to make it minimally functional for our purposes.
 +
 ======March 6th, 2018====== ======March 6th, 2018======
 Aside from an attempt at restarting my status-reporting habits in January of 2017, I totally neglected it for the remainder of the year. Aside from an attempt at restarting my status-reporting habits in January of 2017, I totally neglected it for the remainder of the year.
Line 148: Line 202:
   * [[https://wiki.debian.org/SSDOptimization]]   * [[https://wiki.debian.org/SSDOptimization]]
  
 +
 +
 +=====lab46too SSD updates=====
 +With the pods having seen their SSD updates, I am looking to do the same for lab46too, testing to make sure the similar changes can be applied to that machine before rolling them over to lab46 proper.
 +
 +I've updated the /etc/fstab and /etc/rc.local files accordingly on lab46, so those changes have been synced over to lab46too on a recent rsync run.
 +
 +I had to remove the commit=600 from the /home partition. For some reason it didn't want to mount with that.
 ======Month Status Page Navigation====== ======Month Status Page Navigation======
  
 ^  [[haas/status/status_201701|Previous Month]]  ^  [[haas/status|Current Month]]  ^  [[haas/status/status_201804|Next Month]]  | ^  [[haas/status/status_201701|Previous Month]]  ^  [[haas/status|Current Month]]  ^  [[haas/status/status_201804|Next Month]]  |
haas/status.1520373076.txt.gz · Last modified: 2018/03/06 16:51 by wedge