chuckp@ncr-fc.FtCollins.NCR.com (Chuck Phillips) (01/11/90)
When I installed the 2.2 version of USENET elm on our Sun 3s, Sun 4s, and 386i's there was a problem with the 386i not correctly reading the 'compiled' version of alias files produced by the 3s and 4s and vice versa. (The 3s and 4s produced files were interchangeable.) I *assume* this is due to byte-ordering differences (or padding, perhaps?). Has this been fixed? Thanks, -- Chuck Phillips -- chuckp%bach.ncr-fc.FtCollins.NCR.COM
syd@DSI.COM (Syd Weinstein) (01/12/90)
chuckp@ncr-fc.FtCollins.NCR.com (Chuck Phillips) writes: >When I installed the 2.2 version of USENET elm on our Sun 3s, Sun 4s, and >386i's there was a problem with the 386i not correctly reading the 'compiled' >version of alias files produced by the 3s and 4s and vice versa. (The 3s and >4s produced files were interchangeable.) I *assume* this is due to >byte-ordering differences (or padding, perhaps?). Has this been fixed? You are correct, it is due to the byte ordering of the file being different (actually its in native mode for each machine, rather than in network byte order) In 2.3, a new feature has been added to allow the file to be in network order if NFS is present on the machine. There is no current work around for 2.2 to this problem. -- ===================================================================== Sydney S. Weinstein, CDP, CCP Elm Coordinator Datacomp Systems, Inc. Voice: (215) 947-9900 syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235