Minutes 2024-11-07: Difference between revisions

From MTU LUG Wiki
Jump to navigation Jump to search
m (update to calculations)
m (minor touch-up)
Line 5: Line 5:
## Info about AwesomeWM
## Info about AwesomeWM
### X11
### X11
### Configuration done in Lua
### Configuration and plugins in Lua
## Info about Hyprland
## Info about Hyprland
### Wayland
### Wayland
### single .conf file, automatically reloads on changes
### Single config file, automatically reloads on changes
# Live demo!
# Live demo!
## AwesomeWM
## AwesomeWM
### Fully custom setup
### Fully custom setup
### made from the ground-up using only default awesome widgets
### Made from the ground-up using only default awesome widgets
## Hyprland
## Hyprland
### Customized with some bits from premade configs
### Customized with some bits from premade configs

Revision as of 22:04, 7 November 2024

  1. Waited a minute for Gorkem to finish his very important talk
  2. Presentation from Lucas on ricing WMs!
    1. What is a WM/DE
    2. History of GNOME/KDE
    3. Info about AwesomeWM
      1. X11
      2. Configuration and plugins in Lua
    4. Info about Hyprland
      1. Wayland
      2. Single config file, automatically reloads on changes
  3. Live demo!
    1. AwesomeWM
      1. Fully custom setup
      2. Made from the ground-up using only default awesome widgets
    2. Hyprland
      1. Customized with some bits from premade configs
    3. What programs do you use?
      1. feh for images
        1. Even on Hyprland
        2. Does that mean it's running in XWayland?
      2. vlc for video
      3. ranger as a file manager
  4. NCl Team game stuffs
    1. Hashtopolis clusters are in the works for competitive teams 1 and 2
    2. Hashtopolis cluster of all lab machines in Rekhi 113 for team 1?
      1. They have pretty good
      2. Team 1 is using 113 as our base of operations for the Team game anyway
      3. Is this allowed?
      4. Would NCL get mad with us using more resources than we could feasibly purchase?
        1. We're not spending any money
        2. Not "collaborating" with anyone outside of our team
        3. Doesn't explicitly break any rules?
      5. More importantly, would Tech get mad?
        1. Jury is still out on that
        2. Just shut it down whenever we're not in the room?
  5. Future of RedTeam
    1. Creating docs for RedTeam to better retain knowledge between generations
      1. Host on LUG wiki?
    2. Getting more LUG members on RedTeam eboard next year?
      1. May help for having more technical and hands-on talks
      2. A lot of LUG is on RedTeam already anyway
      3. Majority of the more technical members in RedTeam are in LUG
  6. Finished the meeting and left to try out a USB drive with a portable install of Python+Pip+Hashtopolis on Rekhi 113 machines
    1. All the computers run RHEL and have NVIDIA Quadro T1000's (same as Rekhi 112)
      1. 44 computers in total
      2. 88 across both labs
      3. Each machine gets about 500kH/s, so about four equal my 3060Ti
      4. The T1000 is basically the same in compute to a GTX 1650 [1]
      5. Adding all 88 computers from both labs would net us ~40Mh/s, about ~5x the compute in our current 8Mh/s cluster
      6. Leave a notice on the screen in case someone needs to do lab work?
        1. netcat from the lab computer to shell, respond "hey type something and press enter if you need this machine" and fullscreen the terminal window
        2. on shell's end have a tmux session with 88 panes??
    2. Visited the EERC and looked at the GPUs in 330 and 328
      1. 330 used T1000's
      2. 328 used a mix of potato VGA GPUs and integrated graphics so we didn't even bother checking
    3. The T1000 seems to be standard GPU for lab machines on campus
      1. Maybe one or two labs with beefy GPUs exist on campus?
        1. Probably in the MEEM or EERC if it exists at all
        2. I heard the GLRC has a good computer lab
    4. Visited Rozsa computer lab, was tap-access restricted :(