It's a pain to read your reply because it's wrong. The poster you're replying to correctly wrote the phrases and you are trying to malign his or her painstaking work by such a low effort reply without explaining exactly where he or she is wrong
I used Scribus. Top choice for replacing Publisher by open source software. Scribus is very intuitive and with enough time I could churn out a beautiful looking effective resume on my first try
From Wikipedia "...Lundgren received a degree in chemical engineering from the KTH Royal Institute of Technology in the early 1980s and a master's degree in chemical
engineering from the
University of Sydney in 1982...."
Don't build some software that you are going to sell privately because the company can claim you did it on company time and hence it's company's property and not yours. Just my thought. I'm not expert at the leaglities
Just a few hours ago on the irc channel of OpenBSD someone said that OpenBSD is good at not letting a wonky hardware run compared to linux. So you could use the dmesg and ask it in the OpenBSD mailing list and they will point out which wonky hardware is causing trouble and you can replace that problematic part.
I ran OpenBSD current for 6 years and never faced such issue
Years ago (circa ~2005) I was working for a company with a mix of OpenBSD, FreeBSD, Windows, and Linux. I was more of a fan of OpenBSD and I received a lot of grief when the OpenBSD team suddenly ripped out support for one of the Dell hardware RAID controllers (I don't remember which one, but IIRC it was one based on something from Adaptec), claiming they couldn't reliably reverse engineer it to create stable drivers. Their attempts ultimately always ended up with "random" corruption.
A year or so later our main DB on Windows (long story on why we were running windows DBs with most of the other kit being BSD/Linux) had a total corruption incident (it was painful, but we had a replica failover that we recovered from) - turns out we could get an answer from Dell since Windows was obviously supported by Dell themselves. There was a known issue with that model of RAID controller that would result in random and total corruption - and there was no way to fix it in firmware.
I was smug about it, but had to concede that people should still be given an informed choice. IIRC Dell was very quiet about it, which is certainly not "informed choice". Had we known, we'd have shelled out for different hardware for our databases!
To be fair, there was not much Dell could do as their PERC cards were all rebranded Adaptec and later LSI. Adaptec was the gold standard for ages, but I assume was enshitified somewhere along the way. The long term result was that the entire hardware raid world ditched Adaptec for LSI and/or software RAID (eg ZFS). Dell (in those days, not sure if it's still the case) had excellent support. There was a bug on another server model where the onboard video card would eventually fail and fry the motherboard. Even years later out of support, Dell would for free replace it if it failed with whatever new model equivalent existed.
I left the company before things were totally resolved, but I think dell ultimately gave people who complained LSI cards, but it took awhile for those to be designed and manufactured to fit the internal drive slot. Most people who were also using external arrays moved to third party ones or other hardware.
Not the Grand Poster, but we use the Debian package "unattended-upgrades" to install security updates automatically on our servers, and send an email if a reboot is required to complete the process (kernel upgrade).
Unattended upgrades could be configured to install more than the security release. Even with the stable release, one can add the official APT source for the Debian backports.
Back to OpenBSD... realize that it has no "unattended upgrades" capability. Until syspatch(8) appeared in 6.x you had to download patches and rebuild kernel and userland to get security fixes. Today, you could run syspatch(8) in a cron job but that only covers the base system. You'd need to handle any installed packages separately. And only the current and immediately previous release are supported at all. There are two releases a year, so you have to upgrade every ~6 months to stay in the support window.
Fortunately, with the introduction of the syspatch(8) and sysupgrade(8) utilities this is much simpler than it used to be. And, release numbers are just sequential with one point number, i.e. 7.0 was just the next release after 6.9, nothing more is implied by the "major" number ticking up.
Just curious, how do you manage service restarts, just restart as the update finishes?
I think I’m a bit scarred when a docker upgrade took my entire stack down because of an api mismatch with portainer, so I’m trying to be present during upgrades.
Edit: I’m talking about Debian of course. I’m not familiar with OpenBSD.
Debian still has security fixes, and point releases. unattended-upgrades is the package that automates their install.
I think you can also do unattended release upgrades by using the 'stable' release alias in sources. That will probably result in some stuff breaking since there will be package and configuration churn.
I'm not a chemist but my two cents because I studied a course of Industrial Inorganic Chemistry in my college. My professor of that course used to say Hydrogen Peroxide is a very strong carcinogen. So I hate every Tom Dick n Harry that yaps about the goodness of Hydrogen Peroxide on YouTube or elsewhere without mentioning that it will give you cancer even in small amounts. And yes UV disintegrates the fibres so the more you keep your clothes in the sun or in UV then they will look old. Source: I live in India with too much UV andif I keep anything under the sun for a couple of days then it looks old or atleast no more new to be worn fashionably.
Your professor was teaching Industrial chemistry. At industrial (undiluted) strengths, there aren’t many chemicals that can’t damage tissue or potentially cause cancer. Constantly breathing the undiluted fumes or other exposures will certainly carry some risk in an Industrial application.
Washing clothes in a dilute peroxide solution is not going to cause cancer, therefore simply walking outside to hang your clothes carries substantially more cancer risk than the use of Hydrogen Peroxide.
Saying it causes cancer in “small amounts” is a bit like shouting at someone that stepping on a twig is destroying the entire forest…while standing next to an inferno.
I’m neither ingesting, inhaling, nor bathing in it, so I don’t care either, nor would I be concerned to wash my hands in it were it needed. Just drinking water or being outside is more than enough exposure to cancer to be worried about.
Well, it's part of the cancer process; most cancers couldn't survive without it. But that's also true of, for example, local production of DNA, or anaerobic glycolysis, or angioneogenesis.
It's not true that if you expose tissues to lots of H₂O₂ they'll get cancer.
I'm also not a chemist... but I do have a PhD in mtls science from a top 10 program. My dissertation was on computational chemistry on organic compounds.
You're 100% right.
As long as the photon is energetic enough, it can cause a radical and therefore break a chemical bond.
Brighter the sunlight, more peroxides (or radicals) made, more damage to your skin or your cloth's fibers.
This is also why anti-oxidants are so effective at protecting the body, why inflammation is so damaging (body produces peroxides to eliminate what it believes is a threat), over consumption of food, too much/little exercise, etc. they all affect peroxide concentration or their halflife.
right, been glancing at this thread, and what occured to me is that blue light from LED's having a bleaching effect, specificly on yellow(cebum) organic compounds, then implys that it's not just(famously) hard on our eyes, it's frying them, and possibly worse.
I certainly mind a brite screen, and keep it at the minimum level, except when in sunlight or useing my phone to show family and customers things.
There are other effects to mass use of high powere LED's, where seagulls are flying around in downtown Halifax, NS in.the middle of the night, which I see now, but never happened with the old mercury vapour street lighting, which was it's own kind of wierd, in that it's bright yellow light from a distance, but makes everything under them monocromatic.IE: something in.the LED light wakes birds up.
reply