Linux-Development-Sys Digest #671, Volume #6      Mon, 3 May 99 00:14:15 EDT

Contents:
  Re: serial port termios flag settings ("Sungmin Chun")
  Compiling and installing glibc-2.1 - success AT LAST! (Chris Rankin)
  Re: Q: Notification about termination of parent process. (Frank Sweetser)
  Re: Possible?: glibc-2 system and (old?) Motif libraries (Chris Rankin)
  Who owns the x86emu project? (Kendall Bennett)
  Re: /dev/hda1 has reached maximal mount count, check forced (Neil Rickert)
  Re: Is Linux Y2K compliant? (David Fox)
  CVS (Re: Bill Gates, self made man, NOT!) (Arun Sharma)
  Linux Real-Time I/O (Jim & Lisa Meils)
  Re: Help Installing Linux 5.2 on Dell PowerEdge SP 5166 (Hans Dumbrajs)
  Re: Linux driver ("new.ccu.edu.tw")
  Re: /dev/hda1 has reached maximal mount count, check forced (Paul J Gans)
  Linux + Laptops + APM + X = garbled screen (Arun Sharma)
  Re: [ANN] CodeWarrior for Red Hat Linux, GNU ed. Shipping ("G. Sumner Hayes")
  Re: Journaled Filesystem ("G. Sumner Hayes")
  Problems with serial link while reading or writing CDs (Manfred Lemke)
  Re: Linux system ID, is there such a thing? ("G. Sumner Hayes")
  Re: Help installing Red Hat 5.2 on Dell PowerEdge SP 5166 (Justin Young)
  Re: Linux system ID, is there such a thing? ("G. Sumner Hayes")

----------------------------------------------------------------------------

From: "Sungmin Chun" <[EMAIL PROTECTED]>
Subject: Re: serial port termios flag settings
Date: Mon, 26 Apr 1999 20:10:17 +0900

Hi, there.
I suggest that you should consider the big-/little-endian.
Characters in text file are only one byte. But there are
data with multiple bytes in binary files.

The x86-based(intel) PC is little-endian system. Almost other
platforms are big-endian system.


Scott Lanning <[EMAIL PROTECTED]>��(��) �Ʒ� �޽�����
news:7fng4q$gae$[EMAIL PROTECTED]�� �Խ��Ͽ����ϴ�.
> Hi,
> I'm making programs to transfer files from one PC to another by
> serial port. I was able to transfer text files, but not others
> (in particular, tarballed files). I think maybe I have the termios
> flags set incorrectly. Does anyone know what they should be?
> I have term.c_cflag = CS8|CREAD|CLOCAL. I thought that would
> do it, but...  (It's nothing crucial; I just couldn't get minicom
> to work on one of the PCs, and I wanted to transfer files from
> CD-ROM on that PC to harddisk of the other (CD-ROM-less) PC.)
>
> Any suggestions appreciated.
>
> Thanks,
> Scott



------------------------------

From: Chris Rankin <au.com.zipworld@{no.spam}rankinc>
Subject: Compiling and installing glibc-2.1 - success AT LAST!
Date: Sat, 01 May 1999 23:54:09 +1000

This message is for reference, and is aimed at anyone thinking of
upgrading to the glibc-2.1 library:

- egcs-1.1.2 and glibc-2.1 each seem to install their own (mutually
incompatible) versions of libio.h; glibc-2.1 puts its in /usr/include,
while egcs-1.1.2 puts its in /usr/include/g++. This effectively broke my
g++ compiler on every source file that included cstdio or iostreams.

- apmd-2.4 (power management daemon) - dratted thing has bad fork-code;
in my case it hung the boot procedure and forced me back on my rescue
disks. This was particularly difficult to track down because it happened
at the VERY END of the rc.local script and still managed to put all the
right messages in the logs. (Grrrr... DAYS of downtime!)

- my Vixie-cron daemon started creating Zombies. I have (to-date) solved
this by adding the USE_SIGCHLD #define (which isn't the
package-default).

- libXpm.so.4.11 library somehow needs the private _fxstat symbol from
libc.so.6, so that library needs recompiling from source.

There will probably be more, but anyway...

Chris.

------------------------------

From: Frank Sweetser <[EMAIL PROTECTED]>
Subject: Re: Q: Notification about termination of parent process.
Date: 01 May 1999 08:55:46 -0400

Nils Henrik Lorentzen <[EMAIL PROTECTED]> writes:

> Hi,
> 
> I am writing a GUI-program where I have
> a parent process that fork()s to create a sub-process.
> The GUI is run in the parent process. What I want is the
> subprocess to terminate, when the
> parent process dies (because of user pressing quit or ctrl-c or it
> segfaults
> or whatever). The way I currently do this is by in the
> subprocess regularly checking if getppid() == 1,
> but this is not a very elegant solution IMO.
> Does anyone know a better way to handle this ?

you could have the parent send sigusr1 to the child process when it exits.
might be a good idea to still poll for getppid == 1, though, in case of the
parent exiting ungracefully.

-- 
Frank Sweetser rasmusin at wpi.edu fsweetser at blee.net  | PGP key available
paramount.ind.wpi.edu RedHat 5.2 kernel 2.2.5        i586 | at public servers
Did you ever walk in a room and forget why you walked in?  I think that's
how dogs spend their lives.  --Sue Murphy

------------------------------

From: Chris Rankin <au.com.zipworld@{no.spam}rankinc>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Possible?: glibc-2 system and (old?) Motif libraries
Date: Sun, 02 May 1999 00:03:17 +1000

Remco van den Berg wrote:
> When I try to compile motif applications like Nedit I get linker errors
> of undefined references:
> 
> libXm.so: undefined reference to '_xstat'
>                                  '_fxstat'
>                                  '_Xsetlocale'

Hummm..
I don't know if this will work, but off the top of my head I can't see
why not:

Add these commands to the VERY END of your link line:

-lc /usr/lib/libc.a

Hopefully, this will cause your compiler to use libc.so for as much as
it can, and resort to the static archive for everything else. As I
understand it, the _fxstat symbol is private to the shared library but
must still be in the static archive somewhere.

Cheers,
Chris.

------------------------------

From: [EMAIL PROTECTED] (Kendall Bennett)
Subject: Who owns the x86emu project?
Date: Sun, 2 May 1999 14:16:51 -0500

Hi All,

I am trying to figure out who the author and/or current maintainer of the 
x86emu project is. The current DEC Alpah Milo sources (which don't appear 
to have been updated to 2.2 yet) include the x86emu library, which is 
used to run the BIOS on the ISA/PCI graphics controller to initialise it 
when the system boots. The emulator works on some cards, but it lacking 
lots of support code for 32-bit instructions in 16-bit code (ie: mov 
eax,ebx etc with the operand size prefix).

Anyway, I have had some great success so far on some graphics cards with 
this emulator, and I want to flesh it out and make it work on all 
graphics cards. When I am done, we will be able to use this emulator to 
bring up graphics cards on any system with an ISA/PCI/AGP bus, as well as 
use it to bring up secondary controllers on x86 systems that are not 
POST'ed by the BIOS. It could also be used by the Linux kernel on any 
processor to allow the VESA fbcon driver to safely make calls to the BIOS 
at runtime to do things such as change display modes and program the 
color palette.

However before I dive head first into this, I would like to find out 
where the absolute latest version of the sources are so I don't end up 
doing duplicate work. Also if there is a different, but more complete x86 
emulator library around, perhaps I should work with that instead.

Regards,

-- 

+----------------------------------------------------------------------+
|      SciTech Software - Building Truly Plug'n'Play Software!         |
+----------------------------------------------------------------------+
| Kendall Bennett          | To reply via email, remove nospam from    |
| Director of Engineering  | the reply to email address. Do NOT send   |
| SciTech Software, Inc.   | unsolicited commercial email!             |
| 505 Wall Street          | ftp  : ftp.scitechsoft.com                |
| Chico, CA 95928, USA     | www  : http://www.scitechsoft.com         |
+----------------------------------------------------------------------+

------------------------------

From: [EMAIL PROTECTED] (Neil Rickert)
Crossposted-To: comp.os.linux.hardware
Subject: Re: /dev/hda1 has reached maximal mount count, check forced
Date: 2 May 1999 13:18:26 -0500

Peter Mutsaers <[EMAIL PROTECTED]> writes:

>>> "SSK" == Stephen S Kerr <[EMAIL PROTECTED]> writes:

>    SSK> There's nothing to "fix".  This message is normal, and it's a good
>    SSK> thing.

>I've always found it very annoying and stupid.

>Why on earth would one check after a fixed amount of reboots?

Because there might be something broken.

>If it were after a specific period of time had elapsed it might make
>sense, but still. I know of no other UNIX doing this. If the shutdown
>left the filesystem clean there should be no reason to check,

I recently installed some Sun patches to a solaris system.  It left
the file system broken, but with the clean flag still set.  Normal
reboot did not fix it, since it noted the clean flag.  I had to
reboot from a CDROM to correct things.  On a second system, a power
failure forced the 'fsck, saving me the trouble of having to reboot
from CDROM.  I'm not sure why installing patches broke things (left
some lost directories around).  Perhaps it was because the patch
install replaced some dynamic link objects which were still active.


------------------------------

From: d s f o x @ c o g s c i . u c s d . e d u (David Fox)
Subject: Re: Is Linux Y2K compliant?
Date: 30 Apr 1999 13:22:35 -0700

[EMAIL PROTECTED] (Christopher B. Browne) writes:

> I would argue that the *true* constraint that mandated compression was
> the 72 or 80 columns on the typical punched card.  Many, many, many
> mainframe-based applications are designed around processing streams of
> data that are, in essence, virtual punched cards.

Indeed, the storage medium was often *actual* punched cards.  If your
records exceed the column limit you suddenly have to punch twice as
many cards and carry/store twice as many boxes.
-- 
David Fox           http://hci.ucsd.edu/dsf             xoF divaD
UCSD HCI Lab                                         baL ICH DSCU

------------------------------

Subject: CVS (Re: Bill Gates, self made man, NOT!)
From: Arun Sharma <[EMAIL PROTECTED]>
Date: Sat, 01 May 1999 16:26:37 GMT

"G. Sumner Hayes" <[EMAIL PROTECTED]> writes:

> 
> Linus really hates CVS because it messes with his way of doing
> business.  Bitkeeper is Larry Wall's attempt to make something that
> draws on his experience with Sun and SGI development tools and is
> conducive to the Linux development model.
> 

You mean Larry McVoy ? Larry has a comparision on his website. Apart
from that I don't know of anything negative about CVS. Some people
dislike it's tendency to "automerge" things etc.

        -Arun


------------------------------

From: Jim & Lisa Meils <[EMAIL PROTECTED]>
Subject: Linux Real-Time I/O
Date: Sun, 02 May 1999 17:38:11 -0500

I am a newbie to Linux, and have a somewhat simple question.  I have
written an increadibly simple I/O program for DOS using QBASIC, and
would like to write a similar program for Linux and possibly use the
timing and multitasking capabilities to dim lights with it.  Currently I
use the
parallel port for the output and control up to 8 light circuits.  What
is the best route to take with Linux?  Can Linux control in real-time
i.e. run a routine EXACTLY 120 times/sec ?

The current program simply writes a byte to the printer port, and the
port holds the value.  Each bit is connected(optically) to a light
circuit.  I know the Windows folks are trying to invade the real-time
I/O market to displace PLCs with Windows boxes.  Is there any work being
done in the Linux world to handle similar apps?  It seams a natural due
to it's reliability compared to Windows. The thing I need help on is how
to address the port and send data to it quickly.

Any help would be appreciated.
Thanks
Jim


------------------------------

From: Hans Dumbrajs <[EMAIL PROTECTED]>
Subject: Re: Help Installing Linux 5.2 on Dell PowerEdge SP 5166
Date: Sat, 01 May 1999 13:58:10 +0300

Leslie Smith wrote:

> Can help me out here, I have got a Dell PowerEdge server
> SP 5166 Dual CPU. I am trying to load linux 5.2 kernel
> with no joy. I can build the box with 5.0 but not with
> 5.1 or 5.2 boot disk. Dose anyone know of a fix for
> this.
>
> Regards
>
> Leslie...UK:-)
> =1A

Linux is at version 2.2.7 now.. So I guess this is the reason why you
can't install version 5.2


------------------------------

From: "new.ccu.edu.tw" <[EMAIL PROTECTED]>
Subject: Re: Linux driver
Date: Thu, 29 Apr 1999 08:23:51 +0800

>I've written a driver for a PCI card and have registered the symbols to
>\proc\ksym.  How would an application obtain these symbols?  Is it a
dynamic
>link to the driver functions?  Once I load my driver module, I do see the
>symbols in \proc\ksym.
>
>Thanks,
>


I don't think an user space application can use these symbols directly.
Normally, these exported symbols are to be used by other modules loading
to kernel. Maybe ioctl command is a better way.

J.C. Chuang




------------------------------

From: Paul J Gans <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: /dev/hda1 has reached maximal mount count, check forced
Date: 3 May 1999 01:51:16 GMT

In comp.os.linux.development.system Jens Kristian S�gaard <[EMAIL PROTECTED]> wrote:
>Peter Mutsaers <[EMAIL PROTECTED]> writes:

>> Why on earth would one check after a fixed amount of reboots?
>> If it were after a specific period of time had elapsed it might make
>> sense, but still. I know of no other UNIX doing this. If the shutdown

>I'm not completely sure, but I think Linux does both. I.e. checking
>after a fixed set of mounts, and after a fixed period of time. This is
>f.ex. a dump of one of my filesystem:

>       Last mount time:          Mon Apr  5 18:33:13 1999
>       Last write time:          Sun May  2 20:23:44 1999
>       Mount count:              4
>       Maximum mount count:      20
>       Last checked:             Sun Apr  4 04:11:56 1999
>       Check interval:           15552000 (6 months)
>       Next check after:         Fri Oct  1 04:11:56 199


>This means that if I remounted this filesystem on the 2nd of October,
>it would check the filesystem... even though it hasn't yet reached
>it's maximum mount count of 20.

This is true.  I've had ext2 floppies get the message that
the file system had not been checked for too long.  Useful
for floppies as they seem to develop problems with age.

      ----- Paul J. Gans  [[EMAIL PROTECTED]]

------------------------------

From: [EMAIL PROTECTED] (Arun Sharma)
Crossposted-To: comp.os.linux.x
Subject: Linux + Laptops + APM + X = garbled screen
Reply-To: [EMAIL PROTECTED]
Date: Mon, 03 May 1999 02:30:11 GMT

The subject says it all. When my laptop goes into hibernation and comes
back up, my screen is garbled. If I kill X and restart, everything is
fine.

Is anyone working on making X aware of power management ?  

        -Arun
  

------------------------------

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.unix.programmer
Subject: Re: [ANN] CodeWarrior for Red Hat Linux, GNU ed. Shipping
Date: Sun, 02 May 1999 22:30:44 -0400

[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] (MW Ron) writes:
> [snip]
> > CodeWarrior for Red Hat Linux, GNU Edition is now Shipping.
> [snip]
> 
> GNU Edition?  does that mean it's Free Software?  wow!

No, that means that it doesn't include a CodeWarrior compiler
but is just an IDE for use with egcs/gcc.  The professional
edition (due out in the fall) will include the Metrowerks
compilers and debuggers.

Personally, I still prefer a modern vi or emacs for productivity.

--Sumner

------------------------------

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Subject: Re: Journaled Filesystem
Date: Sun, 02 May 1999 22:43:01 -0400

Dara Hazeghi wrote:
> 
> Hello,
>     I was wondering if Linux will be getting a Journaled Filesystem
> anytime soon and if such a project is in the works (ext3?). 

As others have noted, Stephen Tweedie is working on journalling
extensions for ext2; they'll be released as part of the ext3 work once
2.3 gets underway.  The suggestion to read linux-kernel is good; the
linux-raid and linux-vfs lists also get a fair amount of traffic about
this.  Links to archives are available from www.linuxhq.com.

>  Although such a filesystem is inherently slower it certainly has 
> advantages in terms of reliability and integrity of data. 

It's not my area of expertise, but it may actually be faster for certain 
access patterns if I understand correctly.  Probably slightly slower in
the common case.

--Sumner

------------------------------

From: Manfred Lemke <[EMAIL PROTECTED]>
Subject: Problems with serial link while reading or writing CDs
Date: 29 Apr 1999 23:32:27 GMT

Hello folks!

I have a serious problem on my hand, which exists in kernel 2.2.6 and 2.2.7
at least,
possibly earlier:

When I try to read digital audio from an IDE CD-ROM in my system or try to
write
to an IDE CD-ROM writer, an ongoing PPP connection suddenly seems to slow
down almost to a standstill.

Hardware: Asus P5A
Writer: Yamaha 4416E
CD ROM: Teac 516-E

Running both on SCSI emulation Linux driver

Software:
Reading: cdda2wav 1.0b
Writing: cdrecord 1.8a21

I hope someone can help me!

Thanks in advance,

           Manfred Lemke ([EMAIL PROTECTED])

==================  Posted via SearchLinux  ==================
                  http://www.searchlinux.com

------------------------------

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Linux system ID, is there such a thing?
Date: Sun, 02 May 1999 22:47:16 -0400

"Jonathan A. Buzzard" wrote:
> In fact are stateful dongles practical? 
> What would happen if the software crashed leaving the dongle in some 
> unknown state?

IANAD

Presumably the first call at application startup is to reset the dongle
to some initial (known) state.  Later calls progress from there.  If
the app crashes, the next time it starts the dongle is reset.

--Sumner

------------------------------

From: [EMAIL PROTECTED] (Justin Young)
Subject: Re: Help installing Red Hat 5.2 on Dell PowerEdge SP 5166
Date: Sun, 02 May 1999 02:41:19 GMT

See my reply to your previous post.

Again, I believe the problem is the boot kernel on the RH boot floppy.

Compile a new one and copy it to the RH install disk.

Teehee.  This reminds me of the good old RH 4.1 days...


On 1 May 1999 13:35:52 +0100, [EMAIL PROTECTED] (Leslie Smith)
wrote:

>Can help me out here, I have got a Dell PowerEdge server
>SP 5166 Dual CPU. 
>
>I'm using Red Hat 5.2, when I am using the boot disk to boot
>the machine I only get three dot's then the machine stops dead,
>this also happens with Red Hat 5.1 too. I am able to load Red
>Hat 5.0 OK.
>
>Machine Spec:
>
>CPU = 2 x 166
>SCSI HD = 1 x 1GB
>         2 x 2GB
>          1 x 450GB
>MEM = 128MB
>Display = 1 x Vodoo 4MB
>
>REgards
>
>Leslie...UK:-)
>


------------------------------

From: "G. Sumner Hayes" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: Re: Linux system ID, is there such a thing?
Date: Sun, 02 May 1999 22:59:33 -0400

George MacDonald wrote:
> Yeah a determined hacker will bring down the most secure system, so 
                    ^^^^^^cracker
> you can only make it more difficult. It freaked me out the first time 
> I heard that someone with a scanner can listen to your cpu raidiating, 
> and people are worrying about chip serial numbers!

To be fair, every teenage cracker and his brother can launch software
attacks and go after network insecurities.  A Tempest attack (such as
you are describing) requires some fairly sophisticated equipment and is
less of a casual threat; it's not _that_ expensive, but it isn't
something that all of the script kiddies can abuse.  They also need
physical proximity.

IMO, a Tempest attack is still an espionage-level attack -- if you're
worried about Tempest, you should already know what you're doing and 
have secured the other areas I discussed.  It's certainly not the sort
of widespread concern as when major consumer e-mail clients allow
arbitrary investigation of files without any special equipment, IMO.

> I guess the only safe defense is to feed your data stream with 
> taggit's so you know who listening. Of course you can always give em 
> an earful now and again and see who gets freaked.

A Farraday cage around your machine (e.g. lining the walls with 
aluminum) can prevent Tempest attacks.  You'll need to make sure that 
external network connections are properly shielded so you don't get 
leaks there; fiber optics or other electromagnetically disconnected 
bridges are possibilities.

Also, if you aren't worried about attackers with the sophistication
and resources to log all of your RAM and CPU operations (possibly
beyond anyone's capabilities at current time) but only with reading
your monitor (the biggest source of em in a many modern machines), there 
has been some research into fonts that resist these attacks.  I think
it's still unknown how much they help against a determined attacker,
but as recent events show even the security of RSA is basically unknown.

Make sure you close your windows, or they'll just read over you
shoulders with binoculars.

--Sumner

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.development.system) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Development-System Digest
******************************

Reply via email to