Just had to add myself to the “render” group in /etc/group…
So I don’t need to be running a GUI…
Started reading all sorts of slop that Google’s AI served me about dummy HDMI dongles, BIOS settings, GRUB settings, module settings…
And it was simple as “vigr” - and add my user account to “render” group - logout and SSH back in again… Headless server using my Intel ARC A310 GPU for QSV accelerated transcoding and manual conversions using ffmpeg (via ffpb)…
and on the subject of AI slop… Don’t trust it!!!
Got a new speaker delivered today - a bluetooth speaker… Couldn’t remember how to pair it with my other identical one to use them in Stereo Mode - googled it… Google AI’s answer?
Press BT button on both at the same time for 5 seconds… NADA! Was getting nowhere…
Paired, unpaired, from my phone… Reset to factory (“-” and “+” volume buttons at same time)… Nuthin’!
You know things are desperate when I RTFM!
No!
Power on the 1st speaker and make sure it’s paired to your phone (if that’s your source)…
Power on the 2nd speaker…
Hold the BT button on Speaker1 for 5 seconds…
THEN :
Hold the BT button on Speaker2 for 5 seconds…
They then go into party mode - press the BT button on SPKR1 and it will switch to Stereo mode and SPKR1 is Left and SPKR2 is Right…
That took WAY longer than necessary 'cause of AI’s incompetence - and - my own incompetence, complacency, laziness and gullibility for trusting it
At the end of last season, our association ordered 3 new powered bluetooth speakers 250 w each of them for 3 different locations around our village. They arrived the day before our final meeting and I wanted to test them together. Normally I use our main sound system which takes me around 1 hour to move into place then run all the wired connection then set up radio mics etc. I am the only one who knows it so work alone.
This time though new speakers but could not get bluetooth to pair them and running out of time. I Connected music to one speaker by bluetooth then the 3 microphones to the other by radio.
When I set up this next time going to try your idea and see if they all will work together. I bought a couple of câbles just in case.
2. Speakers stéréo 4 speakers quadraphonic. So what is 3 speakers ?
Dont care just want them to work. Also its outside so stéréo and quand does not matter.
Pairing a single “mono” Tribit 2 Micro speaker to to another is a marketed feature of their product… But using their manual (RTFM) is a much better idea than relying on Google AI…
i.e. the sound is okay from one speaker - 1-2 metres (maybe 3) is acceptable - but it’s mono…
Buy a second speaker of the same make and model - and you can pair them together as a stereo speaker set…
It makes a world of difference when you’re listening to Hi-Fi music… “on the go” (e.g. on my e-bike or e-scooter)…
But… they’re quite usable on their own without that feature…
The only reason I bought a 3rd one - was the first one - which I bought in 2023, from Amazon, started fuzzing and making horrible noise on bass… I got it in early 2023 - and it basically cost me nothing, because I left a bad review on Amazon and they refunded me and let me keep the speaker… The whole problem (as reported in my Amazon "*/***** review) was that I’d gotten so used to holding the power button down on headphones and speakers - I thought these ones were the same… Basically - ALL I needed to do was press the power button once…
But it was awesome getting a refund and a free speaker!
And 3+ years for a speaker I cranked a bunch of heavy metal music out of - not an unreasonable lifespan
Moral of the story?
Read The F–king Manual (before relying on any shonky AI answers)!
BTW - normally I’d just “vi” the /etc/group file - since I’ve been doing forever in UNIX (i.e. mostly Solaris)… But lately I’ve started using the proper tools…
I can still remember running “vipw” on SunOS 4.x (i.e. the pre Srv4 / Syv5 Sun UNIX which was mostly BSD)… I’ve never even investigated, properly, the difference between “vi /etc/passwd” and “vipw” (some UNIX systems, and even some Linux distros don’t have either of those alternatives or “aliases”) or “vigr”…
But I learned a few lessons 20+ years ago - instead of : “vi /var/spool/cron/crontabs/root” just run “crontab -e” as root… And same goes for “visudo”… Just use those - your system will thank you for it … “visudo” does a health check if you’ve changed the file… Not sure what “crontab -e” and “vipw” and “vigr” do… But use those instead of “vi [system-file-that-will-break-your-Linux-if-you-get-it-wrong]” … Damn! Should have a failsafe check for “vi /etc/fstab”!
I think “vigr” will remind you - if you save - to check the shadow file as well… No idea why… They’re not closely bound…
Ours are for outdoor use and concerts or conference use. Plus our animation team use them with the kids club so they tend to get abused. End of season sees me strip and repair what I can and mixing bits to make them work.
Radio microphone was always a issue as they get dropped kicked and more abuse. In the end I bought 10 wired microphone to replace for every day use. And keep the radio microphone for adults and conference use.
When kit goes out it works but coming back not always the case.
Our president got annoyed a few weeks back as he took the kit then complained it did not work. Did he change the battery I gave him as a spare as he doesn’t understand switch off when not in use. No.
I prefer vi. If it is my mistake, I can fix it. If if is vipw’s mistake I would not know what to do because I dont understand what it does.
and
Making a special editor for every task is not a good policy. You end up with a dozen half baked editors instead of one good one.
I can understand that… But where it’s a system with potentially a team of experts supporting it - probably best to use the tools… especially visudo…
Linux actively discourages you from using vi to edit the shadow file… But I do it sometimes…
It’s often sometimes quicker and easier to clone a user from one system to another - you can clone their password even if you don’t know it - copy from source, paste their shadow entry into /etc/shadow… But you’re discouraged from doing that… e.g. /etc/shadow is read-only (probably for good reason)…
Hmmm - I just checked my Ubuntu 24.04 and Debian 13 systems - /etc/shadow isn’t read only… hmmm… Odd…
It actually has ZERO permissions on RHEL and OEL (oracle) systems…
CentOS 7 (same on OEL7 and RHEL9 and RHEL10) :
CentOS 7:
╭─>redacted<@>REDACTED< ~
╰─➤ ls -al /etc/shadow
---------- 1 root root 8045 Dec 17 12:38 /etc/shadow
RHEL 10 :
[x@fungzubz00 ~]$ ls -al /etc/shadow
----------. 1 root root 866 Oct 20 09:51 /etc/shadow
Debian 13 (Ubuntu 24.04 the same) :
╭─x@mimas ~
╰─➤ ls -al /etc/shadow
-rw-r----- 1 root shadow 1036 Jan 10 10:04 /etc/shadow
I learned about “edit” - i.e. you can use systemctl to edit the Unit file for a systemd service…
Most of my posts here (in this thread) are about using JellyFin media streamer…
I just tried this :
sudo systemctl edit jellyfin.service
Guess what editor it launched? F–king nano - which I hate! I LOATHE it…
Several reboots and variable exports - and SystemD is ignoring my $SYSTEMD_EDITOR and $EDITOR (I already had the latter set anyway - in /etc/environment) - it point blank refuses to let me use “vi”…
So - BUGGER THAT! I just edited the unit file directly :
cd /etc/systemd/
vi ./system/jellyfin.service.d/jellyfin.service.conf
another major gripe against f–king Debian - they disable mouse X-select - even when remote! WTF? Why? They’ve been doing it since at least Debian 12 (e.g. on my main Pi4 “headless server” running Raspbian 12 “bookworm”)…
So - I have to edit each user (mine “x” and root’s “root”) .zshrc and/or .bashrc :
syntax on
set mouse-=a
set ttymouse=
I generally, as a rule, don’t change root’s shell - anywhere - I leave it at the default of bash… But I nearly always setup zsh and oh-my-zsh for my own user account “x”…
Anyway - now when I reboot my JellyFin server - it waits to start JellyFin until my NAS is mounted (/mnt/BARGEARSE).
