I upgraded my home network from a Cisco 3750G to a Brocade ICX 6610 a couple years ago...
- 40 GbE to the "new" (in process of being set up and deployed) NAS
- 10 GbE to the "old" (being phased out) NAS (was: 40 GbE)
- 40 GbE to my workstation
- 10 GbE to the "other machine" on my desk
- n x 10 GbE to the cluster of ESXi servers
- 10 GbE to other misc. servers in the rack
- Multiple 10 GbE and 1 GbE links to the PTP GrandMasters and NTP servers
- Plus all the various PoE devices (APs, VoIP phones, etc.) and miscellaneous other hosts (NTP appliances, DRACs, PDUs, NetBotz, etc.) at 1 GbE and/or 100 Mbps
Unfortunately, I'm just about out of 10 GbE ports so I may need to get another ...
Highly recommend the ICX 6610 in particular. The only other Brocade (Ethernet) switches I've personally managed are the "access layer" FCX switches (in an old position 10+ years ago).
The author of the guide linked to by OP has a series of docs for resetting the 6610 to factory settings and licensing all the ports. My understanding is that especially for the old switches like the 6610, it’s not possible to buy licenses anymore so you can just unlock them.
For copper 10gbe connections, you have two main choices: you can use DAC cables which end up being cheap but are hard or impossible to fish through walls or terminate at a patch panel, or you can use a 10G-BASET transceiver which gives you standard RJ45 jack but costs about $50 for each end of the connection plus the cost of a cat6 or better cable.
Edit: obviously if you already have a device with a copper 10gbit port, then you only need one transceiver (for the switch port), and using a DAC is a no-go since DACs require SFP ports at both ends of the connection.
As a "normal" driver, the pulsating lights absolutely are annoying... and don't even get me started on those loud ass pipes!
Now, as a motorcyclist who has been hit head-on more than once by drivers who swore "I didn't even see him!" -- with the last crash leaving me with multiple broken bones and an inability to walk for several months -- you better believe I now have both a pulsating headlamp and a nice set of loud ass pipes (they're even called "Street Cannons")! on my bike.
I've also lost a non-zero number of friends due to folks who swore they didn't see them.
It's now been eight years since I've gotten hit... so I really am sorry if my headlight or pipes bother you as I pass by but, well, I have loved ones I'd like to see again so I hope you'll forgive me.
TIL Loud ass pipes for safety. I never understood how someone can rationalize themselves out of waking up a whole neighborhood at night for the sake of their own transportation.
I have pipes that are pretty loud above ~4000 RPM, but pretty quiet underneath that. When I'm in a residential neighborhood I keep the revs low and shift early (it's less aggressive anyway, which is what you want if a kid or a dog could dart out in front of you). On the freeway and when nobody is around me I also keep it under 4000 RPM. But when I start feeling boxed in or I'm lane splitting I'll drop it down a gear to bump the volume of the pipes. You can see people recognize you're there, and that's the goal.
But yeah, those guys who blare their exhaust on bikes or cars are a-holes.
I ride. 9 years on a second hand GSXR1000 with pipes already swapped - loud. Now 5 years on an MT-09 with standard pipes - normal. City daily commuting the whole time. I won't bother with loud pipes again.
My pet theory: Unlike motorcycle riders, car drivers don't get the benefits of stereo positioning unless you are real close.
By the time people hear it, decide to look for it, place the location, react as required - you are usually on your way anyway.
Mind you, my home park is beside the driveway between two apartment blocks. I don't want to piss off 50 people I live close to, each time I come and go.
I can pinpoint everyone in my 90s Nissan, I cannot do the same in modern cars. Sound deadening has ruined that type of spatial awareness. That is just from tire noise as most cars are pretty quiet too.
I do often hear loud bikes lane splitting in time to give them room though, food for thought!
Too little info to provide any real advice besides the obvious (see below). Out of curiosity, though, do you recognize the name of the merchant?
--
Anyways, there's a toll-free number on your card. Call it and explain the situation to them. They'll likely re-issue your card and call it a day, unless the specific transactions trigger some sort of "red flag" (although, if that were the case, the fraud department would likely have noticed before you did and already took action).
There are certain types of questions that aren't really appropriate for an "Ask HN". This is one of them.
You can’t search for code across the entire GitHub without signing in. You can search in a single repo just fine. That’s a three orders of magnitude smaller concern. I do research on GitHub in incognito windows daily.
Just got some background here, the May 10th update literally broke the ability for many people to logon to a domain. It was extremely broken and businesses that deployed it suffered heavily. The June 14th fix being discussed here in turn broke many backup products in ways people are still trying to understand. Edit: The June 14th update being discussed here also broke Wifi hotspot and RRAS services, the latter being relevant to servers.
So most Windows server admins are quite acceptably delayed in deploying updates. Most standards and policies give an organisation 30 or 60 days to apply a security update outside of a particularly critical issue, and in most cases that's considered appropriate risk management. In this case I don't understand why this is news, there were many CVEs fixed this month but I've generally assessed there are as being very low exposure and no reason to panic. For example, across our whole fleet it took a few minutes to test for the NFS service being installed anywhere and I've found it in zero places.
We don't have the Linux luxury up running an "update Apache" command and getting an update that fixed one CVE, every update is a major cumulative update with its own brokenness and test cycles. Remember at one point Microsoft released an update which broke port binding, and every network service including their own SQL and SMTP servers stopped functioning. That update was rated a critical security fix.
The (edit) July 12th update is the first proper fix for Follina vulnerability, which is now months old. That really should be what people are testing and targetting for rollout.
I wonder who Microsoft sees as Windows customers today.
Not the consumer. There are plenty of anti-consumer features in there. Spontanous reboots for patching, fire risks be damned. Privacy nightmare. Forced microsoft account. DRM.
Not the enterprise. Required manual patch validation. Complexity of upgrade rollouts. Neverending random breakage. Retraining for random vanity UI changes.
All of the above are fixable by listening to the customer and doing the necessary work, and not doing change for the sake of change.
My laptop runs Windows 10 (all my other machines are Debian or Devuan). I have searched, but failed to find any way of preventing this damned OS from downloading and installing updates without asking me. I often get up in the morning to find that all my open windows have been force-closed, because the machine rebooted after an update.
I have no idea what the updates contain; by the time I know about it, it's already installed and running. I don't see much point in reading the release-notes (if I can find them), because they are invariably opaque and full of obfuscation.
And anyway, the updates are unitary; I can't cherry-pick packages or bug-fixes. Win10 is either up-to-date or vulnerable. And "updates" often include new features that I don't want.
I don't know why Windows the OS is so user-unfriendly; possibly because the devs are exclusively focused on enterprise features. I've been using Windows since Win3, but I nowadays find it nigh-impossible to administer my own machine.
I've been thinking of replacing Windows with Devuan on this one hold-out machine for months.
It's user friendly for people that don't know what patches are or why software needs updated. It's frustrating for the people that do and would like control
I remember the Windows XP days where you'd regularly find computers that hadn't successfully updated in months or years and it was a whole day effort to get them patched
Windows 10 Reboot Blocker works ok. It runs as a service and keeps readjusting active hours to prevent reboots
Its only for NFS and not NTFS and only in v4 of NFS at that. Most systems will not need any action and those that do are unique enough that they're should be patched regularly in the first place.
They’re probably also important and harder to support: things like central storage servers or other services which support a wide range of clients, careful security mapping rules, etc. This is less than a month old so I would not be surprised if the places affected are carefully testing since almost by definition anyone running it has a complicated environment to support.
I believe you are mistaken, as HB2319 [0] itself directly states:
> The occupants of a vehicle that is the subject of a police stop may record the encounter if the occupants are not interfering with lawful police actions.
--
On a side note, I encourage everyone to carefully read the actual bill.
There's a lot of intelligent people here on HN but it seems that many of those commenting can't quite comprehend plain English (not as well as I would have expected, at least).
The issue generally isn't with the bill but how the police enforce it. There are videos all over the internet of police officers telling people standing near to stop filming them and threatening to arrest them for interferring with police business. Hell, there is one video of a police office crossing the road to do so.
These used to be big, expensive, standalone devices (I'd occasionally use one in a previous job). Nowadays, there are portable, handheld units specifically for identifying where a break has occurred and the same, basic functionality is often even built into the gear used at either end of connections (e.g., even the "enterprise" switches -- from Brocade and Cisco -- that I use at home).
I was just a teenager around this time, in middle school or perhaps high school, and still in the early stages of programming (after moving on from the Commodore 64 and 6502 assembly), but -- even three decades later -- it's nice to finally have an answer to that one particular question that was asked so often and by so many all throughout those years:
> Just WTF were those Microsoft guys smoking when they designed this shit?
Highly recommend the ICX 6610 in particular. The only other Brocade (Ethernet) switches I've personally managed are the "access layer" FCX switches (in an old position 10+ years ago).