[Freedos-kernel] Will retire the freedos-kernel email list

[Jim Hall]

Hi freedos-kernel developers:

I think everyone on this email list is also on freedos-devel, so you
probably have seen the discussion there about the different
communication channels for FreeDOS.

We obviously use the freedos-devel and freedos-user email lists. But
the freedos-kernel list is not used very much. Looking at the archive,
this hasn't seen more than a few emails per *year* in the last several
years.

Because of the light traffic, let's consolidate our developer
discussions! The freedos-kernel email list will be closed this week.
Instead, please use the freedos-devel email list to discuss any
FreeDOS kernel development topics.

Thanks!

Jim


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

[Freedos-kernel] Closing down the list?

[Jim Hall]

I've noticed that traffic on this list has decreased to the point of a 
trickle.  It's been suggested to me that we try to consolidate lists, to 
re-invigorate discussion among FreeDOS developers and focus discussion 
to relevant development topics.


Closing down some of the lists in order to funnel new users into a 
common discussion area does seem to be the best move.


I copied the list traffic stats into a spreadsheet so I could look for 
trends.  See http://www.freedos.org/jhall/temp/traffic/traffic.png



It's pretty clear that freedos-user, freedos-devel, and freedos-32-dev 
are the most active lists.  The others have declined in traffic since 
about Sept 2004, if they had any traffic to speak of.  That means the 
lists to close down would be freedos-devel-net, freedos-kernel, 
freedos-freecom, freedos-cvs, and fd-doc-list.


So, I'd like to close down freedos-kernel *and* freedos-cvs, and just 
have kernel stuff go to freedos-devel.  What do you think?  If you have 
any objections, please email me (off-list only ... I'm not subscribed to 
this list anymore) and let me know.


-jh


--
I'm sorry my president's an idiot. I didn't vote for him.


---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Re: DELTREE gets error 5 for directories since 2035a

[Jim Hall]

Oops ... should have checked that more closely before posting.  Eric is 
not the maintainer, of course.  I've moved Eric's 1.02f into a subdir on 
ibiblio, and I'll try to reach Raster to see if this can become an 
"official" release of 1.02f.

-jh

Jim Hall wrote:
Eric,
I've mirrored your DELTREE 1.02f at ibiblio:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/deltree/
I'll also update the LSM database.
Feel free to make an announcement on the FreeDOS.org page, if you want 
it announced there.

-jh

Eric Auer wrote:
Hi, Lucho pointed out that DELTREE got error 5 because it had
code which does "if OEM ID is 0FDh and CX is 0 or -1, then
explicitly exclude the DIR attribute when resetting file attribs
in preparation of deletion". This code is triggered by 2035a as
it sets CX to 0, which is needed by 32RTM DOS extender. The -1
value marked VERY old DOS-C / FreeDOS kernels which needed the
special DELTREE behaviour to avoid directories becoming files
(oops)...
The solution is two-part: The http://fdos.org/kernel/ page has
kernels which ignore dir attribute access when you change file
attributes (although it is common and okay to just respond with
error 5, as 2035a does), and I have a patched version of DELTREE
(which also is a bit smaller, less than 3 kB UPXed) which works
with kernel 2035a. No reply from Raster about it yet, strange...
http://www.coli.uni-sb.de/~eric/deltree-1.02f.zip
(temporary location)
Eric


--
I'm sorry my president's an idiot. I didn't vote for him.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Re: DELTREE gets error 5 for directories since 2035a

[Jim Hall]

Eric,
I've mirrored your DELTREE 1.02f at ibiblio:
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/deltree/
I'll also update the LSM database.
Feel free to make an announcement on the FreeDOS.org page, if you want 
it announced there.

-jh

Eric Auer wrote:
Hi, Lucho pointed out that DELTREE got error 5 because it had
code which does "if OEM ID is 0FDh and CX is 0 or -1, then
explicitly exclude the DIR attribute when resetting file attribs
in preparation of deletion". This code is triggered by 2035a as
it sets CX to 0, which is needed by 32RTM DOS extender. The -1
value marked VERY old DOS-C / FreeDOS kernels which needed the
special DELTREE behaviour to avoid directories becoming files
(oops)...
The solution is two-part: The http://fdos.org/kernel/ page has
kernels which ignore dir attribute access when you change file
attributes (although it is common and okay to just respond with
error 5, as 2035a does), and I have a patched version of DELTREE
(which also is a bit smaller, less than 3 kB UPXed) which works
with kernel 2035a. No reply from Raster about it yet, strange...
http://www.coli.uni-sb.de/~eric/deltree-1.02f.zip
(temporary location)
Eric

--
I'm sorry my president's an idiot. I didn't vote for him.
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Fwd: GRUB for DOS and FreeDOS

[Jim Hall]

Kenneth J. Davis wrote:
Jim Hall wrote:
I'm forwarding this for Wengier.  Since the current FreeDOS kernel 
seems incompatible with this version of GRUB for DOS, I'm not sure if 
I should post a note about it on the FreeDOS web site (I'm concerned 
that too many avid Linux/Windows/FreeDOS multi-boot users would try to 
use it, and make their systems unbootable.)

I would prefer you not since this is a bug against the development
kernel (as noted by the w [work in progress]), but if the bug is also
valid against the stable series, then your call.
Agreed.  I'll not post an announcement for it.
-jh

--
_
I'm sorry my president's an idiot. I didn't vote for him.
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

[Freedos-kernel] Fwd: GRUB for DOS and FreeDOS

[Jim Hall]

I'm forwarding this for Wengier.  Since the current FreeDOS kernel seems 
incompatible with this version of GRUB for DOS, I'm not sure if I should 
post a note about it on the FreeDOS web site (I'm concerned that too 
many avid Linux/Windows/FreeDOS multi-boot users would try to use it, 
and make their systems unbootable.)

But, here's the announcement anyway.  If anyone has a kernel patch to 
fix this, I'll happily make a post on the FreeDOS.org site about it.

-jh

[EMAIL PROTECTED] wrote:
Hi!
  First is an announcement:
  The latest version of GRUB for DOS (0.2.0 pre13) has been released recently. 
It is downloadable from here:
http://dos.qiee.com/en/grubdos.htm
  Then is a bug report:
  Unfortunately, there is a compatibility problem with GRUB for DOS and FreeDOS 
again. Just like the old 2030/2032 bug of the FreeDOS Kernel (as discussed in 
an earlier technote - Technote #201, 
http://www.freedos.org/freedos/news/technote/201.html), there is a similar bug 
with FreeDOS Kernel 2035w. Below are the details:
Distributed with FreeDOS beta9 (Service Release #1), the FreeDOS kernel
version 1.1.35w (Build 2035w-UNSTABLE, Nov 28 2004) also saved a wrong
BIOS interrupt vector table, so GRUB.EXE does not run. Details:
FreeDOS build 2035w-UNSTABLE destroyed two hardware interrupt vectors.
FreeDOS build 2035w-UNSTABLE tried to save the original BIOS int 0x08
- int 0x0F vectors at :0710, but the FreeDOS startup code overwrote
the region. On my QEMU virtual machine, this destroyed region is dumped
here:
:0710  A5 FE 00 F0 87 E9 00 F0-53 FF 00 F0 53 FF(04 1A)  S...S...
:0720 (1C 9E)00 F0 53 FF 00 F0-57 EF 00 F0 53 FF 00 F0   S...W...S...
:0730  99 FE 00 F0 53 FF 00 F0-53 FF 00 F0 53 FF 00 F0   S...S...S...
:0740  80 91 00 F0 CE E2 00 F0-D0 95 00 F0 53 FF 00 F0   S...
Note that the above 4 bytes in parenthesis are wrong. These 4 bytes destroyed
two interrupt entry points:
(53 FF 04 1A) corresponds to int 0x0B;
(1C 9E 00 F0) corresponds to int 0x0C.
The addresses 1A04:FF53 and F000:9E1C are invalid interrupt service entries.
They should be a valid value like (53 FF 00 F0) for example.
Hope this bug in the FreeDOS Kernel will be fixed soon!
Wengier


--
_
I'm sorry my president's an idiot. I didn't vote for him.
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] GCC Compiler

[Jim Hall]

ADE> If so, where can I get it?
 AFAIR, www.delorie.com?

For the OP, the DOS version is http://www.delorie.com/djgpp/
-jh
--
_
I'm sorry my president's an idiot. I didn't vote for him.
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] GCC Compiler

[Jim Hall]

Allen D. Evans wrote:
Hello,
I enjoy frustration and would like to compile my own
version of FreeDOS.
Does a DOS/Windows have a GCC compiler?  If so, where
can I get it?  If not, what (inexpensive) options do I
have.

You can get djgpp, but I don't think you be able to compile the kernel. 
 However, try OpenWatcom: http://www.openwatcom.org/index.html

It's free!  :)  Open source, license complies with OSI.
This is a very good compiler, and there _is_ a version for DOS.
-jh

--
_
I'm sorry my president's an idiot. I didn't vote for him.
---
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Updated unstable kernel patches and binary

[Jim Hall]

...
P.S. After sending the above message, I got the following auto-reply:
Your mail to 'Freedos-kernel' with the subject
Updated unstable kernel patches and binary
Is being held until the list moderator can review it for approval.
The reason it is being held:
Message body is too big: 76015 bytes but there's a limit of 40 KB
Either the message will get posted to the list, or you will receive 
notification of the moderator's decision.

I don't know who is that "moderator", but obviously I can't send the 
kernel binary. So here's the patch only. Now you know about the 
limitation. 40 KB must be a SACRED number EVEN for SourceForge!
I'm the moderator of the FreeDOS lists.  So your message was held until 
I could get into the system and deal with it.

40kb is a good number to set the limit, and I don't mind that SF did 
that for all lists.  I often get a number of virus/spam emails around 
49kb, so 40kb limits the number of spams & viruses that make it to the 
FreeDOS lists.

What you don't see is that I have to deal with a number of 
administrative requests each week (usually about one a day) where a 
virus has been sent to the FreeDOS lists, and it's over the 40kb limit. 
  Yes, a few viruses/spams make it to the list because they are smaller 
than 40kb, but trust me - it's _much_ fewer than the ones I have to deal 
with on the administrative requests page.  So increasing the limit 
beyond 40kb to allow larger patches to be submitted would also increase 
the number of spams/viruses that make it onto the list.  And I don't 
think anyone wants that.  :-)

-jh


--
_
This email message has been automatically encrypted using ROT-26.
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] daily tarballs no longer daily

[Jim Hall]

Bart Oldeman wrote:
Cron was disabled on SF, see
http://sourceforge.net/docman/display_doc.php?docid=2352&group_id=1
so the daily tarballs are no longer that (in fact the last one is from 
July 12). Somebody would have to manually update or run a cron job 
from an outside machine. Or just wait until SF sorts out the problem.

Well, that explains why the http://freedos.sourceforge.net/freedos.html 
mirror hasn't been working.  I had to manually run the update last night 
to re-sync it.

-jh
--
_
This email message has been automatically encrypted using ROT-26.
NOTE: I WILL BE AWAY FROM EMAIL (ON VACATION) AUG 6-24.
---
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] commit - UNSTABLE

[Jim Hall]

Jim Hall wrote:
Jeremy:
The [EMAIL PROTECTED] alias is still pointed at Bart.  Did you want me 
to change it to point to you?

-jh

Oops.  Maybe I should have sent that just to Jeremy & Bart.  :-)
-jh
--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] commit - UNSTABLE

[Jim Hall]

Jeremy:
The [EMAIL PROTECTED] alias is still pointed at Bart.  Did you want me 
to change it to point to you?

-jh
--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Kernel bug parade / moving on

[Jim Hall]

I think this kind of bug list would best appear on the 'FreeDOS @ 
SourceForge' page, since it directly relates to the kernel.

Eric: would you like me to add you to that project on SF so you can 
create/maintain this page yourself?

-jh
Eric Auer wrote:
Hi, while we have no real kernel maintainer right now (I assume Jeremy
can at most find enough time to upload patches submitted by others, not
for doing coding / testing himself), I think it would be good to review
some old bugs before we move on to do new optimizations. Of course now
that Arkady already has optimized things: If no new bugs get introduced
those patches can of course be added.
But I think we should focus on a bit of bug testing and fixing now for
a while. I hope there are people on the list who can test some of the
issues (i.e. have the affected type of software / hardware around!).
Bugzilla URLs all look like
http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=
where  is the number of the bug in question (no leading zeroes).
You can also use the http://www.europa.sp.nl/campagne2004/waakhond.shtml
page to get a list of all bugs (just select a "sort by" and submit the
form as-is) and http://www.freedos.org/bugs/bugzilla/ (just enter a bug
number - you actually can NOT enter search terms in the latter form!
Now for the bugs. If you are able to test a bug, please do so.
[...]
Maybe we could put a technote online with this list or something? Some of
the abovementioned bugs are very exotic, so we may have to "search the world"
for testers who can reproduce the described bug triggering conditions... and
most normal people will not read the whole bugzilla system when they find the
FreeDOS homepage and have a glance at the project status.

--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

[Freedos-kernel] Re: [announce] kernel 2035 and bye

[Jim Hall]

Bart,
Sad to see you go, but glad things ended on a good note.  If you & I are 
ever in the same area together, I'll definitely buy you a pint.  :)

-jh

Bart Oldeman wrote:
Hi,
I've uploaded kernel 2035 to
http://sourceforge.net/project/showfiles.php?group_id=5109
important fixes:
Fix problems with USBASPI.SYS, DI1000DD.SYS
Fixed invalid opcode with debug < foo.txt, same with netware redirected
logins.
Don't move the EBDA by default. Use switches=/e:-1 if you want the
auto-sized movement (#1771)
Made int21/ah=25,35 reentrant. Solves problem with Intel PRO/1000
driver.
Fix dir corruption bug if you delete the first entry in the root
directory on FAT32.
Fix non-working F5/F8 for autoexec.bat (#1777)
With this I'm leaving FreeDOS for the next couple of months at least. I
may put up an update for MEM but that's it. There was a bit of noise on
the mailing list but the main reason is that I'm generally happy about
the kernel, all I wanted in the beginning is to get it to cooperate
nicely with DOSEMU. That's done and more. Squeezing even more bytes out
of the kernel and fixing even more bugs is certainly possible, but it's
time to leave that to someone else as my (volunteer) job is finished.
Thanks for your attention and help,
Bart

--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Re: Reference compiler / changing the spec

[Jim Hall]

is it something like the bible, or should it be something
reflecting (intended) reality ?


I suggest that it describes reality, but that original intentions are
not removed but just marked as obsoleted.


I think, that a spec should describe the projects intention.
and it's certainly not the kernels intention to be compilable with any
compiler.
the intention is to build a MSDOS compatible kernel; use the
approriate tools (free if possible)
Yes.  See my other message in the original thread:

The original intent was to have the Spec reflect what people actually 
_use_ so that when a new developer comes into the project, he/she will 
know what tools to use when contributing to FreeDOS (such as OW for C 
compiler, etc.)

When the Spec was first written, no open tools (suitable for 16bit 
deployment) were available.  However, pretty much everyone on the 
FreeDOS lists had (or was already using) TurboC or Borland C, so TC/BC 
were listed as the standard.  Same thing for assembly, except that's 
changed now too.

I'll try to get all of fd-doc updated very soon now.  The Spec will be 
my first goal.

-jh

--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: Reference compiler (was Re: [Freedos-kernel] Re: patch: inthndlr.c)

[Jim Hall]

Steffen Kaiser wrote:
On Mon, 10 May 2004, Bart Oldeman wrote:


Hi Tom,


You don't remember correctly.
the kernel reference compiler has been for a long time TC 2.01 (which
is free), and has been changed to OW because it generates better
(smaller) code, and because it's free and open.
Aitor remembers correctly -- he simply goes a few years further back than
you and me. Before August '99 TC 2.01 couldn't be used. Watcom's been
used as reference since Feb 2002.


http://fd-doc.sourceforge.net/spec/spec.html
Section "Programming Tools To Be Used"
"Our reference standard for a C compiler will be Borland C 3.1. Our
reference standard for Assembly will be Microsoft MASM. Borland C 3.1 was
chosen as the reference standard because this is the compiler used to
build the FreeDOS kernel. Microsoft MASM was chosen as the reference
standard because of the free availability of MASM-compatible assemblers.
The existing code base was also a deciding factor in choosing a reference
standard."
How about to change the reference compiler not only for the kernel, but
for all the project?
There had been a movement from MASM to NASM already, so this can be
reflected here as well. This is missing some documentation as well, right?
It would be helpful to have some port MASM --> NASM document.
I know Jim can phrase the change of the reference tools so that Turbo C
becomes a backup-solution, not to be turned down immediately.
Arkady, how is your progress toward OW going? Did have you assembled a
Mini-DOS-OW development environment, for instance? I just unpacked any
ZIP, except that ones specifically marked as "Fortran".
Bye,



Oops.  I meant to go through and update the fd-doc site a while ago. 
There's even a note about something like that on the SF site.  The Spec 
is very out of date.  It should have been updated long ago.  I'm very 
embarrassed that I haven't done it yet.

I'll get back on this, and start updating the fd-doc site.  The original 
intent was to have the Spec reflect what people actually _use_ so that 
when a new developer comes into the project, he/she will know what tools 
to use when contributing to FreeDOS (such as OW for C compiler, etc.)

When the Spec was first written, no open tools (suitable for 16bit 
deployment) were available.  However, pretty much everyone on the 
FreeDOS lists had (or was already using) TurboC or Borland C, so TC/BC 
were listed as the standard.  Same thing for assembly, except that's 
changed now too.

-jh





--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] cvs refresh

[Jim Hall]

Arkady V.Belousov wrote:
Hi!

24-Апр-2004 17:05 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO> Date: Sat, 24 Apr 2004 17:05:18 +0100 (BST)

When latest patches will be reflected in CVS snapshot on site
(kernel.tgz?)? I wish to check how they are applied "in complete".
BO> every day at 10am GMT

 How GMT relates to UTC (which TZ)? I mean, how GMT relates to my MSK TZ
(which is currently +4 to UTC)?
Arkady:

Your time zone is GMT+0400.  So at 10am GMT, it is 2pm in your TZ.

-jh

--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Q: release files

[Jim Hall]

Arkady V.Belousov wrote:
Hi!

__O\_/_\_/O__
   [107]ke2034_16.zip 167372 0 i386 .zip
   [108]ke2034_32.zip 169797 0 i386 .zip
   [109]ke2034src.zip 426429 0 i386 Source .zip
_
  O/~\ /~\O
 Please, someone remind me, ke2034_16 is kernel for 8086+FAT32 or for
80386+FAT1x? Also, Bart, don' say "at usual place", always mention precise
URL to download.
BTW, I always include a link when this news gets posted on the 
FreeDOS.org web site.  If you don't remember how to find the new kernel, 
check the FreeDOS.org site and you should find a news item about it on 
the front page.

See  , or the news item alone at 


-jh

--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] patch: batch and make files (description)

[Jim Hall]

At least one of your emails was trapped by the SF mail system until I 
was able to free it this morning.  Emails may not be over 40k in length, 
or else they are held until the list owner (me) accepts or rejects them 
(a manual process.)

-jh



Arkady V.Belousov wrote:
Hi!

 [Don't know what happen, but SF silently ignores/losts my letters. B-E
Second day: one was saturday, second was today. Not funny. Below _repost_ of
my letter with new patch from today, monday.]
 New updates for my patches. Because I already remove intermediate
files, there present diff file not to my last patch, but to files, as
patched by Bart.
- buildall.bat, clean.bat: not all DELs was NULed.
- config.b: comment for NASM updated by request of Bernd. :)
- kernel\makefile: not all individual rules was present (asmsupt.asm), not
  all dependencies was present (eg, segs.inc for irqstack.asm).
- kernel\nls_load.c: removed.
PS: config.h also may be removed, because it is dummy (for this only
required to remove reference in globals.h). When (and if!) it will be
required, it may be added back.
PS2: kernel\nls\001-437.hc is desynced with kernel\nls_hc.asm.

PS3: header files in globals.h and init-mode.h included in different order.

PS4: repeat for my previous question: why to duplicate "clean" and
"clobber"? Another one: who make files status.me, *.cod, *.las?



--
_
This email message has been automatically encrypted using ROT-26.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] re: someone should check his system for a real VIRUS

[Jim Hall]

Eric Auer wrote:
Hi Tom, you are completely wrong about that virus. That it SEEMS
to come from Bart, Joe, MartinS, Brian, Jeremy, ... only means
that SOMEBODY is infected who knows all their addresses. Modern
viruses scan the system for addresses and randomly select one
address as target and another one as FAKE sender.
Yes, that is what Tom is saying.  Someone out there with all those 
addresses in his/her addressbook (or in IE browser cache) is sending 
MyDoom virus emails, and Tom is getting some of those.



By the way, QUESTION: On non-Intel chipsets, UMBPCI UMBs are often
not cached at all (i.e. not only write-through but completely uncached).
UMBPCI.txt recommends not to let Windows load performance-critical data
into UMBs for that reason.
[...]

BTW - it's really irritating to have a second, unrelated topic in these 
emails.  If the subject does not apply to me, I tend to skip over the 
thread.  So I might have missed your comments, which were tacked on the 
end of your reply to Tom.  I suspect there are other users who have 
skipped over this thread, and didn't see your comments at all.

Please do a courtesy and don't include lots of unrelated things in your 
emails.  It makes it harder to see them, and to reply to them.

-jh

--
Currently playing: DDR:Max2, SSX Tricky, Ratchet&Clank, Sly Cooper
Favorite DDR dance: "Break Down" (Be For U)
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] A virus???

[Jim Hall]

Eric Auer wrote:
Hi, did this virus REALLY make it on freedos-kernel?
Yuck. What a waste of bandwidth. We should really check
how to disable attachments (and html ;-)) on the lists
soon.
[got the usual mydoom scum probably through freedos-kernel]

The only email that's a virus on the list is the 'failure notice'.  But 
you'll notice it doesn't contain an attachment - it's a rejected email 
from ran-out.mx.develooper.com (and looks like a real rejection, not a 
faked one.)

-jh

--
Currently playing: DDR:Max2, SSX Tricky, Ratchet&Clank, Sly Cooper
Favorite DDR dance: "Break Down" (Be For U)
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Packing kernel with aPack saves 1.3 KB

[Jim Hall]

Patrick J. LoPresti wrote:
Luchezar Georgiev <[EMAIL PROTECTED]> writes:


I don't know really. If anyone is competent on licensing issues
(albeit not a lawyer) fell free to comment.


I am not a lawyer, but I think I understand this stuff reasonably
well.  I do not believe there is any incompatibility with the GPL.


Not quite.

The driving idea behind the GNU GPL is "copyleft".  From 
:

>>In the GNU project, our aim is to give all users the freedom to 
redistribute and change GNU software. If middlemen could strip off the 
freedom, we might have many users, but those users would not have 
freedom. So instead of putting GNU software in the public domain, we 
``copyleft'' it. Copyleft says that anyone who redistributes the 
software, with or without changes, must pass along the freedom to 
further copy and change it. Copyleft guarantees that every user has freedom.

And from the Preamble of the GNU GPL :

>> When we speak of free software, we are referring to freedom, not 
price. Our General Public Licenses are designed to make sure that you 
have the freedom to distribute copies of free software (and charge for 
this service if you wish), that you receive source code or can get it if 
you want it, that you can change the software or use pieces of it in new 
free programs; and that you know you can do these things.

>>To protect your rights, we need to make restrictions that forbid 
anyone to deny you these rights or to ask you to surrender the rights. 
These restrictions translate to certain responsibilities for you if you 
distribute copies of the software, or if you modify it.

>>For example, if you distribute copies of such a program, whether 
gratis or for a fee, you must give the recipients all the rights that 
you have. You must make sure that they, too, receive or can get the 
source code. And you must show them these terms so they know their rights.

And:

>>4.  You may not copy, modify, sublicense, or distribute the Program 
except as expressly provided under this License. Any attempt otherwise 
to copy, modify, sublicense or distribute the Program is void, and will 
automatically terminate your rights under this License. However, parties 
who have received copies, or rights, from you under this License will 
not have their licenses terminated so long as such parties remain in 
full compliance.



So from that, if packed binaries can be freely distributed for 
non-commercial purposes, but commercial use requires a separate license, 
then you have stripped away the freedoms of commercial entities.  Also, 
you have further required sub-licensing of the GNU GPL program, which is 
invalid.

As an example: One user (say, a home user - non-commercial use, so 
that's okay) distributes a copy of the FreeDOS kernel under the terms of 
the GNU GPL to a friend who wants to use it at work (say, to run a print 
system to generate for-sale banners and posters.)  If the kernel were 
aPack'd, now the friend at work has had his freedoms stripped away - he 
cannot use the software unless a separate license is obtained.



The GPL requires that if you distribute binaries, you must also
distribute the corresponding source code.  The GPL puts no further
restrictions on how those binaries themselves are distributed or
licensed.  For example, Red Hat Linux Enterprise Edition has a
restrictive license on its binaries (you have to buy one copy per
machine).  But the source code is still available because the GPL
requires it.


There are a few misconceptions here.

First, the GNU GPL does not require that you distribute the source code 
WITH the program you distribute.  It only requires that the source code 
be available upon request.  From the GNU GPL:

>>3.  You may copy and distribute the Program (or a work based on it, 
under Section 2) in object code or executable form under the terms of 
Sections 1 and 2 above provided that you also do one of the following:

>>* a) Accompany it with the complete corresponding 
machine-readable source code, which must be distributed under the terms 
of Sections 1 and 2 above on a medium customarily used for software 
interchange; or,

>>* b) Accompany it with a written offer, valid for at least three 
years, to give any third party, for a charge no more than your cost of 
physically performing source distribution, a complete machine-readable 
copy of the corresponding source code, to be distributed under the terms 
of Sections 1 and 2 above on a medium customarily used for software 
interchange; or,

>>* c) Accompany it with the information you received as to the 
offer to distribute corresponding source code. (This alternative is 
allowed only for noncommercial distribution and only if you received the 
program in object code or executable form with such an offer, in accord 
with Subsection b above.)

Of course, the safest (and preferred) way to distribute a GNU GPL 
program is to provide the source cod

Re: [Freedos-kernel] Packing kernel with aPack saves 1.3 KB

[Jim Hall]

Steve Gibson wrote:
Guys,

Don't know if this matters, but Joergen Ibsen (a.k.a. Jibz) seems to be 
a terrific guy and may be willing to do whatever the FreeDOS project 
might need license-wise.  Two days ago he made a custom modification to 
aPack for me ...
[...]
I imagine that he would enjoy having aPack being used as the compressor 
for your FreeDOS work, and perhaps he'd be willing to make an amendment 
to his license if that would help?

That sounds like a good idea.  We would need packed executables to be 
distributable under a GNU-friendly license.  For example: if no 
restrictions were placed on packed executables, that would be ideal.

I don't think it's right to ask for a special exception for FreeDOS 
programs packed with aPack.  These days, I'd guess that many of the DOS 
programs likely to be packed with aPack will be FreeDOS programs, or at 
least programs that will be booted on a FreeDOS kernel.  So the 
difficulty becomes in trying to distinguish the intention of an 
exception - if there's an exception for FreeDOS programs, does that mean 
only the programs listed on http://www.freedos.org/freedos/software/ or 
any program where the author intends it to be used on/with FreeDOS or 
any program where the user intents it to be used on/with FreeDOS?  That 
means Joergen needs to make a general change to his aPack license, and 
not a specific change.

Steve: you seem to have worked with Joergen before.  Perhaps you could 
email him, and start a discussion?  If needed, I am willing to be cc'd 
on the discussion, and I'll pitch in where necessary.

-jh

--
Currently playing: DDR:Max2, SSX Tricky, Ratchet&Clank, Sly Cooper
Favorite DDR dance: "Break Down" (Be For U)
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel

Re: [Freedos-kernel] Packing kernel with aPack saves 1.3 KB

[Jim Hall]

Luchezar Georgiev wrote:
On Sat, 31 Jan 2004 15:16:05 + (GMT), Bart Oldeman wrote:

I've now prepared the precompiled kernel binary (OpenWatcom 1.2, FAT32,
8086) in ROMDSK this way. (It always contains the latest CVS kernel.)
Last note: aPack-ed programs can be freely distributed for
non-commercial purposes, but otherwise require a license (the fee is $29
for individual users and $95 for companies, see
http://www.ibsensoftware.com/products_aPACK.html).


i'm a little worried about this -- this may be incompatible with the GPL!


I don't know really. If anyone is competent on licensing issues (albeit 
not a lawyer) fell free to comment. I'm not sure that even UPX is 
compatible with GPL, because its authors themselves violate it by 
REFUSING to publish the source code of the NRV ("Not Really Vanished") 
compression library!

Bart is right - this is incompatible with the GNU GPL, and cannot be 
used to pack the FreeDOS kernel (which is under the GNU GPL.)

-jh

--
Currently playing: DDR:Max2, SSX Tricky, Ratchet&Clank, Sly Cooper
Favorite DDR dance: "Break Down" (Be For U)
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel