reverse engineering things that predecessors left without any documentation and throwing them out the window because devops
Menu
menu

I’m writing this as a set of notes for future Arch Linux installations. I decided to revisit Arch Linux after hearing that their ncurses menu-based installer was long gone and how they have started using install scripts. I came upon this while reading the systemd vs SysV initialization method debate that everyone is raging about. I haven’t installed Arch in years as my current machines still happily run on the old installs which are up to date since Arch is a rolling release distribution. I figured now would be a good time to check it out (along with a growing interest in tiling window managers such as i3 or ratpoison).

Anyhoo, I installed Arch Linux from the latest ISO using the new method along with a help of numerous Arch wikis. I mixed the install a little bit with my way of setting up Linux computers and added LVM. One thing I must say is that installing Arch Linux has become a little bit harder than previous menu-based installation. I’m not saying it’s not doable, but it’s definitely a bit more complex or at least daunting for a newbie than just following some menus. It does help to know how Linux already works but this installation method should teach you a bit if you don’t know.
Continue reading ›

This is a quick note to help me understand STP with trunks.

Suppose you have two switches, switchA and switchB. They both have two trunks between each other. Say I connect nodeA and nodeB to switchA and switchB. I then send a packet from nodeA to nodeB on switchA. SwitchA will not know where to send that frame as it does not have the MAC address so it uses ARP. SwitchA broadcasts the MAC address to every port except on which the frame arrived on. The MAC goes out through one of the trunk ports towards switchB. SwitchB looks at the frame and search for a node with that MAC address. It doesn’t see one thus it sends out the MAC address to all the ports other than the one it received on. That frame goes out towards switchA which then causes a loop.

Spanning Tree Protocol avoids that by closing off one of the trunks so the frame with the MAC will not be able to go back towards switchA from switchB.

Started reading through some of my old posts and noticed how many times I’ve eaten a letter or something didn’t sound grammatically correct. Fixing all mistakes ASAP.

EDIT: I even managed to make a mistake in this post. I’ve spent too much time on the Internet today.