My Linux Based Questions

By +longgonebn,
in Linux

 Share Followers 0

Recommended Posts

+longgonebn
  • Author
  • Subscriber²
Posted

It's not working.

UUID=12498dda-899a-4e48-9d6e-a5372340f3dd /media/Movies ext4 uid=1000,gid=1000,umask=0022,sync,auto,nosuid,rw,nouser 0 0

This was taken from an example I found..

uid=1000,gid=1000,umask=0022 do I need this...I see this no where on the archwiki page?

Also, I am user bman....should i be using nouser, or should I put user or users

** I ended up putting this

UUID=12498dda-899a-4e48-9d6e-a5372340f3dd /media/Movies ext4 sync,auto,nosuid,rw,nouser 0 0

And all mounted without issue.

Link to post
Share on other sites
firey
Posted

you don't need users because you want it to be open. UID=1000 means that it will be accessible for your user by default (unless overriding policies are set on files) and gid=1000 means that your users group will have access to. So it's more of a permissions thing. You could try and remove those settings, but you may run into permissions (mounted as root) issues.

What is not working?

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

As I stated above.

With those details it would give error, I removed it and had only

UUID=12498dda-899a-4e48-9d6e-a5372340f3dd /media/Movies ext4 sync,auto,nosuid,rw,nouser 0 0

And everything mounted without issue, my programs that use it are still working. So it's working.

Thanks guys.

Link to post
Share on other sites
+Majesticmerc
  • MVC
Posted

Wikipedia tells me that uid and gid and unmask are for FAT file systems only, which probably explains why they don't work.

If you want to simplify things, try simply using "default" option only (instead of specifying all the options like sync, auto, nosuid, etc manually), and see if that works. Then if it doesn't do what you want, adjust as necessary.

  • Like 1
Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

Thanks guys, awesome help!

Link to post
Share on other sites
firey
Posted

glad it's working for you :)

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

So I got a chance to reboot since doing all that, and everything worked fine, in terms of mounting.

But now, copying or moving files to these drives are VERY slow. A 1GB file would have taken 1 min or less (usually less), it's now like 15 minutes or something, ridiculous!

I am assuming it's the auto mounting that did something, but what could have caused that?

Link to post
Share on other sites
firey
Posted

Have you only experienced this with copying to the mount? Also what about copying from or creating a copy of a file on the mount inside the mount itself?

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

This is moving and copying, to and from any of the drives.

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

I changed the code to "defaults" instead, rebooted and it's back to normal. Not sure which code was causing the problem but it's all good.

Link to post
Share on other sites
+Majesticmerc
  • MVC
Posted

My guess is because you specified "sync" writes, which you don't need for an internal drive. If necessary, you can further boost performance if you add "noatime" as an option, although it won't write "last accessed" times anymore. :)

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

Yea see I didn't know that. That's what you get for copying stuff from the internet lol

And I was just reading up on noatime, sounds good, but what do you mean by "last accessed"? What exactly will change when using my system?

Also, can I keep defaults, and just add noatime beside it?

Link to post
Share on other sites
+Majesticmerc
  • MVC
Posted

Yes, you can just use "defaults,noatime" without issue. Basically, every time you read or write a file, a timestamp in the file inode will be updated. This means that you can view the time that the file was last accessed if necessary. The obvious downside of this is that every read is also a write, and this has a moderate impact on performance.

'noatime' will prevent these access timestamps from being written, which reduces I/O usage, which is good for performance. This is of course at the cost of the last-access time being updated, which can cause issues for some older email clients and such, which rely on the difference between last accessed time and last modified time to determine if an email is unread.

Looking into it though, Ubuntu has made "relatime" a default option for ext file systems since around 2010 anyway (see here), so you'd probably see no benefit from using noatime anyway. The defaults should be just fine ;)

An explanation of noatime vs relatime can be found here: http://linux.koolsolutions.com/2009/01/30/installing-linux-on-usb-part-4-noatime-and-relatime-mount-options/

  • Like 1
Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

Thanks again. :)

Link to post
Share on other sites
Haggis
  • Veteran
Posted

you can also use nodiratime aswell :)

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

I don't think I have asked this hear, and haven't found a good solution anywhere else.

I have the xscreensaver setup and works great. The only issue is that it comes on even with full screen applications running.

Alright, I use VLC that disables it while its open, great,...uh no. The problem with that is even if I have that VLC window minimized or in the small size (not full screen) the screensaver is still disabled, stupid.

Also, that doesn't work for flash sites like you tube.

Any ideas?

Link to post
Share on other sites
firey
Posted

I don't think I have asked this hear, and haven't found a good solution anywhere else.

I have the xscreensaver setup and works great. The only issue is that it comes on even with full screen applications running.

Alright, I use VLC that disables it while its open, great,...uh no. The problem with that is even if I have that VLC window minimized or in the small size (not full screen) the screensaver is still disabled, stupid.

Also, that doesn't work for flash sites like you tube.

Any ideas?

The same happens on windows with VLC. I think it is a setting as it disables my windows screenwaver

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

Yes, the setting I want enabled because it stops the screensaver from happening when watching videos, but it's like it's not smart enough to know that if I have it minimized I want the screensaver to work.

Link to post
Share on other sites
firey
Posted

Yes, the setting I want enabled because it stops the screensaver from happening when watching videos, but it's like it's not smart enough to know that if I have it minimized I want the screensaver to work.

I get that on Windows. If I have VLC Open the screensaver doesn't work. Even minimized or without a video loaded.

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

A new problem, well not new but haven't posted about it.

This has happened before but let it go because it's only once in a blue moon.

Sometimes randomly the VLC Icon on Unity stops working, at first the minimize and restore feature of the button stop working, then eventually there is no icon at all.

I have to reboot to get it to work again. Sometimes it does come back and start working again, but most of the time no.

Ideas, can't seem to find any information about it.

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

I guess as the rest of the internet, no one here knows either. Alright ignore that for now.

I have Chrome installed and is my main program, I use it for everything. Does anyone know how to properly restart chrome?

When I close Chrome, it's still running in the background, if I look at the System Monitor, its still there. If I try to close all 20 processes it can sometimes cause issues with accounts and stuff, so I don't want to do that, besides it taking long.

I want to be able to restart chrome because after awhile, it uses a lot of resources and kills my fairly old system. Instead of restarting all the time, I'd rather restart chrome.

In Windows, if you exited it, it seemed to close fully, Ubuntu it does not.

Ideas?

Link to post
Share on other sites
Brandon H
  • Supervisor
Posted

I guess as the rest of the internet, no one here knows either. Alright ignore that for now.

I have Chrome installed and is my main program, I use it for everything. Does anyone know how to properly restart chrome?

When I close Chrome, it's still running in the background, if I look at the System Monitor, its still there. If I try to close all 20 processes it can sometimes cause issues with accounts and stuff, so I don't want to do that, besides it taking long.

I want to be able to restart chrome because after awhile, it uses a lot of resources and kills my fairly old system. Instead of restarting all the time, I'd rather restart chrome.

In Windows, if you exited it, it seemed to close fully, Ubuntu it does not.

Ideas?

by default chrome allows extensions to run in the background (even while closed) this could be what you're experiencing when there are still chrome processes running after you close the browser

you can disable this option in settings at the very bottom of the advanced section

Link to post
Share on other sites
+longgonebn
  • Author
  • Subscriber²
Posted

No, I do use that feature, I have a few running in the background for a reason.

But, on Windows it had a Chrome Icon beside the clock, if you right click that and exit, Chrome fully closes. Ubuntu does not have that ability.

Link to post
Share on other sites
This topic is now closed to further replies.
 Share
Followers 0
Go to topic listing

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • Canonical announces full enterprise support for Kubernetes 1.21
      By zikalify
      Canonical announces full enterprise support for Kubernetes 1.21
      by Paul Hill



      Canonical, the firm behind the Ubuntu operating system, has announced full enterprise support for Kubernetes 1.21. It said that support ranges from public cloud to edge and covers Charmed Kubernetes, MicroK8s, and kubeadm. According to Canonical, MicroK8s is suited for workstations, DevOps, edge and IoT, Charmed Kubernetes is aimed at multi-cloud clusters, and kubeadm is designed for manual operations.

      Notable changes in Kubernetes 1.21 include a memory manager which will improve the performance of some applications, new scheduler features, improvements to ReplicateSet downscaling, support for indexed jobs, and the deprecation of Pod Security Policy before its complete removal in Kubernetes 1.25.

      Commenting on the launch of Kubernetes 1.21, Canonical Product Manager Alex Chalkias said:

      Enterprise support for Kubernetes on Ubuntu is provided by Canonical as a part of the Ubuntu Advantage for Infrastructure (UA-I) support subscription. The package includes long-term security maintenance, kernel Livepatching, and mission-critical infrastructure support for the full stack from the kernel to the container across public clouds, Vmware, OpenStack, and bare metal.

      In terms of product releases from Canonical, this month is turning out to be a bit busy. On the first day of the month, Canonical launched Ubuntu 21.04 beta and is intending to release the finished product on April 22.

    • Canonical releases Ubuntu 21.04 Hirsute Hippo beta
      By zikalify
      Canonical releases Ubuntu 21.04 Hirsute Hippo beta
      by Paul Hill

      Canonical has announced the availability of Ubuntu 21.04 Hirsute Hippo beta for Desktop, Server, and Cloud. There are also downloadable beta images of alternative Ubuntu flavours including Kubuntu, Lubuntu, Ubuntu Budgie, UbuntuKylin, Ubuntu MATE, Ubuntu Studio, and Xubuntu.

      The main Ubuntu 21.04 for Desktop is quite a good release this time around; it includes the newer 5.11 Linux kernel so more hardware will be supported and Canonical has switched to Wayland sessions by default away from X.org. Unlike Fedora 34, Canonical has decided to stick with GNOME 3.38 so that it can adapt its desktop extensions to work properly with GNOME 40.

      In its announcement, Canonical said:

      If you’d like to take Ubuntu 21.04 beta for a spin before the final release drops on April 22, head over to the mailing list announcement where you can find the links to all of the available Ubuntu 21.04 beta editions and flavours. Keep in mind that this software is still in development and you could run into bugs. If you do, you can report them to Canonical so they can be fixed before the final release later this month.

    • Linux Mint outlines better, unobtrusive update notifications
      By zikalify
      Linux Mint outlines better, unobtrusive update notifications
      by Paul Hill



      Clem Lefebvre, head of the Linux Mint project, has written a blog post outlining new notifications that try not to be annoying but also remind users that they need to perform software updates to keep their computer secure. The details arrive a little over a month since Lefebvre pointed to stats that show some users were not applying security updates and in some cases, people were even running end of life versions of Linux Mint.

      The Linux Mint team prides itself on its users controlling their computer rather than the other way around. New Mint versions only ever introduce conservative changes so that the whole operating system doesn’t need to be relearned and users are also given complete control over when, how, and which updates are installed; unfortunately, this mindset has led to some users running outdated, vulnerable software.



      To remedy the issue, a new pop-up has been created which lets the user know how many updates are available, it says why updates need to be applied, it lets users view available updates, and gives users the option to turn on automatic updates. If the user dismisses the notification it will come back two days later so it’s not overbearing.

      If the user decides to install updates, the notification will disappear for quite a while on the default settings. By default, the notification will appear if an update has been available for more than seven logged-in days or if it’s older than 15 calendar days. The number of days can be changed to anything between two and 90 days depending on how often you want to see updates. Additionally, these notifications will only be triggered by security and kernel updates but this can be adjusted in the settings.

      There is also a grace period setting which is set to 30 days by default, essentially, this means that if an update has been applied in the last 30 days, you will not be bugged by notifications until that time has elapsed.

      The Mint team hopes that the default settings will work for most people in that they keep their system moderately up-to-date without being overburdened with constant reminders to update their machine. The new notifications are set to arrive in Linux Mint 20.2 but Lefebvre has also said that it could be backported to older versions.

    • Debian 10.9 released with updates to popular packages
      By zikalify
      Debian 10.9 released with updates to popular packages
      by Paul Hill

      Image via Alex Makas The Debian project has announced the availability of Debian 10.9. The new ISO image, which can be used to install Debian, comes with all the latest package updates which will save you time when installing the operating system on a computer. If you already have Debian 9 installed on your computer, there is no need to download Debian 10.9, simply apply any available updates to your system and you’ll be on the latest release.

      Commenting on the launch, the project said:

      Some of the packages that are updated in Debian 10.9 include LibreOffice, the Linux kernel, Python, Firefox ESR, Chromium, and Tor. The Debian installer has also been updated to include the latest fixes.

      Debian 10 was first released on July 6, 2019, and will continue to receive updates until 2024. As big Debian releases come out every two years, we should see Debian 11 at some point this year but so far no release date has been given. Upon release, Debian 10 will be demoted from Stable to Old Stable with Debian 9 being cut off from updates in mid-2022.

    • Tails 4.17 launched with improved upgrade process
      By zikalify
      Tails 4.17 launched with improved upgrade process
      by Paul Hill



      The team behind the privacy-oriented operating system, Tails, has launched Tails 4.17. This update includes several important updates to key packages such as the Tor Browser which are essential for maintaining your privacy but it also comes with several improvements to the upgrade process which should result in less failed upgrades.

      The first of the reliability improvements to automatic upgrades pertains to the file system. The release notes state that automatic updates were previously failing because of an unclean file system. To address this, Tails now automatically repairs the file system being used during an upgrade to eliminate the issue.

      Another change to improve upgrade reliability is the download process of new updates. Each Tails upgrade requires the users to download the new image over Tails’ Tor connection which can sometimes be spotty. With Tails 4.17, downloads will now automatically resume if they do stop so it’ll save users a lot of time.

      In terms of new package updates, the Tor Browser has been updated to 10.0.14, Thunderbird has been bumped to 78.8.0, Tor is now on 0.4.5.7, the GRUB bootloader is on 2.04-16, and several firmware packages that improve Intel, Broadcom, and Cypress interfaces have been included too.

      If you’re running Tails 4.14 or above you will get a notification telling you to update your system as soon as you connect to the internet. If you do not yet have a Tails USB to boot from but would like one, you can find instructions on downloading and installing Tails on the project’s website.