search for: openrheinruhr

...some GNU make versions. > So that's a bit odd, also, wouldn't shell sh do a double shell? Shell Apparently not, otherwise it'd work without. bye, //mirabilos -- ?Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.? -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: ?[?]uhr.gz is a reason to install mksh on every system.?)

...lding klibc >and any software linked against klibc. I would much prefer to We can enforce this in klcc, just like -mregparm=3 is used by the i386 target. bye, //mirabilos -- ?Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.? -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: ?[?]uhr.gz is a reason to install mksh on every system.?)

Hey Greg, On 08-09-2020 22:07, Thorsten Glaser wrote: > Greg Thelen dixit: > >> This doesn't work with older versions of make. ?make 4.2.1 seems common >> now and does not support $(shell command). >> >> $ cat Makefile >> $(info take1: $(shell command -v ls)) >> $(info take2: $(shell bash -c 'type -p ls')) >> >> all: >>

On 11/08/2013 09:12 AM, Steve Capper wrote: > + > +/* > + * x19-x28 are callee saved, also save fp, lr, sp. > + * d8-d15 are also callee saved. > + */ > + > +struct __jmp_buf { > + uint64_t __gregs[13]; > + uint64_t __fpregs[8]; > +}; > + Since the index of these arrays have no connection with what is stored in them, they should be named fields in the structure,

Hi Ben, >Thorsten: I've attached a patch which I tested briefly in QEMU. Let me >know if this works for you. sorry for the delay. I was able to test this on eller today. To reproduce the issue, this was needed, because the value read was a nanosecond field and so the test didn?t always fail: (sid_mips64el-dchroot)tg at eller:~$ while sleep 0.1; do :>b; ./mksh -c 'test a -nt

On 2020-07-27 19:20, hpa at zytor.com wrote: > > I'm not so sure they have dealt with it in the sense of having it work on all architectures. *Most* of the problems are related to the shifting the arguments by one, which can cause a bunch of problems, especially if it means the arguments spill to memory. However, I have absolutely no idea how to correctly implement syscall(3) on s390

- Convert the "old style" GNU field designator extension to the new style. - Use proper indexing into a string literal. - Use "%s" for the format string in "fmtstr". - Add or remove casts of the "void *" argument of ioctl. - Convert "if (!exitstatus == isor)" to "if ((!exitstatus) == isor)" which retains the current semantics, but may

Hi, sifting through my system's logs, I noticed many break-in attempts by rogue ssh clients trying long lists of common passwords. For some time now I pondered different approaches to counter these, but could not come up with a solution that really satisfied me. I finally reached the conclusion that any countermeasures required support in sshd itself, and created the attached patch. If

Hi, I've noticed some ssh behaviour that I wish didn't happen. I was wondering if someone can explain how I can stop it from happening, or explain why it's unavoidable. If I ssh-with-agent-forwarding from one host to a second host, and on the second host use something like nohup/screen/tmux/daemon, and from within that new process session, start a long-running command via