Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
I don't know about palemoon (I doubt it actually) but any firefox that can use the Widevine drm module should be able to.Jerry3904 wrote: Sun Sep 01, 2019 10:21 am I just tried running Netflix in the current Opera-stable and it works fine--it's a Chrome derivative, so it should, just didn't realize it.
Do any (all?) of the Firefox derivatives run Netflix? Thanks.
Drm encryption by widevine, which I think Netflix and Amazon prime is using, is not supported by Pale Moon.Jerry3904 wrote: Sun Sep 01, 2019 10:21 am I just tried running Netflix in the current Opera-stable and it works fine--it's a Chrome derivative, so it should, just didn't realize it.
Do any (all?) of the Firefox derivatives run Netflix? Thanks.
Pale Moon future roadmap wrote:... we do not intend to have DRM in Pale Moon's core program, unlike other applications that build on UXP, and the browser will as such remain properly DRM-free.
On Windows 10 you would just do it this way:Jerry3904 wrote: Sun Sep 01, 2019 3:31 pm I got a message that the md5/sha check methods in W7 and W8 no longer work in W10. I looked around the web, and that appears to be true.
Can someone please check to see if this app works in W10:
https://download.cnet.com/MD5-SHA-Check ... 11445.html
If not, then I am on the hunt. Not just a question for the Manual, but also for our directions on the website.
TIA
Code: Select all
Get-FileHash .\MX-19beta-1_x64.iso -Algorithm MD5
Code: Select all
Algorithm Hash Path
--------- ---- ----
MD5 E4E63DAC86674A47053152A396216B70 C:\ISO\MX-19beta-1_x64.iso
Code: Select all
Get-FileHash .\MX-19beta-1_x64.iso -Algorithm sha256
Code: Select all
Get-FileHash .\MX-19beta-1_x64.iso
Code: Select all
Algorithm Hash Path
--------- ---- ----
SHA256 5D957194310F094299610881D6FD7DD5ABCF0FF86304EA4ED44110D564DD065F C:\ISO\MX-19beta-1_x64.iso
Code: Select all
Get-Content .\MX-19beta-1_x64.iso.md5
e4e63dac86674a47053152a396216b70 MX-19beta-1_x64.iso
Get-Content .\MX-19beta-1_x64.iso.sha256
5d957194310f094299610881d6fd7dd5abcf0ff86304ea4ed44110d564dd065f MX-19beta-1_x64.iso
The easiest to open PowerShell in Win10:Eadwine Rose wrote: Sun Sep 01, 2019 5:03 pm When you tell me to do that I will go: where is this powershell program?
I wager many Windows users with me
EDIT:Yes, I already posted my reply right after. Post 7 and 8.
Totally missed that, sorry. I like it and will include it with the powershell option.Eadwine Rose wrote: Sun Sep 01, 2019 5:10 pmYes, I already posted my reply right after. Post 7 and 8.
Let me know when you're ready. The Master Document is all screwed up so I am ignoring it for now.Gordon Cooper wrote: Sun Sep 01, 2019 5:11 pm I can do some proof reading for you Jerry. Nearly finished the archiving project, only another cou0ple of thousand pages to go.
Can't hurt indeed to include both options.Jerry3904 wrote: Sun Sep 01, 2019 5:13 pmTotally missed that, sorry. I like it and will include it with the powershell option.Eadwine Rose wrote: Sun Sep 01, 2019 5:10 pm Yes, I already posted my reply right after. Post 7 and 8.
I've just tried running Netflix under Opera and I get Error Code: O7701-1003 Missing Component.Jerry3904 wrote: Sun Sep 01, 2019 10:21 am I just tried running Netflix in the current Opera-stable and it works fine--it's a Chrome derivative, so it should, just didn't realize it.
Do any (all?) of the Firefox derivatives run Netflix? Thanks.
That's a useful info. In fact, Rufus is the best thing about Windows (to me at least).dreamer wrote: Sun Sep 01, 2019 6:19 pm Rufus is a better option for hash-checking ISOs. It's open source and you need it anyway to transfer the ISO to USB.
Just load the ISO into Rufus and click the check mark next to it. It will calculate MD5, SHA1 and SHA256 hashes for the ISO. Tested with Rufus 3.6.
The link doesn’t work….Detailed Help on this screen can be found in this document.
Yes, it is correct, but for a newbie it seems to me not clear enough, maybe might be better to write something like this:If the Installer detects multiple partitions, the default option will be presented to allow you to select the partition into which you want to make the installation.
In 3.2.15 Sound Card → the link to HELP: here, under Figure 3-20, doesn’t work.Jessie is old old stable. It should be:◦ Some Nvidia cards are no longer supported in Debian Stable (“Jessie”)
They aren’t 3 popular brands, but 2Here are driver websites for the three most popular brands (do a web search on “<brandname> linux driver” for others):
◦ Nvidia
◦ Intel
Yes,but I realized that MX tweak, in MX 19, has added an extra tab:"Display" with a GUI for xrandr, so maybe you could fix it with something like that:Finer control of some features is sometimes available with xrandr.
No need to install xrandr being present in MX tweak: it is installed by default.3.3.1 Resolution
Click Start Menu > Settings > Display. Use the pull-down menus to set the correct values for the monitor you want to adjust. For more options and finer control, install xrandr from the repos.
might be corrected with something like this:“For more options and finer control, install xrandr from the repos.”
The link in "copying this long command" doesn’t workA list of programs you installed via the apt system will appear that you can copy and paste into a document for storage and reference.
You can create an inventory of all packages on your system installed since installation by copying this long command and running it in a terminal.
In this sentence, MX User Manager should be replaced with MX CleanupAfter it had been cleaned using MX User Manager, the percentage dropped to about 63% and the sluggishness was gone.
deb package > Open Thunar here uhmm, that's not correct, you probably meant:2. Right-click an empty space to open a terminal and become root. Alternatively, click the arrow to move up one level and right-click the folder with the deb package > Open Thunar here.
the link Budgie Desktop doesn’t workBudgie Desktop, a simple and elegant desktop using GTK+
the link doesn’t work• KDE5 Standard, a very large and powerful environment adapted to the MX Linux environment. See the MX/antiX Wiki.
I think it is better that point 5 is written like this:Anyone who wanted to use such a script would have to carry out a few execution steps:
5. Change any names, locations, etc. to what they are on your particular system. In the example above, you may well have different names and/or locations for the directories to be backed up, and different devices where they are supposed to go.
the link doesn’t workinxi
MORE: MX/antiX Wiki
the link doesn’t workHELP: here.
. the link doesn’t workHELP: here
the link doesn’t workHELP: here.
the link doesn’t workCLI
....... To change this behavior, consult the MX/antiX Wiki.
the link doesn’t work, this should be correct: https://www.linux.com/tutorials/underst ... rmissions/File Permissions
the link doesn’t workDdrescue
You can do this with Master PDF Editor. There's a limited selection of colours but you can control opacity. There's also an option to use a file as background, which I haven't tried.Jerry3904 wrote: Thu Mar 26, 2020 2:18 pm There may be a way to deal with the PDF itself, but I don't know what that would be without some research--which I leave to you!
I downloaded the mxum.odt file but it's only 62.1 kB in size with 3 pages representing some kind of HTML structure.Jerry3904 wrote: Thu Mar 26, 2020 2:18 pm I just use LibreOffice. In the GitHub repo you can see the individual *odt files which I simply join together and then click the PDF icon.
There are some good stuff there, thanks for putting the time and thought into the question. I suggest you pull down S2.odt from the GitHub repo and go to work. Once you have a draft, people here can take a look.Antediluvian wrote: Sun Apr 12, 2020 9:52 pm Hi Jerry,
Thanks for your untiring efforts on MX documentation and for your help in the forum. I am willing to revise part of the manual under your supervision if you are interested. For example, I've meant to say something about Chapter 2 of the manual ever since I first joined the forum two years ago.
Chapter 2 "Installation"
My problem with Ch 2 is that it is too long and complicated for users new to Linux and presents things in a unnatural order for the majority of users. The basic problem is that Section 2.3 is out of order. It should be placed after Section 2.4. That said, this chapter would less daunting if it were also split into two chapters to reduce the inertia of getting started.
Imagine someone wants to try out MX. Typically they want to proceed in the fastest way possible with a minimum amount of preparation. The preparation involved, especially in Section 2.3 "Pre-Installation", is potentially overwhelming for a beginner. They don't need the information in 2.3 before they run the live-USB in 2.4. In addition, they want to protect the current state of their computer in case they decide not to stay with MX. I don't think Ch 2 should include installation. That is too great an initial commitment of time and hardware. It should be about downloading and running MX from live media. Leave the relatively complicated procedure of full installation to a new Ch 3 after they gain some experience with MX, have time to think over the prep involved in Section 2.3, and get familiar with GParted, disk identification, and partitions.
A revised Ch 2 "Creating and Using Bootable Live Media (USB or DVD)" could cover the following topics:
1) Introduction including a general work flow chart.
2) Preparatory decisions to make based on your computer hardware.
(Sections 2.1.1, 2.1.2)
3) How to download and validate the ISO.
(Sections 2.2.1, 2.2.2)
4) How to create a bootable live-USB or live-DVD.
(Section 2.2.3)
5) How to run an MX-live USB (w/o persistence) including changing the BIOS.
(Section 2.4)
6) Overview of modifying the OS, saving changes w/ persistence, remastering if necessary, creating a snapshot, installing from a live OS, etc. Flow chart of steps and optional steps. This overview would reference other pages of the manual and not present detailed information on these subjects.
Create a new Ch 3 "Installation of MX" by moving some sections in the present Ch 2. Specifically, move sections 2.3, 2.5, and 2.6 to Ch 3.
The current Ch 3 and every chapter after would become X+1. For example, Ch 3 "Configuration" becomes Ch 4. If splitting Ch 2 is not advisable because it would create too much work renumbering all the chapters, sections, tables and figures for the remainder of the manual, then at least it should be reordered and partially rewritten. Perhaps have a Ch 2 Part 1 and Ch 2 Part 2. Alternatively, the rewrite could be done in two steps: rearrange Ch 2 for MX 19.2 & 19.3 and split the chapter for MX 20.0.
What do you think? [You don't have to be gentle. I'm not that sensitive.]
Remember that the information in the MX User Manual is primarily about functions provided by MX Linux. There are other resources for information about functions provided by Xfce.mxer wrote: Sat Jul 25, 2020 7:25 am Something is missing - I couldn't find how to turn off automounting of external disks!
I think it should have something about how to turn it off, because it really annoys me no end, having disks auto mounted.
)
And searching the manual for xfce reveals a link to that documentation, and one to the Xfce FAQs.chrispop99 wrote: Sat Jul 25, 2020 8:13 amRemember that the information in the MX User Manual is primarily about functions provided by MX Linux. There are other resources for information about functions provided by Xfce.mxer wrote: Sat Jul 25, 2020 7:25 am Something is missing - I couldn't find how to turn off automounting of external disks!
I think it should have something about how to turn it off, because it really annoys me no end, having disks auto mounted.
Chris
And let alone the possibility that that someone doesn't master the English language and is using a translated manual...mxer wrote: Sat Jul 25, 2020 8:20 am That is a somewhat round about way for someone who may have just installed MX - a bit more guidance wouldn't go amiss.
Not sure if this could be a solution. Certainly not until I get a decodification of what ATF stands for, which I couldn't find after a search on the Internet. Taking RTM as "Read The Manual" it just gets us back to the complain itself...
Well, You're not aware, but I did start translating the thing, back already a couple of years ago. In the process I've realized that the user was/is systematically being sent to outside material in English via links: videos, web pages, help info. So, I thought to myself that if the user is systematically sent back to material in English than he is expected to master the English language. Hence, it doesn't make much sense for me to spend a lot of time translating material from English for people that are supposed to know English.wrote:Another solution: do something, like help translate the thing.
I perfectly know that the MX team is a small team. As said, I've been involved with it somehow for more than a couple of years now. What I don't know is what you mean when you say that I "seem to want" something:Eadwine Rose wrote: Sun Jul 26, 2020 5:32 pm Plainly put: It is not possible to put everything in the manual like you seem to want. Also.. as far as I know only two or three people are actively working on it. Remember we are a SMALL team.
#45 Post by mxer » Sat Jul 25, 2020 12:25 pm
Something is missing - I couldn't find how to turn off automounting of external disks!
I think it should have something about how to turn it off, because it really annoys me no end, having disks auto mounted.
#48 Post by mxer » Sat Jul 25, 2020 1:15 pm
In case others are having difficulty with this, it's
Edit - Preferences - Advanced - Volume Management - Enable Volume Management
(Volume Management - it's not under Disk Manager....
It's much easier & more obvious on AntiX....
I still think there should be a searchable item to be able to turn off automounting, not everyone wants it.
Plainly put: if you are not able to satisfy a request, just say you can't satisfy it, don't start telling the request doesn't make sense or the users are asking too much or users just complain and do not help or something alike.#50 Post by mxer » Sat Jul 25, 2020 1:20 pm
That is a somewhat round about way for someone who may have just installed MX - a bit more guidance wouldn't go amiss.
I figured that, but I think I knocked out two birds with one stone.asqwerth wrote: Mon Jul 27, 2020 5:18 am I think the posters are suggesting some edits to the manual to propose better solutions to their problems, rather than wanting help with a problem?
That's what I thought as well when I've seen the post on the matter. I jumped in just to raise the issue of it potentially being even less easy to find some "not so clear info" in a translated version of the manual.asqwerth wrote: Mon Jul 27, 2020 5:18 am I think the posters are suggesting some edits to the manual to propose better solutions to their problems, rather than wanting help with a problem?
Chapter 3 mentions peripherals (section 3.1) but doesn't mention internal drives. So, to me there is some point in raising the issue.However, I think we're rather shorthanded right now so it might be better if the posters actually come up with the actual wording and changes you wish to propose to a specific section/page etc of the manual.
Agree.
I'd say that that would depend on your target users. If your target users include newcomers from other OSes that aren't so keen about OSes but rather want a reliable and easy to use OS, then I think you should understand their position. Anyway, the sole ones entitled to define the target users are the MX team members. I am not, for sure.Users should want to and be exciting to explore the OS and all that is in it,
Agree, provided there is a common understanding on what spoon feed may mean. The line between proving helpful info and spoon feeding can be very thin, so there should be some defining of what is supposed to be what in a matter like this.not be spoon feed every little thing because that’s impossible anyway.
Agree again, particularly regarding the info in English. If you want to think of non English speaking users,than some thought on the matter would be useful again.Also I think our wiki is a better place for some of this stuff,
Here we get back to the fact that the MX Linux team is a small team I guess...I’d like our wiki to be of the quality of say Arch, Gentoo, or Debian.