Forum comments in chronological order
Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.
Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
Aug 2024
Anonymous
Wed 7-Aug-2024 10:17
Wed 7-Aug-2024 10:17
"Don't let a broken tool ruin your weekend! Take a look around the room and hack something together"
Chapeau bas! Couldn't say it any better :-))
Chapeau bas! Couldn't say it any better :-))
marky
Thu 8-Aug-2024 22:41
Thu 8-Aug-2024 22:41
Nice post! Instead of me asking you a question, let me sort-of/kind-of answer one that you implicitly asked. You wrote:
"I don't know why the designers of UNIX had to go all the way to invent SIGTTOU and SIGTTIN instead of relying on blocking I/O"
I don't know the historical motivation, but I do know this: there are nice things you can do with these signals that you can't accomplish just by letting the operation block.
To see this, consider what it would mean if trying to read from the terminal was just a normal blocking read. This read will never complete until the job becomes the foreground job again. Thus, that process, and presumably the entire pipeline, is now stuck.
But the shell has no knowledge of this, and thus the user won't either! The user backgrounded the job in the hopes that "eventually it will finish and let me know" and doesn't realize that the job is now waiting for the user to foreground it.
But the shell DOES know if the process gets suspended! So then it can then tell the user, who can then type "fg" and reply to the password prompt or whatever it is that the program decided it needed.
Sadly, this nice property seems to break over SSH, as I recently lamented about at stack overflow, here:
https://stackoverflow.com/questions/78843587/how-to-run-ssh-in-the-background-without-writing-my-own-os-kernel-and-ssh-server
To fix this issue, I think we'd need new kernel APIs and a change to the SSH protocol
"I don't know why the designers of UNIX had to go all the way to invent SIGTTOU and SIGTTIN instead of relying on blocking I/O"
I don't know the historical motivation, but I do know this: there are nice things you can do with these signals that you can't accomplish just by letting the operation block.
To see this, consider what it would mean if trying to read from the terminal was just a normal blocking read. This read will never complete until the job becomes the foreground job again. Thus, that process, and presumably the entire pipeline, is now stuck.
But the shell has no knowledge of this, and thus the user won't either! The user backgrounded the job in the hopes that "eventually it will finish and let me know" and doesn't realize that the job is now waiting for the user to foreground it.
But the shell DOES know if the process gets suspended! So then it can then tell the user, who can then type "fg" and reply to the password prompt or whatever it is that the program decided it needed.
Sadly, this nice property seems to break over SSH, as I recently lamented about at stack overflow, here:
https://stackoverflow.com/questions/78843587/how-to-run-ssh-in-the-background-without-writing-my-own-os-kernel-and-ssh-server
To fix this issue, I think we'd need new kernel APIs and a change to the SSH protocol
A case against syntax highlighting
Anonymous
Sat 31-Aug-2024 18:18
Sat 31-Aug-2024 18:18
This article totally miss the point.
There is good syntax highlighting, and there is bad syntax highlighting.
If I had infinite free time like the author, I might actually write an article about bad vs good.
There is good syntax highlighting, and there is bad syntax highlighting.
If I had infinite free time like the author, I might actually write an article about bad vs good.
Anonymous
Sat 31-Aug-2024 20:06
Sat 31-Aug-2024 20:06
The best the awesome the incredible the legend. Love. Come back to revision !