Shdwdrgn

joined 2 years ago
[–] Shdwdrgn@mander.xyz 6 points 1 day ago

I've have long hair for about 35 years now. I guess mine is wavy too (?) although when it's humid I'll get some tight pipe curls. Just tie it back out of the way. Best hair bands I've found are made of pantyhose material, they don't snag or wrap up in your hair. They do come in different sizes so if you have thick hair you can get a larger band.

Regardless, no matter what you do you'll always eventually get some hair in your food.

[–] Shdwdrgn@mander.xyz 2 points 6 days ago (1 children)

I guess it bugs me more because I've watched ST:TOS and never had such a horrid feeling from those episodes. Someone once told me the early episodes showed how much the Doctor grew over time, from an elitist to someone who truly cared for everyone, but I have to wonder how much of that was simply the writers themselves realizing they could do better?

[–] Shdwdrgn@mander.xyz 6 points 1 week ago (4 children)

If you decide to jump back to the original series, also keep in mind the time at which they were filmed. I tried watching the original 1963 run and was just disgusted by how the female actors were treated... The whole "you need a strong man to save you", and the constant "woman screams every time an alien shows up". I know we've come a long way since then, but it's really a slap in the face considering how relatively recent that is within our history.

Then again, cartoons from the 1930's? Hoo boy the massive amount of open racism.

But if you really get interested in Doctor Who and want to see the history of the many story lines, then you just have to bite down and blast through them.

[–] Shdwdrgn@mander.xyz 19 points 1 week ago (2 children)

Why? Is he suddenly running scared and realizing just how badly he has crippled the US military and national security, not to mention any hope of counting on our allies to back us up when the threats start coming?

Then again, Trump is gullible enough to actually believe other countries were disarming and would shut down our entire program without a hint of assurances. And then he'd have to tell his MAGAts to be shocked when a few of our cities got nuked because how could anyone have predicted this could happen.

[–] Shdwdrgn@mander.xyz 8 points 1 week ago

What, you mean just because Trump is Putin's lap dog? Or because Gabbard is now head of Intelligence?

[–] Shdwdrgn@mander.xyz 3 points 1 week ago

Yeah you're probably right. Reality is a foreign concept to these people.

[–] Shdwdrgn@mander.xyz 36 points 1 week ago (12 children)

Looks like the majority of the storage facilities are in Red states. Even though some are near me, I feel like saying screw it, let them stay unmonitored and lets see what blows up. A blunder of that magnitude would shake up even the most die-hard MAGAt.

[–] Shdwdrgn@mander.xyz 8 points 1 week ago (2 children)

Man what are the odds??? I just finished the last episode today too! I've been dragging along on this last season because, ya know, last season and all, but it did certainly end with quite a bang.

[–] Shdwdrgn@mander.xyz -1 points 1 week ago (2 children)

Why would that have any affect on heart attacks? That reminds me of people saying that changing the clocks leads to more car wrecks when it's just really showing how many people are unable to drive in the dark.

[–] Shdwdrgn@mander.xyz 33 points 1 week ago (13 children)

Trump's ratings are going to fall like a rock as his supporters realize how much his policies are hurting them directly. I saw a post over the weekend from a lady screeching that her package from Temu was being held for a $42 tariff payment but Trump told her tariffs wouldn't affect Americans... Welcome to the "find out" phase, idiot.

[–] Shdwdrgn@mander.xyz 3 points 1 week ago

Haha yeah storage capacity just keeps going up fast. Now that you mention it, I do recall the performance on these drives was supposed to be just absolute crap, but it was a massive innovation before chip storage came out. And some day the next big thing will be released and we'll wonder how we put up with SSD drives.

[–] Shdwdrgn@mander.xyz -1 points 1 week ago (1 children)

The numbers on the clock have magical powers as far as what time I am expected to report to work. Most people do not start work at 4:30am when the sun come up (if you do NOT change the clocks), so that would mean more hours of the day lost. If you have the energy to get up early and do things for work, great for you, but the rest of us sleep until the alarm and use that extra evening hour to get things done. Now it's easy to say 50% of the population is wrong when we look at the current administration, but having the sub come up at 4:30am doesn't really help you and for most people it means trying to get those last couple hours of sleep while the sun is shining in your eyes. What you're suggesting is useful for a small handful of people in exchange for fewer hours of good rest for the majority of the population.

 

I'm wondering if anyone has found (free) sources of data to use for live elections results, specifically the Presidential race? I've been building a map of poll results but would also like to put something together to watch the race tomorrow night.

 

A 1930s-era breakthrough is helping physicists understand how quantum threads could weave together into a holographic space-time fabric.

 

I would love to have them light up like a scoreboard as each representative takes the floor, showing all of the commandments they have broken. If people want so badly to bring religion into politics then lets just show them exactly who they've been voting for. Maybe we can get the news networks in on this too, displaying it on the side of the screen similar to a sporting event.

 

Marjorie Taylor Greene, the bastion of factual information, has once again shown the nature of her character by claiming that peaceful protestors at the Capitol are in fact an "insurrection of terrorists". Don't you see all the violence and mayhem being caused in this video clip? No, me either...

If you want to make such bold comparisons, lets start out by checking how many people are running for their lives or the number of deaths involved between these two events. Or maybe we should be asking why MTG thought it was an "honor" to meet with the people responsible for murder and the attempt to destroy our democracy?

 

I have an annoying problem on my server and google has been of no help. I have two drives mirrored for the OS through mdadm, and I recently replaced them with larger versions through the normal process of replacing one at a time and letting the new drive re-sync, then growing the raids in place. Everything is working as expected, with the exception of systemd... It is filling my logs with messages of timing out while trying to locate both of the old drives that no longer exist. Mdadm itself is perfectly happy with the new storage space and has reported no issues, and since this is a server I can't just blindly reboot it to get systemd to shut the hell up.

So what's the solution here? What can I do to make this error message go away? Thanks.

[Update] Thanks to everyone who made suggestions below, it looks like I finally found the solution in systemctl daemon-reload however there is a lot of other great info provided to help with troubleshooting. I'm still trying to learn the systemd stuff so this has all been greatly appreciated!

 

Just in case there are others like myself who rarely check reddit any more, I thought it would be helpful to cross-post this. It won't look like much unless you have the solar eclipse glasses, but I plan to break out my tracker and camera (with solar filters!) to try and get some pics.

 

I've spent the past day working on my newest Poweredge R620 acquisition, and trying to nail down what things I can do without checking. Google has shown me that everyone seems to be having similar issues regardless of brand or model. Gone are the days when a rack server could be fully booted in 90 seconds. A big part of my frustration has been when the USB memory sticks are inserted to get firmware updated before I put this machine in production, easily driving times up to 15-20 minutes just to get to the point where I find out if I have the right combination of BIOS/EUFI boot parameters for each individual drive image.

I currently have this machine down to 6:15 before it starts booting the OS, and a good deal of that time is spent sitting here watching it at the beginning, where it says it's testing memory but in fact hasn't actually started that process yet. It's a mystery what exactly it's even doing.

At this point I've turned off the lifecycle controller scanning for new hardware, no boot processes on the internal SATA or PCI ports, or from the NICs, memory testing disabled... and I've run out of leads. I don't really see anything else available to turn off sensors and such. I mean it's going to be a fixed server running a bunch of VMs so there's no need for additional cards although some day I may increase the RAM, so I don't really need it to scan for future changes at every boot.

Anyway, this all got me thinking... it might be fun to compare notes and see what others have done to improve their boot times, especially if you're also balancing your power usage (since I've read that allowing full CPU power during POST can have a small effect on the time). I'm sure different brands will have different specific techniques, but maybe there's some common areas we can all take advantage of? And sure, ideally our machines would never need to reboot, but many people run machines at home only while being used and deal with this issue daily, or want to get back online as quickly as possible after a power outage, so anything helps...

 

I have been struggling with this for over a month and still keep running into a brick wall. I am building a new firewall which has six network interfaces, and want to rename them to a known order (wan[0-1], and eth[0-3]). Since Bullseye has stopped honoring udev rules, I have created link files under /etc/systemd/network/ for each interface based on their MAC address. The two WAN interfaces seem to be working reliably but they're not actually plugged into anything yet (this may be an important but untested distinction).

What I've found is that I might get the interfaces renamed correctly when logging in from the keyboard, and this continues to work for multiple reboots. However if I SSH into the machine (which of course is my standard method of working on my servers) it seems to destroy systemd's ability to rename the interface on the next boot. I have played around with the order of the link file numbers to ensure the renumbering doesn't have the devices trying to step on each other, but to no avail. Fixing this problem seems to come down to three different solutions...

  • I can simply touch the eth*.link files and I'm back up afte a reboot.
  • Sometimes I have to get more drastic, actually opening and saving each of the files (without making any changes). WHY these two methods give me different results, I cannot say.
  • When nothing else works, I simply rename one or more of the eth*.link files, giving them a different numerical order. So far it doesn't seem to matter which of the files I rename, but systemd sees that something has changed and re-reads them.

Another piece of information I ran across is that systemd does the interface renaming very early in the boot process, even before the filesystems are mounted, and that you need to run update-initramfs -u to create a new initrd.img file for grub. OK, sounds reasonable... however I would expect the boot behavior to be identical every time I reboot the machine, and not randomly stop working after I sign in remotely. I've also found that generating a new initrd.img does no good unless I also touch or change the link files first, so perhaps this is a false lead.

This behavior just completely baffles me. Renaming interfaces based on MAC addresses should be an extremely simple task, and yet systemd is completely failing unless I change the link files every time I remote connect? Surely someone must have found a reliable way to change multiple interface names in the years since Bullseye was released?

Sorry, I know this is a rant against systemd and this whole "predictable" naming scheme, but all of this stuff worked just fine for the last 24 years that I've been running linux servers, it's not something that should require any effort at all to set up. What do I need to change so that systemd does what it is configured to do, and why is something as simple as a remote connection enough to completely break it when I do get it to work? Please help save my sanity!

(I realize essential details are missing, but this post is already way too long -- ask what you need and I shall provide!)

tl;dr -- Systemd fails to rename network interfaces on the next cycle if I SSH in and type 'reboot'

 

Your dreams and imagination evolved as a view into another universe. As with the current beliefs, you cannot decipher technical information -- no words in books, no details of how devices work, so even if you can describe things you see from another place, you could not reproduce a working version.

Now how do you convince others that the things your are seeing are really happening without being labeled insane? And how could you use this information to benefit yourself or others? Take a peek into the multiverse to see how other versions of yourself have solved these problems...

view more: next ›