Linux & My Secondary NTFS Drive


Recommended Posts

Hello,

I'd like some help on my dilemna please. I've been wanting to install Linux specially Lubuntu with LXDE for its quick boot time and not to worry about viruses anymore.

BUT my secondary hard drive which is filled with precious datas is in NTFS and looking at it abandoning windows will mean abandoning NTFS which is how my backup and important datas are kept. Is there a way to change file system without moving my data or formatting? Or NTFS support on Linux this days are good?

Link to comment
https://www.neowin.net/forum/topic/1097873-linux-my-secondary-ntfs-drive/
Share on other sites

Hello,

I'd like some help on my dilemna please. I've been wanting to install Linux specially Lubuntu with LXDE for its quick boot time and not to worry about viruses anymore.

BUT my secondary hard drive which is filled with precious datas is in NTFS and looking at it abandoning windows will mean abandoning NTFS which is how my backup and important datas are kept. Is there a way to change file system without moving my data or formatting? Or NTFS support on Linux this days are good?

Why not just use WUBI -- that way Windows Install is not changed and your Linux is inside a compressed image on the NTFS drive.

That would be my suggestion...

http://www.ubuntu.co...ndows-installer

I think with 12.04 lubuntu is now an option from the drop-down.

Or if not -- then install the standard Wubi Ubuntu then go into the package manager and install the LUBUNTU desktop.

then choose it for your DE when you log in.

For mine I have also have the KDE and XFCE . On my laptop I also do have the LXDE ...

If the important data is on your secondary hard drive and Windows is on your primary, you could wipe the primary, install Ubuntu (or Lubuntu) on it, and mount your secondary (NTFS) hard drive as secondary. NTFS support in modern versions of Linux is fairly good, so you don't need to worry about it corrupting your data, but it doesn't support *nix file permissions and cannot be used as your root file system. If you still plan on doing regular backups to it, you should probably figure out some way to temporarily backup your data, reformat it as EXT4, and restore your data to it. Otherwise, if you are just using it for regular data and document storage, it is probably fine to leave it as is.

NTFS support is excellent with current gen linux distros, except the *nix file permissions - as xorangekiller mentioned above. Reading data from, and writing data to NTFS works just fine so I'd recommend leaving it as-is.

Wipe your primary partition and go Lubuntu exclusively.

There isn't a perfect mapping between *nix permissions and NTFS ACLs, *nix permissions are much too limited for starters. NTFS-3G does support mapping between NTFS ACLs and Linux ACLs, but those aren't supported with every distro (Failed to gain much traction, although there are new attempts)

You can still assign *nix permissions though, so in practice you shouldn't have any issue (Especially if it's a single user machine, etc.)

There isn't a perfect mapping between *nix permissions and NTFS ACLs, *nix permissions are much too limited for starters. NTFS-3G does support mapping between NTFS ACLs and Linux ACLs, but those aren't supported with every distro (Failed to gain much traction, although there are new attempts)

You can still assign *nix permissions though, so in practice you shouldn't have any issue (Especially if it's a single user machine, etc.)

I had never heard of this ACL mapping of which you speak before now. I managed to find an article on the NTFS-3G project site about the current (or what I'm assuming is current) ACL mapping system in their driver. However, I definitely agree that on a single user machine permissions on the drive are basically irrelevant anyway.

Would you mind explaining what you see as the limitations of the *nix permissions system as opposed to the Windows one? I'm sure this is a topic where people are very opinionated. I don't mean to start another holy war. More than likely I can already guess your bias and you mine, but I respect your opinion and am truly interested in hearing your perspective.

Windows has an awesome permissions system, you can adjust permissions for multiple users/groups at a time (So you can say that a user that is in Group A can read and write to a folder, but everybody else in Group A can only write, while everybody in Group B can read the files in the folder and a user in Group B can read, execute and modify extended attributes of files in the folder, etc.)

*nix permissions on the other hand only has the concept of a Owner, Group and Everybody, and from that you can only assign Read/Write/Execute permissions. So while you can give one user permission to change everything in a folder and his group the ability to read only, you then can't give another group read permissions without giving every user on the system read permissions (A folder/file can only have one owner/group at a time, so you cant set permissions for 2 groups, or for 2 users without adding them to a custom group).

Well, it's more like Linux considers groups to be something distinct, while Windows considers them to just be groups of users. Linux maintains different permissions for users and groups (And as I mentioned, only one set for each), while on Windows a group is just another user really, you can add multiple sets of permissions for different items, whether they be users or group.

Yeah, the POSIX ACLs have been around for a while, but I don't think they ever got merged into the kernel (And if they did, I don't think they're built by default, etc.), so they don't come with every distribution. The "newer" NFSv4 ACLs seem nicer, but even they've been around for a while with little to no uptake (And they require support from the file systems, so you can't just use them with any random configs.), although there is some activity in that area recently (Richacls adds support for the EXT4 Filesystem)

Yeah, I couldn't find much information about ACL support in Linux (Which surprised me honestly), I think I found a single reference to them being part of the kernel, and a bunch that mentioned patches.

And as you mentioned, you need to mount the FS with the right option, which no distro does, etc.

So, in your opinion, what is the advantage to me enabling and using ACLs on one of my Debian systems versus sticking with classic *nix permissions?

Also, since ACL support seems to be mostly a file-system thing, can I use it on a Debian GNU/BSD system similarly to how I would on a Debian GNU/Linux system?

  • 3 weeks later...

Thanks all for the help.. Wubi is not an option why run linux on top of windows? I guess Live CD or USB is a better option for that.

So im going with Debian minimal instead, one of my reason im going with Linux is speed and Debian for its slow stable updates and XFCE for my DE.. But im still keeping Windows XP still no replacement for my Foobar Dolby w/ headphone wrapper setup.

why run linux on top of windows?

Because you said -- " Important Files" Wubi would run inside a compressed file instead of changing the actual contents of the drive

To note Live runs just in memory which performs slower

while wubi runs inside two compressed files.

One for the OS and one for a Swap disk.

It only runs inside that directory that it is installed into.

With Live it will load and run only in memory-- and upon each reboot or setup -- you will have to re-do your settings...such as for your sound.

Unlike the Wubi where it works just like an install.

With a live linux -- you would have to re-setup your video drivers and sound drivers each time you reboot.

Plus any other customization you have done. with the Wubi it retains that.

With Live it will load and run only in memory-- and upon each reboot or setup -- you will have to re-do your settings...such as for your sound.

Unlike the Wubi where it works just like an install.

With a live linux -- you would have to re-setup your video drivers and sound drivers each time you reboot.

Plus any other customization you have done. with the Wubi it retains that.

that is unless you have a persistent live copy on a flash drive (which will still run slower than being installed on the hard drive)
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Also known for https://www.theguardian.com/technology/2009/jan/29/adware-internet.   Regards, Aryeh Goretsky    
    • Hello, I have used a few TEAM Group SSDs, USB flash drives, and Micro SDXC cards in the past. They all seemed to work fine. Regards, Aryeh Goretsky
    • "just $100 per TB"? Just? Are we trying to make this seem like the new normal? Kinda weird to make it sound like that is not a ridiculously expensive asking price.
    • The reviews you refer to mean nothing. Where there is no journalism there is no reason to call the gaming media's opinion pieces "reviews". For GP games there is indeed a metric for success - increasing subscriptions. Which turns in revenue. The only circumstance in which subs do not rise when great is being released is a Game Pass system where the company is close to fully saturated with customers in a subscription. However, in that case as the theory goes you spend aplenty in all kind of games - from shady live service cash cows and customer offending agitprop crap in purple colours to robust and entertaining single player games. And keep a solid level of profitability. Ignoring the simply innocuous but mid games MGS has released primarily of the second kind.
    • Report: Microsoft to use AWS to help GitHub deal with a major surge in demand by Pradeep Viswanathan Thanks to the surge of coding AI agents, GitHub's usage has skyrocketed over the past 12 months. To meet this demand, GitHub started with a plan in October 2025 to increase capacity by 10x. However, by early this year, the company realized that it needed 30x scale. This rapid growth has caused severe strain on the platform's reliability, resulting in several small outages over the past few months. In April, GitHub published a long blog post explaining the steps it is taking to resolve these reliability issues. In the post, the company also confirmed that it is working toward a multi-cloud architecture for better resilience. Today, Business Insider reported that GitHub is turning to Amazon Web Services to help deal with a major surge in AI-driven coding activity. It is important to note that GitHub is still in the process of moving completely to the Azure cloud. The current plan is to move the platform fully to Azure by 2027 so that it can scale better as per developer demand. Therefore, the current decision to utilize AWS might be part of a short-term plan to meet immediate demand. A Microsoft spokesperson confirmed that GitHub is using multiple cloud providers with the following statement: For Microsoft, the decision highlights the operational pressure behind the AI boom. GitHub has to stay reliable for developers at a time when rivals such as Codex, Cursor, Claude Code, and other AI coding tools are gaining attention. And the decision to use AWS for computing capacity seems practical given the circumstances.
  • Recent Achievements

    • Collaborator
      vjlex earned a badge
      Collaborator
    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      182
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!