I appreciate the faith you had in me by giving me your e-mail address, that information remains closed and guarded. Today I finally assembled the machine that is to be my new office workstation, although I wasn't anywhere near brave enough to change over to using it on a Friday.For the most part I expect the change over to be pretty straightforward, because I'm just going to transplant all of my current disks into it (and then I'll have to make sure the network interface gets the right name, although I have a plan).So, take a stroll down memory lane to remember all of our past Word of the Year selections.
2 advanced Erweiterte preferences Einstellungen language tools Sprachtools colspan id all radio checked label for Das lgr lr lang Seiten Deutsch cty cr country DE aus Deutschland ads Werbung services Unternehmensangebote about ?
This helpfully gives me a live Linux that I can poke around on and save things from, although it also means that I have pre-existing UEFI boot entries that are going to become invalid the moment I remove the scratch disk.
So I think that what I want to do is something like this: Assuming that I got everything right, at this point I should be able to boot my machine through UEFI instead of through MBR booting.
But having sponsors also meant I had schedules, deals, commitments, ... Some sponsors want to time their new software launch with a big campaign (of which cron.weekly would be one aspect), so I can't just shift them around on a weekly basis. It's no longer a spontaneous non-committal newsletter, it's now a business. If I couldn't get it done on Friday evening, I would spend the rest of the weekend worrying that I couldn't get it done in time. I don't want to say I completely quit, because I might pick it back up again.
Sponsors -- rightfully so -- want to know when they get featured. I all honesty, I'm burned-out from writing cron.weekly. It would keep haunting me in the back of my head " of commitment, something I can't give at the moment. But for now, I need a mental break from the weekly deadlines and to be able to enjoy my weekends, once again. If returns, it will give me the ability to rethink the newsletter, the timings & my commitments.However, I want to switch my Fedora install from its current MBR based booting to UEFI booting (probably with Secure Boot turned on), because it seems pretty clear that UEFI booting is the way of the future (my toe-stubbing not withstanding).My current set of SSD root disks are partitioned with GPT and have an EFI system partition, although the partition is unused and unmounted; while I have a , get populated with the necessary contents (whatever they are), and then set up an UEFI boot entry or two. Currently I have the machine set up with a Fedora 27 install on a scratch disk, so I can run burnin tests and similar things.Today, I'm sending the last issue in what is probably going to be a pretty long time. For now, cron.weekly doesn't fit in that list anymore. A need to read more technical content that I couldn't seem to find in a convenient form. A few years ago my role at Nucleus, my employer, shifted from a purely technical one to the role of being a manager/management.So I started reading news & blogs more intensely and bookmarking whatever I found fascinating. It meant I was losing my touch with open source, projects, new releases, ... Writing cron.weekly forced me, on a weekly basis, to keep up with all the news, to read about new releases, to find new projects. After 2 years, a whopping 8.000 monthly newsletter readers.Or maybe I should just stick to having the basic EFI shell and Grub2 boot environment present, and assume that if I have to boot off the second SSD I'll need to glue things together by hand.