@Gilles What I'd like to see is a discussion on meta between people like you and Michael, derobert, goldilocks and the like, who have a deep understanding of kernel hacking. I feel like we haven't really clarified how to draw the line.
Then again, as I said before, that might just be that I don't understand the line.
I don't think there's a clear line here, but the "no programming questions" rule leads to kneejerk responses, and migration is the one kind of closure we can't fix afterwards
Well, the two categories are quite connected. I'd consider something like "Here's my code, it's supposed to do X by using API functions but functionFOO() isn't behaving the way I expect it to" to be on topic. It's still programming but it's very *nix.
@MichaelHomer Compiling someone else's code is on-topic. Patching is on-topic. And I'm not noticing these questions being closed as off-topic. Examples please.
@MichaelHomer Compiling and applying existing patches are certainly on topic. It only gets murky when the issue is with your own code. If you're trying to make someone else's package work, you're fine.
@MichaelHomer Distribution packagind is definitely on-topic. As far as I know, that has never been at issue.
@terdon Which two categories?
@terdon I think that's fine, personally. But like I said, there is no concensus about that. Those sorts of questions are actually (or could be) quite interesting.
I think I was a bit unclear there. It's clearly on-topic, but a reasonable subset of those questions are about build errors or configuration, which sets people off.
@MichaelHomer I don't see why it sets people off. But I'll take your word for it. Actually, I don't thinK I've ever seen a packaging question be closed as off-topic. Do you have an example?
Granted, questions about kernel modules are not about the C API.
No, I'm actually looking through outward migrations now and there aren't as many as I expected. Perhaps they actually are getting stopped in the queue.
Wearing my distribution-maintainer's hat, I often wrote patches to other people's code (to fix paths, compile in the sandbox, and suchlike), and I'm uncertain of where those stand. They're not "existing patches", so it sounds like a no from the room.
It's not an existing patch, and it's a problem I created for myself by trying to compile in a sandbox/with funny paths/..., so it's a bit of a grey area. At some point patching really does just become writing entirely new code. There actually is a distinction to draw somewhere there.
Personally, I'd like to see some Unix programming type questions in preference to yet another brainless "manipulate my text file so it does something totally uninteresting" questions. Though maybe it is politically incorrect to say so.
how would I go about properly closing a file descriptor? I currently have to write a simple unix shell. For example, if the user entered sort < someFile, I have the following code:
freopen(commandArg[<location + 1],"r",stdin);
executeArg(commandArg);
fclose(stdout);
When I execute the command ...
The overarching goal is more one of drawing together currently-disparate groups than of directly improving, I think. I'm not sure whether it's effective or not
It'd be less broad, but more effective. Or at least, if it weren't, that would be an interesting result vis-a-vis accuracy and generalisability of that literature.
@MichaelHomer <Shrug>. That's debatable. But I guess if you're professionally involved in the area, you have your professional opinion.
Having said that, people are perhaps more likely to appreciate Lisp if they come to it after having discovered the deficiencies of other languages. As I did.
Java. C/C++ users typically don't even know there are alternatives.
I don't have a formal CS background, otherwise I might have known about CL earlier.
A language like C++ is actually quite horrible for something who is trying to learn it. Then again, C++ is a horrible language generally. Like walking through a forest of thorns naked.
I think some languages are easier to learn than others. E.g. Python is easier to learn than C.
But in my case, nobody taught me anything. I was trying to learn C in a semester to use in a numerical programming class. And I already had a lot of other things going on. It was horrible.
The instructor was a Fortran user, I think. I think he knew C, though.
Anyway, I got help from a friend in another country, the Uk. But no local help.
@terdon You originally introduced me to the Suspender Chrome/Chromium extension. For some reason it's stopped suspending recent pages. Any idea why this might have happened?
Or, indeed, how to debug it?
Hmm. Excessive number of tabs. I think I need to take a timeout and do some mass deleting.
Anyway, to check, just print the output and compare them. Do echo /usr/share/doc/*/copyright >a and find /usr/share/doc -name copyright -type f > b and compare the output.
@Pandya OK, I think I figured it out. I also had different results on my Debian and it's because of links. The glob approach will expand all links. For example:
Note that those two have the same inode number, they're the same file. That's because:
$ ls -l usr/share/doc/wpa_supplicant
lrwxrwxrwx 1 root root 13 Jan 19 2013 usr/share/doc/wpa_supplicant -> wpasupplicant
Since find is searching for files, it will i) ignore files that are links and ii) will only find the link's target since that is the only existing file.
The glob on the other hand, will list both usr/share/doc/wpa_supplicant/copyright and usr/share/doc/wpasupplicant/copyright despite the fact that wpa_supplicant is a link to wpasupplicant and so is the same file.
By the one advantage of find : It also include files like /usr/share/doc/ca-certificates/examples/ca-certificates-local/debian/copyright which can't be found with /usr/share/doc/*/copyright
should we include it? or we should set maxdepth with find?
By the way, @Pandya, what's your avatar? I just noticed that the last letter is Pa (or at least, the sanskrit Pa). The line on top would make an I (or O, I have forgotten my sanskrit) but it would affect the 1st letter, so it can't spell Pandya, right?
@Pandya The other advantage is that it actually finds the right number. Also, you can use globstar: shopt -s globstar; grep -l "General Public License" /usr/share/doc/**/copyright.
Devanagari (/ˌdeɪvəˈnɑːɡəriː/ DAY-və-NAH-gər-ee; Hindustani: [d̪eːʋˈnaːɡri]; देवनागरी devanāgarī a compound of "deva" [देव] and "nāgarī" [नागरी]), also called Nagari (Nāgarī, नागरी), is an abugida (alphasyllabary) alphabet of India and Nepal. It is written from left to right, has a strong preference for symmetrical rounded shapes within squared outlines, and is recognisable by a horizontal line that runs along the top of full letters. In a cursory look, the Devanagari script appears different from other Indic scripts such as Bangla, Oriya or Gurmukhi, but a closer examination reveals they are very...
At that time You @terdon and @Avinash Raj are competitor (for sed,awk,perl etc answer) example I've first accepted his answer, then you improved your and I accepted your answer. At that time I was not so aware of Unix&Linux.SE
@cuonglm working fine; +1
In brief that was probably my first message on chat on SE network! which was for @terdon!!
After knowing that "grep doesn't ignore anything. *, by default, does not match files with a leading .", should I edit my question (like wild-card * ignores files starting with dot) or should leave it as it is?
If anyone has any thoughts regarding the trivial point of tag wiki default text, feel free to @ send them here, or join the chat room I probably messed up
the "this tag has no wiki" default text says "...along with guidelines on its usage" -- yet my most recent edits were updated to put the tag usage in the excerpt (up top) versus down in the wiki.
maybe meta would be a better place, but if anyone sees this and has a preference, chime in! :)
@shaggy Is a Chromebook all you have access to? I wish I had more knowledge of using a Chromebook as a native Linux (OS) box. Any ideas on which distro you're settling on?
I'm using Debian Stretch and today I did apt-get upgrade && apt-get dist-upgrade. After that, nearly every action is started to ask root password, including external monitor plug/unplug, USB harddisk mount, suspend, etc...
Why is that? How can I trace this issue?
@NAltun I have pretty much have access to anything at this point, so i'm not limited to a chromebook. I just don't need something super fancy to learn linux on, as well as keeping it financially practical, the cheaper the better. But with that kept in mind, It would be good for all the hardware to be well supported OOTB.
I'm only considering a chromebook due the fact that chromeOS is linux based so the hardware support is there, its a modern machine, and is super portable. If there is a better option i'm totally open to it.
Before my discovery of the chromebook, I was planning on going down the thinkpad path.
@MichaelHomer yeah, that's a strange one. I even voted to close it as off-topic on SO.
Questions about general computing hardware and software are off-topic for Stack Overflow unless they directly involve tools used primarily for programming. You may be able to get help on Unix & Linux. — GillesJan 7 at 23:49