main
vitrinekast 9 months ago
parent 12680c2dde
commit 795065b209

@ -332,10 +332,12 @@ q {
body {
font-family: "CascadiaCode VTT";
font-size: .8em;
}
article {
padding: 2em 2em;
border: 3em solid orange;
page-break-after: always;
text-align: left;
text-justify: none;
@ -347,6 +349,10 @@ ul {
margin-bottom: 1em;
}
ul, ol, li {
font-size: .8rem;
}
dfn,
samp,
dd {
@ -363,7 +369,6 @@ mark {
white-space: normal;
text-align: left;
text-justify: none;
font-size: .8em;
}
h1,
@ -380,7 +385,6 @@ h6 {
p {
margin-bottom: 1em;
font-family: "CascadiaCode VTT";
font-size: .8em;
text-align: left;
text-justify: none;
}

@ -25,7 +25,7 @@
<body>
<article>
<h1>pface</h1>
<h1>Preface</h1>
<p>
TL;DR researches ways to make sense of the hidden labour that goes on in a feminist server through log files and unlogged activity.
</p>
@ -69,19 +69,20 @@
</mark>
{% endif %}
<p><em>tldr@chopchop:~ $</em>sudo journalctl -S today _COMM=useradd -r</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl -S today _COMM=useradd -r</Pre>
<mark>
Users are assigned to groups, which allow them rights to read or edit files, run commands or apply infrastructural changes. For chopchop, we all have 'sudo rights': the ability to perform any command, including the more sensitive ones. Sudo is a command that's short for 'superuser do', with it, a user has more privileges, like installing or updating a package or performing a restart.
</mark>
{% if list_package_installs|length > 0 %}
<p><em>tldr@chopchop:~ $</em> grep 'install' /var/log/dpkg.log</p>
<Pre><em>tldr@chopchop:~ $</em> grep 'install' /var/log/dpkg.log</Pre>
<b>Something here in the if statement is not working</b>
<ul>
<mark>
Today the following packages were installed:
</mark>
<ul>
{% for item in list_package_installs %}
<li>{{ item }}</li>
{% endfor %}
@ -98,7 +99,7 @@
{% endif %}
{% if list_package_upgrade|length > 0 %}
<p><em>tldr@chopchop:~ $</em> grep 'upgrade' /var/log/dpkg.log</p>
<Pre><em>tldr@chopchop:~ $</em> grep 'upgrade' /var/log/dpkg.log</Pre>
<b>Something here in the if statement is not working</b>
<mark>
Out of the installed packages, these ones were upgraded:
@ -108,7 +109,7 @@
<li>{{ item }}</li>
{% endfor %}
<mark>
Packages are upgraded to fix pvious bugs they had, or allow new options for usage they did not have prior.
Packages are upgraded to fix Previous bugs they had, or allow new options for usage they did not have prior.
</mark>
</ul>
{% endif %}
@ -119,7 +120,7 @@
{% endif %}
{% if list_package_remove|length > 0 %}
<p><em>tldr@chopchop:~ $</em> grep 'remove' /var/log/dpkg.log</p>
<Pre><em>tldr@chopchop:~ $</em> grep 'remove' /var/log/dpkg.log</Pre>
<mark>
These package were removed today:
</mark>
@ -141,8 +142,8 @@
<mark>
These actions are only a portion of the work... There's also the relationships of the people who care for the server enough to maintain it... The hours they put into meeting each other, discussing and deciding on how to move forward... They are sharing a digital landscape in which there are no hierarchies of landlords and renters... So, they find different ways to make a space for learning and co-habitation... This list is not exhaustive.
</mark>
<p><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=systemd-login
--output-fields=MESSAGE -S today -g "New session" | grep -v 'Boot'</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=systemd-login
--output-fields=MESSAGE -S today -g "New session" | grep -v 'Boot'</Pre>
<mark>
Users can login to the server using the SSH (secure shell) protocol. This allows a user to explore files, make changes, run commands and speak to the server from their own machine. This is useful when working remotely, and also to allow multiple users logging into the server simultaneously. Current XPUB1 students have a chopchop user, as well as the tutors. Additionally, there are some users not associated with a person, like our shared user 'chipchip' and users for running specific processes or creating projects.
</mark>
@ -159,7 +160,7 @@
{% endif %}
{% if groups_created|length > 0 %}
<p><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=groupadd -r --output-fields=MESSAGE</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=groupadd -r --output-fields=MESSAGE</Pre>
<mark>
This command shows whether groups were added today.
</mark>
@ -179,7 +180,7 @@
{% endif %}
<b>For some reason this if statement is not working, i didn't apply it to the next 4 categories because i wanted to check it works first</b>
<p><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=groupmove -r --output-fields=MES</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=grouPremove -r --output-fields=MES</Pre>
<mark>
This command shows whether groups were removed today.
</mark>
@ -192,7 +193,7 @@
{% endfor %}
</ul>
<p><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=usermod -r</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=usermod -r</Pre>
<mark>
This command shows whether users were modified today.
</mark>
@ -205,7 +206,7 @@
{% endfor %}
</ul>
<p><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=userdel -r</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=userdel -r</Pre>
<mark>
This command shows whether users were removed today.
</mark>
@ -220,7 +221,7 @@
<hr />
<p><em>tldr@chopchop:~ $</em>sudo service --status-all</p>
<Pre><em>tldr@chopchop:~ $</em>sudo service --status-all</Pre>
<mark>
These are all of the services that are active, running, working to execute requests that enable everything on the server. They are marked with an [+].
The rest, marked with a [-], are idle, not running, or waiting to be activating upon sending a request.
@ -231,8 +232,8 @@ The rest, marked with a [-], are idle, not running, or waiting to be activating
{% endfor %}
</ul>
<p><em>tldr@chopchop:~ $</em>sudo journalctl -S today -u kitchen-stove.service -u
kitchen-bin.service -u kitchen-fridge.service -r -n</p>
<Pre><em>tldr@chopchop:~ $</em>sudo journalctl -S today -u kitchen-stove.service -u
kitchen-bin.service -u kitchen-fridge.service -r -n</Pre>
{% if kitchen_services|length > 0 %}
<ul>
{% for item in kitchen_services %}

Loading…
Cancel
Save