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

    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
    • Microsoft, totally not confusing /s 25H2 - Current for non-Arm based Windows 26H1 - Current for Arm based Windows 26H2 - Only for non Arm Windows
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!