HECnet

hecnet@lists.dfupdate.se

15589 discussions

User mode DECnet (was Multinet Tunnel Connections to SG1::)

by bqt＠softjar.se

On 2012-06-07 18:18, Bob Armstrong wrote: I was meaning as in non-root. Ah, well, but that's good because it means kernel hacks are not required. Right. Basically, you need to interface to ethernet. That you do the same way as my bridge, for instance. All the rest is just massaging the data in the packet, and eventually passing data to the next higher/lower level. The one semi-sensitive thing is that there are timers that needs to be kept, and things that needs to happen at times. But I think they all have such tolerances that you will be good even running it all in userland. Johnny

13 years, 8 months

Size of HECnet

by bqt＠softjar.se

On 2012-06-07 18:11, Kari Uusim ki wrote: On 7.6.2012 5:05, Joe Ferraro wrote: On Wed, Jun 6, 2012 at 7:13 PM, Sampsa Laine <sampsa at mac.com <mailto:sampsa at mac.com>> wrote: I've got a Windows NT 4.0 VM up occasionally too.. Sampsa boy that gives me bad memories of long days ... perhaps you should've gone for NT 3.50 while you were at it... I do have a Win 3.11 box running... perhaps there's a decnet stack for it?!!? There is a DECnet stack for DOS and Windows in the Pathworks V5 or V6 client kit. Those versions were meant to be used on Windows'es before Windows NT4. Then the Pathworks32 kit was released and that could be used on WNT4.0 and Windows 2000. Maybe on XP as well. Don't remember for sure. Some pretty recent version of Pathworks32 works on Windows XP anyway. Johnny

13 years, 8 months

User mode DECnet (was Multinet Tunnel Connections to SG1::)

by bob＠jfcl.com

I was meaning as in non-root. Ah, well, but that's good because it means kernel hacks are not required. Bob

13 years, 8 months

Size of HECnet

by uusimaki＠exdecfinland.org

On 7.6.2012 5:05, Joe Ferraro wrote: On Wed, Jun 6, 2012 at 7:13 PM, Sampsa Laine <sampsa at mac.com <mailto:sampsa at mac.com>> wrote: I've got a Windows NT 4.0 VM up occasionally too.. Sampsa boy that gives me bad memories of long days ... perhaps you should've gone for NT 3.50 while you were at it... I do have a Win 3.11 box running... perhaps there's a decnet stack for it?!!? There is a DECnet stack for DOS and Windows in the Pathworks V5 or V6 client kit. Those versions were meant to be used on Windows'es before Windows NT4. Then the Pathworks32 kit was released and that could be used on WNT4.0 and Windows 2000. Maybe on XP as well. Don't remember for sure.

13 years, 8 months

New bridge.c feedback

by bqt＠softjar.se

On 2012-06-07 17:53, Marc Chametzky wrote: Marc, are you sure ? It means that the assignment gets evaluated as a boolean expression?? Yes... you've got "port == DPORT" with two equal signs. That's not an assignment. That is going to evaluate to see whether it's true or false. Since DPORT = 0 by default, then it's evaluating "port == 0" which is true, thus its value is 1. So, you've got a statement which is: 1; Essentially, it's a no-op. With DPORT = 0, it doesn't make any difference, save for a compiler warning. If you were to set DPORT to some other number, though, the assignment wouldn't take place as would otherwise be expected. The assignment never took place, as it should have, since there was no assignment. If you changed DPORT to something else, you'd just get a if (port == 0) 0; which is just as meaningless as the result of DPORT was set to 0, which gave if (port == 0) 1; Johnny

13 years, 8 months

New bridge.c feedback

by bqt＠softjar.se

On 2012-06-07 17:50, hvlems at zonnet.nl wrote: Marc, are you sure ? It means that the assignment gets evaluated as a boolean expression?? No, he's right. The *original* code (not what I wrote further down), is (was): if (port == 0) port == DPORT; Johnny -----Original Message----- From: Marc Chametzky<marc at bluevine.net> Sender: owner-hecnet at Update.UU.SE Date: Thu, 07 Jun 2012 11:44:31 To:<hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] New bridge.c feedback 1171 cc: WARNING File = bridge.c, Line = 684 The indicated expression has no effect. if (port == 0) port == DPORT; ^ Apart from putting in a conditional? DPORT is a constant that I intended for users that compile to be able to change, if they want to. By default is't zero, thus the compiler sees: if (port == 0) port = 0; No, that's not what the compiler is seeing. Instead, it's seeing this: if (port == 0) 1; That's because you have "port == DPORT" (a conditional, not an assignment statement). which is pretty meaningless, and thus something to warn about. But how should I change the code to avoid that? I could (of course) add a check to the if, but that makes it look more complicated, and silly. Oh well, checking if DPORT have been defined to something non-zero is a pretty reasonable solution I think. --Marc

13 years, 8 months

New bridge.c feedback

by bqt＠softjar.se

On 2012-06-07 17:44, Marc Chametzky wrote: 1171 cc: WARNING File = bridge.c, Line = 684 The indicated expression has no effect. if (port == 0) port == DPORT; ^ Apart from putting in a conditional? DPORT is a constant that I intended for users that compile to be able to change, if they want to. By default is't zero, thus the compiler sees: if (port == 0) port = 0; No, that's not what the compiler is seeing. Instead, it's seeing this: if (port == 0) 1; That's because you have "port == DPORT" (a conditional, not an assignment statement). Jeeeez. When the f* did that sneak in there??? I'm way too tired today (obviously). That was totally meaningless. (Maybe just my brain, knowing what it should say just managed to ignore that extra equal sign.) Thanks for pointing out the obvious. Fixed now. Johnny

13 years, 8 months

New bridge.c feedback

by marc＠bluevine.net

Marc, are you sure ? It means that the assignment gets evaluated as a boolean expression?? Yes... you've got "port == DPORT" with two equal signs. That's not an assignment. That is going to evaluate to see whether it's true or false. Since DPORT = 0 by default, then it's evaluating "port == 0" which is true, thus its value is 1. So, you've got a statement which is: 1; Essentially, it's a no-op. With DPORT = 0, it doesn't make any difference, save for a compiler warning. If you were to set DPORT to some other number, though, the assignment wouldn't take place as would otherwise be expected. --Marc

13 years, 8 months

New bridge.c feedback

by hvlems＠zonnet.nl

Marc, are you sure ? It means that the assignment gets evaluated as a boolean expression?? -----Original Message----- From: Marc Chametzky <marc at bluevine.net> Sender: owner-hecnet at Update.UU.SE Date: Thu, 07 Jun 2012 11:44:31 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] New bridge.c feedback 1171 cc: WARNING File = bridge.c, Line = 684 The indicated expression has no effect. if (port == 0) port == DPORT; ^ Apart from putting in a conditional? DPORT is a constant that I intended for users that compile to be able to change, if they want to. By default is't zero, thus the compiler sees: if (port == 0) port = 0; No, that's not what the compiler is seeing. Instead, it's seeing this: if (port == 0) 1; That's because you have "port == DPORT" (a conditional, not an assignment statement). which is pretty meaningless, and thus something to warn about. But how should I change the code to avoid that? I could (of course) add a check to the if, but that makes it look more complicated, and silly. Oh well, checking if DPORT have been defined to something non-zero is a pretty reasonable solution I think. --Marc

13 years, 8 months

New bridge.c feedback

by hvlems＠zonnet.nl

Wouldn't an #ifndef DPORT statement solve that? Hans (And I'm an algol programmer, not very well versed in C magic ;-) ------Origineel bericht------ Van: Johnny Billquist Afzender: owner-hecnet at Update.UU.SE Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] New bridge.c feedback Verzonden: 7 juni 2012 17:18 On 2012-06-07 16:32, Marc Chametzky wrote: cc-1171 cc: WARNING File = bridge.c, Line = 684 The indicated expression has no effect. if (port == 0) port == DPORT; ^ Blech! Well, DPORT is by default set to 0. See the documentation of the define in the sources... This one will stay. I saw your second message about putting this in a conditional, but out of curiosity, why wouldn't you want to fix it? You don't have an assignment statement here, so if you do define DPORT, it won't take effect the way you want with the code like this. Apart from putting in a conditional? DPORT is a constant that I intended for users that compile to be able to change, if they want to. By default is't zero, thus the compiler sees: if (port == 0) port = 0; which is pretty meaningless, and thus something to warn about. But how should I change the code to avoid that? I could (of course) add a check to the if, but that makes it look more complicated, and silly. Oh well, checking if DPORT have been defined to something non-zero is a pretty reasonable solution I think. Johnny

13 years, 8 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet