| 2010-10-14 16:03:45 |
Mariano Abel Coca |
bug |
|
|
added bug |
| 2010-10-14 16:04:18 |
Mariano Abel Coca |
description |
Binary package hint: udisks
In udisks changelog says:
"udisks (1.0.1+git20100614-1) unstable; urgency=low
* Upgrade to current git HEAD:
- [...]
- Do not have files executable on NTFS."
I have a 16Gb pendrive partitioned with ntfs which I use to carry my development environment as I switch from one computer to another, and I have it with ntfs because I need to move large files. I have Ubuntu 10.10 maverick installed and updated and udisks 1.0.1+git20100614-3.
The problem comes when I try to run a .sh script to launch the development environment on linux. I can't do it because the excecution bit isn't set anymore on ntfs. So now I have to copy my entire environment to my home, change the excecution bit, and only then I'm able to run it. It's annoying. I don't want to have it duplicated on every computer I use, and I need the filesystem formatted with ntfs to interface with windows computers and to carry large files.
Please can someone fix or rollback this?
Or at least can anyone give me a hint on what should I do to rollback this behavior on my system?
Thanks,
Mariano. |
In udisks changelog says:
"udisks (1.0.1+git20100614-1) unstable; urgency=low
* Upgrade to current git HEAD:
- [...]
- Do not have files executable on NTFS."
I have a 16Gb pendrive partitioned with ntfs which I use to carry my development environment as I switch from one computer to another, and I have it with ntfs because I need to move large files. I have Ubuntu 10.10 maverick installed and updated and udisks 1.0.1+git20100614-3.
The problem comes when I try to run a .sh script to launch the development environment on linux. I can't do it because the excecution bit isn't set anymore on ntfs. So now I have to copy my entire environment to my home, change the excecution bit, and only then I'm able to run it. It's annoying. I don't want to have it duplicated on every computer I use, and I need the filesystem formatted with ntfs to interface with windows computers and to carry large files.
Please can someone fix or rollback this?
Or at least can anyone give me a hint on what should I do to rollback this behavior on my system?
Thanks,
Mariano.
|
|
| 2010-10-15 03:02:53 |
Mariano Abel Coca |
description |
In udisks changelog says:
"udisks (1.0.1+git20100614-1) unstable; urgency=low
* Upgrade to current git HEAD:
- [...]
- Do not have files executable on NTFS."
I have a 16Gb pendrive partitioned with ntfs which I use to carry my development environment as I switch from one computer to another, and I have it with ntfs because I need to move large files. I have Ubuntu 10.10 maverick installed and updated and udisks 1.0.1+git20100614-3.
The problem comes when I try to run a .sh script to launch the development environment on linux. I can't do it because the excecution bit isn't set anymore on ntfs. So now I have to copy my entire environment to my home, change the excecution bit, and only then I'm able to run it. It's annoying. I don't want to have it duplicated on every computer I use, and I need the filesystem formatted with ntfs to interface with windows computers and to carry large files.
Please can someone fix or rollback this?
Or at least can anyone give me a hint on what should I do to rollback this behavior on my system?
Thanks,
Mariano.
|
In udisks changelog says:
"udisks (1.0.1+git20100614-1) unstable; urgency=low
* Upgrade to current git HEAD:
- [...]
- Do not have files executable on NTFS."
I have a 16Gb pendrive partitioned with ntfs which I use to carry my development environment as I switch from one computer to another, and I have it with ntfs because I need to move large files. I have Ubuntu 10.10 maverick installed and updated and udisks 1.0.1+git20100614-3.
The problem comes when I try to run a .sh script to launch the development environment on linux. I can't do it because the excecution bit isn't set anymore on ntfs. So now I have to copy my entire environment to my home, change the excecution bit, and only then I'm able to run it. It's annoying. I don't want to have it duplicated on every computer I use, and I need the filesystem formatted with ntfs to interface with windows computers and to carry large files.
Please can someone fix or rollback this?
Or at least can anyone give me a hint on what should I do to rollback this behavior on my system?
Thanks,
Mariano.
Edit: I've read https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/14335 and I know that this was a decision taked to improve the desktop, but actually in the case of ntfs it's better to let it as it was. Unless Nautilus could read the extensions or the content to decide if it's excecutable or not. For now that it doesn't, just let them all excecutable please. |
|
| 2016-12-03 09:21:30 |
Rolf Leggewie |
summary |
Not able to run shell scripts saved on ntfs partitions |
please enable override for .sh files to be executable on NTFS partitions |
|
| 2016-12-03 09:21:50 |
Rolf Leggewie |
udisks (Ubuntu): status |
New |
Incomplete |
|
| 2016-12-03 09:21:50 |
Rolf Leggewie |
udisks (Ubuntu): assignee |
|
Rolf Leggewie (r0lf) |
|
| 2016-12-03 09:22:10 |
Rolf Leggewie |
udisks (Ubuntu): importance |
Undecided |
Medium |
|
| 2016-12-03 09:26:55 |
Rolf Leggewie |
summary |
please enable override for .sh files to be executable on NTFS partitions |
please enable override for .sh files to be executable on NTFS and vfat partitions |
|
| 2017-02-22 14:25:27 |
Phillip Susi |
udisks (Ubuntu): assignee |
Rolf Leggewie (r0lf) |
|
|
| 2017-02-22 21:43:06 |
Rolf Leggewie |
udisks (Ubuntu): status |
Incomplete |
Invalid |
|
