janos

1,181 reputation

bio	website	janosgyerik.com
	location	Paris, France
	age	34
visits	member for	1 year, 1 month
	seen	Apr 16 at 20:20
stats	profile views	34

I have a natural passion for programming, especially to create practical software for everyday use. Ultimately I want to put my skills to use in the field of green energy or health, as I am very concerned about these areas and I believe that having great software could help a lot and make a big difference.

	1,181 reputation	bio	website	janosgyerik.com	visits	member for	1 year, 1 month
29 badges		location	Paris, France		seen	Apr 16 at 20:20

summary answers questions tags badges favorites bounties reputation activity

48 Comments

suggestions reviews revisions comments badges posts accepts all

Mar 17	comment	A bunch of files have 777 permissions Normally you don't need to check the permissions every time, unless you want to be suspicious. It's strange how those application files got such permissions.
Feb 20	comment	setuid programs don't seem to run setuid in TinyCore Linux The live CD I use is tiny, 8MB to begin with. I doubt it would be that sophisticated, but maybe you're right, I should check on this (not sure how...). As per `/tmp`, I used that only to simplify the question. In my real setup it's in my home directory, not mounted `nosuid`. In fact, the vulnerability test works in the native environment, then I `chroot` into it there it doesn't.
Feb 20	comment	setuid programs don't seem to run setuid in TinyCore Linux I don't execute anything from a mounted CD. While remastering the CD, the `chroot` directory is on a regular filesystem not a CD mount. When booting into the completed remastered live CD, the files are on the root filesystem, which is NOT mounted with `nosuid`.
Feb 20	comment	setuid programs don't seem to run setuid in TinyCore Linux It doesn't have to. If you try the above steps it should work in any Linux system, and when you run `PATH=.:$PATH ./prog`, the file `/tmp/test.txt` will be created and owned by `uid=1200`, even if it does not exist.
Feb 12	comment	SSH tunnel hanging I run `autossh` within a `screen` session. It's better then background, as I have a dedicated "window" for it that I can detach from and re-attach later to check on the status.
Dec 20	comment	Review changes in .tex files You don't have to persuade anybody. You can use a DVCS by yourself and enjoy all the benefits.
Oct 31	comment	pysqlite install error on FreeBSD in virtualenv Crap. I'm out of ideas then...
Oct 31	comment	pysqlite install error on FreeBSD in virtualenv in that case, it looks like something's wrong with the libraries in your system that `sqlite` depends on. Perhaps you can try to reinstall them if possible. Basically reinstall dependencies until everything is nice and clean. It might also be a good idea to create a completely clean VM and see if it works there.
Oct 30	comment	Can't locate shell script If the script is running after reboot, then what is starting it? Check the output of `crontab -l` of your user and root. How does it logon to the server? If `ssh` then you can find the process with `ps` and track down the parent process leading to the script and its details such as the path
Oct 15	comment	Equivalent of date --reference in Solaris the awk in this system here is `/usr/bin/awk`, but it doesn't have neither `sub` nor `gsub` and it also cannot assign values to `$0`. Definitely the most primitive awk I've ever seen. Bottom of man page: `SunOS 5.10 Last change: 4 May 2010`
Oct 15	comment	Equivalent of date --reference in Solaris Nice, thanks! In your answer you are mentioning both `-e` and `-E`, that's a bit confusing. In the Solaris I have here (5.10) it works only with `-E`, and using `nawk` instead of `awk`. Actually this way is easier for me: `ls -Ego /path/to/file \| awk '{print $4 "_" $5}' \| tr -d : \| sed -e 's/\..*//'`
Oct 12	comment	Equivalent of date --reference in Solaris I'm in Solaris 10. I found GNU date in `/usr/local/bin/date`. That's a good workaround, but it would be good to know another solution in case GNU date is not available.
Oct 12	comment	How to detect dos format files in git bash No `od` in Git Bash. But the `tr` trick is pretty clever and it works! There is just one relatively minor issue with it: it detects CR anywhere in the file, but I need to detect CR at line endings. You have lead me to the solution, using `sed` instead of `tr`. See my answer for more details, and thanks again!
Oct 12	comment	How to detect dos format files in git bash Thanks @DavidKohen but I'd rather install cygwin than VS* ;-)
Oct 12	comment	How to detect dos format files in git bash @cjm This is not necessarily for files under version control but any files
Oct 12	comment	How to detect dos format files in git bash @DavidKohen you're right, `-exec` would work too. But it's irrelevant for the question, so I removed that now.
Oct 11	comment	How to detect dos format files in git bash Edited the question to clarify what is Git Bash. Moderator: please remove these comments, thanks.
Oct 11	comment	How to detect dos format files in git bash No gcc or cc comes with Git Bash. I don't want to install cygwin. So, thanks, but nevermind. My workaround is to convert all files which I suspect to have CR line-endings. The files which don't have will not be changed so it should be ok, it's just an ugly solution.
Oct 11	comment	How to detect dos format files in git bash Same as `printf`, none of the files match that way.
Oct 11	comment	How to detect dos format files in git bash Yeah it should normally work, but it does not work in Git Bash. Unfortunately none of your tips work: the `printf` doesn't work, `grep` doesn't have `-P` flag, and there is no `file` command in Git Bash... Any other ideas?