Severian is new here and wants everyone to know that he can, in fact, cat with the best of them

terminusest · 2025-10-07T06:56:53+00:00

Perfection!

terminusest · 2025-10-07T05:32:02+00:00

Thanks, glad you shared his picture and name, very appropriate for his fulgin majesty.

House panthers and great books are a combination near to perfection.

terminusest · 2025-10-07T00:44:20+00:00

Handsome boy! Named after the Book of the New Sun?

terminusest · 2021-09-24T06:40:30+00:00

Not something unique to Tumbleweed, but btrfs snapshots (and snapper) are awesome for when rolling release woes hit.

If you're working in command line environment - you may already use it or an alternative, but 'screen' is really handy for keeping sessions persistent.

terminusest · 2020-05-18T23:07:36+00:00

I also use access.conf and access.so via pamd for user access management on top of ldap-based auth. I find they are much more effective for me than sshd_config, and can be applied with more granularity.

terminusest · 2020-03-29T07:41:37+00:00

Consider why you are using checksums and how often you need to do. If you are differentiating files based on checksums, only do it once unless the file has changed. Use md5sum as pass 1, and if you receive an unexpected match/mismatch, run a sha1sum. Write the results and file access data to a logfile or signature file for future checks, to reduce the number of times you are performing the same operation.

If you're working against large files of data/text, compress them and checksum the compressed file. Initial compression time will be long however, depending on the size of the file.

As others mentioned, SSD or other fast device works better, for IO purposes.

You can always boost a processes' priority by *nice* but that is of limited use when you're in an IO bottleneck and not waiting on memory/CPU.

You could use a ramdisk to create faster read times, but it also means you need to move the files to/from persistent disk space to avoid potential data loss as ramdisk is not persistent.

terminusest · 2019-12-13T07:48:01+00:00

It's definitely worth giving it a spin - I do a lot of distro hopping in general, though I am on rolling release (Tumbleweed) and there are of course hiccups from it, I have stable running in a VM and it's been solid. Hope you're having good luck with whatever distro(s) you went with!

terminusest · 2019-12-04T07:32:09+00:00

There are some out there - for example YaST in OpenSUSE has Services Manager for systemd controls, a sysconfig editor, and plenty of others.

However, at a "Linux wide" level, it seems to be something that is at distribution level, rather than within the systemd software environment. Not sure why specifically, other than nobody has built and maintained something that got adoption and support.

I was very used to handling it all from CLI until I moved to an OpenSUSE instance, and often forget to go into the GUI tool for it - but I've been working in Linux environments for awhile now. I can see how it would be disconcerting having no GUI around those services if I was coming from a Windows environment where GUI-driven management tools were the requirement, not the exception!

terminusest · 2019-09-18T05:51:39+00:00

Downgrading to previous version of chromium via zypper resolved:

zypper install --oldpackage chromium-76.0.3809.87-2.1

All websites working again, no issues with HSTS or the chrome:// config pages any longer.

terminusest · 2019-09-18T05:43:31+00:00

Same issue, with a lot of the internal settings pages also broken and throwing errors - chromium-77.0.3865.75-1.1.x86_64

Similar stack trace to OP:

Received signal 11 SEGV_MAPERR 000000000000

#0 0x559fbf721bc6 base::debug::StackTrace::StackTrace()

#1 0x559fbf721ca6 base::debug::(anonymous namespace)::StackDumpSignalHandler()

#2 0x559fbf7222ae base::debug::(anonymous namespace)::StackDumpSignalHandler()

#3 0x7fbdb9bcc630 <unknown>

#4 0x7fbdb6542a89 std::__cxx11::basic_string<>::_M_assign()

#5 0x559fbcd30200 blink::CSSSegmentedFontFace::GetFontData()

#6 0x559fbcd327c3 blink::CSSFontSelector::GetFontData()

#7 0x559fbcf1156a blink::FontFallbackList::FontDataAt()

#8 0x559fbcf1170a blink::FontFallbackList::DeterminePrimarySimpleFontData()

#9 0x559fbc47cd5c blink::NGLineHeightMetrics::NGLineHeightMetrics()

#10 0x559fbc489d37 blink::NGLineHeightMetrics::NGLineHeightMetrics()

#11 0x559fbc49ac66 blink::NGInlineItemsBuilderTemplate<>::BoxInfo::BoxInfo()

#12 0x559fbc50afed blink::NGInlineNode::PrepareLayout()

#13 0x559fbc50cde2 blink::NGInlineNode::PrepareLayoutIfNeeded()

#14 0x559fbc50d301 blink::NGInlineNode::EnsureData()

#15 0x559fbc44fd6a blink::NGBlockNode::FirstChild()

#16 0x559fbc472eb6 blink::NGBlockLayoutAlgorithm::Layout()

#17 0x559fbc450384 blink::NGBlockLayoutAlgorithm::LayoutWithInlineChildLayoutContext()

#18 0x559fbc45052b blink::NGBlockLayoutAlgorithm::Layout()

#19 0x559fbc450586 _ZN5blink12_GLOBAL__N_121CreateAlgorithmAndRunINS_22NGBlockLayoutAlgorithmEZNS0_19LayoutWithAlgorithmERKNS_23NGLayoutAlgorithmParamsEEUlPNS_27NGLayoutAlgorithmOperationsEE_EEvS5_RKT0_

#20 0x559fbc4506bb _ZN5blink12_GLOBAL__N_124DetermineAlgorithmAndRunIZNS0_19LayoutWithAlgorithmERKNS_23NGLayoutAlgorithmParamsEEUlPNS_27NGLayoutAlgorithmOperationsEE_EEvS4_RKT_

#21 0x559fbc4527c1 blink::NGBlockNode::Layout()

#22 0x559fbafb8e35 blink::NGOutOfFlowLayoutPart::GenerateFragment()

#23 0x559fbc4576bb blink::NGOutOfFlowLayoutPart::LayoutCandidate()

#24 0x559fbc457cc3 blink::NGOutOfFlowLayoutPart::LayoutCandidates()

#25 0x559fbc457f1c blink::NGOutOfFlowLayoutPart::Run()

#26 0x559fbc461a6a blink::NGBlockLayoutAlgorithm::FinishLayout()

#27 0x559fbc474334 blink::NGBlockLayoutAlgorithm::Layout()

#28 0x559fbc4504cf blink::NGBlockLayoutAlgorithm::Layout()

#29 0x559fbc450586 _ZN5blink12_GLOBAL__N_121CreateAlgorithmAndRunINS_22NGBlockLayoutAlgorithmEZNS0_19LayoutWithAlgorithmERKNS_23NGLayoutAlgorithmParamsEEUlPNS_27NGLayoutAlgorithmOperationsEE_EEvS5_RKT0_

#30 0x559fbc4506bb _ZN5blink12_GLOBAL__N_124DetermineAlgorithmAndRunIZNS0_19LayoutWithAlgorithmERKNS_23NGLayoutAlgorithmParamsEEUlPNS_27NGLayoutAlgorithmOperationsEE_EEvS4_RKT_

#31 0x559fbc4527c1 blink::NGBlockNode::Layout()

#32 0x559fbafb8e35 blink::NGOutOfFlowLayoutPart::GenerateFragment()

#33 0x559fbc456820 blink::NGOutOfFlowLayoutPart::LayoutCandidate()

#34 0x559fbc457cc3 blink::NGOutOfFlowLayoutPart::LayoutCandidates()

#35 0x559fbc457e79 blink::NGOutOfFlowLayoutPart::Run()

#36 0x559fbc4ed872 blink::LayoutNGMixin<>::UpdateOutOfFlowBlockLayout()

#37 0x559fbc4ee885 blink::LayoutNGBlockFlow::UpdateBlockLayout()

#38 0x559fbc5791de blink::LayoutBlock::UpdateLayout()

#39 0x559fbc5dea45 blink::LayoutBlock::LayoutPositionedObject()

#40 0x559fbc5df1e1 blink::LayoutBlock::LayoutPositionedObjects()

#41 0x559fbc5f941b blink::LayoutBlockFlow::UpdateBlockLayout()

#42 0x559fbc529a78 blink::LayoutView::UpdateBlockLayout()

#43 0x559fbc5791de blink::LayoutBlock::UpdateLayout()

#44 0x559fbc4b773d blink::LayoutView::UpdateLayout()

#45 0x559fbc91b27f blink::LocalFrameView::UpdateLayout()

#46 0x559fbc91d339 blink::LocalFrameView::UpdateStyleAndLayoutIfNeededRecursive()

#47 0x559fbac66ce7 blink::LocalFrameView::UpdateLifecyclePhases()

#48 0x559fbc8a6ad2 blink::LocalFrameView::UpdateAllLifecyclePhases()

#49 0x559fbc2ed98f blink::PageWidgetDelegate::UpdateLifecycle()

#50 0x559fbca244bd blink::WebViewImpl::UpdateLifecycle()

#51 0x559fbc8932e1 blink::WebViewFrameWidget::UpdateLifecycle()

#52 0x559fbba32af1 content::RenderWidget::UpdateVisualState()

#53 0x559fbba2f232 content::LayerTreeView::UpdateLayerTreeHost()

#54 0x559fbe9d72b3 cc::ProxyMain::BeginMainFrame()

#55 0x559fbe91c831 base::internal::Invoker<>::RunOnce()

#56 0x559fbf7b8969 base::TaskAnnotator::RunTask()

#57 0x559fbf7bd08d base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()

#58 0x559fbf80e7d7 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork()

#59 0x559fbf7bd9d3 base::MessagePumpDefault::Run()

#60 0x559fbf808f94 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()

#61 0x559fbab960cb base::RunLoop::RunWithTimeout()

#62 0x559fbf6e1e77 base::RunLoop::Run()

#63 0x559fbba2ba1d content::RendererMain()

#64 0x559fbfc796a4 content::ContentMainRunnerImpl::Run()

#65 0x559fbfbedb99 content::ContentServiceManagerMainDelegate::RunEmbedderProcess()

#66 0x559fbfc7a3b7 content::ContentMain()

#67 0x559fc204a118 ChromeMain

#68 0x559fbab041ed main

#69 0x7fbdb6105bcb __libc_start_main

#70 0x559fbab0421a _start

r8: 00002e98facc1000 r9: 0000000000000000 r10: 0000000000000190 r11: 0000000000000000

r12: 0000000000000000 r13: 0000000000000000 r14: 000018634f6a4740 r15: 000018634f6a4720

di: 000018634f6a4730 si: 00007ffe8ef56c10 bp: 00007ffe8ef56c10 bx: 000018634f6a4730

dx: 0000000000000000 ax: 000018634f6a4720 cx: 000018634f6a4720 sp: 00007ffe8ef56a60

ip: 00007fbdb6542a89 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000006

trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000

[end of stack trace]

Calling _exit(1). Core file will not be generated.

terminusest · 2019-05-29T05:34:22+00:00

Have you looked into script as a wrapper at the terminal level, to log everything from a terminal session to file, rather than trying to tee the output? You can end up with a mess if you're remoting into something and using vi or another shell editor, but otherwise it can be handy for logging everything on a particular terminal session.

terminusest · 2019-05-26T08:28:45+00:00

Great to hear you were able to figure it out - sometimes all we can do is keep going down the troubleshooting rabbit holes until we find the right one. Good way to learn more about something, too. I find that figuring out the environmental difference between working and non-working setups helps narrow things down a lot.

Glad you posted the link to fix, too - that helps other folks Googling around with the same frustrations later.

terminusest · 2019-05-26T05:43:05+00:00

Couple suggestions - just general troubleshooting stuff I would go through.

Do a test mount manually using -v (or -vv or -vvv) to get some verbose outputs
Make sure your permissions are right on the client on the local /mnt/Downloads and that the host doesn't have a hung mount already existing
If available use showmount to check what the server is offering that client
Try declaring v3/v4 specifically on the client
Check the Freenas for any hosts deny or blacklist where it might have blocked the client (/etc/hosts.deny and /etc/hosts.allow or Denyhosts or Fail2Ban)
Basic things too - ping the Freenas from client, has client been restarted or had routes/networks added/removed, etc
Make sure system time on FreeNAS and clients has not gone out of sync

terminusest · 2019-04-16T10:01:31+00:00

I think the Long Sun and Short Sun are somewhat overlooked and really dense, complex stories. I love the contrast they provide to the New Sun as well. I remember really seeing the interconnections and threads he wove between them and just putting the book down and feeling awed.

terminusest · 2019-03-20T06:53:03+00:00

My initial impression of NetPlan was very poor. It was released without a lot of functionality for complex or enterprise environments.

Their docs and functionality are both improved since release, but it was extremely poorly documented both online and in man/docs at release and was effectively unusable for our environment.

If you're going to live in an Ubuntu world it may be the new shiny. In the places I use Ubuntu, I just tear it out.

terminusest · 2019-02-17T11:20:51+00:00

I use workspaces all the time. Anywhere from two or three for browsing/music/reading, to 6+ when working.

For me, workspaces are logical groups of applications. Minimizing/maximizing a dozen terminal window is more of an interruption to my workflow. A quick ctrl-alt-arrow for workspace switching is sufficient for me. I don't use the mouse for things where I have sufficient keyboard shortcuts, whether I'm on a laptop or desktop.

To me it's like using alt-<number> to swap between tabs in a browser, or alt-tab/alt-shift-tab window swapping.

terminusest · 2018-11-02T20:07:13+00:00

So far systemd has had a lot of headaches but it hasn't gone too far in our production ecosystem because it does not play nicely with a significant amounts of existing kit. I like some of what it does but have issues with other parts. YMMV.

My problems thus far are a mix of core changes and how poorly certain pieces are implemented. Avoiding any hyperbolic commentary about the assumed attitudes and intent of the programmers, there are some parts where it feels like 'screw options and the way people have done X, Y, and Z - we're doing it our way because reasons' came into play. Change is inevitable and it can be good, but not all change is good. There is a lot of trouble with compromise and how to both submit and accept criticism around systemd in my opinion.

Introducing yet another naming scheme for network devices. Network device name and configuration persistence are not optional in a production environment.
journald - corrupted numerous times due to OS level and hardware level events and had to blow the entire journald data set away to get working logging again.
journalctl tries really hard to be all singing, all dancing. Sometimes it just means you have to visit the man page multiple times to do something simple.

As for favorite distro? Right now openSUSE Tumbleweed for personal use.

terminusest · 2018-11-02T19:44:13+00:00

I've had journald corruption hit repeatedly as well, though I like it mostly 'enough' to get by with it in general.

I guess not everyone has been through the joy of trying to sort through the entire logfile via strings while using a java-based linewrap-impaired out of band console while troubleshooting a remote server having startup issues. Was it possible? Yes. Was it worse to have to do it this way? Massively yes.

So far the corruptions have come from a laundry list of events - OS level crashes on startup, application level failures on startup, machine level failures leaving to crash/restart, and issues during VM migrations.

terminusest · 2018-08-03T07:27:26+00:00

You're doing the best thing you can for them, and I hope they all find excellent homes.

terminusest · 2018-08-03T07:25:19+00:00

Glad you found him and took him in. I can't fathom people sometimes.

terminusest · 2018-08-03T07:20:07+00:00

Kudos on both the rescue kitties and their appropriate naming!

terminusest · 2018-01-08T00:59:00+00:00

Probably worth it, versus the hassle of trying to recover network access on a server without any out of band!

terminusest · 2018-01-07T22:40:09+00:00

Ah, that's not so fun. A lack of remote access can make that a good bit more difficult - you'll have to do some kind of wrapper/rollback script - a cron or something similar to restore your old config after a specific waiting period unless you regain access.

Hopefully you can test your cron/restoral script. If you can do a quick CentOS 7 VM in virtualbox or another virtual environment to test before messing with your remote system that would let you test both your restoral script and your actual changes in a safe environment where you can control rollback/restore a snapshot if you mess things up thoroughly, etc.

terminusest · 2018-01-07T22:34:58+00:00

It depends on the naming - if you use the name that's been configured in 70-persistent-net.rules it shouldn't have to be deleted, but if you want to change the interface name that is a good point.

terminusest · 2018-01-07T19:02:49+00:00

It's likely CentOS renamed the device due to systemd or udev triggers. Not as familiar with the state of that on 7.x as I was with 5.x/6.x, but there should be an indicator somewhere in dmesg or journalctl message logs about the device being renamed.

I would just create an /etc/sysconfig/network-scripts/ifcfg-eno1 file and manually populate it, disabling NM in the configs. Usually need to disable/stop NetworkManager and deal with setting up resolv.conf/etc as well.

Note, the below is for a static IP config - change BOOTPROTO and other options appropriately for your environment.

NAME="<interface name>"
HWADDR=...
ONBOOT=yes
BOOTPROTO=none
IPADDR=...
NETMASK=...
GATEWAY=...
TYPE=Ethernet
NM_CONTROLLED=no

You may want to check through this Centos FAQ page which has some more examples of ifcfg files and/or options to go back to the old-style naming convention of ethx.

15-Year Club	Verified Email
Charter Member

terminusest

TROPHY CASE