X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: ANNOUNCE: DJGPP port of GNU Emacs 23.3 uploaded
Date: Thu, 26 May 2011 15:23:25 -0700 (PDT)
Organization: http://groups.google.com
Lines: 82
Message-ID: <47cebf55-5d64-4d50-bf73-1a5a281c4d31@14g2000yqo.googlegroups.com>
References: <201104251501 DOT p3PF1pXS011872 AT delorie DOT com> <ipeqs4$5sb$1 AT news DOT onet DOT pl>
 <8339l07wbn DOT fsf AT gnu DOT org> <bc8ba0ee-3b1d-4a2d-81f7-e00bede5a926 AT z7g2000prh DOT googlegroups DOT com>
 <83zkmvggv4 DOT fsf AT gnu DOT org> <a247b893-6e70-4901-9210-6f158cde30c7 AT x1g2000yqb DOT googlegroups DOT com>
 <6621d833-5d9a-4f43-8b36-1fe53191e293 AT d26g2000prn DOT googlegroups DOT com>
 <E1QKNyW-0002Ko-SC AT fencepost DOT gnu DOT org> <80c58cc8-0175-4094-b0be-70ff8cb8c860 AT z7g2000prh DOT googlegroups DOT com>
 <83boz7hlsf DOT fsf AT gnu DOT org> <2459042b-be39-40bd-9d58-4abb85924a98 AT p13g2000yqh DOT googlegroups DOT com>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1306448605 19259 127.0.0.1 (26 May 2011 22:23:25 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Thu, 26 May 2011 22:23:25 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: 14g2000yqo.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESNKRC
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.10)
 Gecko/20101005 Fedora/3.6.10-1.fc14 Firefox/3.6.10,gzip(gfe)
Bytes: 6244
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

On May 14, 3:42=A0pm, Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com> wrote:
>
> I don't think it's my (admittedly noob-ish) .sh files. "emacs blah.sh"
> works fine, font-lock works, and sh-script mode is loaded. It's just
> somehow through Dired it doesn't work. Similarly with auto-compression-
> mode on a .ZIP (crash). I'm fairly certain it's just a quirk (no)
> thanks to AMD64 / DOSEMU. I really need to try on my 32-bit Linux
> machine too.

Hours and hours and hours of testing later ... yes, DOSEMU (32-bit)
works fine. sh-script-mode works fine via Dired ('v') via Unzip. And I
discovered that modula-2-mode is the one with the '\' bug, yet for the
exact same thing, pascal-mode works fine (go figure). More minor
testing will follow eventually, but I'll try not to bug you, Eli, at
all if possible (only big stuff, not silly things like syntax
highlighting).

I probably shouldn't have even wasted your time with such an oddball
testing environment (DOSEMU, esp. x86-64), but I figured it was worth
(barely) testing. My bad.  :-/

<rant>
Not to rag on Fedora (sorry, DJ), but I couldn't get my wifi to work
initially. I (very naively) thought a "full upgrade" (400 MB) would
get me a newer ("better"??) kernel, but that literally took all night.
And it hosed the jump drive's install, heheh. Then I grabbed F15 beta
to test. And then I could get wifi to work (once I found the correct
firmware, *shakes fist*) with goofy GNOME 3. When F15 final came out
two days ago, I upgraded, and I finally decided to stop being crazy
and just use 32-bit DOSEMU (V86 mode, ftw!). However, F15 doesn't save
persistent changes! I ended up downloading at least twice, reimaging
several times, even tried again after they (finally) updated the
liveUSB tool. And it still doesn't save changes. So back to F14 (i686)
I went. At least now (!) wifi and DOSEMU work okay and save changes
for me, sheesh.

Of course, you'll have to use rpmfind.net to grab "non-free" DOSEMU as
Fedora is insanely strict (same as Debian) because the FreeDOS kernel
(compact model) needs OpenWatcom to *rebuild!!!!* (OSI approved but
"not good enough"). DOSBox is not even close to suitable, "only meant
for games"! Once you get that installed and kill the initial crash /
bug (can't find shell but it figures it out later anyways), you also
have to do two things (or something similar, this is from memory):
"su -c 'sysctl -w vm.mmap_min_addr=3D0" and "su -c 'sesetbool -P
mmap_low_allowed 1'". So yeah, works great once you get all that
sorted out! (But no, I haven't done any heavy DJGPP testing yet. In
very limited prior experience a few months ago, I had lots of problems
with DJGPP's "./configure && make", which I think actually hung DOSEMU
a few times at the config.status generation stage, ugh. Dunno why.)
</rant>

> (Yeah, probably should've avoided 64-bit, but long story
> short, I didn't, I took the easy way out. Also should probably get my
> old laptop repaired, but that's more to do. And get wifi working under
> Fedora. And a billion other things. Ugh.)

Old old P166's floppy drive broke (again). One P4 (which had XP until
that hosed itself, HD problems?) has PuppyLinux + DOSEMU via USB boot,
but I don't use it as much (kinda a kludgy machine). Other P4 has XP
but is disconnected (need a KVM, "yet another" thing to do!!). And (I
hate to say) I've been somewhat more preoccupied than usual. So my
options for running DJGPP's Emacs weren't perfect.

I guess I (have to) give up on the (semi-useful) Windows + DJGPP combo
unless I can resurrect that old P4 (either buy a KVM or find bro's old
one, but none of that's urgent by any means). I just wasn't too
careful (and honestly have no "need") re: 32-bit vs. 64-bit. I just
poke around, just a silly hobbyist. For laughs I thought "trying"
DOSEMU x86-64 would be interesting, but long story short, some stuff
works, most doesn't. So it's not perfect by any means. And VirtualBox
would be nice but needs a decent FreeDOS setup / image, which I don't
have [yet] (and nobody else seems to care to make one). FD 1.0 is too
big and too old, IMHO. But perhaps I should've tried that anyways.
(Unfortunately, I'm not sure any of it is ideal for building DJGPP
stuff, neither pure FreeDOS [even w/ DOSLFN] nor DOSEMU nor WinXP. But
at least the latter mostly works. Too bad that's the worst choice
nowadays.)

So there. Hopefully that explains some stuff or helps somebody
somewhere (barely, though I doubt it).   :-P