Re: [Freedos-devel] Python on freedos.

[Kenway, Owain]

Hi,

I looked at this briefly a while ago and stopped because I don't have a 
cross-compiler set up (which is what that Makefile appears to be for), and I 
was only mildly interested in having a working Python 3(ish).

I don't think it should be too hard to modify it to build natively on FreeDOS 
though?  I suspect from my attempts/successes on other things the main problem 
may be long filenames getting mangled at some point between the machine you 
"git clone" on and actually building the code on FreeDOS.

Cheers,
Owain

--
/UCL/ISD/RITS/RC Applications & Support Team Leader/Owain Kenway
Twitter: @owainkenway   || E-mail: o.ken...@ucl.ac.uk
Internal: 59834 || External: 02031089834
The Green Zone, 1 St Martin's Le Grand, London, EC1A 4NP



From: Pär Moberg 
Sent: 29 January 2019 23:12
To: Technical discussion and questions for FreeDOS developers.
Subject: Re: [Freedos-devel] Python on freedos.

MicroPython has a target for freedos:
https://github.com/micropython/micropython/blob/master/ports/unix/Makefile#L229
I don't know if it builds. It is too late to find out for me.

On Tue, 29 Jan 2019 at 23:51, Rugxulo  wrote:
>
> Hi,
>
> On Tue, Jan 29, 2019, 4:40 PM Matej Horvat >
>> On Tue, 29 Jan 2019 23:20:21 +0100, Rugxulo  wrote:
>>
>> > There also was a guy, a few years ago, who was building ("Lightning")
>> > Python for Win32 via OpenWatcom. I never tried it, but that would
>> > probably
>> > build for DOS/32-bit. Even the Win32 .EXE almost certainly runs under HX
>> > in
>> > DOS. So maybe you could try that.
>>
>> I was just going to suggest that.
>>
>> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flightningpython.org%2Fdata=02%7C01%7Co.kenway%40ucl.ac.uk%7Cac10630f89fd4a1b6ef108d6863f5ba9%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C0%7C636844004011952747sdata=ONxU7hdyO85d5O3niNuMhnT7Pb4dHbjZOmdLIAfQ44Q%3Dreserved=0
>>
>> Unfortunately, it doesn't run with HX. It's missing ShellExecuteW,
>> RegConnectRegistryW, RegLoadKeyW, RegSaveKeyW, and possibly other
>> functions. This might be solvable by adding dummy implementations to HX; I
>> don't know.
>
>
> HX 2.17? Set DPMILDR=136 and try again (hoping it won't actually call such 
> unresolved imports). Or try the latest HX prerelease on Github, maybe it 
> works better, who knows.
>
> ___
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ffreedos-develdata=02%7C01%7Co.kenway%40ucl.ac.uk%7Cac10630f89fd4a1b6ef108d6863f5ba9%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C0%7C636844004011952747sdata=Rc4XPu2cu6hiGad8cLPBvMAsQWjY60eF6%2F%2BQeurt8iI%3Dreserved=0


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ffreedos-develdata=02%7C01%7Co.kenway%40ucl.ac.uk%7Cac10630f89fd4a1b6ef108d6863f5ba9%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C0%7C636844004011952747sdata=Rc4XPu2cu6hiGad8cLPBvMAsQWjY60eF6%2F%2BQeurt8iI%3Dreserved=0


___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] irc oper required at #freedos

[Kenway, Owain]

Hi,

It's not just #freedos, the whole of Freenode has been under attack (I didn't 
even realise there was a #freedos on there - I use it to talk to other HPC 
people):

https://freenode.net/news/spambot-attack

Might pop by #freedos on there at some point if other people go there :)

Cheers,
Owain

--
/UCL/ISD/RITS/RC Applications & Support Team Leader/Owain Kenway
Twitter: @owainkenway   || E-mail: o.ken...@ucl.ac.uk
Internal: 59834 || External: 02031089834
The Green Zone, 1 St Martin's Le Grand, London, EC1A 4NP


From: Jim Hall 
Sent: 02 August 2018 15:52
To: Technical discussion and questions for FreeDOS developers.
Subject: Re: [Freedos-devel] irc oper required at #freedos

Thanks Steve, very helpful.

Having a little more time to research: looks like +q effectively bans(?) users 
from chatting, except for matching users. And the $~a pattern seems to match 
registered users?

At least, that's what I get from reading jjasghar's channel operator quick 
reference and freenode's 
channel modes document.

Another note from jjasghar's 
page says "if you are 
overwhelmed, you can regain some stability by muting unregistered users with 
/mode #reddit-diabetes +q $~a while you ban the ip addresses that the troll is 
wielding." So that suggests when Mdasoh said "we have had an enjoyable time 
hanging out in #freedos/irc.freenode.net [..] until 
the day before yesterday" that the day before yesterday the #freedos channel on 
irc.freenode.net got spammed and/or trolled? I am not 
usually on IRC, so I hadn't heard of this.






On Thu, Aug 2, 2018 at 6:34 AM, Steve Nickolas 
mailto:usots...@buric.co>> wrote:
On Thu, 2 Aug 2018, Jim Hall wrote:

Hi!

So, what happened on IRC the day before yesterday?

I'm afraid you've lost me with the other IRC stuff you mention. I don't
know what "/mode #freedos +q $~a" does. Is that something visitors on IRC
would do in their clients, or is this an IRC server setting? (Note that I
don't run the IRC server at freenode.)

It's a channel mode.  (I don't know what it does because over on Hoshinet we 
use Unrealircd, which does things different from whatever Freenode's current 
ircd is.)

Also not sure what "irssi scripts" do. Again, is this something for the IRC
clients, it something in the server? I looked at the scripts you linked to
but don't know enough about IRC to know what I'm looking at.

irssi is an IRC client for Linux.  I suppose the scripts in question are to 
make channel management easier.

(For what it's worth, about 6 years ago I wrote an IRC client for DOS.)

-uso.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Re: [Freedos-devel] What is FreeDOS 2.0?

[Kenway, Owain]

(sorry if the formatting is messed up, OWA is a horror)

From: Jim Hall 
Sent: 17 October 2017 16:44
To: freedos-devel@lists.sourceforge.net
Subject: [Freedos-devel] What is FreeDOS 2.0?

> Hi all

> I don't know if you saw on our Twitter or on Facebook, but since its
> release on December 25 2016, FreeDOS 1.2 passed 500,000 downloads in
> June 2017. And passed 600,000 in August. As of this week, FreeDOS 1.2
> has been downloaded over 671,500 times.

> I've lately wondered what should come after FreeDOS 1.2. I think it's
> time to talk about "FreeDOS 2.0." I wanted to start a conversation
> thread for it.


> My thoughts:


> FreeDOS is meant to be an open source software replacement for MS-DOS.
> As such, "FreeDOS 2.0" must maintain compatibility with MS-DOS. I am
> not suggesting changing core compatibility. "FreeDOS 2.0" needs to 
> remain 16-bit, with a single-user single-tasking command-line
> environment that runs on PCs. Compatibility is key!

> However, in looking at what "FreeDOS 2.0" might be, I think we are
> maintaining some legacy softare that doesn't need to be part of "base"
> anymore. So in looking at "FreeDOS 2.0," I am thinking about changing
> what tools and utilities are installed when you choose "Base packages
> only" versus "Full installation."

> Let's start a discussion:

> (1) What does "Base" mean in 2017 or 2018? I think there are some
> packages we might take out of "Base" and move into a "Compat" package
> group, such as:

> APPEND
> ASSIGN
> GRAPHICS
> JOIN
> SUBST
> others?

Sounds good to me!

> (2) Are there other packages we should install "Base" by default? I
> don't want to make this a free-for-all, but perhaps there are some
> utilities that should be "promoted" to "Base." What utilities do you
> think should be moved to "Base" in "FreeDOS 2.0"?

> (3) What packages do we include in FreeDOS 1.2 that shouldn't exist in
> "FreeDOS 2.0"?

> (4) Is there anything missing in FreeDOS 1.2 that should be included
> in "FreeDOS 2.0"?

Personally I'd like (note like, not need!) more of the development tools from 
Open Watcom and DJGPP to be available as packages.  Currently these are 
(reasonably, due to popularity!) skewed towards C/C++ but both provide 
compilers for other languages (Fortran, Ada etc.) which we don't have packages 
for.  DJGPP also has an Emacs build which might interest some people.

Similarly there are a couple of nice DOS Open Source languages we could add - 
UCBLogo and Gambit Scheme (I've not found a good Open Source Common LISP for 
DOS but I am looking!).  Both work well on FreeDOS 1.2, it'd just be nice to 
have packages for them!

The only other thing I'm missing a bit more generally is better USB support for 
things like serial <-> USB (increasingly a problem for modern hardware :( ) but 
there doesn't appear to be anything that could be added off the shelf for that 
so it's a bit of work.

Perhaps some applications for OpenGEM?

> When replying to this discussion, I ask that you reply in-line (not
> reply-top or reply-bottom) and to keep your discussion focused and
> on-topic. This discussion is about "FreeDOS 2.0."


> Jim


> Other references:

> http://www.freedos.org/software/
> http://wiki.freedos.org/wiki/index.php/FreeDOS_Road_Map


Cheers,
Owain

--
/UCL/ISD/RITS/RC Applications & Support Team Leader/Owain Kenway
Twitter: @owainkenway   || E-mail: o.ken...@ucl.ac.uk
Internal: 59834 || External: 02031089834
First Floor, The Podium, 1 Eversholt Street, London, NW1 2DN

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel