CSCWiki - User contributions [en]

Historical:CAS

2026-04-05T18:04:58Z

C256zhao: C256zhao moved page CAS to Historical:CAS without leaving a redirect

{{Outdated|Starting from 2019, the IST is migrating from CAS to [[ADFS]].}}

IST provides a service called CAS that can be used to authenticate UW accounts.
Relevant docs from IST are http://ist.uwaterloo.ca/~mpatters/cas/user.html and https://strobe.uwaterloo.ca/~twiki/bin/view/ISTCSS/CASClientAuth

CSC also provides WebAuth for authenticating against CSC accounts instead of UW accounts.

===Using CAS in the CSC webhost environment===
We've got the CAS module installed on the CSC webserver.

You can use Authtype CAS in your .htaccess files
For the simplest case, just require any UW password:

AuthType CAS
require valid-user

If you put that in an .htaccess, anything in that folder will require a username to log in.

If you want to require a few specific users, try this:

Authtype CAS
require user ctdalek dbelange mimcpher

== CGI apps with CAS ==

Apache puts the $REMOTE_USER variable into your application's environment, so you can use that to
get the username. For example, in PHP, use $_SERVER['REMOTE_USER'], or os.environ['REMOTE_USER'] in a Python cgi.

Historical:CAS

2026-04-05T18:03:32Z

C256zhao: add outdated note

Template:Outdated

2026-04-05T18:02:18Z

C256zhao:

{| style="margin: 1em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 5px;"
|-
| style="width: 50px; text-align: center; font-size: 30px;" | ⚠️
| style="padding: 5px;" | '''This page contains outdated information that may be inaccurate.''' {{{1|Please help [{{fullurl:{{FULLPAGENAME}}|action=edit}} update this page] to reflect the current situation if you can.}}}
|}<includeonly>[[Category:Outdated pages]]</includeonly><noinclude>
== Usage ==
This template adds a warning box and automatically categorizes the page into [[:Category:Outdated pages]].

To place this at the top of an article, simply use:
<code><nowiki>{{Outdated}}</nowiki></code>

To specify that only a specific section is outdated, use:
<code><nowiki>{{Outdated Section}}</nowiki></code>

</noinclude>

Template:Outdated Section

2026-04-05T18:00:16Z

C256zhao: add custom note

{| style="margin: 0.5em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 2px;"
|-
| style="width: 40px; text-align: center; font-size: 18px;" | ⚠️
| style="padding: 2px;" | This section contains outdated information that may be inaccurate. {{{1|}}}
|}
<includeonly>[[Category:Outdated pages]]</includeonly><noinclude>
== Usage ==
This template adds a warning box and automatically categorizes the page into [[:Category:Outdated pages]].

To place this before a specific section, simply use:
<code><nowiki>{{Outdated Section}}</nowiki></code>

To mark a whole page as outdated, use:
<code><nowiki>{{Outdated}}</nowiki></code>

</noinclude>

Template:Outdated

2026-04-05T17:59:27Z

C256zhao: add custom note

{| style="margin: 1em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 5px;"
|-
| style="width: 50px; text-align: center; font-size: 30px;" | ⚠️
| style="padding: 5px;" | '''This page contains outdated information that may be inaccurate.''' {{{1|}}} Please help [{{fullurl:{{FULLPAGENAME}}|action=edit}} update this page] to reflect the current situation if you can.
|}<includeonly>[[Category:Outdated pages]]</includeonly><noinclude>
== Usage ==
This template adds a warning box and automatically categorizes the page into [[:Category:Outdated pages]].

To place this at the top of an article, simply use:
<code><nowiki>{{Outdated}}</nowiki></code>

To specify that only a specific section is outdated, use:
<code><nowiki>{{Outdated Section}}</nowiki></code>

</noinclude>

Historical:Openstack Compute Node Setup

2026-04-05T17:44:27Z

C256zhao: C256zhao moved page Cloud: Compute Node Setup to Historical:Openstack Compute Node Setup without leaving a redirect

UPDATE: this page is deprecated, as it is for the old cloud which used OpenStack. We are now using [[CloudStack]] instead.

== Machine setup ==

=== Disk configuration ===

A block device with lost of disk space (to be mounted at /var/lib/nova/instances)

=== Networking configuration ===

'''Do not register the IPv6 address in DNS. This may cause issues with OpenStack services.'''

We will be using 2 interfaces on the machine:

* 1gbps for management (VLAN 529 (CSC Cloud Management))
* 10gbps for VMs (VLAN 134 (MSO), 425 (CSC Cloud))

==== Fix ebtables ====

<pre>
update-alternatives --config ebtables
</pre>

and choose "ebtables-legacy". This is necessary to work around missing features in ebtables-nft.

==== <code>/etc/sysctl.d/10-ipv6.conf</code> ====

<pre># Disable autoconf
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.default.autoconf=0

# Stop accepting router advertisments
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.default.accept_ra=0

# Do not use temporary addresses
net.ipv6.conf.all.use_tempaddr=0
net.ipv6.conf.default.use_tempaddr=0</pre>

==== <code>/etc/network/interfaces</code> ====

Configure the switch port with VLAN 529 as the untagged VLAN, and VLANs 134 and 425 as the tagged VLANs.

<pre># Management interface
auto $INTERFACE
iface $INTERFACE inet static
address 172.19.168.XX
netmask 255.255.255.224
gateway 172.19.168.1

iface $INTERFACE inet6 static
address fd74:6b6a:8eca:4902::XX
netmask 64
gateway fd74:6b6a:8eca:4902::1

#################
# VM NETWORKING #
#################

auto $INTERFACE.134
iface $INTERFACE.134 inet manual
iface $INTERFACE.134 inet6 manual
vlan-raw-device $INTERFACE

auto $INTERFACE.425
iface $INTERFACE.425 inet manual
iface $INTERFACE.425 inet6 manual
vlan-raw-device $INTERFACE
</pre>

== Compute service ==

=== Prerequisites ===

* <code>debian.csclub</code> APT repository configured

=== Installation ===

==== Configure virtualization ====

<code>sudo apt install qemu qemu-kvm libvirt-bin bridge-utils</code>

==== Install Nova Compute ====

Based on the official OpenStack document:

* https://docs.openstack.org/ocata/install-guide-ubuntu/nova-compute-install.html
* https://docs.openstack.org/ocata/install-guide-ubuntu/neutron-compute-install.html

<code>sudo apt install nova-compute neutron-linuxbridge-agent</code>

Now configure:

===== <code>/etc/nova/nova.conf</code> =====

<pre class="conf">[DEFAULT]
state_path=/var/lib/nova
enabled_apis=osapi_compute,metadata
transport_url=rabbit://$USER:$PASS@rabbit.cloud.csclub.uwaterloo.ca
auth_strategy=keystone
my_ip=172.19.168.XX
use_neutron=true
firewall_driver=nova.virt.firewall.NoopFirewallDriver
default_availability_zone = csc-mc
compute_monitors = cpu.virt_driver,numa_mem_bw.virt_driver

[oslo_concurrency]
lock_path=/var/lock/nova

[database]
connection=mysql+pymysql://$USER:$PASS@db.cloud.csclub.uwaterloo.ca/nova_api

[libvirt]
use_virtio_for_bridges=True
inject_password=true
live_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE,VIR_MIGRATE_TUNNELLED
block_migration_flag = VIR_MIGRATE_UNDEFINE_SOURCE, VIR_MIGRATE_PEER2PEER, VIR_MIGRATE_LIVE, VIR_MIGRATE_TUNNELLED, VIR_MIGRATE_NON_SHARED_INC
cpu_mode = custom
cpu_model = Broadwell

[keystone_authtoken]
auth_uri = https://auth.cloud.csclub.uwaterloo.ca
auth_url = https://admin.cloud.csclub.uwaterloo.ca
memcached_servers = memcache1.cloud.csclub.uwaterloo.ca:11211
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = service
username = $USER
password = $PASS

[vnc]
enabled = true
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = $my_ip
novncproxy_base_url = https://console.cloud.csclub.uwaterloo.ca/vnc_auto.html

[glance]
api_servers = https://image.cloud.csclub.uwaterloo.ca

[neutron]
url = https://network.cloud.csclub.uwaterloo.ca
auth_url = https://admin.cloud.csclub.uwaterloo.ca
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
region_name = csc-mc
username = $USER
password = $PASS

[placement]
os_region_name = csc-mc
project_domain_name = Default
project_name = service
auth_type = password
user_domain_name = Default
auth_url = https://admin.cloud.csclub.uwaterloo.ca/v3
username = $USER
password = $PASS</pre>

===== <code>/etc/neutron/neutron.conf</code> =====

<pre class="conf">[DEFAULT]
# ...
transport_url=$USER:$PASS@rabbit.cloud.csclub.uwaterloo.ca
auth_strategy=keystone

[keystone_authtoken]
auth_uri = https://auth.cloud.csclub.uwaterloo.ca
auth_url = https://admin.cloud.csclub.uwaterloo.ca
memcached_servers = memcache1.cloud.csclub.uwaterloo.ca:11211
auth_type = password
project_domain_name = Default
user_domain_name = Default
project_name = service
username = $USER
password = $PASS</pre>
===== <code>/etc/neutron/plugins/ml2/linuxbridge_agent.ini</code> =====

<pre class="conf">[linux_bridge]
physical_interface_mappings=mso-internet:$INTERFACE.134, mso-intranet:$INTERFACE.425

[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

[vxlan]
enable_vxlan=true
local_ip=172.19.168.XX
l2_population=true</pre>
Then:

<code>sudo systemctl restart nova-compute neutron-linuxbridge-agent</code>

=== Add mapping ===

On controller1.cloud:

<pre>. ~/cloud-admin
su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova</pre>

=== Setup migration ===

* Add SSH keys for root and nova on each compute node
* Change nova user shell to /bin/sh
* Enable <code>--listen</code> flag for Libvirt (/etc/default/libvirtd)
* Enable listen_tcp and auth_mode_tcp = none in /etc/libvirt/libvirtd.conf

Sunlight

2026-04-05T05:52:58Z

C256zhao: fix link

On occasion, sunlight reflects off the DC, through mathsoc, into the CSC.

On 11 July, 2012, sunlight was observed at 4:08 PM.

On 25 October, 2012, sunlight was observed at 5:45 PM.

==geometry==

The square of light in the CSC was approximately 15cm high by 20cm wide. It was approximately 150cm off the floor. These are from memory, and need to be re-confirmed. I believe the CSC door being partly open was restricting the width of the square.

Measurements:
* 162 cm top 177 cm. 32 cm wide 5:13 pm Sept 10

Although solar alignments are not uncommon among passage graves, the [[Computer Science Club|University of Waterloo Computer Science Club]] is one of few to contain the additional roofbox feature ([[Cairn G]] at [[Carrowkeel Megalithic Cemetery]] is another, and it has been suggested that one can be found at [[Bryn Celli Ddu]].). The alignment is such that although the roofbox is above the passage entrance, the light hits the floor of the inner chamber. Today the first light enters about four minutes after sunrise, but calculations based on the precession of the Earth show that 5,000 years ago first light would have entered exactly at sunrise.

Historical:Math CnD

2026-04-05T01:40:27Z

C256zhao: C256zhao moved page Math CnD to Historical:Math CnD without leaving a redirect

The '''Math C&D''', or '''Mathematics Coffee et Doughnaught Shoppe''', is a local distributor of cheap bacteria and also ice-cream. Notable mainly for the hilarious [[2001]] absconding of venerable '''C&D''' manager Jeff Stewart[http://old.uwstudent.org/article.php?story=20001101195750000] and thousands upon thousands of [[Mathsoc]]'s hoarded gold ducats.

Kerberos

2026-04-05T01:34:49Z

C256zhao: /* Configuring Kerberos */ fix link

'''IF YOU ARE LOOKING FOR A PASSWORD RESET, PLEASE VISIT''' https://csclub.uwaterloo.ca/ceo/pwreset '''FOR A SELF-SERVICE PORTAL FOR PASSWORD RESETS! (If you experience any issues, please contact Syscom)'''

---

We use [http://web.mit.edu/Kerberos/ MIT Kerberos 5] for authentication. Our kerberos realm is CSCLUB.UWATERLOO.CA. This realm is CASE-SENSITIVE. KDCs run on [[Machine_List#auth1|auth1]] (kdc1) and [[Machine_List#auth2|auth2]] (kdc2).

[[File:kerberos.png|frame|Kerberos, the network authentication protocol]]

= ehashman's guide to MIT Kerberos v5 on Debian =

== Preparatory Reading ==

# [http://web.mit.edu/kerberos/dialogue.html Kerberos: A Dialogue in Four Scenes] ('''''definitely''''' read this)
# [http://www.roguelynn.com/words/explain-like-im-5-kerberos/ Explain Like I'm 5: Kerberos] (less entertaining than the stage play)
# [http://www.rjsystems.nl/en/2100-d6-kerberos-master.php A very practical configuration guide to Kerberos on Debian squeeze] (things don't change much in the Debian world)
# [http://web.mit.edu/kerberos/krb5-latest/doc/admin/index.html The official Kerberos documentation]

== Set up host records ==

<ul>
<li>We will need host records to correspond to our Kerberos admin server and key distribution center, <code>kadmin.wics.uwaterloo.ca</code> and <code>kdc1.wics.uwaterloo.ca</code>. These can just be A records pointing to our auth server (currently <code>129.97.134.212</code>).</li>
<li>We can also set up [http://web.mit.edu/kerberos/krb5-latest/doc/admin/realm_config.html special SRV records] as well. This is recommended but not necessary. They look like this:
<pre>_kerberos._udp.wics.uwaterloo.ca SRV 0 0 88 kdc1.wics.uwaterloo.ca
_kerberos-master._udp.wics.uwaterloo.ca SRV 0 0 88 kdc1.wics.uwaterloo.ca
_kpasswd._udp.wics.uwaterloo.ca SRV 0 0 464 kdc1.wics.uwaterloo.ca</pre>
You may have guessed that the third integer is the port the service runs on.</li></ul>

== Install packages ==

<ul>
<li>First, install some common system utils that may be missing from the fresh container:
<pre># apt-get install ssh ntpdate xinetd nmap</pre></li>
<li>Do NOT install ntp on the container. Install it on the host system instead. See [[ntp|NTP]] for info on NTP servers.</li>
<li>Next, install the Kerberos server:
<pre>apt-get install krb5-{admin-server,user}</pre></li>
<li>During the install process, <code>dpkg</code> will ask you for the following three values, specified below:
<pre>Default Kerberos version 5 realm: WICS.UWATERLOO.CA
Kerberos servers for your realm: kdc1.wics.uwaterloo.ca
Administrative server for your Kerberos realm: kadmin.wics.uwaterloo.ca</pre></li>
<li>You'll encounter this lovely error, from <code>xinetd</code>:
<pre>Note: xinetd currently is not fully supported by update-inetd.
Please consult /usr/share/doc/xinetd/README.Debian and itox(8).</pre>
To solve this, we create a file <code>/etc/xinetd.d/krb_prop</code> with the following contents:
<pre>service krb_prop
{
disable = no
socket_type = stream
protocol = tcp
user = root
wait = no
server = /usr/sbin/kpropd
}</pre>
And then restart <code>xinetd</code>:
<pre># service xinetd restart</pre></li>
<li>You'll also note that the <code>krb5-kdc</code> service failed to start. This is okay. > This is because the realm, EXAMPLE.COM, or rather the database file for it (<code>/var/lib/krb5kdc/principal</code>), has not yet been created. – http://www.rjsystems.nl/en/2100-d6-kerberos-master.php</li></ul>

== Configuring Kerberos ==

<ul>
<li>The first thing we'll configure is the access control list. Edit <code>/etc/krb5kdc/kadm5.acl</code> and enable/add the following line:
<pre>*/admin *</pre>
Our primary admin principal will be <code>sysadmin/admin@WICS.UWATERLOO.CA</code>, so there is no need to add a separate <code>admin</code> principal to the ACL.</li>
<li>Let's configure Kerberos client-side in [https://git.uwaterloo.ca/wics/documentation/blob/master/krb5.conf <code>/etc/krb5.conf</code>]. Consulting with the CSC's config, [https://www.rjsystems.nl/en/2100-d6-kerberos-master.php#rcfg our favoured setup guide], and [http://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html the Kerberos krb5.conf manual], we'll mostly select default settings. Notable additions include
<pre>[libdefaults]
allow_weak_crypto = false # default is currently false but hey

# If DNS breaks we don't want auth to fail
dns_lookup_kdc = false
dns_lookup_realm = false

[logging]
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmin.log
default = FILE:/var/log/krb5.log</pre></li>
<li>We also want to ensure we're using good crypto for our Key Distribution Center, so let's set that up next in [https://git.uwaterloo.ca/wics/documentation/blob/master/kdc.conf <code>/etc/krb5kdc/kdc.conf</code>]:
<pre>[kdcdefaults]
kdc_ports = 750,88

[realms]
WICS.UWATERLOO.CA = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 12h 0m 0s
max_renewable_life = 1d 0h 0m 0s
master_key_type = aes256-cts-hmac-sha1-96
supported_enctypes = aes256-cts-hmac-sha1-96:normal aes128-cts-hmac-sha1-96:normal
default_principal_flags = +preauth
}</pre></li>
<li>We didn't choose to create a new krb5 log directory but we should set up logrotate. Create a file [https://git.uwaterloo.ca/wics/documentation/blob/master/logrotate.d.krb5 <code>/etc/logrotate.d/krb5</code>] with three of the following entries (one for each log file):
<pre>/var/log/FILENAME.log {
weekly
missingok
rotate 8
compress
delaycompress
notifempty
postrotate
/etc/init.d/SERVICENAME restart > /dev/null
endscript
}</pre></li>
<li>Make sure you also create those files so the service can write to them:
<pre># touch /var/log/{krb5,krb5kdc,kadmin}.log</pre></li></ul>

== Creating the Kerberos Realm ==

<ul>
<li>Now we're going to create the realm:
<pre># krb5_newrealm
This script should be run on the master KDC/admin server to initialize
a Kerberos realm. It will ask you to type in a master key password.
This password will be used to generate a key that is stored in
/etc/krb5kdc/stash. You should try to remember this password, but it
is much more important that it be a strong password than that it be
remembered. However, if you lose the password and /etc/krb5kdc/stash,
you cannot decrypt your Kerberos database.
Loading random data</pre>
The script may pause at this point until there is sufficient available entropy to generate a key. Then it will prompt for a password. USE A LONG, RANDOM ONE. THIS PASSWORD IS VERY IMPORTANT.
<pre>Initializing database '/var/lib/krb5kdc/principal' for realm
'WICS.UWATERLOO.CA',
master key name 'K/M@WICS.UWATERLOO.CA'
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.
Enter KDC database master key:
Re-enter KDC database master key to verify:

Now that your realm is set up you may wish to create an administrative
principal using the addprinc subcommand of the kadmin.local program.
Then, this principal can be added to /etc/krb5kdc/kadm5.acl so that
you can use the kadmin program on other computers. Kerberos admin
principals usually belong to a single user and end in /admin. For
example, if jruser is a Kerberos administrator, then in addition to
the normal jruser principal, a jruser/admin principal should be
created.

Don't forget to set up DNS information so your clients can find your
KDC and admin servers. Doing so is documented in the administration
guide.</pre></li>
<li>We'll now configure the default and maximum ticket life for the Kerberos Ticket Granting Ticket (<code>krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA</code>):
<pre># kadmin.local
Authenticating as principal root/admin@WICS.UWATERLOO.CA with password.
kadmin.local: getprinc krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA
Principal: krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA
Expiration date: [never]
Last password change: [never]
Password expiration date: [none]
Maximum ticket life: 0 days 12:00:00
Maximum renewable life: 1 day 00:00:00
Last modified: Thu Dec 03 03:59:04 UTC 2015 (db_creation@WICS.UWATERLOO.CA)
Last successful authentication: [never]
Last failed authentication: [never]
Failed password attempts: 0
Number of keys: 2
Key: vno 1, aes256-cts-hmac-sha1-96, no salt
Key: vno 1, aes128-cts-hmac-sha1-96, no salt
MKey: vno 1
Attributes: REQUIRES_PRE_AUTH
Policy: [none]</pre>
Let's set the max life to 4 hours and the renewable life to 10 hours, for extra security.
<pre>kadmin.local: modprinc -maxlife "4 hour" -maxrenewlife "10 hour" krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA
Principal "krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA" modified.</pre></li></ul>

== Adding Principals ==

<ul>
<li>We need some root users in our system in order to bootstrap the rest, so let's create our sysadmin user, and give them our root password for authentication:
<pre># kadmin.local
Authenticating as principal root/admin@WICS.UWATERLOO.CA with password.
kadmin.local: addprinc sysadmin/admin
WARNING: no policy specified for sysadmin/admin@WICS.UWATERLOO.CA; defaulting to no policy
Enter password for principal "sysadmin/admin@WICS.UWATERLOO.CA":
Re-enter password for principal "sysadmin/admin@WICS.UWATERLOO.CA":
Principal "sysadmin/admin@WICS.UWATERLOO.CA" created.</pre></li>
<li>Now we need to add a principal and keytab for our KDC host. While <code>addprinc -randkey</code> does add a key, we need to use <code>ktadd</code> to ensure it's copied over to the client host (in this case, auth1).

('''keytab:''' a key table file containing one or more keys. A host or service uses a keytab file in much the same way as a user uses his/her password.)

<pre>$ kadmin -p sysadmin/admin
Authenticating as principal sysadmin/admin with password.
Password for sysadmin/admin@WICS.UWATERLOO.CA:
kadmin: addprinc -randkey host/auth1.wics.uwaterloo.ca
WARNING: no policy specified for
host/auth1.wics.uwaterloo.ca@WICS.UWATERLOO.CA; defaulting to no policy
Principal "host/auth1.wics.uwaterloo.ca@WICS.UWATERLOO.CA" created.
kadmin: ktadd host/auth1.wics.uwaterloo.ca
Entry for principal host/auth1.wics.uwaterloo.ca with kvno 2, encryption type
aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
Entry for principal host/auth1.wics.uwaterloo.ca with kvno 2, encryption type
aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.</pre></li>
<li>Now we can test that the KDC can grant principals tickets:
<pre>$ kinit sysadmin/admin
Password for sysadmin/admin@WICS.UWATERLOO.CA:
$ klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: sysadmin/admin@WICS.UWATERLOO.CA
Valid starting Expires Service principal
12/03/2015 05:31:38 12/03/2015 09:31:38 krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA
renew until 12/03/2015 15:31:38
$ kdestroy
$ klist
klist: Credentials cache file '/tmp/krb5cc_0' not found</pre></li>
<li>Next, we'll probably want to add principals for any users that we created in LDAP. We can do this in <code>weo</code> using the following command, and we can even test that principal after its creation:
<pre>$ python weo.py --add-krb-princ --username=ehashman
Okay, adding Kerberos principal ehashman@WICS.UWATERLOO.CA
Enter Kerberos admin password:
Enter password for principal ehashman@WICS.UWATERLOO.CA:
Retype password:
Adding Kerberos principal...
Principal ehashman@WICS.UWATERLOO.CA successfully added.
$ kinit ehashman
Password for ehashman@WICS.UWATERLOO.CA:
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: ehashman@WICS.UWATERLOO.CA
Valid starting Expires Service principal
15-12-03 17:36:22 15-12-03 21:36:22 krbtgt/WICS.UWATERLOO.CA@WICS.UWATERLOO.CA
renew until 15-12-04 03:36:22</pre></li>
<li>From now on, though, Kerberos principals will automatically be generated when we add new users! Like this:
<pre>$ python weo.py --adduser --username=fhboxwal --fullname="Fatema Boxwala"
Okay, adding user fhboxwal
Please enter the new user's password:
Retype password:
Enter LDAP admin password:
Enter Kerberos admin password:
Locking LDAP database...
Adding user...
Unlocked database.
Adding Kerberos principal...
User fhboxwal successfully added.</pre></li>
<li>Awesome! Now we're ready to configure Kerberos for clients.</li></ul>

== Setting Up Client Machines with SSSD ==

<ul>
<li>On your machine of choice, install the Kerberos client packages:
<pre># apt-get install krb5-user</pre></li>
<li>Now copy over your Kerberos config, [https://git.uwaterloo.ca/wics/documentation/blob/master/krb5.conf <code>krb5.conf</code>], into <code>/etc/krb5.conf</code>.</li>
<li>Next, set up a host keytab for the local machine:
<pre># kadmin -p sysadmin/admin
Authenticating as principal sysadmin/admin with password.
Password for sysadmin/admin@WICS.UWATERLOO.CA:
kadmin: addprinc -randkey host/mother-goose.wics.uwaterloo.ca
WARNING: no policy specified for host/mother-goose.wics.uwaterloo.ca@WICS.UWATERLOO.CA; defaulting to no policy
Principal "host/mother-goose.wics.uwaterloo.ca@WICS.UWATERLOO.CA" created.
kadmin: ktadd host/mother-goose.wics.uwaterloo.ca
Entry for principal host/mother-goose.wics.uwaterloo.ca with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.
Entry for principal host/mother-goose.wics.uwaterloo.ca with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab FILE:/etc/krb5.keytab.</pre></li>
<li>In order to configure authentication, we'll use a package called SSSD. (It has 234823840 dependencies.) Install it and its utilities:
<pre># apt-get install sssd sssd-tools</pre></li>
<li>Next, copy over the following configs:</li>
<li>[https://git.uwaterloo.ca/wics/documentation/blob/master/ldap.conf <code>/etc/ldap/ldap.conf</code>]</li>
<li>[https://git.uwaterloo.ca/wics/documentation/blob/master/sssd.conf <code>/etc/sssd/sssd.conf</code>]</li>
<li>[https://git.uwaterloo.ca/wics/documentation/blob/master/sshd_config <code>/etc/ssh/sshd_config</code>]</li>
<li>[https://git.uwaterloo.ca/wics/documentation/blob/master/ssh_config <code>/etc/ssh/ssh_config</code>]</li>
<li>[https://git.uwaterloo.ca/wics/documentation/blob/master/hosts <code>/etc/hosts</code>] (because what the heck)</li>
<li>Restart <code>sssd</code> and <code>sshd</code>. The former can be very temperamental:
<pre># service ssh restart
# service sssd restart</pre></li>
<li>Test that this all worked by attempting to log in:
<pre># Just try logging in
$ ssh me@machine.wics.uwaterloo.ca

# Try logging in using Kerberos
$ kinit me
$ ssh -o GSSAPIAuthentication=yes me@machine.wics.uwaterloo.ca

# Test that sudo is working
machine:~$ sudo -i</pre></li></ul>

== Tools for Debugging SSSD ==

<ul>
<li>It turns out <code>sssd</code> is not the greatest at telling us things. If it starts breaking, stop it and start it in the foreground in debugging mode:
<pre># service sssd stop
# sssd -d 5 -i</pre></li>
<li>Some problems with <code>sssd</code> may be cache-related, and restarting it does not clear the cache. If you need to invalidate the cache, run
<pre>sss_cache -E</pre></li></ul>
and then reboot (or restart sssd).

= Password Resets =
To change your own password you can run passwd on any of the club's machines.

== Changing other user's passwords (new) ==
The [[ceo]] utility now has the ability to reset members' passwords, and it also takes care of expiring it. Usage:
<pre>
ceo members pwreset <username>
</pre>

== Changing other users' passwords (old) ==
* <pre>ssh auth1</pre>
* <pre>sudo kadmin.local</pre>
* <pre>cpw username</pre>
* Enter new password and confirm
* <pre>modify_principal +needchange username</pre>

[[Category:Software]]

[http://web.archive.org/web/20120202205851/http://cryptnet.net/mirrors/docs/krb5api.html API Documentation.] While not even close to enough to let you do most things that you'd want to do with Kerberos (and also being somewhat woefully out-of-date, considering it's from 1996), it's at least a start.

= Expiring Passwords =

If you are on syscom, you can force a user to change their password by doing this:
* <pre>ssh auth1</pre>
* <pre>sudo kadmin.local</pre>
* <pre>modify_principal +needchange [username]</pre>

= Suspending an Account =

If you are on syscom, you can prevent a user from logging with a Kerberos ticket by doing this:
* ssh auth1
* sudo kadmin.local
* modify_principal -allow_tix [username]
If you are seriously locking out an account, you may want to do some other things as well, including but not limited to changing the user's password (prevents password login) and changing the ownership and permissions on .ssh/authorized_keys* (prevents SSH key login). Don't do these things without a strong reason (but know how to do them when the time comes).

= Siracha's Lessons in Hell =
I died to write these, do not take the lessons on this page lightly. We cried figuring out these things

=== Connecting to auth1 ===
Get the leader's PID<syntaxhighlight lang="bash">
machinectl status auth1 | grep Leader
</syntaxhighlight>Connect to the Process using result in last command<syntaxhighlight lang="bash">
nsenter -a -t <Leader PID>
</syntaxhighlight>

= bofh's Kerberos5 cheat sheet, or "what does *that* error message mean, exactly?" =

* If GSSAPI complains about "Wrong Principal in Request", make sure there's no clockskew on the machine trying to get the service ticket and the machine running the service that you are trying to get a GSS token to. This will cause this error for some insane reason, despite there being ANOTHER message for clockskew that specifically says "your clocks are off" - it just never seems to be used in the source code anywhere (as of MIT-KRB5 1.9, at least).
* There are some "generic" errors that are hard to debug. A few possible causes: unreadable krb5.keytab, reverse resolution of a host does not match its principal.

= Replication =

auth1 replicates to auth2 using kpropd. This requires additional setup that needs to be documented here.

Occasionally, the replication results in "ulog_replay failed (Cannot allocate memory), updates not registered". To correct this, run `kproplog -R` on auth1 and start the `kpropd` server again.

= raymo's guide to keytabs =

Adapted from https://stackoverflow.com/a/55826172/9206488 and https://sfu.teamdynamix.com/TDClient/255/ITServices/KB/ArticleDet?ID=3932

You can follow this guide to never need to <code>kinit</code> or enter your password for CEO again. Note that all caps is needed for the Kerberos realm, and replace <code><user></code> with your CSC username.

ktutil
addent -password -p <user>@CSCLUB.UWATERLOO.CA -k 1 -e aes256-cts-hmac-sha1-96
# enter password at the prompt
wkt <user>.keytab
quit

Then move your keytab to a secure directory:

mkdir -m700 ~/keytabs
mv ~/$USER.keytab ~/keytabs/
chmod 600 ~/keytabs/$USER.keytab

Finally, add this line to the TOP of your <code>bashrc</code> (or before any command to disable it for non-interactive shells, unless you don't want <code>kinit</code> to be triggered when running remote commands:

kinit -kt ~/keytabs/$USER.keytab $USER@CSCLUB.UWATERLOO.CA

Alternatively, use k5start so that your tickets automatically get renewed in the background:

KEYTAB_FILE=~/keytabs/$USER.keytab
if command -v k5start >/dev/null && ! pgrep -u $USER k5start >/dev/null && [ -f $KEYTAB_FILE ]; then
k5start -K 60 -H 70 -b -f $KEYTAB_FILE
fi
unset KEYTAB_FILE

Tada! Now you'll automatically get a kerberos ticket on SSH/shell. You can test this by running

ssh hfcs@csclub.uwaterloo.ca klist

You should see a valid ticket from a second or two ago.

Elections Guide

2026-04-05T01:28:09Z

C256zhao: bulk namespace moving

This guide is intended to help the Chief Returning Officer (CRO), who is responsible for running the elections to select the club's executive officers.

Before reading this guide, please ensure you are familiar with the elections procedure outlined in the [https://csclub.uwaterloo.ca/about/constitution/ CSC Constitution]. This guide will focus on suggested implementation details, and does not replace the official procedure documented in the constitution.

== In-person Elections ==

=== Structure ===

There are 6 main parts to the in-person event. Suggested timestamps and lengths of each part are provided with reference to the start of the elections buffer time.

* Preparation (T0 minus 3 weeks, 2 day (preferably more))
* Nomination period (T0 minus 1 week, 2 day)
* Grace period (T0 minus 2 day)
* Absentee voting (T0 minus 1 day)
* Elections buffer time (T0)
* Elections meeting (T0 + 1 or 2 hour)

For instance,
* Preparation: starting December 10th
* Nomination period: Jan. 1st at 5:00 PM - Jan 8th 5:00 PM
* Grace period: Jan 8th 5:00 PM - Jan 9th 5:00 PM
* Absentee voting: Jan 9th 5:00 PM - Jan 10th 5:00 PM
* Buffer time: Jan 10th 5:00 PM - 6:00 PM
* Elections: Jan 10th 6:00 PM - 8:00 PM

=== Preparation ===
1. Decide on a date and a time for the elections meeting, preferably an evening on a weekday during the first week of lectures in the beginning of the term. Then, work backwards and outline a general calendar schedule for the event, keeping in mind the required lengths of time for nominations and the grace period. See example above.

2. Submit a WUSA club event form to book a room for the elections. Allow at least two weeks for WUSA to reply. Some specifics when filling out the form:

* Use <code>exec@csclub.uwaterloo.ca</code> when asked for the "Society/Club Official Email." You may leave the alternative email blank.
* When asked for rooms, if you do not have a specific room in mind, you may put "a classroom in MC or DC" or similar, then check the box that indicates the need for room-booking assistance.
* One hour and thirty minutes should be enough for the event, though it is recommended to book for two hours just in case.
* The name of the event would be <code>CSC *TERM* Elections</code>. For instance, the elections of the winter 2024 term would be <code>CSC Winter 2024 Elections</code>.
* For "Target Audience", select "restricted to society members."
* Select "yes" to "spending society funds" if you plan on purchasing snacks for the event.

3. Simultaneous with the above, submit a design request and ask for a similar design to the previous term's elections promotions post. After the design is done, submit a marketing request for the design to be marketed on the major social media platforms (i.e., IG, Discord, Facebook, LinkedIn) on the first day of nominations. See below for IG captions reference.

4. Create a private Google Drive folder and prepare the following items

*Elections one-pager, outlining the events proceedings to be referenced in preparation and execution. For reference, the one-pager for winter 2024 is shown below

W24 Elections One-Pager

Title: Winter 2024 Elections & General Meeting
Date: Thursday, January 11, 2023; 6:00 pm - 8:00 pm ET
Event Schedule:
- 5:30 - 5:50 pm - Set up (banner, slideshow, projector, any other equipment)
- 5:50 - 6:00 pm - Let people wander in, process memberships
Hand out donuts/Timbits to people at the door
- 6:05 - 6:15 pm - Quick presentation about CSC, what we do, etc.
- 6:15 - 6:30 pm - Constitutional Amendments
- 6:30 - 7:00 pm - Elections for Prez, VP, Trez, AVP; Ratification of Sysadmin
- 7:00 pm - 8:00 pm - Buffer time & Wrap-up

Location: MC 2034
- We have the room booked from 6 - 8 pm

Sign-up Form: N/A

Description: Elections for CSC's Winter 2024 Executive Council, and voting on constitution amendments. The President, Vice-President, Treasurer, and Assistant Vice-President will be elected, and the Systems Administrator will be appointed.

Materials:
- donuts/Timbits
- Laptops (for presenting + membership sign-ups)
- Machine Usage Agreement binder + membership money cup + pens
* Announcement email, similar to the following
Subject: CSC *TERM* Election Nominations

Hello everyone,

The Computer Science Club will be holding elections for the *TERM* term in person on *WEEKDAY*, *DATE* at *TIME WITH TIMEZONE* in *ROOM LOCATION*. The President, Vice-President, Assistant Vice-President, and Treasurer will be elected, and the Sysadmin will be appointed.

If you'd like to run for any of these positions or nominate someone, you can send an email to cro@csclub.uwaterloo.ca, present your nomination in-person to the CRO, *CRO NAME*, or write your nomination on the whiteboard in the CSC office (MC 3036/3037). Nominations will close on *WEEKDAY*, *DATE* at *TIME WITH TIMESTAMP*. Nominees will be reached out to for their platforms.

If you are unable to vote in person on election day, please email cro@csclub.uwaterloo.ca before *WEEKDAY*, *DATE* at *TIME WITH TIMEZONE* to request an absentee ballot. You will then receive an email containing further information on the nominee platforms and how to vote. Requests after this time will likely not be granted.

If you have any further questions about elections or nominations, please email cro@csclub.uwaterloo.ca.

--
*CRO NAME* (*PRONOUNS*)
*TERM* Chief Returning Officer (CRO)
Computer Science Club of the University of Waterloo

* Nominee platform prompt email, similar to the following.

<nowiki>
Hello,

You have been nominated for *NOMINATED POSITION* in the UW Computer Science Club for the *TERM* term. Please submit a nominee platform for the position(s) above by replying to this email with a paragraph of a maximum of 200 words per position. Your platform will be published on Discord and submitted into a document to be viewed by members.

If you have been nominated for more than one position, feel free to write more than one paragraph outlining your platform for each position. The deadline for submitting a nominee platform is *ABSENTEE VOTING START TIME*. If you do not respond by this deadline, then you will be entered into the election without a platform and will still be able to be voted for.

Elections will take place in-person on *DATE* from *START TIME* - *END TIME* in *ROOM LOCATION*. It is strongly recommended that you appear in-person where you will be asked to deliver a 2-3 minute speech about why people should vote for you for the position(s) you have been nominated for. If for any reason you are unable to show up in-person to the elections, please let me know by replying to this email beforehand.

If you have any further questions, please also email cro@csclub.uwaterloo.ca.

--
*CRO NAME* (*PRONOUNS*)
*TERM* Chief Returning Officer (CRO)
Computer Science Club of the University of Waterloo</nowiki>

* Absentee ballot email, similar to the following
Subject: CSC *TERM* Election Absentee Ballot

Hello,

This is your absentee ballot for the *TERM* CSC Election. Please do not share this link with anyone: *LINK TO ABSENTEE BALLOT*.

The form will open on *TIME* and will close on *TIME*. Please fill in the form within this window for your vote to be counted. Do not vote in person if you will vote through this form.

Nominee platforms can be found here: *LINK TO PLATFORM*

Please ensure your membership is valid for this term before you vote.

If you have any further questions, please email cro@csclub.uwaterloo.ca.

--

*CRO NAME* (*PRONOUNS*)
*TERM* Chief Returning Officer (CRO)
Computer Science Club of the University of Waterloo

* Elections IG post captions, similar to the following
🗳 The CS Club will be holding elections for the *TERM* term on *WEEKDAY*, *DATE* at *TIME* in *ROOM LOCATION*.

👉 Come to learn more about CSC, sign up for membership, and vote on our new execs! The President, Vice-President, Assistant Vice-President, and Treasurer will be elected, and the Systems Administrator will be appointed. *INCLUDE THE NEXT SENTENCE FOR CONSITUTION AMENDMENTS* Furthermore, we will vote on some changes to our constitution outlined here: <nowiki>https://csclub.ca/constitution-changes</nowiki>.

✋ If you'd like to run for any of these positions or nominate someone, you can send an email to cro@csclub.uwaterloo.ca; present your nomination in-person to the CRO, *CRO NAME*; or write your name on the whiteboard in the CSC office (MC 3036/3037). Nominations will close on *DATE* at *TIME*. Nominees will be reached out to for their platforms.

❗If you are unable to attend the elections in-person, please email cro@csclub.uwaterloo.ca by *WEEKDAY*, *DATE* at *TIME* in order to request an absentee ballot and vote remotely.

❓ If you have any questions about elections, please email cro@csclub.uwaterloo.ca.

* Curated document of nominee platforms, in the following format for each position and nominee,

*Title* (ex. President)

*Nominee 1 Name* (*Nominee 1 WatIAM ID*) (ex. John Doe (j88doe))

*Submitted platform*

*Nominee 2 Name* (*Nominee 2 WatIAM ID*) (ex. Jane Doe (j99doe))

*Submitted platform*

* Slideshow to present at the meeting, with a brief introduction to the club outlining the clubs visions, past events and initiatives, the office space, and what membership means for members.
* Absentee ballot form, asking the following mandatory questions:
*#Waterloo email
*#WatIAM ID (e.g., t27ding)
*#Ranking for each of the nominees for each of the positions (1, 2, 3, ..., decline to rank)
*#Ratification of Sysadmin
*#(if applicable) Ratification of constitution amendments

=== Nomination Period ===
1. Announce that nominations are open by sending the prepared elections announcement email to <code>csc-general@csclub.uwaterloo.ca</code>. Note that the email will have to be accepted by syscom or other execs before being sent out and will only contain plain text (aka, fancy formatting such as links and bolds will not show up (as of Winter 2024)).

Ensure the marketing team has made the requested posts on the requested platforms.

Note that Nominations should remain open for at least a week, as specified in the [https://csclub.uwaterloo.ca/about/constitution/ constitution].

2. Keep track of all nominations received during the nomination period, consolidating nominations from different sources if applicable. Ensure that nominees are actually eligible to run (ie. undergraduate students who are CSC members).

Send the prepared nominee platforms email to each of the nominees (you may send one email prompting for multiple positions), requesting a platform.

Once the platforms come in, add them to the nominee platforms document, which should be publically available (via public Google Doc or similar) and easily accessible (ex. QR-code in the office, link in Discord, etc.).

3. Decide on whether or not to offer food/snacks at the elections (Timbits are a good choice if you are unsure of what to purchase). We should have ~$30 allocated to the elections meeting.

=== Absentee voting period ===

1. Note down the name and email of individuals who've requested for absentee ballot.

2. Be sure the form opens at the specified time and closes at the specified time.

3. Whether or not the absentee ballot are to be provided to those who make a request during this period is up to the CRO's discretion.

4. After this time ends, count the votes. You may wish to leave a good chunk of time to count rank-based voting as it may be complicated to discern the number of votes for each person, especially if candidates are running for multiple positions.

=== The Big Day ===

1. Count the number of eligible voters who come (eg. by asking people at the door) and ensure that quorum is met. Eligible voters are undergraduate students who have paid their CSC membership fee for the term. It is a good idea to have a setup by the door for people to become members/renew their membership.

2. Keep track of meeting minutes (or designate someone else to help track meeting minutes), noting down when the elections begin + end, and when each position is elected. Refer to the [[Meeting:Meetings/2022-05-05|Spring 2022 Election Meeting Minutes]] for an example.

3. [Optional] Give a brief (2-5 minutes) introduction to CSC, or designate some other qualified person to do this, in case someone has wandered in with no idea what this club is about.

4. Preside over the elections for each position, as specified in the [https://csclub.uwaterloo.ca/about/constitution/ constitution]. For each position:
* Clearly announce all candidates, verbally and/or visually (eg. by writing on the board or by screen-sharing an electronic document). Also remember to announce the option to abstain.
* [Optional] If there are several candidates, it might be helpful to have each candidate quickly (2-3 minutes seconds) introduce themself and their reasons for running.
* Instruct all present individuals to lower their heads, and then go through the list of candidates, counting and recording the number of votes (raised hands) for each. Note that the CRO may not vote except to break a tie, however candidates and already-elected execs are allowed to vote. Alternatively, use the webcom's voting app (still in progress as of Winter 2024) and proceed similarly. Do not count the votes of non-eligible individuals (i.e., non-members).
* Announce the winner, optionally revealing the numbers of votes for each candidate.

5. For taking nominations from the floor (ie. in the case that there were no nominations for that position during the nomination period), give people a few minutes to talk to the CRO to nominate themselves/others, then follow the same voting process as usual.

6. For ratifying the sysadmin, allow the elected officers to announce their choice, then follow the same voting process as usual.

7. After the elections have concluded, add the meeting minutes to the Wiki here: [[Meeting:Meetings]]. Don't forget to serve snacks (if present)!

8. Announce the results more broadly by sending an email following this template to <code>csc-general@csclub.uwaterloo.ca</code>, and/or by adding an announcement to the CSC website. Note that the email would have to be accepted by syscom before being sent out.
<nowiki>
SUBJECT: [TERM] Election Results

[TERM] elections have concluded. Here are your executives for the term:

President: [NAME] ([USERID])
Vice-President: [NAME] ([USERID])
Assistant Vice-President: [NAME] ([USERID])
Treasurer: [NAME] ([USERID])
Sysadmin: [NAME] ([USERID])

--
[NAME] ([PRONOUNS])
[ROLE, eg. [TERM] Chief Returning Officer]
Computer Science Club of the University of Waterloo</nowiki>
9. Be sure to take down all elections related setups (info on office whiteboard, nominee-platforms discord channel, etc.) and upload the private Google Drive Folder to the appropriate CSC Drive folder (removal of the voting Google Form is optional, but recommended, in order to keep confidentiality).

== Online Elections ==

Elections should only be held online if the University has suspended in-person activity for the beginning of a term, as was the case during the COVID-19 pandemic.

=== Nominations ===

Announce that nominations are open by sending an email following this template (approximately) to <code>csc-general@csclub.uwaterloo.ca</code>. Note that the email will have to be accepted by syscom before being sent out.
<nowiki>
SUBJECT: [TERM, eg. Winter 2022] Election Nominations

Hello everyone,

Due to the closure of campus this term, the Computer Science Club will be holding elections for [TERM] virtually. The president, vice-president, treasurer, and assistant vice-president (formerly secretary) will be elected, and the sysadmin will be appointed.

If you'd like to run for any of these positions or nominate someone, please email cro@csclub.uwaterloo.ca. Nominations will close on [DATE] at {TIME].

If you have any further questions about elections or nominations, please email cro@csclub.uwaterloo.ca.

--
[NAME] ([PRONOUNS])
[TERM] Chief Returning Officer (CRO)
Computer Science Club of the University of Waterloo</nowiki>
Nominations should remain open for at least a week, as specified in the [https://csclub.uwaterloo.ca/about/constitution/ constitution].

=== Elections ===

1. Go to https://civs1.civs.us/ and press "Create a poll."

2. Name the poll following this template: <code>CSC [TERM, eg. Winter 2022] Elections</code>

3. The name of the supervisor should be the name of the CRO. The email address of the supervisor should be an email that the CRO has access to, ie. either <code>cro@csclub.uwaterloo.ca</code>, or the CRO's personal csclub.uwaterloo.ca email.

4. Insert the date and time you plan to stop the poll. Note that this isn’t automatic - you'll have to manually stop it later on.

5. For the description section, follow this template:
<nowiki>
This is the CSC Executive Election for the [TERM, eg. Winter 2022] term. We have [NUMBER] people running for four different positions. Rank the choices in order of preferences, and the top four non-conflicting options will be chosen. For example, if the aggregate results in order of votes are: Juthika for President, Nobody for President, Eric for VP, Nobody for VP, then both Juthika and Eric will be confirmed to their respective roles. Conversely, if the results in order of votes are: Juthika for President, Nobody for VP, Eric for VP, Nobody for President, then only Juthika will be confirmed and the VP position will remain unfilled.</nowiki>

6. For the names of choices, enter all the candidates in the order of President, VP, Treasurer, and AVP, following this template:
<nowiki>
[NAME] for President
[NAME] for Vice President
[NAME] for Treasurer
[NAME] for Assistant Vice President
Nobody for President
Nobody Vice President
Nobody for Treasurer
Nobody for Assistance Vice President</nowiki>

7. For the number of choices will win, enter '''4'''.

8. For the question "Do you want the poll to be private or public?", click on Public.

9. Under more options, check off "Present choices on voting page in exactly the given order."

10. Make sure that all of the dates and names are correct!

11. Click "Create poll."

12. The CRO should receive an email with a link to start and stop the poll, and a public link for voting.

13. Click the link that will allow you to start/stop the poll, and start the poll.

14. Using the script in CSC's repo, find out who are eligible CSC members for the term. Unfortunately, this may include some Alumni emails.

15. Copy and paste the list of eligible emails into the '''BCC''' part of an email, and put <code>exec@csclub.uwaterloo.ca</code> as the '''To''' part of the email.

16. Write the body of the email using the following template:
<nowiki>
SUBJECT: Computer Science Club [TERM, eg. Winter 2022] Elections

Note: This email is intended for undergraduate members of the Computer Science Club. Please ignore it if you are not an undergraduate member.

Hello everyone,

CSC is currently having its elections for the [TERM, eg. Winter 2022] term, and would like to invite you to vote. You can vote at this link: [LINK]

Voting will close on [DATE] at [TIME].

--
[NAME] ([PRONOUNS])
[TERM] Chief Returning Officer (CRO)
Computer Science Club of the University of Waterloo</nowiki>

17. Send the email to commence voting!

18. Close the poll at the specified time, and announce the results following the same process as outlined the [[#In-person Elections]] guide.

Exec Todo

2026-04-05T01:27:00Z

C256zhao: bulk namespace moving

Update wiki pages:
* [[Alumni Project]]
* [[Budget Guide]]
* [[Clothing Ideas]]
* [[Enhancement Project]]
* [[History]]
* [[Library]]
* [[Meeting:Meetings]] which is kind of worthless
* [[Mentorship]]
* [[New Member Guide]]
* [[Office Staff]] should probably be merged with [[Office Policies]]
* [[Other Clubs]] should get a look
* Merge [[Propaganda]] and [[Publicity Guide]]
* [[SCS Guide]]
* [[Security Workshops]] <-- might wanna tag that as F13
* Merge [[Space Project]] and [[Space plan]]
* [[Talk Archive]] <-- [[User:Ehashman]] should probably update this

Meeting:Meetings

2026-04-05T01:24:07Z

C256zhao: bulk namespace moving

==Minutes of Meetings (Executive)==
* [[Meeting:Tuesday 16 September 2008]]

==General Meetings==

* [[Meeting:Meetings/2025-01-13|Monday 13 January 2025]]
* [[Meeting:Meetings/2024-01-11|Thursday 11 January 2024]]
* [[Meeting:Tuesday 12 September 2023]]
* [[Meeting:Wednesday 11 May 2023]]
* [[Meeting:Meetings/2023-01-12|Thursday 12 January 2023]]
* [[Meeting:Meetings/2022-09-12|Monday 12 September 2022]]
* [[Meeting:Meetings/2022-05-05|Thursday 5 May 2022]]
* [[Meeting:Thursday 2 October 2008]]
* [[Meeting:Friday 19 October 2007]]

==Weekly All-Hands Meetings==
* [[Meeting:Monday 5 December 2022]]
* [[Meeting:Monday 28 November 2022]]
* [[Meeting:Monday 21 November 2022]]
* [[Meeting:Monday 14 November 2022]]
* [[Meeting:Monday 7 November 2022]]
* [[Meeting:Monday 31 October 2022]]
* [[Meeting:Monday 24 October 2022]]
* [[Meeting:Monday 17 October 2022]]
* [[Meeting:Monday 3 October 2022]]
* [[Meeting:Sunday 21 March 2021]]
* [[Meeting:Sunday 14 March 2021]]
* [[Meeting:Sunday 7 March 2021]]
* [[Meeting:Sunday 28 February 2021]]

== Termcom/Syscom Meetings ==
* [[Meeting:09 Mar 2025 Termcom Meeting]]
* [[Meeting:Saturday 29 July 2023 Termcom Meeting]]
* [[Meeting:Saturday 24 June 2023 Termcom Meeting]]
* [[Meeting:Saturday 10 June 2023 Termcom Meeting]]
* [[Meeting:Saturday 27 May 2023 Termcom Meeting]]
* [[Meeting:Saturday 13 May 2023 Termcom Meeting]]
* [[Meeting:Saturday 25 March 2023 Termcom Meeting]]
* [[Meeting:Saturday 11 February 2023]]
* [[Meeting:Saturday 31 May 2024 Termcom Meeting]]

== Source ==

* '''CSC All-hands Meeting Notes - Fall 2022''': https://docs.google.com/document/d/1Tl_E5nM3bguw9if9O2Woc4jNmeZxG7QVel5fzHdZgfQ/edit#

[[Category:Meetings]]

Finance:Budget/W2009

2026-04-05T01:22:20Z

C256zhao: bulk namespace moving

See also: [[Finance:Budget/F2008]] and [[Finance:Budget/S2009]]

==Wishlist==

* CD-R's
* Whiteboard markers
* New binder for MUP
* Whiteboard eraser,
* Cat 5e
* Sticky notes
* PDP-8
* Velcrow cable ties
* Rails
* Logo stamp
* Tapes for the video camera

==Proposed Budget==
{| class="wikitable"
|+ Fall 2008
|-
| '''Revenue''' || Revenue
|-
| * Membership Fees (MathSoc) || 294 (147 mathsoc members * 2)
|-
| * Membership Fees (Non-MathSoc) || 82 (41 nonmathsoc members * 2)
|-
| '''Total Revenue''' || 376
|-
| '''Expenses''' ||
|-
| '''Events''' ||
|-
| * 3 Code Parties || 180
|-
| * SIGGRAPH || 40
|-
| * Office Day || 40
|-
| * Pentathalon || 20
|-
| '''Events Total''' || 280
|-
| '''Talks''' ||
|-
| * IQC || 90
|-
| * Prabhakar Ragde || 90
|-
| * Computer Graphics Lab (2) || 180
|-
| * Student Projects || ??
|-
| '''Talks Total''' || 270
|-
| '''Office Supplies''' ||
|-
| * CDs || 50
|-
| * Whiteboard Markers || 30
|-
| * Tape || 10
|-
| * Scotchgaurd || 20
|-
| * Safe || 400
|-
| '''Office Supplies Total''' || 510
|-
| '''Other''' ||
|-
| * Appreciation || 120
|-
| * Hardware Failure || 200
|-
| '''Other Total''' || 320
|-
| '''Requested Total''' || 1380
|-
| '''MathSoc Funding Cap''' || 147 * 9.50 = 1396.50
|-
|}

[[Category:Budget|Budget200901]]

Finance:MEF Proposals/W2008

2026-04-05T01:22:16Z

C256zhao: Text replacement - "[[MEF Proposals/" to "[[Finance:MEF Proposals/"

See also: [[Finance:MEF Proposals/F2007]] and [[Finance:MEF Proposals/S2008]]

== Mirror ==

[[Category:MEF]]

Finance:MEF Proposals/S2008

2026-04-05T01:22:13Z

C256zhao: Text replacement - "[[MEF Proposals/" to "[[Finance:MEF Proposals/"

See also: [[Finance:MEF Proposals/W2008]] and [[Finance:MEF Proposals/F2008]]

== UPS ==

[[Category:MEF]]

Finance:MEF Proposals/F2007

2026-04-05T01:22:10Z

C256zhao: Text replacement - "[[MEF Proposals/" to "[[Finance:MEF Proposals/"

See also: [[Finance:MEF Proposals/S2007]] and [[Finance:MEF Proposals/W2008]]

== New mirror server(s) ==

=== Background ===

* The CSClub is running a mirror for Debian and Ubuntu GNU/Linux distributions.
* Before this, there was no local Debian or Ubuntu mirror. We became a mirror in response to many CSClub members (and non-members) requesting this service.
* The machine that is running the mirror is under-powered and over-loaded for the task of mirroring, so we would like to replace the machine.

=== Who will this benefit? ===

* This will benefit members of the university interested in Linux and open-source software.
* We also plan to mirror additional archives as resources permit, so more people will likely benefit from this project.

=== What will the machine be used for? ===

* Mirroring Linux and other software distributions

=== What exactly are you asking for? ===

* 4U Antec case with 550W power supply ($285)
* Rails (2 x $45 = $90)
* Gigabyte GA-P35-DS3R motherboard ($155)
* Intel Core 2 Duo E6550 processor ($200)
* G.SKILL F2-6400CL5D-4GBPQ PC2-6400 4GB 2X2GB RAM (2 x $200 = $400; 8 GB total)
* Seagate Barracuda 7200.10 SATA2 160GB disk ($65; root disk)
* Seagate Barracuda 7200.10 SATA2 750GB disks (4 x $240 = $960; 3 TB total; mirror disks)
* Intel PRO/1000 PT Server Gigabit PCI Express network adapter ($90)
* SATA cables (5 x $4 = $20)
* 120mm fan ($11)

Total = $2276

We are looking at purchases two of these servers, but we would accept funding for only one.

=== How would you acknowledge MEF's contribution ===

* We would add a notice to the main mirror page indicating that hardware was provided by the Mathematics Endowment Fund, and provide a link to MEF's site.
* We would attach a MEF sticker to the front/side of the server(s).

=== Anticipated questions ===

* CSCF runs a mirror service (mirror.cs). Why can't people use this?
** Mirror.cs is not available to off-campus users.
** The CSClub mirror is already established as an official Ubuntu, Debian, and OpenOffice mirror.
** We would also like to mirror files/distributions that CSCF doesn't mirror.

[[Category:MEF]]

Finance:Budget/S2008

2026-04-05T01:21:52Z

C256zhao: bulk namespace moving

See also: [[Finance:Budget/W2008]] and [[Finance:Budget/F2008]]

The following budget was approved in the MathSoc council meeting on June 17, 2008.

{| class="wikitable"
|+ Summer 2008
|-
|'''Revenue''' ||Revenue
|-
| * Membership Fees (in faculty of Math) || 240
|-
| * Membership Fees (outside faculty of Math) || 84
|-
|'''Total Revenue''' || 324
|-
|'''Expenses''' ||
|-
|'''Events''' ||
|-
| * Movie Night || 50
|-
| * SIGGRAPH Night || 60
|-
|'''Talks''' ||
|-
| * 3 talks || 150
|-
| * Michael Geist || 500
|-
|'''Total for Events''' || 760
|-
|'''Office Supplies''' ||
|-
| * UV lamp/bulb || 25
|-
| * Network cable || 100
|-
| * Books || 100
|-
| * Rails || 100
|-
| * Whiteboard Markers || 15
|-
| * CDs || 10
|-
| * CD Sleeves || 10
|-
| * Bank Fees || 15
|-
|'''Total for Office Supplies''' || 375
|-
|'''Total''' || 1135
|-
|'''Total Minus Revenue''' || 811
|-
|'''MathSoc Funding Cap''' || 1140
|-
|}

== Budget Ideas ==
Kinda Need
* Book: Matrix Computations by Gene Golud, Charles Van Loan: $55
* Cat5 spool: $100
* PCI serial ports: 2 x $40 = $80
* Case for acesulfame-potassium (no PSU needed): $70
* Rails (caffeine and artificial-flavousrs): 2 x $50 = $100

Like To Need
* Speaker wires: $20
* Webcam (640x480 minimum): $60
* Disks for taurine (375861-B21): 2 x $290 = $580

Kinda Don't Need
* 750G music/backup disks: 2 x $145 = $290

Talks/Events
* SIGGRAPH Night Refreshments: $60

Office Supplies
* White board markers: $15
* CD markers: $5
* Cotton swabs: $5
* CD sleeves (100 pack): 2 x $4 = $8

[[Category:Budget|Budget200805]]

Finance:Budget/W2008

2026-04-05T01:21:50Z

C256zhao: bulk namespace moving

See also: [[Finance:Budget/F2007]] and [[Finance:Budget/S2008]]

== Initial Budget (Approved) ==

{| class="wikitable"
|+ Winter 2008 Budget
|-
|'''Revenue''' ||Revenue
|-
| * Membership Fees (in faculty of Math) || 274
|-
| * Membership Fees (outside faculty of Math) || 68
|-
|'''Total Revenue''' || 342
|-
|'''Expenses''' ||
|-
|'''Events''' ||
|-
| * Linux Awareness Week || 30
|-
| * Movie Night || 50
|-
|'''Talks''' ||
|-
| * RIM Feb 1st || 40
|-
| * Week of Feb 25th, IQC || 75
|-
| * Week of Mar 3rd, second IQC || 75
|-
| * Week of Mar 10th, Game theory, Kate Larson || 75
|-
|'''Programming contests''' ||
|-
| * Feb 14th - Risk || 45
|-
| * Programming contest Mar 27th Robocode or Tron || 45
|-
|'''Total For Events''' || 435
|-
|'''Office''' ||
|-
| * White Board Markers, per package || 6
|-
| * Extension cord || 10
|-
| * Tape || 10
|-
| * Misc Office expenses || 15
|-
| * Banking fees || 15.60
|-
| * Hardware repairs || 200
|-
| * USB extension cable || 5
|-
| * Wireless Router || 80
|-
|'''Total For Office''' || 341.60
|-
|'''Total''' || 776.60
|-
|'''Total Including A-F''' || 1352.60
|-
|'''Total minus Revenue''' || 1010.60
|-
|}

== Artificial-flavours Upgrades (Approved) ==

{| class="wikitable"
| Western Digital SE16 500GB SATA2 Disk (x2) || 206
|-
| Corsair XMS2 TWIN2X2048-5400C4 2GB 2X1GB || 46
|-
| Intel Pentium Dual Core E2160 1.8Ghz Processor || 75
|-
| Intel S3000AH Server Board || 198
|-
| ||
|-
| Subtotal || 525
|-
| Tax/Shipping || 51
|-
| '''Total''' || 576
|}

== Additional Hardware (Approved) ==

{| class="wikitable"
|-
| Disk for artificial-flavours || 55 || Replacing disk that recently died
|-
| Rackmount case for artificial-flavours || 230 || CSCF prefers rackmount cases over desktop cases
|-
| Rails for case || 43 || Rails are needed to secure a rackmount case in a rack
|-
| Null modem cables (4) || 12 || If network dies on a machine, we can still connect using a null-modem/serial port connection
|-
| Gigabit NIC for acesulfame-potassium || 25 || Acesulfame-potassium is an office terminal and we tend to transfer large files over the network, so we need a fast network card
|-
| Shipping || 6 || -
|-
| Tax || 20 || -
|-
| '''Total''' || '''391''' || -
|}

[[Category:Budget|Budget200801]]

Finance:Budget/S2009

2026-04-05T01:21:47Z

C256zhao: bulk namespace moving

See also: [[Finance:Budget/W2009]] and [[Finance:Budget/F2009]]

==Proposed Budget==

{| class="wikitable"
|+ Spring 2008
|-
| '''Revenue''' ||
|-
| * MathSoc Members || 118
|-
| * Non-MathSoc Members || 37
|-
| * Membership Fees || 310
|-
| '''Expenses''' ||
|-
| '''Events''' ||
|-
| * 3 Code Parties || 180
|-
| * SIGGRAPH || 40
|-
| * Sci Fi Movie Night || 50
|-
| * Talks || 270
|-
| '''Events Total''' || 540
|-
| '''Office Supplies''' ||
|-
| * CDs || 57
|-
| * Whiteboard Markers || 24
|-
| * Labelmaker Tape || 20
|-
| * Three Hole Punch || 15
|-
| '''Office Supplies Total''' || 116
|-
| '''Technology''' ||
|-
| * Networking Supplies || 150
|-
| * Acesulfame-Potassium Upgrades || 578
|-
| * Soldering Iron || 10
|-
| '''Technology Total''' || 738
|-
| '''Miscellaneous''' ||
|-
| * Bank Fees || 17
|-
| * Photocopying || 20
|-
| '''Miscellaneous Total''' || 37
|-
| '''Total Expenses''' || 1431
|-
| '''Requested Funding''' || 1121
|-
| '''MathSoc Funding Cap''' || 1121
|-
|}

[[Category:Budget|Budget200905]]

Finance:Budget/F2008

2026-04-05T01:21:44Z

C256zhao: bulk namespace moving

See also: [[Finance:Budget/S2008]] and [[Finance:Budget/W2009]]

==Wishlist==

* CD-R's
* Whiteboard markers
* CD markers
* CD sleeves
* New binder for MUP
* Whiteboard eraser,
* Cat 53
* Sticky notes
* PDP-8
* Velcrow cable ties
* Rails
* Logo stamp
* Tapes for the video camera

* Switch: http://www.newegg.ca/Product/Product.aspx?Item=N82E16817111479&Tpk=TEG-S80TXE

==Proposed Budget==
{| class="wikitable"
|+ Fall 2008
|-
| '''Revenue''' ||Revenue
|-
| * Membership Fees (MathSoc) || 450.00
|-
| * Membership Fees (Non-MathSoc) || 86.00
|-
| '''Total Revenue''' || 536.00
|-
| '''Expenses''' ||
|-
| '''Talks''' ||
|-
| * Theo de Raadt || Unknown
|-
| * Jeff Siskind || 0
|-
| * Relic CTO || Unknown
|-
| * Faculty Talk || 75.00
|-
| * IQC || 75.00
|-
| '''Talks Total''' || 150 + Unknown
|-
| '''Office Supplies''' ||
|-
| * Cat 5e || 118.64
|-
| * Other (Details Later) || 140.17
|-
| '''Office Supplies Total''' || 258.81
|-
| '''Total''' || 584.98
|-
| '''Total minus Revenue''' || TBA
|-
| '''MathSoc Funding Cap''' || 2137.50
|-
|}

[[Category:Budget|Budget200809]]

Meeting:Meetings

2026-04-05T01:20:18Z

C256zhao: bulk namespace moving

==Minutes of Meetings (Executive)==
* [[Meeting:Tuesday 16 September 2008]]

==General Meetings==

* [[Meetings/2025-01-13|Monday 13 January 2025]]
* [[Meetings/2024-01-11|Thursday 11 January 2024]]
* [[Meeting:Tuesday 12 September 2023]]
* [[Meeting:Wednesday 11 May 2023]]
* [[Meetings/2023-01-12|Thursday 12 January 2023]]
* [[Meetings/2022-09-12|Monday 12 September 2022]]
* [[Meetings/2022-05-05|Thursday 5 May 2022]]
* [[Meeting:Thursday 2 October 2008]]
* [[Meeting:Friday 19 October 2007]]

==Weekly All-Hands Meetings==
* [[Meeting:Monday 5 December 2022]]
* [[Meeting:Monday 28 November 2022]]
* [[Meeting:Monday 21 November 2022]]
* [[Meeting:Monday 14 November 2022]]
* [[Meeting:Monday 7 November 2022]]
* [[Meeting:Monday 31 October 2022]]
* [[Meeting:Monday 24 October 2022]]
* [[Meeting:Monday 17 October 2022]]
* [[Meeting:Monday 3 October 2022]]
* [[Sunday 21 March 2021]]
* [[Sunday 14 March 2021]]
* [[Sunday 7 March 2021]]
* [[Sunday 28 February 2021]]

== Termcom/Syscom Meetings ==
* [[09 Mar 2025 Termcom Meeting]]
* [[Meeting:Saturday 29 July 2023 Termcom Meeting]]
* [[Meeting:Saturday 24 June 2023 Termcom Meeting]]
* [[Meeting:Saturday 10 June 2023 Termcom Meeting]]
* [[Meeting:Saturday 27 May 2023 Termcom Meeting]]
* [[Meeting:Saturday 13 May 2023 Termcom Meeting]]
* [[Meeting:Saturday 25 March 2023 Termcom Meeting]]
* [[Meeting:Saturday 11 February 2023]]
* [[Meeting:Saturday 31 May 2024 Termcom Meeting]]

== Source ==

* '''CSC All-hands Meeting Notes - Fall 2022''': https://docs.google.com/document/d/1Tl_E5nM3bguw9if9O2Woc4jNmeZxG7QVel5fzHdZgfQ/edit#

[[Category:Meetings]]

Meeting:Orgcom Updates/Syscom and Termcom 2023 Fall

2026-04-05T01:20:09Z

C256zhao: bulk namespace moving

== December 28, 2023 ==

* '''Meeting Notes''':

== December 14, 2023 ==

* '''Meeting Notes''':

== November 30, 2023 ==

* '''Meeting Notes''':

== November 16, 2023 ==

* '''Meeting Notes''':

== November 2, 2023 ==

* '''Meeting Notes''':
* Installed and setup X99 office terminal with CSC systems

== October 19, 2023 ==

* '''Meeting Notes''':
* Diarized server room maintenance visit

== October 5, 2023 ==

* '''Meeting Notes''': [[Meeting:Saturday 14 October 2023 Termcom Meeting]]
* Talked to CSCF about hardware acquisition
* Determined potential CSC Cloud server specifications
* Got quote for CSC Cloud server through CSCF
* Assembled new team for Mirror Checker rewrite.
* CSC Cloud and CSC Club Rep Infrastructure Upgrades
* Web Hosting maintenance

== September 21, 2023 ==

* '''Meeting Notes''': [[Meeting:Saturday 23 September 2023 Termcom Meeting]]
* Researched new CSC Cloud server specifications
* Started new PyCeo tickets:
** https://git.csclub.uwaterloo.ca/public/pyceo/issues/103
* Continued development on new Linux mirror monitoring software
* Reached out to CSCF about Netapp migration
* Managed dozens of member registrations
* Onboarded a dozen club reps and new clubs/design-teams for club hosting for F23
* Revamped observability stack of CSC infrastructure (Vector and ClickHouse)
** Improved data durability and metric quality
** Improved monitoring capabilities and system reliability
* Mitigated security risks with banned member
* Performed system upgrades to some General Use machines (Debian Bookworm upgrade and migration)

Meeting:Meetings

2026-04-05T01:15:24Z

C256zhao: bulk namespace moving

==Minutes of Meetings (Executive)==
* [[Tuesday 16 September 2008]]

==General Meetings==

* [[Meetings/2025-01-13|Monday 13 January 2025]]
* [[Meetings/2024-01-11|Thursday 11 January 2024]]
* [[Tuesday 12 September 2023]]
* [[Wednesday 11 May 2023]]
* [[Meetings/2023-01-12|Thursday 12 January 2023]]
* [[Meetings/2022-09-12|Monday 12 September 2022]]
* [[Meetings/2022-05-05|Thursday 5 May 2022]]
* [[Thursday 2 October 2008]]
* [[Friday 19 October 2007]]

==Weekly All-Hands Meetings==
* [[Meeting:Monday 5 December 2022]]
* [[Meeting:Monday 28 November 2022]]
* [[Meeting:Monday 21 November 2022]]
* [[Meeting:Monday 14 November 2022]]
* [[Meeting:Monday 7 November 2022]]
* [[Meeting:Monday 31 October 2022]]
* [[Meeting:Monday 24 October 2022]]
* [[Meeting:Monday 17 October 2022]]
* [[Meeting:Monday 3 October 2022]]
* [[Sunday 21 March 2021]]
* [[Sunday 14 March 2021]]
* [[Sunday 7 March 2021]]
* [[Sunday 28 February 2021]]

== Termcom/Syscom Meetings ==
* [[09 Mar 2025 Termcom Meeting]]
* [[Saturday 29 July 2023 Termcom Meeting]]
* [[Saturday 24 June 2023 Termcom Meeting]]
* [[Saturday 10 June 2023 Termcom Meeting]]
* [[Saturday 27 May 2023 Termcom Meeting]]
* [[Saturday 13 May 2023 Termcom Meeting]]
* [[Saturday 25 March 2023 Termcom Meeting]]
* [[Saturday 11 February 2023]]
* [[Saturday 31 May 2024 Termcom Meeting]]

== Source ==

* '''CSC All-hands Meeting Notes - Fall 2022''': https://docs.google.com/document/d/1Tl_E5nM3bguw9if9O2Woc4jNmeZxG7QVel5fzHdZgfQ/edit#

[[Category:Meetings]]

Meeting:Term Notes/W2010

2026-04-05T01:13:54Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/F2009]] and [[Meeting:Term Notes/S2010]]

= Prez Notes =
* bought new fridge and registered it with manufacturer (in name of Lord Calum Dalek, exec@csclub)
* with CIF money ordered 2 new office chairs and a new desk (a-f, thin-client, and O2)
* Power Outage on the 24,25 we had some experience booting our core servers
* floor waxing on the 26th, machines and desks were dusted off
* Google-sponsored programming contest was a big hit, thanks to j3camero for that

== Things to do in Future Terms ==
* Keys are now arranged through SCS, rather than MathSoc (except for Prez MathSock key)
* Keep up the new Office Staff method and policy
* We were given MEF funding for new disks for the mirror. Profs want us to mirror Fedora. Talk to Dave Gawley of CSCF who is supplying partial funding.
* Monthly Meeting with MWG: good for discussion things like funding
* CS Exec Meeting, UAC Meeting, we need to send reps to these '''every term'''
* Need to make us a Student Chapter of the ACM again, need student members...
* "CS10" lecture series that we had (mostly) in DC1304 was very successful, we need to keep up the momentum with these
* Still need to ask PlantOps-maintenance people for: new shelves (CIF funding), coathooks in the walls

= Veep Notes =
* Gerald Sussman is coming May 24,25. Jacob Parker is the point of contact and primary organizer on progcom, with Edgar Bering helping out.
* Edgar Bering is trying to get in touch with John H. Conway for a talk/panel, he will keep you posted on the efforts, and may come asking for money to support it.
* DC1304 is booked for the Tuesday slot we had for CS10, they were very successful, with both prof and member talks. I suggest that as soon as you are elected you put out
a call for member talks (and put one with a deadline) and get together a shortlist of professors you would like to hear from.
* Edgar Bering has a cocktail of publicity scripts. They will be in a git repo in /users/exec/veep/ and handle a large portion of advertising an event, considering their spammy nature I'm not sure placing them in a public git repo is a good idea, feel free to contradict my judgment.
* Open Shot is installed on Natural Flavours and is a very nice program for video editing. There is a /video directory there for storing high quality masters.
* There are also nice logo templates for making title cards. A wiki article might go up on video mastering for talks.
* Brennan Taylor has created a bunch of talk encoding scripts that are in the CSC git repo.
* We still owe John Watrous dinner. Edgar Bering will try to make this happen, it goes on last terms budget and I believe we are still able to claim it. Double check with MathSoc and re-budget if necessary.
* A CSC Frisbee team might be cool, MathSoc has funding for such things.
* Code Parties are always good fun, and you can find one person to do most of the organization for them.
* The membership has spoken: Last term we ran a talk a week, and they were almost always very well attended, so try to keep that pace.
* Coffee and Doughnuts can be ordered from the CnD for about $30 for a talks worth, they come on a cart and everything.
* There is probably more that can go here that I don't recall at this time. Feel free to ask me (Edgar Bering) any other questions you may have about the job.

= Others' Notes =
post-mortems

[[Category:Term_Notes|TermNotes201001]]

Meeting:Term Notes/S2010

2026-04-05T01:13:24Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/W2010]] and [[Meeting:Term Notes/F2010]]

no notes?

[[Category:Term_Notes|TermNotes201005]]

Meeting:Term Notes/W2009

2026-04-05T01:13:11Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/F2008]] and [[Meeting:Term Notes/S2009]]

== Reminders for Veep ==

# MEF Has given us $600 to purchase a digital cutter and adobe illustrator. These need to be purchased, and billed to MEF.

Done. Cutter documented at [[Digital Cutter]].

# Joel Spolsky is coming on Jan 22. His hotel has been arranged by ebering. A room needs to be booked. Funding is from MEF.

Joel came, we had a good time, monies were changed about and the talk was recorded. He's a nice guy, fills a room.

# We have funding to bring Michael Geist, however we need to finish tagging up with him.

Geist backed out.

# RMS is coming on Jan 29. His accommodations are likely to be handled by someone in Toronto, but if they back out we'll need to find a place for him. HH Theatre has been booked tentatively, pending conformation with RMS for changing the talk time. If he doesn't agree we need to book AL. All of it.

This was madness. But it happened and is done.

# Craig Kaplan has agreed to give us a series of lectures on NPR and computer generated abstract geometry, using our shiny new digital cutter. Be sure we work with him to run these.

This ended up as one talk which was successful and recorded. See [[Talks]] for future collaboration ideas.

# The IQC really wants to give us talks, they like us. Make sure they're spoken to, mgregson has sent out the preliminary invitation.

These happened as talks and lab tours and a potential future arrangement.

# Unix tutorials are currently available on the page given in the F2008 term notes, if ebering moves them yell at him. Also, try and expand on the body of knowledge, a unix 103 and 104 would be nice.

Didn't get expanded, but were held.

# /users/exec/veep/* has more things of use/interest including publicity tools and specific templates for putting together events.

It actually doesn't. I (Ebering) should get on fixing that...

== Reminders for Librarian ==

# The books were scanned in, cataloged, categorized, and shelved in an orderly fashion. See [[Library project]] for the current status.
# There is a large deficiency between the library, modern reference, and the current curriculum, perhaps a MEF proposal to correct this.

[[Category:Term_Notes|TermNotes200901]]

Meeting:Term Notes/W2011

2026-04-05T01:13:08Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/F2010]] and [[Meeting:Term Notes/S2011]]

= Prez Notes =

= Veep Notes =

= Trez Notes =
* Signing authority process is almost normal, but the addition start now is that we also have to sign a second ID form for each signing officer. See the forms in the safe.

= Secz Notes =

[[Category:Term_Notes|TermNotes201101]]

Meeting:Term Notes/F2009

2026-04-05T01:13:02Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/S2009]] and [[Meeting:Term Notes/W2010]]

= Veep Notes =

== Talks ==

Details on pending talk activities can be found on the progcom mailing list.

Confirmed invitations from:
* Geoff Hinton - ebering is heading up this, Jan26, SCS funding secured.
* Paul Lutus - jmsaunde is heading up this, Jan18 tentative, funding unknown, many details to be worked out asap. Talk will be done via videoconference
* Gerald Sussman - j3parker is heading up this, May-June tentative, funding partly form SCS, should submit MEF proposal as well, multiple talks.

Invitation from Conway has heard nothing :(

No new invitations sent out, should do this some time in January to fill program for the rest of spring and into next fall. Ideas include the original ENIAC programmers, if they're still able.

Prabhakar and Kaplan might also be willing to give talks, they make usual goto guys from the faculty. Other faculty talks (Kate Larson?) should be explored.

== Contests ==

j3camero ran a successful Google sponsored contest in the Fall, we had a large participation and whatnot. It was not all peaches and roses, there were lapses in implementation (not enough documentation, not well tested starter packages, engine bugs). These can be hammered out by getting more people to work on the contest, a contest committee mailing list was created for this purpose. ebering has a large amount of software for a contest, but the 90%-90% rule is coming into effect on it, much more work will be needed to get it operable. Recruiting for this task might happen over the first week of the term, but the key to a good contest is an early start on preparation.

== Publicity ==

The street team was a modest success, needs to be better co-ordinated. The creation of the csc-general mailing list was super effective for publicizing things, continue to use it. ebering has some scripts to aid with publicity, they still need work to be usable by anyone not him.

[[Category:Term_Notes|TermNotes200909]]

Meeting:Term Notes/S2011

2026-04-05T01:12:56Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/W2011]] and [[Meeting:Term Notes/F2011]]

= Prez Notes =

= Veep Notes =

= Trez Notes =
* Do try to submit receipts for reimbursement to MathSoc as soon as the money is spent, rather than all at once at the end of term.
* Keep the cashbox supplied with 5 or 10 dollar bills.
* Batteries for the safe numpad were replaced.

= Secz Notes =

[[Category:Term_Notes|TermNotes201105]]

Meeting:Term Notes/F2011

2026-04-05T01:12:47Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/S2011]] and [[Meeting:Term Notes/W2012]]

= Prez Notes =

= Veep Notes =

= Trez Notes =

= Secz Notes =

[[Category:Term_Notes|TermNotes201109]]

Meeting:Term Notes/F2008

2026-04-05T01:12:44Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/S2008]] and [[Meeting:Term Notes/W2009]]

== Ideas ==
# Build a solid community: hold meetings every two weeks

This needs more thought, the meetings didn't go over well with the membership

# CSC Frisbee Team (Dodgeball for W2009)

Never done

# An event every week at least and get a program committee formed to help the veep with this effort (we should have one in theory)

We got the progcom up, see the relevant mailman list. We averaged 1 event/week but the distribution was not homogeneous.

# Get the library ship shape. See [[Library Project]]

Steps have been made, see further on [[Library Project]] but this is far from done.

=== UNIX Tutorials for the Froshies ===
b4taylor was going to write an undergrad environment tutorial. Perhaps we could have a few sessions working through this.

These ended up being realized as [http://csclub.uwaterloo.ca/~ebering ebering's tutorials] which will be moved to a more permenant location and noted
more permenantly on the wiki. If he forgets feel free to pester him.

=== Movie Night ===
The Princess Twin and Cinema can play any DVD you've got on the big screen. This costs $150, as of this writing I don't know how long that books the theater for or if we can play more than one DVD. This information is available if we call their office at 519-885-1048 between 9am and 2pm when the person in charge of DVD screening bookings is around.
The ACM SIGGRAPH does still produce a video review. In fact it produces 6 per SIGGRAPH conference as of 2008. They can be purchased on [https://campus.acm.org/public/Estore_window/estore_foyer2.cfm?src=svr the ACM E-store] for $60 each or $40 for members. The [http://www.cgl.uwaterloo.ca/ Computer Graphics Lab] might have a subscription or buy them, I've e-mailed [mailto:csk@cgl.uwaterloo.ca Craig Kaplan] asking about this.

Just got this done in the comfy, possibly still run with princess?

[[Category:Term_Notes|TermNotes200809]]

Meeting:Term Notes/S2009

2026-04-05T01:12:42Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/W2009]] and [[Meeting:Term Notes/F2009]]

* Requested money from CIF for books --> the list of books was taken from MEF proposal that was rejected last term
* MEF proposal for new disks for taurine wasn't accepted since it was submitted past deadline.

== Veep notes ==

# We sent out 5 letters so far inviting people to give talks, but during the remainder of exams Ebering will probably send more. See [[Talks]].
# We have a bunch of old miniDV tapes. Talk recordings can now be digitized easily, so these have been sorted in FC2 with more high profile talks being saved on DV and the rest able to be considered 'blank tape'.
# UW AV Is slow.
# SCS Gives us money for talks. You might spend some of it and do a big talk from an out of town lecturer, like one of the ones we invited. Also, send out invitations, if anyone bites get a MEF proposal in. In the coming year we could have many big talks. If veeps like you can handle the stress. Use your progcom well.
# We have an rt server, its useful for managing progcom.
# PR wants to give a talk a term. Be sure you talk to him about this.
# Ebering would like to start a talks archive, this involves finding old talks and archiving them, as well as making sure our new talks are archived in a uniform manner. See [[Talk Archive]] for information.

[[Category:Term_Notes|TermNotes200905]]

Meeting:Term Notes/F2010

2026-04-05T01:12:41Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/S2010]] and [[Meeting:Term Notes/W2011]]

= Secz Notes =
* consider requiring memberships/renewals to be in 8-month blocks to reduce administrative overhead
* talks: keep up the scheduling
* ACM Student Chapter: What are the pros and cons?
* frosh: more recruiting
* office space: what would we do with space in the DC?
* Determined that it's probably not worth it to be an ACM Student Chapter, we already get most of the perks by being on campus.

[[Category:Term_Notes|TermNotes201009]]

Meeting:Term Notes/S2008

2026-04-05T01:12:36Z

C256zhao: bulk namespace moving

See also: [[Meeting:Term Notes/W2008]] and [[Meeting:Term Notes/F2008]]

== Reminders ==

* We got $7000 from MEF for purchasing a mirror.
* We got $390 from CIF for purchasing an office terminal; suggested hardware:
** Gigabyte GA-P35-DS3L or GA-EP35-DS3L Motherboard ($91)
** ASUS GeForce 6200LE Video Card ($28)
** Corsair XMS2 TWIN2X2048-5400C4 2GB 2X1GB RAM ($46)
** FSP Fortron FSP300-60THN 300W Power Supply ($26)
** Intel E7200 Processor ($145)
* We got $800 for purchasing chairs ($400 from SLEF and $400 from CIF).

[[Category:Term_Notes|TermNotes200805]]

Meeting:Orgcom Updates/

2026-04-05T01:11:29Z

C256zhao: bulk namespace moving

Updates in OrgCom

https://wiki.csclub.uwaterloo.ca/Orgcom_Updates/Assistant_Vice-President_2023_Fall

[[Meeting:Orgcom Updates/President 2025 Winter]]

Meeting:Orgcom Updates

2026-04-05T01:11:24Z

C256zhao: bulk namespace moving

The Organizing Committee periodically gives updates throughout the term. Check out the linked pages to stay in the know!

== President ==

=== Responsibilities ===

* Generally oversee everything and lead the club
* Coordinate among execs to make sure [important] things get done
* Act as the club's primary liaison with MathSoc, our parent society
* Generally help out wherever it's needed

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/President_2023_Fall|Fall]]

== Vice-President ==

=== Responsibilities ===

* Oversee the club like President, and take charge in the case of the President’s absence
* Help out with Presidential duties as needed
* Coordinate with team leads, make sure events/initiatives are running smoothly, and relay feedback

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Vice-President_2023_Fall|Fall]]

== Assistant Vice-President ==

=== Responsibilities ===

* Oversee club correspondence and respond to member inquiries
* Alert members of external opportunities such as company events, speakers, etc. via the CSC Discord Server
* Help out with Presidential duties as needed

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Assistant_Vice-President_2023_Fall|Fall]]

== Treasurer ==

=== Responsibilities ===

* Prepare and present the budget to MathSoc
* Ensure that the club stays within budget, and reallocate budget as necessary
* Sign off on cheque request forms, for reimbursement on club expenditures
* Track membership revenue and create membership lists
* Track swag revenue and inventory
* Track pop/snacks revenue

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Treasurer_2023_Fall|Fall]]

== Syscom and Termcom ==

=== Responsibilities (imagine... Platform Engineering + Devops) ===

* Manage existing CSC servers and services
* Update and improve CSC infrastructure based on user needs
* Ensuring CSC infrastructure is reliable, secure and performant
* Assisting other committees with all things related to CSC infrastructure
* Architecting and deploying systems for new and existing services

=== Ideal Candidate ===

* '''TLDR; be interested. be nice to work with. have skills/experience.'''
* highly-motivated to be part of Syscom/Termcom
* interested in CSC infrastructure and services which benefit CSC members and external users (eg. Linux Mirror, MathSoc)
* capable of self-learning and acquiring new skills
* strong time management skills and communication skills
* deep experience in software development and/or GNU/Linux operating systems
* preferably have (some) experience in self-hosted software

'''''NOTE''': Syscom and Termcom work quite closely together in maintaining all CSC infrastructure (both hardware and software). Although the responsibilities of Termcom are (technically) a "subset" of Syscom's responsibilities, Termcom's responsibilities are fairly similar to Syscom. Thus, they will be grouped together above!''

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Syscom_and_Termcom_2023_Fall|Fall]]

== CodeyBot Developers ==

=== Responsibilities ===

* Develop, maintain and brainstorm features for CodeyBot, our Discord server bot.
** Previous features include coffee chat matching, Discord currency (Codey coin), mock interview scheduling, etc.
* Contribute to our project board to keep track of tasks and issues.
* Collaborate and review other developers' code.

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/CodeyBot_Developers_2023_Fall|Fall]]

== Community Representatives ==

=== Responsibilities ===

* Coordinate long term (>1 month) initiatives for the broader CSC community
* Procure and distribute swag, while getting insights and collect data on swag interest
* Create internship and academic guides for students interested in computer science and software development
* Organize internal socials for the orgcom

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Community_Representatives_2023_Fall|Fall]]

== Design ==

=== Responsibilities ===

* Create graphics for the following list of initiatives:
** Events promotional material
** Website
** Class Profile
** Merch
*Contribute to and expand our CSC Figma components library

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Design_2023_Fall|Fall]]

== Events ==

=== Responsibilities ===

* Coming soon!

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Events_2023_Fall|Fall]]

== External Affairs ==

=== Responsibilities ===

* We make money

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/External_Affairs_2023_Fall|Fall]]

== Marketing ==

=== Responsibilities ===

* Manage social media
* Create posts to market events
* Create memes

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Marketing_2023_Fall|Fall]]

== Office Staff ==

=== Responsibilities ===

* Help us maintain good vibes and a safe and welcoming environment in the office
* Signing up new members at events or in the office
* Assist in managing the office fridge

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Office_Staff_2023_Fall|Fall]]

== Photography ==

=== Responsibilities ===

As a photographer, your main responsibility is to help take photos at our events. Those who own a DSLR camera will be preferred. Responsibilities include but are not limited to:

* Capturing memories at events throughout the term.
* Taking professional headshots for other members.
* Photographing CSC merchandise as they are released.
* Manage inventory and photography equipments
* Meeting and getting to know others!

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Photography_2023_Fall|Fall]]

== Webcom ==

=== Responsibilities ===

* Maintain our website (https://csclub.uwaterloo.ca) by adding or updating content
* Maintain various APIs and full-stack web applications to support CSC membership verification and membership sign-up
* Design and develop new full-stack web applications for the club (Currently, working on a voting app and a library management app)

=== Updates ===

==== 2023 ====

* [[Meeting:Orgcom_Updates/Webcom_2023_Fall|Fall]]

Meeting:Termcom/Saturday 22 January 2022

2026-04-05T01:08:50Z

C256zhao: bulk namespace moving

[[Meeting:Termcom/Saturday 29 January 2022]] →

= Termcom members in attendance =
r389li, a268wang, dzlin, r345liu, d278liu, j2767wan

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin
* a268wang will also migrate the prometheus VM to the k8s cluster
* j2767wan and r389li will migrate the projects under [https://git.uwaterloo.ca/csc Git.UW/CSC], except for <code>SpamAssassin Training</code>, to [[Gitea]], under the <code>old</code> org. All migrated repos will be public except for <code>Executive Committee</code> and <code>Program Committee and Events</code>
* r345liu will fix and re-enable the Artix project in mirror-checker and make the special projects less special
* r345liu will also make an Alpine image for CloudStack, using [[CloudStack Templates]]
* dzlin will fix the Sorbitol netdata errors
* s7raviku will upgrade coffee to Bullseye, taking care to first backup the VM and ensure Postgres data is migrated to the new database

Syscom mailing list moderator: r389li

[[Category:Termcom]]

Meeting:Termcom/Saturday 12 February 2022

2026-04-05T01:08:47Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 5 February 2022]] | [[Meeting:Termcom/Saturday 19 February 2022]] →

= Termcom members in attendance =
r389li, a268wang, d278liu, dzlin, j2767wan, r345liu, s7raviku

= Tasks completed last week =
* dzlin fixed sorbitol netdata errors by adjusting the systemd unit file
* r389li migrated exec 2fa auth to CSC machines. They can be accessed using <code>~exec/hacks</code>.

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin
* a268wang and d278liu will also migrate the prometheus VM to the k8s cluster
* j2767wan will migrate the [https://git.uwaterloo.ca/csc/LinkList LinkList] project to [[Gitea]]
* r345liu and d9hui will fix the failing projects in mirror-checker
* r345liu will also make an Alpine image for [[CloudStack]], using [[CloudStack Templates]]
* r389li will pick up keys from the CSC office and start and upgrade the Office terminals
* r389li will also convert the [[Ceph]] mount on [[Machine_List#Cloud|Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* s7raviku will upgrade coffee to Bullseye, taking care to first backup the VM and ensure Postgres data is migrated to the new database

Syscom mailing list moderator: merenber

[[Category:Termcom]]

Meeting:Termcom/Saturday 5 March 2022

2026-04-05T01:08:47Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 26 February 2022]] | [[Meeting:Termcom/Saturday 26 March 2022]] →

= Termcom members in attendance =
r389li, a268wang, d9hui, dzlin, j2767wan, r4tandon (👋), s7raviku

= Tasks completed last week =
* merenber and r389li recompiled [[Kerberos]] 1.17 for focal and bullseye. Cloud machines and office terminals now mount the <code>/users</code> directory successfully from NetApp.

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin and migrate the prometheus VM to the k8s cluster
* dzlin will fix sorbitol again (more errors)
* j2767wan will continue looking into how to make the Visual Editor on this Wiki work
* r345liu will fix the last failing project (Apache IIRC) in mirror-checker
* r345liu will also make an Alpine image for [[CloudStack]], using <s>[[CloudStack Templates]]</s> something he found on GitHub (hmm sus)
* r389li/merenber will look into and fix the I/O errors on focal (related to NetApp mounting).
* r389li will also convert the [[Ceph]] mount on [[Machine List#Cloud Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* s7raviku will upgrade coffee to Bullseye, taking care to first backup the VM and ensure Postgres data is migrated to the new database

= Unix 101 =
Description: Join CSC's Systems Committee (syscom) for an introductory series on GNU/Linux!

== Final Plans ==
4 talks this term, the rest in the future.

=== Unix 101 - SSH & Bash/CLI ===
Location: In-person, room TBD

Date/Time: Friday March 18th, 2-3pm
* j2767wan: SSH - 15 mins
* dzlin: bash and basic CLI commands - 30-40 mins

=== Unix 101 - FS/Perms & vim ===
Location: Online (Twitch)

Date/Time: Saturday March 26th, 2-3pm
* s7raviku: FS/perms
* r345liu: vim

= Syscom mailing list moderator =
r345liu

[[Category:Termcom]]

Meeting:Termcom/Saturday 29 January 2022

2026-04-05T01:08:43Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 22 January 2022]] | [[Meeting:Termcom/Saturday 5 February 2022]] →

= Termcom members in attendance =
r389li, d278liu, d9hui, j2767wan

= Tasks completed last week =
* All Git.UW/CSC repos were migrated, with the exception of LinkList (500 error)
* r389li tested rebooting [[Machine_List#Cloud Cloud machines]] in preparation for [[CloudStack]]'s general release

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin
* a268wang will also migrate the prometheus VM to the k8s cluster
* dzlin will fix the Sorbitol netdata errors
* j2767wan will migrate the [https://git.uwaterloo.ca/csc/LinkList LinkList] project to [[Gitea]]
* r345liu and d9hui will fix and re-enable the Artix project in mirror-checker and make the special projects less special
* r345liu will also make an Alpine image for [[CloudStack]], using [[CloudStack Templates]]
* r389li will convert the [[Ceph]] mount on [[Machine_List#Cloud Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* s7raviku will upgrade coffee to Bullseye, taking care to first backup the VM and ensure Postgres data is migrated to the new database

Syscom mailing list moderator: a268wang

[[Category:Termcom]]

Meeting:Termcom/Saturday 26 February 2022

2026-04-05T01:08:42Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 19 February 2022]] | [[Meeting:Termcom/Saturday 5 March 2022]] →

= Termcom members in attendance =
r389li, dzlin, j2767wan, r345liu, s7raviku, y226shen (👋 just joined us!)

= Tasks completed last week =
* r389li did more work on 2fa <code>/usr/local/lib/2fa</code> is now sourced from <code>/etc/profile</code> on all the general-use machines, using the <code>.2fa</code> directory in every user's home directory.
* j2767wan finished migrating LinkList after r389li upgraded Gitea to the latest version, completing the UW GitLab → CSC Gitea migration
* r389li picked up keys from the CSC office and started all the [[Machine_List#Office_Terminals|office terminals]] except maltodextrin (black screen and can't SSH into it)
* r389li also upgraded bit-shifter and strombola to focal from bionic, and packaged [https://git.csclub.uwaterloo.ca/public/libpam-csc.git libpam-csc] and [[Ceo]] for focal. However, focal's [[Kerberos]] doesn't work with [[New NetApp|NetApp]] so we're still trying to figure out how to make them work.

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin
* a268wang and d278liu will also migrate the prometheus VM to the k8s cluster
* j2767wan will look into how to make the Visual Editor on this Wiki work, so I can stop using stupid MediaWiki markup to write this like I'm doing rn
* r345liu will fix the last failing project (Apache IIRC) in mirror-checker
* r345liu will also make an Alpine image for [[CloudStack]], using <s>[[CloudStack Templates]]</s> something he found on GitHub (hmm sus)
* r389li will continue attempting to try to get NetApp-compatible Kerberos working on focal.
* r389li will also convert the [[Ceph]] mount on [[Machine List#Cloud Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* s7raviku will upgrade coffee to Bullseye, taking care to first backup the VM and ensure Postgres data is migrated to the new database

= Unix 101 topics =
In order of presenting, one or two a week:
* j2767wan: SSH
* <insert presenter>: bash and basic CLI commands
* s7raviku: FS/perms
* r345liu: vim
* d278liu: sed
* y226shen: package managers
* dzlin: Docker
* merenber: iproute2

= Syscom mailing list moderator =
a268wang

[[Category:Termcom]]

Meeting:Termcom/Saturday 2 April 2022

2026-04-05T01:08:41Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 5 March 2022]] | [[Meeting:Termcom/Saturday 2 April 2022]] →

Last meeting of the term, good luck on exams!

= Termcom members in attendance =
r389li, dzlin, j2767wan, jtoft (👋), r345liu

= Tasks completed last few weeks =
* r389li got USBs for the office, plugged in Nullsleep and booted it up

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin and migrate the prometheus VM to the k8s cluster
* j2767wan will continue setting up NextCloud locally
* r4tandon will continue looking into how to make the Visual Editor on this Wiki work
* r345liu and y266shen will fix the last failing project(s?) (Apache/Debian/???) in mirror-checker
* r389li will try and fix Nullsleep's networking
* r389li will also upload the Unix 101 recording and update [https://csclub.uwaterloo.ca/~termcom/unix101 https://csclub.uwaterloo.ca/~termcom/unix101]
* dzlin and s7raviku will upgrade Postgres on coffee, ensuring data is migrated to the new database

= TODO =
* Convert the [[Ceph]] mount on [[Machine List#Cloud Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* MathNEWS container migration (LXC -> systemd-nspawn)
* Fix Guayusa
* Get the specs of the FusioIO card

= Syscom mailing list moderator =
a268wang

[[Category:Termcom]]

Meeting:Termcom/Saturday 5 February 2022

2026-04-05T01:08:40Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 29 January 2022]] | [[Meeting:Termcom/Saturday 12 February 2022]] →

= Meeting cancelled =
See [[Meeting:Termcom/Saturday 29 January 2022]] for tasks for the week

Syscom mailing list moderator: r345liu

[[Category:Termcom]]

Meeting:Termcom/Saturday 26 March 2022

2026-04-05T01:08:32Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 5 March 2022]] | [[Meeting:Termcom/Saturday 2 April 2022]] →

= Termcom members in attendance =
r389li, a268wang, d9hui, dzlin, j2767wan, jy36li (👋), y266shen

= Tasks completed last few weeks =
* dzlin fixed sorbitol again, hopefully for good
* j2767wan, dzlin, s7raviku and r345liu gave their Unix 101 talks
* r389li replaced xylitol's failed disk and pulled Guayusa to the office to fix it
* s7raviku upgraded coffee to Bullseye

= Tasks for the week =
* a268wang and d278liu will continue working on Merlin and migrate the prometheus VM to the k8s cluster
* j2767wan will look into setting up NextCloud
* r4tandon will continue looking into how to make the Visual Editor on this Wiki work
* y266shen will fix the last failing project (Apache IIRC) in mirror-checker
* r389li will convert the [[Ceph]] mount on [[Machine List#Cloud Cloud machines]] to a systemd.mount so NGINX won't try to start (and fail) before its FS is mounted
* r389li will also upload the Unix 101 recording and update [https://csclub.uwaterloo.ca/~termcom/unix101 https://csclub.uwaterloo.ca/~termcom/unix101]
* s7raviku will upgrade Postgres on coffee, ensuring data is migrated to the new database

= Syscom mailing list moderator =
r389li

[[Category:Termcom]]

Meeting:Termcom/Saturday 19 February 2022

2026-04-05T01:08:31Z

C256zhao: bulk namespace moving

← [[Meeting:Termcom/Saturday 12 February 2022]] | [[Meeting:Termcom/Saturday 26 February 2022]] →

Meeting cancelled for reading week

Syscom mailing list moderator: r389li

[[Category:Termcom]]

Template:Outdated Section

2026-04-05T00:55:46Z

C256zhao: Created page with "{| style="margin: 0.5em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 2px;" |- | style="width: 40px; text-align: center; font-size: 18px;" | ⚠️ | style="padding: 2px;" | This section contains outdated information that may be inaccurate. |} <includeonly>Category:Outdated pages</includeonly><noinclude> == Usage == This template adds a warning box and automatically categorizes the page into :Category:Ou..."

{| style="margin: 0.5em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 2px;"
|-
| style="width: 40px; text-align: center; font-size: 18px;" | ⚠️
| style="padding: 2px;" | This section contains outdated information that may be inaccurate.
|}
<includeonly>[[Category:Outdated pages]]</includeonly><noinclude>
== Usage ==
This template adds a warning box and automatically categorizes the page into [[:Category:Outdated pages]].

To place this before a specific section, simply use:
<code><nowiki>{{Outdated Section}}</nowiki></code>

To mark a whole page as outdated, use:
<code><nowiki>{{Outdated}}</nowiki></code>

</noinclude>

Template:Outdated

2026-04-05T00:53:31Z

C256zhao: Created page with "{| style="margin: 1em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 5px;" |- | style="width: 50px; text-align: center; font-size: 30px;" | ⚠️ | style="padding: 5px;" | '''This page contains outdated information that may be inaccurate.''' Please help [{{fullurl:{{FULLPAGENAME}}|action=edit}} update this page] to reflect the current situation if you can. |}<includeonly>Category:Outdated pages</inclu..."

{| style="margin: 1em auto; width: 80%; border: 1px solid #a2a9b1; border-left: 10px solid #f28500; background: #fbf9f4; padding: 5px;"
|-
| style="width: 50px; text-align: center; font-size: 30px;" | ⚠️
| style="padding: 5px;" | '''This page contains outdated information that may be inaccurate.''' Please help [{{fullurl:{{FULLPAGENAME}}|action=edit}} update this page] to reflect the current situation if you can.
|}<includeonly>[[Category:Outdated pages]]</includeonly><noinclude>
== Usage ==
This template adds a warning box and automatically categorizes the page into [[:Category:Outdated pages]].

To place this at the top of an article, simply use:
<code><nowiki>{{Outdated}}</nowiki></code>

To specify that only a specific section is outdated, use:
<code><nowiki>{{Outdated Section}}</nowiki></code>

</noinclude>

Electronics

2026-04-05T00:22:37Z

C256zhao:

= Overview =
The Computer Science Club occasionally builds things in the physical world with electronics. This page outlines the major projects and the resources the CSC has acquired for this purpose.

= Special Equipment =
The CSC has purchased or otherwise acquired the following specialized equipment. The following list is not by any means complete or exhaustive, the CSC has many more basic tools and materials for electronics projects. The following is a list of expensive or difficult to acquire equipment that should not be lost or damaged.

* DSO Nano Pocket Oscilloscope
* Wave Generator (on loan from jj2baile)
* 3 Soldering Irons
* Helping Hands (for soldering)
* Table-mount Vice
* 2 Solder Suckers (1 heated)
* 2 Multimeters
* Depth Gauge
* Precision calipers
* ARM touchscreen

=Projects=
== Current (Ongoing) Projects ==

* [[Robot Arm]]
* [[Point of Sale System]]
* [[LED Cube]]
* [[Automatic Light Switching]]

== Completed Projects ==

* [[Historical:7 Segment Display]]

Historical:7 Segment Display

2026-03-24T13:22:29Z

C256zhao: C256zhao moved page 7 Segment Display to Historical:7 Segment Display

= Overview =

We have mounted a large 7 segment display on the wall in the office, hooked up to an ATMega microcontroller that displays the number of people currently viewing the webcam feeds.

= Status =
Completed. No further work to be done, barring repurposing of the hardware

= Resources =
* Code: "git clone ~ssalbiz/dev/7seg"
** Contains both microcontroller code and daemonized scripts that run on the webcam host
* Circuit diagram: yell at j3

= Notes =
* Daemon: code is committed to the repo, documentation of how it works is also there.
* There is an upstart init job on bit-shifter that is responsible for starting this daemon in /etc/init/camcount.conf. The config file is also stored in the repo.

Historical:Webcams

2026-03-24T13:22:18Z

C256zhao: C256zhao moved page Webcams to Historical:Webcams

The live webcam feed of the office is no longer available.

See the previous history of this page for historical information about the webcam feed.