[SOLVED] How to run a standalone browser in a live session?

JASlinux · 01-15-2024, 11:22 PM

This is in Ubuntu by USB with no install. On my command line, standalone USB browsers are not displayed as executable and generate a permissions error. Permissions do not change on the command line or file manager with no error feedback, eg.,

Code:

chmod u+x firefox

as root leaves Firefox permissions unchanged.

I can't get a standalone to run, & I do not know if this is by design or something I am missing.

I discovered the problem in 16-era Lubuntu which only updates to Firefox 65.

lvm_ · 01-15-2024, 11:37 PM

Usually it indicates that filesystem is mounted with noexec option, check by running mount with no options and remount if it is indeed the case.

JASlinux · 01-15-2024, 11:45 PM

Quote:

Originally Posted by lvm_

Usually it indicates that filesystem is mounted with noexec option, check by running mount with no options and remount if it is indeed the case.

Specifically do you mean

Code:

mount

with no options (the list of mounted partitions only), or

Code:

mount [specific partition]

? Force exec if

Code:

noexec

is default? I probably did not manually mount the USB partition.

enigma9o7 · 01-16-2024, 12:47 AM

Not the answer to your question, but a possible alternative. Should work on live as long as you have enough ramdisk to install it.

Quote:

Originally Posted by JASlinux

I discovered the problem in 16-era Lubuntu which only updates to Firefox 65.

https://launchpad.net/~mozillateam/+..._filter=xenial
Mozilla Team's Firefox Stable (currently 119), Firefox ESR (currently 115.6), and Thunderbird. Support for Ubuntu 16.04 is included.

JASlinux · 01-21-2024, 08:30 AM

https://launchpad.net/~mozillateam/+..._filter=xenial

Quote:

Originally Posted by enigma9o7

Should work on live as long as you have enough ramdisk to install it.

I don't want anything in ramdisk. I want a standalone browser, e.g., on a partition outside the Linux system, specifically for the purpose of preserving ram.

jefro · 01-22-2024, 07:55 AM

The problem with some live to usb installs is the fact that the compressed hard drive image is in a single file on the usb. Not easy to edit.

Consider installing a distro to the usb normally so that you can fully update it.

JASlinux · 01-24-2024, 08:53 AM

Quote:

Originally Posted by jefro

The problem with some live to usb installs is the fact that the compressed hard drive image is in a single file on the usb. Not easy to edit.

Consider installing a distro to the usb normally so that you can fully update it.

I normally boot for functions (i.e., a specific task) & like the security of a read-only os slightly customized with scripts.

If I can boot an .iso live then use a browser not installed to ram, that would be ideal.

JASlinux · 02-19-2024, 04:06 AM

Problem arose again & I think I discovered the reason:

Like symlinks, FAT32 does not support Linux file system permissions.

So while Linux supports FAT32, it's not with full compatibility.

It's a shame because despite its limitations, FAT32 is the most compatible, useful file system.

Copy the standalone browser to different file system & voilà, file permissions are alterable.

Djoisan · 02-26-2024, 03:16 PM

Hi. Running a standalone browser in a live session can be tricky.

JASlinux · 02-28-2024, 09:10 AM

Quote:

Originally Posted by jefro

The problem with some live to usb installs is the fact that the compressed hard drive image is in a single file on the usb. Not easy to edit.

Consider installing a distro to the usb normally so that you can fully update it.

That's a valid technical adjustment, but my interest in LIVE sessions is security. I can't marry a Linux distro anyway (wish I could), so I won't be setting up a workstation but sessions. Especially with older distros, read-only bucks all the update-for-security dogma.