(LIke who gives a bleep in heck about all this crap? It's not a
NECESSARY part of our lives - Thanks to Windows with all it's faults.)

https://www.geeksforgeeks.org/7-things-you-should-know-before-switching-to-linux/

Basic Technical Knowledge is Required

As a Linux user, you can control the complete system through the
terminal. Linux comprises various commands to simplify daily tasks.
Hence, it is essential to have the basic technical skills to handle
advanced tasks, like installing-uninstalling software, installing
packages, setting up a server, and many more. For example, if you are
configuring and setting up a VPN in Linux, you need to use multiple
Linux commands to accomplish the task quickly. If you already have
some basic technical knowledge and want to learn about these commands,
Linux can be a good choice. 6. Creating Bash Scripts is Much Easier in
Linux

With bash scripts, you can execute various tasks, such as adding
formats, handling mailing lists, creating filters, and many more. At
first, bash scripts are hard to understand, but once you master them,
you will develop unique solutions for your system. The syntax of bash
is straightforward, and it takes little effort to identify errors when
debugging. Linux has super easy options to create excellent scripts
and execute them quickly. Hence, Linux OS can be a brilliant choice
for working on shell scripts.

On 10/15/2022 1:06 PM, Nomen Nescio wrote:
> (LIke who gives a bleep in heck about all this crap? It's not a
> NECESSARY part of our lives - Thanks to Windows with all it's faults.)
>
> https://www.geeksforgeeks.org/7-things-you-should-know-before-switching-to-linux/
>
> Basic Technical Knowledge is Required
>
> As a Linux user, you can control the complete system through the
> terminal. Linux comprises various commands to simplify daily tasks.
> Hence, it is essential to have the basic technical skills to handle
> advanced tasks, like installing-uninstalling software, installing
> packages, setting up a server, and many more. For example, if you are
> configuring and setting up a VPN in Linux, you need to use multiple
> Linux commands to accomplish the task quickly. If you already have
> some basic technical knowledge and want to learn about these commands,
> Linux can be a good choice. 6. Creating Bash Scripts is Much Easier in
> Linux
>
> With bash scripts, you can execute various tasks, such as adding
> formats, handling mailing lists, creating filters, and many more. At
> first, bash scripts are hard to understand, but once you master them,
> you will develop unique solutions for your system. The syntax of bash
> is straightforward, and it takes little effort to identify errors when
> debugging. Linux has super easy options to create excellent scripts
> and execute them quickly. Hence, Linux OS can be a brilliant choice
> for working on shell scripts.
>

Newsflash. There's no need to write entire scripts in bash.

Any more than a Windows user is forced to write .bat files
or .ps1 Powershell scripts.

In Bash, I can do this:

firefox

Now, why would I do that ? Well, to see the Mozilla folks, drop
debug messages into the terminal. This gives "hints" why the GUI
will not start, on a Firefox run.

You can do *exactly* the same thing in Windows:

Command Prompt:

cd /d C:\Program Files\Mozilla Firefox\

firefox

Powershell:

cd "C:\Program Files\Mozilla Firefox"

.\firefox

When you quit firefox, the prompt comes back.

I can type "firefox" into Bash on a real Linux install,
or I can type "firefox" into Bash in Windows 11 Bash Shell.
Exactly the same thing happens. Firefox starts.

If I install Ubuntu Server on real hardware, I would do:

sudo apt install ubuntu-desktop # This likely installs both firefox and thunderbird
firefox

and that's because Ubuntu Server is a minimalist thing
where components are added on top. You can add roles
to Ubuntu Server, like add a web server, a mail server,
or other chacha. Trained Linux maintainers would not
even know about that package, but I do, because I've done
that before. A trained Linux maintainer "loves the terminal"
and does not seek GUI crutches. They would scoff at me doing
that to a Ubuntu Server installation (it compromises security
to install "lard" on a server -- you're not supposed to do that).

Paul

Paul <nospam@needed.invalid> wrote in
news:tig74o$13v$1@gioia.aioe.org:

> In Bash, I can do this:
>
> firefox
>
> Now, why would I do that ? Well, to see the Mozilla folks,
> drop debug messages into the terminal. This gives "hints"
> why the GUI will not start, on a Firefox run.
>
> You can do *exactly* the same thing in Windows:
>
> Command Prompt:
>
> cd /d C:\Program Files\Mozilla Firefox\
>
> firefox
>

I'm using FF 94.0.2 on Win10 1909.

No debug info is shown, and the prompt comes back immediately, not waiting for FF to
close.

Following your instructions directly above, starting from a command prompt doesn't show
debug info like (I've seen other programs do) in Linux. (I'd never started FF from a
terminal session in Linux.)

On 10/28/2022 4:52 PM, DanS wrote:
> Paul <nospam@needed.invalid> wrote in
> news:tig74o$13v$1@gioia.aioe.org:
>
>> In Bash, I can do this:
>>
>> firefox
>>
>> Now, why would I do that ? Well, to see the Mozilla folks,
>> drop debug messages into the terminal. This gives "hints"
>> why the GUI will not start, on a Firefox run.
>>
>> You can do *exactly* the same thing in Windows:
>>
>> Command Prompt:
>>
>> cd /d C:\Program Files\Mozilla Firefox\
>>
>> firefox
>>
>
> I'm using FF 94.0.2 on Win10 1909.
>
> No debug info is shown, and the prompt comes back immediately, not waiting for FF to
> close.
>
> Following your instructions directly above, starting from a command prompt doesn't show
> debug info like (I've seen other programs do) in Linux. (I'd never started FF from a
> terminal session in Linux.)
>

Here is an example of Firefox running in WSL2/WSLg on Windows 11.
Sequence starts with me opening Windows 11 Terminal as user, starting
bash, executing firefox, exiting bash, shutting down wsl, exiting terminal.
You don't HAVE to do all those steps, but I always tidy up after a run,
as I hate surprises.

*******
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\Users\paul> bash
Welcome to Ubuntu 20.04.5 LTS (GNU/Linux 5.10.102.1-microsoft-standard-WSL2 x86_64)

* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support: https://ubuntu.com/advantage

System information as of Fri Oct 28 12:41:41 EDT 2022

System load: 0.32 Processes: 8
Usage of /: 1.7% of 250.98GB Users logged in: 0
Memory usage: 0% IPv4 address for eth0: 192.168.217.182
Swap usage: 0%

0 updates can be applied immediately.

The list of available updates is more than a week old.
To check for new updates run: sudo apt update

This message is shown once a day. To disable it please create the
/home/paul/.hushlogin file.

paul@WALLACE:/mnt/c/Users/paul$ firefox
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
[2022-10-28T16:41:59Z ERROR glean_core::metrics::ping] Invalid reason code startup for ping background-update
ATTENTION: default value of option mesa_glthread overridden by environment.
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
[2022-10-28T16:47:16Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-10-28T16:47:16Z ERROR viaduct::backend::ffi] Missing HTTP status
paul@WALLACE:/mnt/c/Users/paul$ exit
logout
PS C:\Users\paul> wsl --shutdown

*******

This is Windows 10 on the other machine. So I don't have
to boot into Windows 10 on this machine.

C:\Program Files\Mozilla Firefox>firefox.exe -attach-console

C:\Program Files\Mozilla Firefox>[2022-10-28T22:05:52Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-10-28T22:05:52Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-10-28T22:05:53Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-10-28T22:05:53Z ERROR viaduct::backend::ffi] Missing HTTP status
[2022-10-28T22:05:53Z ERROR viaduct::backend::ffi] Missing HTTP status

C:\Program Files\Mozilla Firefox>

*******

There aren't too many options that Firefox accepts on the
command line. The profilemanager argument is one it accepts,
but most people don't need that particularly. If you try --help
or -h or whatever, Firefox won't even start now. (In the past
it would just ignore stuff like that and carry on.)

Firefox starts a number of processes, and most of them cannot respond
to the console as stderr/stdout. So maybe only the parent process
has emitted the four lines above or something. I can see a bugzilla
that mentions "pass_thru=True" but I'm not going to spend the time
to investigate. You can do a debug build of Firefox, if you want
to get more of their arcane output. I've pretty well stopped doing that,
because they're not really trying to help with that stuff.

I did the above, just so I could have some of their fine output.
Maybe you'll get something similar.

Paul