search for: microsoftian

...ng else. >> Python?c? C++? >> > If I thought C was an appropriate choice to get this done, I'd be > patching the expect source code instead to deal with Microsoft's > non-implementation of POSIX. > > If a language conceals the differences between POSIX and Microsoftian C > for interprocess control, hides badly non-POSIX filepaths from me, and > has a reasonable track record of forward compatibility, and has a > reasonably universal build process, I'll consider crash-learning the > language if I'm not already working in it. For my test sui...

...-3.10.0-229.1.2.el7.x86_64, among many other things. When I rebooted, I was asked to confirm (or renew, or some such) my license. My LICENSE ??? I was booting in text mode and the actions required were a) unfamiliar, and b) hard to understand. As I recall, I had to read the EULA - a worrisomely Microsoftian demand - and accept it. Of course, the terms were pretty benign. Then I had to continue. I can't remember the exact language. Of course, now when I reboot, all this cruft is gone. Is this a cute April Fool joke? If not, WTF is going on? -- David A. De Graaf DATIX, Inc. Hende...

...ut for much beyond that, something else. > Python?c? C++? > If I thought C was an appropriate choice to get this done, I'd be patching the expect source code instead to deal with Microsoft's non-implementation of POSIX. If a language conceals the differences between POSIX and Microsoftian C for interprocess control, hides badly non-POSIX filepaths from me, and has a reasonable track record of forward compatibility, and has a reasonably universal build process, I'll consider crash-learning the language if I'm not already working in it. [I do some programming in Python al...

On Jul 30, 2008, at 1:15 PM, Kenneth Boyd <zaimoni at zaimoni.com> wrote: > I've been thinking of constructing a mirror test suite coordinated > using > shell scripts (bash) Please no, pick a real language. I love bash and it is fine for any 200 line or less program, but for much beyond that, something else. Python?c? C++?

...of these languages but I'm trying > not to let personal preference get in the way. :) Neither I do. This sub-thread started with a discussion about the feasibility of leaving behing DejaGNU and using `bash' instead or: > > If a language conceals the differences between POSIX and Microsoftian C > > for interprocess control, hides badly non-POSIX filepaths from me, and > > has a reasonable track record of forward compatibility, and has a > > reasonably universal build process, I'll consider crash-learning the > > language if I'm not already working in it....

...Python?c? C++? > > > > If I thought C was an appropriate choice to get this done, I'd be > > patching the expect source code instead to deal with Microsoft's > > non-implementation of POSIX. > > > > If a language conceals the differences between POSIX and Microsoftian C > > for interprocess control, hides badly non-POSIX filepaths from me, and > > has a reasonable track record of forward compatibility, and has a > > reasonably universal build process, I'll consider crash-learning the > > language if I'm not already working in it....

...any other things. > When I rebooted, I was asked to confirm (or renew, or some such) > my license. My LICENSE ??? > > I was booting in text mode and the actions required were > a) unfamiliar, and b) hard to understand. > > As I recall, I had to read the EULA - a worrisomely Microsoftian > demand - and accept it. Of course, the terms were pretty benign. > Then I had to continue. I can't remember the exact language. > Of course, now when I reboot, all this cruft is gone. > > Is this a cute April Fool joke? > If not, WTF is going on? RHEL 7, which is upstre...

When I try to compile e2fsprogs-1.24a I receive the following snippet: tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a# mkdir build;cd build tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a/build# ../configure <<SNIP>> ./mk_cmds: Files/e2fsprogs-1.24a/lib/ss: No such file or directory mk_cmds: Couldn't find mk_cmds's template files. make[2]: ***

On Monday 04 August 2008 16:59, Óscar Fuentes wrote: > David Greene <dag at cray.com> writes: > >> For my test suite I use Tcl (with TclX, no Expect). It watches stdout > >> and stderr, gets exit codes and has a timer for killing hanged > >> processes. Process control works the same on Windows and Unix and takes > >> a less than 30 lines of code. >

David Greene <dag at cray.com> writes: >> For my test suite I use Tcl (with TclX, no Expect). It watches stdout >> and stderr, gets exit codes and has a timer for killing hanged >> processes. Process control works the same on Windows and Unix and takes >> a less than 30 lines of code. >> >> What else do you need? > > A way to examine asm output and