ls -I myExecutable is listing the rest of the dir files instead of showing info about the file
Working on Raspian, after compiling using make, I do a ls -I myFile in order to see the permissions of the file and if it is marked as executable as it should and instead of getting something like that -rw-r--r-- 1 pi pi 24204 Dec 26 09:49 myFile I get what I would get if I ran a simple ls but without the myFile listed. What am I doing wrong?
files permissions ls chmod
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Working on Raspian, after compiling using make, I do a ls -I myFile in order to see the permissions of the file and if it is marked as executable as it should and instead of getting something like that -rw-r--r-- 1 pi pi 24204 Dec 26 09:49 myFile I get what I would get if I ran a simple ls but without the myFile listed. What am I doing wrong?
files permissions ls chmod
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Working on Raspian, after compiling using make, I do a ls -I myFile in order to see the permissions of the file and if it is marked as executable as it should and instead of getting something like that -rw-r--r-- 1 pi pi 24204 Dec 26 09:49 myFile I get what I would get if I ran a simple ls but without the myFile listed. What am I doing wrong?
files permissions ls chmod
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Working on Raspian, after compiling using make, I do a ls -I myFile in order to see the permissions of the file and if it is marked as executable as it should and instead of getting something like that -rw-r--r-- 1 pi pi 24204 Dec 26 09:49 myFile I get what I would get if I ran a simple ls but without the myFile listed. What am I doing wrong?
files permissions ls chmod
files permissions ls chmod
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 12 hours ago
Christos K.
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 12 hours ago
Christos K.
1113
asked 12 hours ago
Christos K.
1113
1113
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Christos K. is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The answer is found in man ls,
-I, --ignore=PATTERN
do not list implied entries matching shell PATTERN
In other words, you asked ls to ignore the file, to only list the other files.
If you want a long list, you should use the option -l lower case 'ell'.
-l use a long listing format
So try
ls -l myFile
answered 12 hours ago
sudodus
1,03116
add a comment |
You add your file in ignore list with key -I (letter i caps). You should replace it with -l (letter L small)
ls -l myFile
answered 12 hours ago
Romeo Ninov
5,19231827
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Christos K. is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490953%2fls-i-myexecutable-is-listing-the-rest-of-the-dir-files-instead-of-showing-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The answer is found in man ls,
-I, --ignore=PATTERN
do not list implied entries matching shell PATTERN
In other words, you asked ls to ignore the file, to only list the other files.
If you want a long list, you should use the option -l lower case 'ell'.
-l use a long listing format
So try
ls -l myFile
answered 12 hours ago
sudodus
1,03116
add a comment |
The answer is found in man ls,
-I, --ignore=PATTERN
do not list implied entries matching shell PATTERN
In other words, you asked ls to ignore the file, to only list the other files.
If you want a long list, you should use the option -l lower case 'ell'.
-l use a long listing format
So try
ls -l myFile
answered 12 hours ago
sudodus
1,03116
add a comment |
The answer is found in man ls,
-I, --ignore=PATTERN
do not list implied entries matching shell PATTERN
In other words, you asked ls to ignore the file, to only list the other files.
If you want a long list, you should use the option -l lower case 'ell'.
-l use a long listing format
So try
ls -l myFile
answered 12 hours ago
sudodus
1,03116
The answer is found in man ls,
-I, --ignore=PATTERN
do not list implied entries matching shell PATTERN
In other words, you asked ls to ignore the file, to only list the other files.
If you want a long list, you should use the option -l lower case 'ell'.
-l use a long listing format
So try
ls -l myFile
answered 12 hours ago
sudodus
1,03116
answered 12 hours ago
sudodus
1,03116
answered 12 hours ago
sudodus
1,03116
answered 12 hours ago
sudodus
1,03116
1,03116
add a comment |
add a comment |
You add your file in ignore list with key -I (letter i caps). You should replace it with -l (letter L small)
ls -l myFile
answered 12 hours ago
Romeo Ninov
5,19231827
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
add a comment |
You add your file in ignore list with key -I (letter i caps). You should replace it with -l (letter L small)
ls -l myFile
answered 12 hours ago
Romeo Ninov
5,19231827
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
add a comment |
You add your file in ignore list with key -I (letter i caps). You should replace it with -l (letter L small)
ls -l myFile
answered 12 hours ago
Romeo Ninov
5,19231827
You add your file in ignore list with key -I (letter i caps). You should replace it with -l (letter L small)
ls -l myFile
answered 12 hours ago
Romeo Ninov
5,19231827
answered 12 hours ago
Romeo Ninov
5,19231827
answered 12 hours ago
Romeo Ninov
5,19231827
answered 12 hours ago
Romeo Ninov
5,19231827
5,19231827
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
add a comment |
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
2
2
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
You were both correct and I can't tell which one was the first to answer.
– Christos K.
10 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChristosK. This answer was 24 seconds earlier. If you mouse over the text above their name that gives the relative time of their answer, it will tell you the exact time. Personally, however, I would accept sudodus's answer because it explained your error in more detail.
– Nonny Moose
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
@ChrisosK: Hovering over the "answered ... ago" text should give you the UTC timestamp for the answer. Alternatively, you can choose to display the answers in "oldest" order (the tab above the answers) though this doesn't seem to be functioning correctly for these answers. In this case Romeo Ninov answered 24 seconds earlier. I think sudodus' answer is better though.
– Alex Hajnal
4 hours ago
add a comment |
Christos K. is a new contributor. Be nice, and check out our Code of Conduct.
Christos K. is a new contributor. Be nice, and check out our Code of Conduct.
Christos K. is a new contributor. Be nice, and check out our Code of Conduct.
Christos K. is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490953%2fls-i-myexecutable-is-listing-the-rest-of-the-dir-files-instead-of-showing-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
