• 0 Posts
  • 20 Comments
Joined 6 months ago
cake
Cake day: May 20th, 2024

help-circle


  • I don’t want to keep replying to this but in response to your ‘this is from a .mil site specifically …’ I linked to the DOD’s actual gov website.

    This article is relevant for NAVPERS 18068F because the Navy has all of this annoying traditions, like referring to ‘-’ as Tack like they are pretending to be a flagman from 1835 on a ship and refer to a snackbar as a gedunk and blah blah blah.

    But they still have a military rank. Sure, if you ask someone enlisted person what their ‘rate’ is they are going to respond with “PO1” if they are a Petty Officer First Class but if you have a CAC ID, under RANK it is going to say PO1 with the USN’s seal in the top-right. Because it is their military rank. The USN can call it a rate as well and traditionally it can be known as a rate in the USN but it is still a military rank. It will even say that on your ID card if you have one or have had one. As I recall, this is also true for the old green ID cards.


  • OK, let me just break this down for you. Rates are a job in the Navy. For example, in that wikipedia article, a Fireman recruit is a rate – their job. Their rank would be a Seaman Recruit. Their paygrade would be an E-1.

    In your example, a Constructionman would be an E-3. Constructionman would be their rate. Their rank would be Seaman.

    You can see this better at https://www.defense.gov/Resources/Insignia/

    They don’t list rates, because there’s many, many, many different jobs in the different branches. The Navy is odd in that they usually refer to each other by rates, not ranks. In every other branch, people usually refer to each other by rank and not their MOS/AFSC/Whatever. It would be weird in the USAF for example to refer to some Airman First Class as 2A33C or whatever.

    You can see this further explained at https://www.military.com/navy/enlisted-rates.html where they list the rates and talk about them but then they list the ranks and talk about them. They are tied together by paygrade.

    And once again, in the US Navy, an enlisted person can literally not have a rate and be called Unrated until they are assigned a rate. Usually this happens to very junior enlisted.





  • Effectively they did through obfuscation. The Command Chief renamed it to look like their wireless printers. She did that because so many more junior people (relative to the Chief’s Mess) complained that the officers tried to check (with their phones) for some wifi Internet. They couldn’t find it because they thought it was a printer. The Command Chief is obviously trusted since she’s the most senior enlisted but she’s also the one that lead the entire scheme. When asked directly by the Commander, she denied it existed, so after not finding it, they just assumed it was a rumor. So, they had a ship-wide call and told everyone that there was no rogue Internet access point on the ship.

    It took months because when a tech from a port they were at was installing a Starshield transceiver they physically saw the Starlink transceiver.




  • Guest wifi does not mean it is unsecure, it is simply just another logical network. Sure amazon could equip their trucks with wifi I suppose and maybe some TVs would have good connection to update fast enough while a truck is there without a lot of tcp retransmits due to lack of efficient lack of penetration but that’s not going effect all brands and surely it isn’t something that is currently happening in a large effect.

    You could talk about hypotheticals in the future sure but they aren’t going to scan for these magical “network ports” that are just hanging around the ether. It needs to have a connection and one that is reasonable in quality and time.







  • Yes, but has it taken both OS’ out at the same time? It hasn’t but it could happen, however, the chances are even less. There’s obvious risk mitigation in mixing vendors in infrastructure for both hardware and software in the enterprise.

    If some critical services were lost in your enterprise last time until RH updated their kernel then you could have benefitted from running that service from Windows as well. Now the reverse is true. You could have another DC via Samba on Linux in your forest if you wanted to, in order to have an AD still for example. Same goes for file share servers, intermediary certificate servers (hopefully your Root CA is not always on the network) and pretty much most critical services.

    Most enterprises run a lot of services off of a hypervisor and have overhead to scale (or they are already in a sinking ship), so you can just spin up VMs to do that. It isn’t as if it is unreasonably labor intensive compared to other similar risk mitigation implementations. Any sane CCB (obviously there are edge cases but we are talking in general here) will even let you get away without a vendor support contract for those, since they are just for emergency redundancy and not anywhere near critical unless the critical services have already shit the bed.



  • It’s also difficult for developers to publish to Linux because of the wide variety of different Linux systems.

    I disagree there. The issue is that in Windows people bring over their own version of libraries they compiled on (the millions of .dll files) and you can even look in your Uninstall Apps settings where there’s a bunch of MS specific runtime bundles to see that’s even an issue in the MS ecosystem.

    In Linux, developers have relied on the library versions just being there. It is, I’d argue, the most compelling reason package managers basically had to come into existence. On the flip-side this can cause issues where there is some version on the system by the package manager that replaces another version. And something not a part of that package management system isn’t a part of those dependency checks and if they don’t put the libraries with the binaries…well it is just luck if you have them all or if other versions can support those library calls in the same way still.

    In Linux that is all those .so’s in /var/lib and stuff.

    You don’t really see many proprietary things using package managers and those that do are packaged by someone else and are in some sort of repo that isn’t part of the vanilla install because of legal caution.

    Companies that made their money on porting games to Linux prior to Proton basically causing them to shutter Linux porting would put their .so’s in with the game bundle themselves, just like you see happening in Windows when .dll’s are inside the actual program’s folders.

    However, the more that this sort of dependency management has become abstracted by development suites that take care of this for the developers, the less they understand about it.

    Flatpaks actually take care of this and it is one reason they are so popular. They figure out (well that’s a simplification) those library dependencies, sandbox the apps with those dependencies so the library paths don’t interfere with other flatpaks or the base system itself. People complain about this as a con because “the download is BIGGER” even though flatpak doesn’t install the same runtimes over and over again, so once they are there, the download may still be bigger but the installed storage isn’t.

    Anyway, yes Linus Torvalds complained about the “Linux fragmentation” issue but it was about DE’s not the state of the development ecosystem itself as I recall, though the rant is very old, so maybe I don’t remember all of it.

    Wider application support would be a start.

    Sure, but that’s not a Linux problem, that’s a developer problem. Linux supports application development just fine. It is a kernel and the surrounding ecosystem is the operating system after all. It is developers that don’t support it. That isn’t really something Linux in and of itself can effectively solve. Users have to increase and developers supporting applications for Linux will also increase. The classic Linux Chicken and the Egg problem but it is capitalism and that’s just going to be how it has to work.