Search results

Ah, the good old IRC days... I lived them.. one of the biggest moments in my early work experiences was getting approval from the big boss himself that I was allowed to keep an IRC window open during Friday, also because I also used it to talk about tech (Linux / Unix) in addition to some more...

When in doubt about where a file or directory came from try using pkg-which, this checks the package database to look for matches, that should give you more clarity. I never heard of such a folder myself, but obviously that only means so much.

You should have mentioned this in the OP. Context is key in trouble solving. And not started with waving accusations. I mean... if you never used Steam, never installed it, yet suddenly followed a link towards a community then stuff could happen. Not a fault of the link of those who shared it...

I don't disagree, but also fail to understand what's unreliable here. Still, it would be nice if the site could focus on more parts of the community than merely the forum & mailinglists. Maybe a mention of (unofficial) online communities? Because I can definitely see people enjoying those...

I can't help but consider the complaint bogus. If there is an issue it's with OP's local setup, not the wiki nor the links. My client is on Windows and I don't really use Discord all that often (do have it running in the background). So I click on the link... and the next moment I'm there...

Good find T-Daemon! However... I think there's more to this story. When I check vt it confirms that the default on BIOS is text mode, but... So theoretically it should also be possible to use fonts when booting with BIOS. However, it's going to take more work to set it up. Also... and in...

Are you doing this on an actual virtual console (/dev/ttyv0) or are you logged in and thus using pseudo terminals / virtual consoles like /dev/pts/0? Because that can make a major difference.

So, in the mean time I've done a re-install of 14.2 while keeping my eyes peeled and sure enough: I can reproduce the issue: I also get the brief firmware prompt: Right after the enabling of services and before the question about adding new users, easy to miss for sure! I then dove onto the...

What "firmware installation" are you talking about? I think you may have gotten some facts mixed up here, and the reason I say that is because even Google can't tell me anything about this allegid "firmware installation". FreeBSD doesn't even have firmware; though it does provide firmware for...

FreeBSD is all about "The power to serve..." ergo... I'd say the 'experience' is just what you make of it. It can be different for everyone. For me, personally, it's all about control. Full control: try removing wireless tools from a Linux distrbution and you'll most likely see dozens of other...

There's more to this story, also see uefi. When all else fails you should consider falling back to the generic default: /efi/boot/bootx64.efi (note: this is for AMD64, other architectures use other names).

I would strongly recommend against doing that. The correct method is to ensure that whatever user is firing up that logging program has the right permissions to write whatever it wants, whereever it needs. This is normally done using chmod and/or chown, optionally with chflags. This is probably...

OpenZFS has different versions, if those differ too much then you cannot "just" access pools. (edit: the same thing could have happened on FreeBSD too btw.).

Thanks covacat! That leads us to my next question OP: what does # file -s /dev/ada2s3 tell you? Are we sure this is actually EXT4?

Does /dev/ada2s3 even exist? Shouldn't that be ada2p'x's3?

So I figured I'd look into this again, also to see what happened and made it go on... well... That actually made me laugh, thanks for that. I'm a vivid Microsoft 365 user and a vivid user & supporter of VBA (even use VB.NET at times though I prefer C#.NET by far). And within that context: the...

This is just me, myself, and I but I can't help ask: can you share a link with us that shows you asking the same kind of question towards the Linux community? I mean.. just to put the minds of some of us at rest? It would definitely help your credibility. And before you ask: I am fully...

I'm assuming you mean to use the SSH implementation of Windows itself (C:\Windows\system32\openssh\)? Keep in mind that Windows' own implementation of SSH is seriously lacking. I say this because... even with a full blown graphics manager behind it Windows still doesn't accept graphics...

First: consider using a code block, because the above doesn't only work.. it also tries to mock us! :what: Also... it wouldn't even work anyway because: why sh? You're missing a shebang: #!/bin/sh. <= My oversight (= edit2), this is indeed the safer way to go about your command. (edit) =>...

Using CURRENT by any chance? ;) (aka: checked out the source and didn't select a specific Git branch?)