Yes, I need constant reminders of this command. Somehow I always think it's some github coder's child, and not part of coreutils as cat itself. Hopefully it'll stick now.

Typically, I learn a small bit more, with answering questions. This is not Linux, but instead programming.

As part of a discussion about binary versus text files, I included with my answer that the 'b' flag can be used for file open calls, but I've also found that one does not have to use it and they can interpret file contents as either binary or text, no matter if they use, or do not use, the binary flag when opening a file.

As part of that discussion, researching a reference link, and also someone else's response, I've learned that this old notation is truly ancient and that 20-30 years ago the necessity of of requiring that flag was removed from the libraries.

1 members found this post helpful.

I learned that Zoom works quite nicely on Ubuntu MATE, but you have to get the *.deb from the Zoom website. Zoom is not in the repos (not a complaint, just an observation).

I just learnt about the mv command's --backup=numbered argument tonight because of this thread. I posted a demo of that argument here for those that are interested.

Never would of thought to even look for that argument if it wasn't for the OP of said thread claiming that mv is "broken". Always amazing when you come across a thread here not expecting much and discover something that's been sitting right under your nose the whole time... but you just didn't think to look - I've lost count of the number of times that's happened to me here now, really have.

Simon Peter, aka probonopd, maintains a Zoom AppImage. It works well for me.
http://https://github.com/probonopd/...Image/releases

My 'I just learned' is sl -l is not the same as ls -l.

1 members found this post helpful.

Hi Ben. That link doesn't work.

Just remove the extraneous http:// https://github.com/probonopd/Zoom.AppImage/releases

1 members found this post helpful.

Cheers, shruggy. I knew that, I just wanted to highlight it in case others come across it.

Use the inxi command to get system info.

1 members found this post helpful.

GRUB how I hate you, god I miss the days of LILO a simple chroot run the command it wrote using the simple config file you would edit and be done with it and installed. What a steaming pile of dung GRUB is to get the same done, as you may guess I have been doing it this past week I re-learned my total disgust with it....

Edit: Though on a more positive note I do know where every setting is the damn thing uses, now I have had to dig into the guts of it to get it done.

^ Nothing keeps you from using LILO. They say it's outdated, but if it works for your setup, there's no reason not to use it afaics.

I switched to syslinux some time ago, no regrets.

1 members found this post helpful.

'Ctrl + L' doesn't clear the terminal screen; It just scrolls down to a new frame where you can't see the previous output.

2 members found this post helpful.

Depends on the terminal. _rl_term_clrpag and _rl_term_clrscroll are defined in terminal.c in terms of termcap codes.

Not with an EFI setup, it is BIOS only bootloader. And there is something new I learn for this week, elilo and using a stub in your EFI to just boot a kernel without any grub they say. The syslinux seems to be i386 only boot loader the way that page puts it with the 386 & amd64 listed at top for the others, with it specifically omitted from its description, the amd64 it only says i386 (32bit system). With elilo being dead option as it only goes until oldstable in packages by Debian.

https://wiki.debian.org/BootLoader
https://packages.debian.org/search?keywords=elilo

1 members found this post helpful.

syslinux can definitely do EFI setup.

By "i386 only" do you mean it only works on IBM PC type computers? Because it definitely works on Archlinux, which is a 64 bit distro.
I suspect the Debian wiki is outdated, rather than the bootloader(s). Or you just misunderstood.

https://wiki.archlinux.org/index.php/Syslinux