What kind of crops are you going to grow at 125°? That's still within OP's specification of triple digits and with temps getting hotter we're likely to see a lot more of this happening within our lifetime.
Yeah I think there's some good ideas that have been built up with the ABL devices over the years, and that mesh leveling seems great. However I also feel like more people should take the time to get their beds physically as flat as possible first, because otherwise your printer spends a lot of time micro-stepping the Z, and I've seen some mesh maps that looked absolutely horrible.
Playing around with arduino devices, I have some laser rangefinders that seem like they could work well for an ABL. That might also be a good way to map out the idea I mentioned about creating a thin full-bed shim to get a truly flat bed, and after that perhaps you would only need to do a fast four-corner calibration with the ABL to make sure nothing has changed.
I've never had auto-leveling on my own printer, but the one at work has it and I wouldn't want it. It was great for the first couple years, then the sensors started suffering from corrosion and now it just doesn't work for crap.
So on my own printer (fully manual) I have always treated the paper test as nothing more than an initial step to make sure the nozzle doesn't plow your bed during the leveling process. It will get you close, but not close enough. To really dial in your bed, you need at least a 5-point 1st-layer print test so you can really get that initial layer adhering nicely at all points, and this of course performs the calibration with the bed at full heat so it matches conditions during actual prints.
The biggest problem I had was my aluminum bed was badly warped when I got it, but fortunately just bowl-shaped. I cut CD-sized discs of aluminum foil to build up the center -- 13 layers in total, then put a glass or G10 bed over that to really get a flat surface. I finished mine with a PEI sticker on top of the G10.
Another problem is that all beds will be completely unique from each other. I have one of the original Ender 3 Pro printers, and purchased a Creality glass bed with it. There was nothing that wouldn't stick to that bed, and I used a 10mm calicat (which has 4mm feet pads) as my tests for all new filament. Clean the surface occasionally with 91% ISO, and life was good... but after a few years the surface wore out and I was forced to get a new bed. Ordered directly from Creality again, and man, nothing at all would stick to that piece of glass, even for large prints. I tried everything down to brake cleaner to solve the problem and finally gave up on it. That's when I started working with the G10. The point of this is that you can tell someone a particular bed will solve all their problems, and you will be wrong. The reality is that sellers use different manufacturers to make their product and you never know what you'll get.
Your observations about the bed warping from the tightness of the screws is interesting, I never thought about that part before. I have heavy springs under my bed, and I have always suggested people get those springs as tight as possibly without being completely closed, then adjust the Z-switch to that point before you start your leveling process. Tight springs means the screws should never wander. It's been around 3 years since the last time I even touched my leveling screws, and I just fired up the printer and ran some new pieces last week without any issues. A good tool is one that you can ignore for a year, then use it without having to recalibrate. Anything else is just frustrating!
There are a lot of suggestions we can make to help newcomers get their bed leveling correct, and there are a lot of variables that we simply can't account for including manufacturer defects. One idea I had years ago but never got around to trying is to print a thin sheet of filament the size of the entire bed, ironed to create a top surface perfectly flat to the nozzle but taking up any imperfections in the aluminum plate. Then put a thin bed over the top of that, and you should have a perfect surface that lasts nearly the life of the printer. Seems like a good idea, but how do you figure out where to fill in those first layers until you have a final layer that covers the full bed?
Oh I have a pretty good idea about that... But I was actually referring to the fact that Trump's platform was the first thing attacked after he bombed the country. Yeah it would be great if we had a government that was focused on letting the various agencies do their jobs rather than dismantling everything that keeps us safe and healthy.
When they're talking about "poorly secured US networks", they're referring to Truth Social, right?
Yes! One of my most favorite Johnny Depp roles.
That's a good point, although flashing does help to grab attention, but it can also be annoying when the person is driving with their foot on the brake pedal.
I suspect a lot of that has to do with the entitled way people are driving these days. If you leave a car length gap, some kid will wrecklessly attempt to cram their way in because your lane momentarily moved slightly faster.
I suspect because there's no consistency in the brightness of vehicle lights. But that's one of the reasons why I think an incremental light bar would be better, there's no variation between vehicles. You could even make it more informative by flashing the whole bar when you first brake, so someone behind you can more easily see how much of the bar is being lit up.
That could probably be implemented in most existing vehicles, and at least it would provide more information.
They don't want to admit they've been screwing us over even though we all know it's happening. All these companies could have rolled out suitable internet speeds a decade earlier but they would rather limit everyone to the lowest common denominator so they don't have to admit just how terrible their equipment is in most locations.
I've gotta say, having city-owned fiber is great, folks here don't have to wait weeks for Comcast to send out a tech who conveniently never shows up on the scheduled day, and customer service actually has a clue what they're talking about. This is how a public service should operate.
I would say cable TV coax has quite a lot more capacity than what the providers let on. In my city they offered up to 50mbps at over $100/month. Then they lost their lawsuit trying to prevent the city from installing its own fiber network and suddenly the cable company decided they could offer 150mbps for around $75/month (with no equipment changes). Once the fiber network started becoming operational (offering 1gbps bidirectional for$50/month) the cable company decided they're better also offer gigabit connection speeds, but once again they simply flipped a switch to increase your bandwidth. This capability has been in place for quite some time, they just didn't want to offer it and their illegal "monopoly" gave them no incentive to provide competitive speeds.
- I say "monopoly" even though we technically also have DSL available in town. However when I asked one of the techs why DSL couldn't give me more than 896kps upload speed, I was told that the cable company had an arrangement with them which prevented the DSL from providing the speeds needed by businesses. After the lawsuit that broke up the state-wide bans on other providers, this practice was exposed and also broken up, so now the telco is able to max out their DSL speeds.
I still think rear signaling could be improved dramatically by using a wide third-brake light to show the intensity of braking.
For example -- I have seen some aftermarket turn signals which are bars the width of the vehicle, and show a "moving" signal starting in the center and then progressing towards the outer edge of the vehicle.
So now take that idea for brake. When you barely have your foot on the brake pedal, it would light a couple lights in the center of your brake signal. Press a little harder and now it's lighting up 1/4 of the lights from the center towards the outside edge of the vehicle. And when you're pressing the brake pedal to the floor, all of the lights are lit up from the center to the outside edges of the vehicle. The harder you press on the pedal, the more lights are illuminated.
Now you have an immediate indication of just how hard the person in front of you is braking. With the normal on/off brake signals, you don't know what's happening until moments later as you determine how fast you are approaching that car. They could be casually slowing, or they could be locking up their wheels for an accident in front of them.
Yikes, that sucks... but at least Linux is still usable.
Hooray for no safety and hooray for death.
Isn't that the Musk philosophy? Kill anyone who gets in the way, and sue everyone else who survives his death traps?
If you want stability, you probably can't beat Debian, and you should be fairly used to the backend by now. I suspect the stylus use is just going to be figuring out what package provided your current access to it.
Before you wipe the laptop, I would recommend finding a command to list all the installed packages, then at least you'll have a reference to what was in place before. And if possible, maybe grab a backup of the /etc folder (or whatever might still be accessible) so you can reference the current configs on various packages to recreate whatever doesn't work by default.
There are a number of lightweight desktops you can choose from. I personally like Mate, but maybe you can play around with others on the new system and purge the ones you don't like. And while you're swapping drives, check the memory slots, maybe you can drop another 8GB stick in there to give the whole system a boost.
Maybe if the administration wasn't actively dismantling out national security, this wouldn't be as big a problem. Russians attacking out computer systems? Meh, we'll just stop looking and maybe they'll go away. And lets just make enemies of all our allies so they don't trust sharing security information with us -- what could go wrong? And for the cherry on top, let's threaten a military takeover of neighboring friendly countries, because "trust me, bro".
This is just another manifestation of the alternate reality Trump lives in. He's so convinced that everything he does is golden, and he's surrounded himself with yes-men who hide the truth from him (like Gabbard telling agents they need to change their intelligence reports to make Trump happy), so every time reality intrudes on his fantasy world he lashes out as if companies are doing this just to make HIM look bad. No dumbass, they're doing it because you fucked things up so badly that the market cannot cover up your gross negligence.
You might check if a simple CPU upgrade would get you there. I previously ran some 2005 Poweredge servers that came with a Pentium D processor, and it cost me something like $8 from ebay to upgrade to a Xeon and start running KVM.
Keep an eye out for people trashing perfectly good desktop machines because Windows 10 is being retired.
If you want a server that "does it all" then you would need to get the most decked-out top of the line server available... Obviously that is unrealistic, so as others have mentioned, knowing WHAT you want to run is required to even begin to make a guess at what you will need.
Meanwhile here's what I suggest -- Grab any desktop machine you can find to get yourself started. Load up an OS, and start adding services. Maybe you want to run a personal web server, a file server, or something more extensive like Nextcloud? Get those things installed, and see how it runs. At some point you will start seeing performance issues, and this tells you when it's time to upgrade to something with more capability. You may simply need more memory or a better CPU, in which case you can get the parts, or you may need to really step up to something with dual-CPU or internal RAID. You might also consider splitting services between multiple desktop machines, for instance having one dedicated NAS and another running Nextcloud. Your personal setup will dictate what works best for you, but the best way to learn these things is to just dive in with whatever hardware you can get ahold of (especially when it's free), and use that as your baseline for any upgrades.
I built a new firewall under Debian 12. The machine has eight network ports, and during configuration I accidentally used the same name for a couple of the ports in the files under /etc/systemd/network/*.link. I ended up with two link files referencing two different MAC addresses but naming each of them as WAN0, and once systemd got that configuration it wouldn't let it go.
From what I could find online, normally I would just issue systemctl daemon-reload followed by a update-initramfs -u and after a reboot systemd should have had the updated information... but no dice this time. The way I finally discovered the problem was when I noticed under ifconfig that my wan0 port was pointing to the wrong MAC address (even though the link files had been corrected).
After several hours of fighting with it, I finally managed to get it to work by renumbering all of my link files, and now the information for each port matches up correctly. But my real question here is WHY did systemd refuse to read updated link files? Is there another step I should have taken which was mysteriously never mentioned in any of the dozens of web pages I looked at trying to fix this? I really need to understand the proper process for getting it to correctly use these files so I can maintain the machine in the future.
(God I miss the reliability of udev already)
I'm building a new rack server (Poweredge R620) and am using the option "consoleblank=600" in the GRUB_CMDLINE_LINUX setting. During the setup I used the wrong memory stick and installed Bullseye, and screen blanking was working correctly there. Since I had already finished nearly all the configuration this week, I thought it would be easier to just do a regular dist upgrade than reloading the whole system.
After upgrading to Bookworm and rebooting, I notice that now when the screen blanking is supposed to kick in (which normally just turns off the display), I am instead getting what looks like rolling static on the screen. I have several other R620 racks running Buster so I know the screen blanking should work with this hardware, but this appears to be an issue specific to Bookworm.
Note that even when I try something like setterm -blank 1 or setterm -powerdown 1 I get the same resulting static after 1 minute. To be clear, this is specifically for the command line, I do not run desktops on my servers.
A google search for the problem has been unsuccessful so I'm hoping someone can point me to a solution or help with the proper search terms.
The U.S. Army Corps of Engineers just opened up two California dams. A spokesperson says the flows are 'controlled' and being coordinated with local officials.
This is all pretty bonkers for a lot of reasons.
U.S. public health officials have been told to stop working with the World Health Organization, effective immediately. A U.S. Centers for Disease Control and Prevention official, John Nkengasong, sent a memo to senior leaders at the agency on Sunday night telling them that all staff who work with t...
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've seen the occasional blip here, but this is the first time I've seen a complete outage of this instance. Hoping @Salamander wanders through and gives us the scoop?
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!
The Saturday, Oct. 14, 2023, annular solar eclipse will cross North, Central, and South America. It will be visible in parts of the United States, Mexico, and many countries in South and Central America.
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
touchthe 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...
I have a self-hosted matrix-synapse server up and running on a Debian linux server, but before I open it up I want to at least get a captcha service in place to reduce spamming. The only module I've seen to handle this function appears to require setting up a Google recaptcha though, however I would prefer to keep all of this entirely self-contained for the privacy of my users. Can anyone recommend a module that allows for a local captcha option? For that matter, can anyone also recommend a captcha system that is pretty straightforward to set up (which is compatible with matrix-synapse) and uses basic preinstalled code bases like perl or python?
And while I'm here, I would also like to provide the option of registering with an email address, but I'm having trouble finding any clear how-to pages on this. Seems like that function might be built directly in to matrix-synapse but I'm just not finding anything helpful. Any suggestions?
I'm fairly new to matrix in general, but I have an initial setup running with the homeserver, Element web page, and an IRC bridge, so if I can just nail down the validation part of registrations I'll have what I think is a good starting point to launch from.
I was reading another article which discussed taking measurements of distance stars at 6-month intervals to create a 3D map of their relative positions and direction of movement. This got me to thinking... has anyone proposed 'dropping' stationary satellites outside of Earth's orbital path for continuous monitoring even when our planet is no longer in that spot? It seems like such an arrangement could provide constant monitoring of things that are happening on the far side of the sun, and they could each act as a relay to each other, bringing the signals back around where we could receive them.
It could be fascinating to be able to constantly monitor the path of know comets, or perhaps even to detect large meteors which are safely away from us now but might some day pose a threat. Studies like mapping star positions could rapidly expand with the availability of continuous data feeds, and I'm sure if such a tool were available scientists would come up with a host of new experiments to try.
A couple other things also come to mind. First off is radio telescopes, which can gather more sensitive data by having sensors further apart. Of course in this case they would only be able to peer in two directions unless you set up the array to rotate as a singular ring (which greatly increases the complexity). The other idea was that I know some phenomena are so large that it takes a huge array of telescopes or sensors to even detect them, and something this large could detect truly astounding low frequency events. Throw in some gravity detectors and watch as the waves propagate through our solar system.
I'm just thinking there's a lot of possibilities here and a lot more data could be collected if we could drop four or eight satellites along the way. I would assume the idea has been proposed before, I just didn't know if this is even feasible?
Turns out both grow in my area, and look identical to this when young. Yikes! So based on a post yesterday, I took this outside and sliced it in half. So far it looks promising (I think?) and I'm not dead yet.
This was found growing in a Colorado yard near the base of an elm tree, in an area where there are also rotting cottonwood roots. Altitude is right at 5000 feet. It wasn't my yard so I'm not sure how many days it may have been growing before I picked it today. I have put both halves in the fridge for now, is there any other information I can provide to help identify it?
A full size copy of the inside can be viewed here: http://sourpuss.net/projects/mycology/2023-08-13/IMG_7239.JPG
I've been running systems up to Buster and have always had the 'quiet' option in the grub settings to show the regular service startup messages (the colored ones showing [ok] and such but not all the dmesg stuff). I just upgraded a server to bullseye and there are zero messages being displayed now except an immediate message about not being able to use IRQ 0. Worse, google can't seem to find any information on this. If I remove the quiet option from grub then I see those service messages again, along with all the other stuff I don't need.
What is broken and how do I fix this issue? I assumed it would be safe to upgrade by now but this seems like a pretty big problem if I ever need to troubleshoot a system.
[Edit] In case anyone else finds this post searching for the same issue… Apparently the trick is that now you MUST install plymouth, even on systems that do not have a desktop environment. For whatever reason plymouth has taken over the job of displaying the text startup messages now. Keep your same grub boot parameters (quiet by itself, without the splash option) and you will get the old format of startup messages showing once again. It’s been working fine the old way for 20+ years but hey let’s change something just for the sake of confusing everyone.
[Edit 2] Thanks to marvin below, I now have a final solution that no longer requires plymouth to be installed. Edit /etc/default/grub and add systemd.show_status=true to GRUB_CMDLINE_LINUX_DEFAULT. In my case to full line is:
GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.show_status=true"
Don't forget to run update-grub after you save your changes.
I run my own email server, and a friend received a compromised laptop from work which resulted in a spam attack from Russia yesterday. Turtle settings saved the days with thousands of emails still in the queue when I saw the problem, however it made me realize that everyone with accounts on my server are local, do not travel, and have no requirement to send emails from outside the country.
I found how to use the smtpd_discard_ehlo_keyword_address_maps setting in postfix to block a CIDR list of IPs, then found a maintained list of IPs by country codes on github. Cool so far, and a script to keep my local list updated was easy enough.
Now the question is, what countries should I be blocking? There are plenty of lists of the top hacking sources, but it's hard to block #2 (the US) when that's where I am located. But otherwise, does anyone have a list of countries they outright block from logging on to their servers? From the above google searches I have 17 countries blocked so far, and in the first 30 minutes already stopped login attempts from three of those countries, so it appears to be working.
Of course I could write a script to parse my logs to see who has already made attempts, but that's what services like fail2ban are for, and I'm just wondering if there are any countries in particular I should directly block? My list so far includes the following: ae bg br cn de hk id in ir iq il kp ng ru sa th vn
The question itself may not be that interesting, but I thought at the very least some folks might be interested in my experience and think about doing something similar themselves. I can post more details of what I did if there is any interest.
A person with way too many hobbies, but I still continue to learn new things.