Oh no, you!

  • 13 Posts
  • 601 Comments
Joined 1 year ago
cake
Cake day: November 3rd, 2024

help-circle






  • Some VLAN-related nuggets that you may find useful for your post/blog:

    • 99% of the time when people refer to VLAN, they’re talking about 802.1Q (tag-based VLANs). There are others (Such as port based), so it’s up whether you want to cover those as well.
    • The word “Trunk” can mean different things, depending on vendor. In the Cisco world, it means a line/port carrying multiple VLANs. With many other vendors, such as Aruba/HPE, it refers to link aggregation which isn’t necessarily relevant to VLANs
    • A lot of hardware still use VLANs even if none have been configured. For example, defaulting all switch ports to have an Access tag of 1 makes it behave like a dumb switch. This can cause issues later if you’re configuring VLANs elsewhere
    • Anything non-vlany connected to a VLAN-enabled switch will have to be connected to a port with a default VLAN tag. This is usually referred to as an “Access port” or an “Untagged port”
    • “How do I configure the switch to allow units on VLAN 123 to talk to VLAN 321?”. You don’t. Connect both VLANs to a router which will route between them. Either connect the router to both VLANs individually and skip the tagging on the router, or you can run a single trunk between the switch and the router which carries both VLANs. The latter requires you to configure VLANs on your router accordingly.
    • It might make sense in many cases to have the VLAN tag the same as the last octet in the IPv4 subnet. Makes it easier to keep track of.
    • A PC can implement VLANs on its network port, allowing you to connect to a trunk port and access several VLANs with one cable.

    Source: VLANs have been an integral part of my career for 20ish years.


  • “Defeated” might be overstating it, but Pakistan generally overperformed compared to expectations with a smaller airforce, as they have a significant advantage in AWACS capabilities (Saab 340, I think?), whereas India is more limited, in the form of a few IL76 and some homebrewed systems in the works.

    In this age of BVR capabilities and standoff munitions, airborne radar and intelligence is key to operational success, and Pakistan knows this, whereas India has taken more of a brute force approach to modern aerial warfare, something that was obsolete 40 years ago, if not before.




  • Possible, but highly unlikely.
    For starters, if that many were killed, I think it’d be really hard to keep a lid on it these days.

    Secondly, I’ve done a lot of reading on the atrocities of WW2, and two immediate constraints come to mind:

    • Bodies. While possible, disposing of that many bodies without anyone noticing will be really hard.
    • The gas chambers of ww2 were only planned during the Wannsee conference in 1942, long after the holocaust actually started. The gas chambers were built because the original plan was not sustainable: People killing other people at an industrial scale. No matter how vile a person is, the human mind was not built to deal with having to mow down swathes of humans with a gun. Even the worst SS troops largely couldn’t deal with killing that many defenseless people, even if they were convinced it was “for the greater good”. The amount of SS troops who ended up unable to continue due to the mental after effects is staggering.

  • If it works on mint, it’ll most likely work on debian, with the caveat that debian is a lot more CLI and a lot less handholding. Depending on your setup, debian might be a better choice for you, as Mint is desktop oriented.

    But don’t fix something that already works. If there’s no issues with your Mint setup, I’d say keep it. Next time you set up a server, you can go for debian instead.

    Source: I use both extensively. Mint on desktop, debian on headless stuff.







  • I use beegfs at work for the redundancy and clustering aspect. 1.8PB of storage with 100% redundancy.

    While it supports a lot and CAN be quite involved, a very basic setup is in fact pretty simple:

    A filesystem on a machine is a storage target.
    A machine with storage targets is a storage node. (beegfs-storage)
    A management server (beegfs-mgmtd) connects these together into a filesystem.
    Any machine runs beegfs-client to mount this filesystem.
    One machine needs to run beegfs_meta for the Metadata. It doesn’t require a lot.