search for: lugaru

When I use "ls -al" on a directory, for files with only owner read/write permission, the displayed attributes are "-rw-", not "-rw-------". That means the file names don't line up with other files in the directory, which makes the listing harder to read. What changed where and how do I fix that?

On Fri, 25 Oct 2019 at 20:14, Kenneth Porter <shiva at sewingwitch.com> wrote: > > Found it. It happens from the process buffer inside Lugaru Epsilon. I think > ls thinks it's doing a DIRED output instead of a shell output. Now I need > to figure out why it thinks that. This wasn't happening in CentOS 7. > Lugaru Epsilon? I think you need to give a lot more explanation on what is going on because I (at least) have no id...

Found it. It happens from the process buffer inside Lugaru Epsilon. I think ls thinks it's doing a DIRED output instead of a shell output. Now I need to figure out why it thinks that. This wasn't happening in CentOS 7.

Hello lsit, I''am new to rails (about 2 hours) and after the first lines of code I must say: Great! I love it! Can someone recommend me a editor? I run Ubuntu Dapper. Th?ngs -- Jochen Kaechelin, fvgi242ss, wlanhacking.de http://mail.wlanhacking.de/cgi-bin/mailman/listinfo http://www.gissmoh.de - Mein sonstiges Leben!!

--On Friday, October 25, 2019 6:13 PM -0700 Kenneth Porter <shiva at sewingwitch.com> wrote: > Found it. It happens from the process buffer inside Lugaru Epsilon. I > think ls thinks it's doing a DIRED output instead of a shell output. Now > I need to figure out why it thinks that. This wasn't happening in CentOS > 7. I'm puzzled. I can't find anything in the Gnu coreutils manual to describe this format. I do note that out...

It's not a ls bug. I've stepped through the code with gdb and it looks just fine. At this point I think Epsilon (a 32-bit app) is corrupting the image of its child process in a strange way. I'm working with the author at Lugaru (who's very responsive) to track it down. He couldn't reproduce it right away. I just reproduced it on a virgin CentOS 8 image at Linode with utterly no modifications. I just spun up the VM, logged in, scp'd the Epsilon RPM, dnf installed it, and demonstrated the issue. I extracted...