Linux-Development-Sys Digest #27, Volume #7 Fri, 6 Aug 99 18:14:14 EDT
Contents:
Re: unique machine ID for Linux on ix86 platform? (Remco van den Berg)
Re: Graphics Library (not X) (Tristan Wibberley)
Re: patching 2.2.x kernels ("Steven J. Hill")
Re: Graphics Library (not X) (subvert)
SUSE 6.1 Permission differences between running a program from rc.d versus root
(Michael Samson)
Re: Network Driver Ioctl (Andi Kleen)
Re: unique machine ID for Linux on ix86 platform? ([EMAIL PROTECTED])
Re: Graphics Library (not X) (Torbjorn Tallroth)
Re: no-lilo problem (Horst von Brand)
Re: is there a book about the 2.2.x internals? (Andrew I Rothstein)
CLDD - a checkpointing disc driver (Allan Latham)
Re: The beginnings of a protected-mode boot loader (Konrad Mierendorff)
patching 2.2.x kernels ("x256")
Re: patching 2.2.x kernels (Paul Kimoto)
problems with new kernels on redhat 6.0 (Johan Kullstam)
Re: GCC byte alignment flag for structures (Torbjorn Tallroth)
GCC byte alignment flag for structures (Matthew Carl Schumaker)
Re: The beginnings of a protected-mode boot loader (H. Peter Anvin)
Re: Changing a driver from char to tty? (Chris Butler)
Re: patching 2.2.x kernels ("Robert B. Hamilton")
Re: no-lilo problem (H. Peter Anvin)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Remco van den Berg)
Subject: Re: unique machine ID for Linux on ix86 platform?
Date: 6 Aug 1999 16:15:26 GMT
On 06 Aug 1999 11:13:05 -0400, Robert Krawitz wrote:
>[EMAIL PROTECTED] (Remco van den Berg) writes:
>
>> We don't want to use our own computing resources. That's why I wanted
>> to port the application to Linux and put some protection in it.
>
>You're really asking a lot here: you want to restrict the application
>to certain machines (but not your own), you don't want to use a
>dongle, you don't want to trust your users.
Exactly, that was my question. And I think the answer is that it isn't
possible. Unlucky me...
Anyway, everybody thanks for the information,
- Remco van den Berg
============================================================================
Philips Semiconductors B.V. tel:(+31 40 27)22031 fax:22764 Room: BE-326
mailto:[EMAIL PROTECTED] seri: rvdberg@nlsce1
home Email: [EMAIL PROTECTED] (preferred for non-commercial mail)
============================================================================
Microsoft and Lotus Notes free. Don't send me any Microsoft attachments.
============================================================================
------------------------------
From: Tristan Wibberley <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.x
Subject: Re: Graphics Library (not X)
Date: Thu, 05 Aug 1999 16:25:44 +0100
Reply-To: [EMAIL PROTECTED]
JC wrote:
> I'm now interested to know how to program in graphics mode.
Have a look at LibGGI, you can find details at www.ggi-project.org
--
Tristan Wibberley
------------------------------
From: "Steven J. Hill" <[EMAIL PROTECTED]>
Subject: Re: patching 2.2.x kernels
Date: Fri, 06 Aug 1999 13:45:49 -0500
Based upon the size of the patch files from 2.2.5 through 2.2.10, I
would just download the 2.2.10 kernel. I'm lazy though too :)
-Steve
======================================================
Steven J. Hill
Diversified Software Industries, Inc.
625 South Gilbert Suite 2
Iowa City, IA 52240
E-mail: [EMAIL PROTECTED] URL: http://www.dsi-inc.net
Phone: (319) 337-2668 ext. 105
------------------------------
From: subvert <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.x
Subject: Re: Graphics Library (not X)
Date: Fri, 06 Aug 1999 13:43:06 -0500
Here is a snippet of code using libvga (also support svga). I am not
sure if this will work for you but here it is anyway. To compile: gcc
foo.c -o foo -lvga. To get it to do higher resolutions/color depth
you'll need to edit libvga.config in /etc/vga .... It is similar to the
X config file (although I could never get higher resolution because I
don't think my TNT2 is supported by svgalib...if I am wrong someone
please point me in the correct direction).
Also, I *do* remember BGI (Borland Graphics Interface)...It was sooo
cool...
#include <unistd.h>
#include <vga.h>
main()
{
if(vga_hasmode(G640x480x16))
{
vga_setmode(G640x480x16);
vga_setpalette(0,0,0,0);
vga_setpalette(1,0,0,53);
vga_setcolor(1);
vga_drawline(0,0, 639,479);
vga_waitevent(VGA_KEYEVENT | VGA_MOUSEEVENT, NULL,NULL,NULL,NULL);
vga_getkey();
}
}
JC wrote:
> Hello,
> This may probably sound stupid to most of you but
> I'm just a Linux newbie.
> So far, I've been programming console apps in Linux using
> gcc and cc.
> I'm now interested to know how to program in graphics mode.
> I don't know how to explain this but I used to program
> in DOS using Borland Turbo C, which has a (documented) graphics
> library. I'm sure some of you know what I'm talking about
> and have used it.
> I'm looking for an equivalent in gcc linux. (It doesn't have
> graphics.h does it?) I don't want to resort to assembly language
> since I know linux has a (documented) graphics library somehow.
>
> Please help me, I'd really appreciate it.
> Please email me. Thank you!
>
> JC
> [EMAIL PROTECTED]
>
> ------------------ Posted via CNET Linux Help ------------------
> http://www.searchlinux.com
------------------------------
From: Michael Samson <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc
Subject: SUSE 6.1 Permission differences between running a program from rc.d versus
root
Date: Fri, 06 Aug 1999 18:30:38 GMT
My problem occurs on SUSE 6.1 (and not on Redhat).
Are their any types of permission differences from running a program from
rc2.d as compared to running a program from the command line (while logged
in as root)?
I am having a cu /dev/modem "/var/lock/tmpfile" access problem when my
program runs during startup (from the rc2.d).
If I kill the program and run it manually when logged in as root, the cu
access problems disappear.
Does anybody have a clue to as what is going on?
Thanks,
Mike Samson
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: Andi Kleen <[EMAIL PROTECTED]>
Subject: Re: Network Driver Ioctl
Date: 06 Aug 1999 11:47:35 +0200
[EMAIL PROTECTED] writes:
> I am trying to implement ioctls with a network driver. However I am
> confused as to where the driver is. In order to find the file
> descriptor
> of a character devices one simply uses
> file =fopen("dev/foo","r");
> fd=fileno(file);
>
> and
>
> ioctl(fd,cmd,arg);
>
>
> but the network interface doesn't appear on the filesystem. what do i
> do?
You fetch man-pages-1.24 and read netdevice(7)
-Andi
--
This is like TV. I don't like TV.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: unique machine ID for Linux on ix86 platform?
Date: 5 Aug 1999 20:25:01 GMT
Stuart R. Fuller <[EMAIL PROTECTED]> wrote:
: No, the problem is that you are seeking a technical solution to a
: non-technical problem. The problem is that you are afraid that someone will
: attempt to run this software outside of Philips. The technical solution you
: are looking for is easily thwarted by someone who wants to do so. Ethernet
: address can be changed, and your solution now breaks. Even if there is a
: machine readable serial number, they can be changed to be whatever they need
: to be.
: Again, the problem is non-technical in nature, and will require a
: non-technical solution.
Not necessarily. In this case, there is a technical
solution to this problem. Restructure the software
so that most of it runs on a server which is suitably
secure and runs at Philips on a closed LAN. The only
part of the software that runs on the client is a
thin client interface to the software. Modulo some
security problems, you can give out copies of the client
side of the software to your users who then run it
on the closed LAN, and be fairly safe in the knowledge
that whatever marvellous IP is vested in the software
is Philips specific.
Rich.
PS. I'll verify the software for you: just mail me
a copy of it :-)
--
[EMAIL PROTECTED] | Free email for life at: http://www.postmaster.co.uk/
BiblioTech Ltd, Unit 2 Piper Centre, 50 Carnwath Road, London, SW6 3EG.
+44 171 384 6917 | Click here to play XRacer: http://xracer.annexia.org/
--- Original message content Copyright � 1999 Richard Jones ---
------------------------------
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.x
Date: Fri, 6 Aug 1999 18:48:53 +0200
From: Torbjorn Tallroth <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Graphics Library (not X)
On Fri, 6 Aug 1999, JC wrote:
> I'm now interested to know how to program in graphics mode.
Have a look at svgalib ("man svgalib").
--
tth
------------------------------
From: [EMAIL PROTECTED] (Horst von Brand)
Subject: Re: no-lilo problem
Date: 6 Aug 1999 00:15:44 GMT
On Wed, 04 Aug 1999 22:10:45 -0400, J. Escalante <[EMAIL PROTECTED]> wrote:
>Since I don't have any other OS than Linux Slackware running in my
>computer, what I want is not to have lilo at boot up time.
Not possible. The linux kernel can't boot by itself (too big), it needs some
helper to load it. This may be lilo, syslinux, grub, even ntldr or the
Partition Magic bootloader (the last two AFAIU). If you don't want lilo's
prompt, check the lilo configuration. OTOH, lilo allows you to select among
several linux configurations...
--
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vi�a del Mar, Chile +56 32 672616
------------------------------
From: [EMAIL PROTECTED] (Andrew I Rothstein)
Subject: Re: is there a book about the 2.2.x internals?
Date: 6 Aug 1999 17:13:09 GMT
Check out The Linux Kernel, version 0.8-3 by David A. Rusling available
off of sunsite.unc.edu/LDP in the Linux Documentation Project Guides.
Andrew
Arnoud de Geus ([EMAIL PROTECTED]) wrote:
: Hello,
: Is there a good book about the linux 2.2.x
: kernel internals (besides /usr/src/linux)?
: Greetings,
: [EMAIL PROTECTED]
--
Andrew I. Rothstein <[EMAIL PROTECTED]>
PGP: finger -l [EMAIL PROTECTED] ICQ: 4707090
"Can't this wait till I'm old? Can I live while I'm young?" -phish
"Nothing left to do but smile, smile, smile." -gd
------------------------------
From: Allan Latham <[EMAIL PROTECTED]>
Subject: CLDD - a checkpointing disc driver
Date: Fri, 06 Aug 1999 20:54:12 +0200
=====BEGIN PGP SIGNED MESSAGE=====
Any sysop who would like to experiment with a logical disc driver which
allows
snapshots of a real disc at fixed points in time might like to look at
my home
page.
One use of such a device is to allow backups to be taken of whole discs
while
still allowing the users to be logged on and working.
http://linux01.gwdg.de/~alatham
Any feedback most welcome - it is just an experimental project at this
stage.
Allan Latham
=====BEGIN PGP SIGNATURE=====
Version: PGPfreeware 6.0.2i
iQCVAwUBN6shMeJCY/+xqTOxAQHVfwP/TnWrCFVZsnHGQYofLnFqBbm6DFpw+SyF
NAfFD3NSNqlg/c5A2SfZ3JHkr9NiirGwQfCtmOUpSh3FVhb54kiyPlOQ7hj09lNs
SgjcRiNnUu8RarUczMW0iwdcVdKKiUKAu8lz2CsSGLxF9Q534V8URPCKCk0zSMBg
1RrfqEb9/CA=
=CFCe
=====END PGP SIGNATURE=====
------------------------------
From: Konrad Mierendorff <[EMAIL PROTECTED]>
Subject: Re: The beginnings of a protected-mode boot loader
Date: Fri, 06 Aug 1999 19:32:11 +0200
Etienne Lorrain wrote:
>
> Hi,
>
> "H. Peter Anvin" wrote:
> > Just for kicks, I uploaded the feeble beginnings of an ext2-reading
> > bootloader for Linux/i386 onto
> > ftp.zytor.com:/pub/linux/lbcon-0.01.tar.gz. This is far from
> > complete (in fact, it doesn't really do anything yet), but since there
> > was some talk about a boot loader using gcc to generate real-mode code
> > I thought I'd suggest an alternative.
> >
> > Right now, all this code does is bootstrap itself from an ext2
> > filesystem (using either the regular BIOS or -- if available -- the
> > ABIOS calls which don't have the 1024-cylinder limit),
>
> It is boring, I do not have extended disk BIOS but have IDE disks
> with more than 1024 cylinder, even bigger than 8 Gb...
But IMHO your kernel-image has to be below the 1024th cylinder
- Konrad Mierendorff
------------------------------
From: "x256" <[EMAIL PROTECTED]>
Subject: patching 2.2.x kernels
Date: Fri, 6 Aug 1999 20:02:03 +0200
hi
how can i upgrade my 2.2.5 kernel to 2.2.10 ? ( i have 'patch-2.2.6' - ... -
'patch-2.2.10' )
thx
------------------------------
From: [EMAIL PROTECTED] (Paul Kimoto)
Subject: Re: patching 2.2.x kernels
Date: 6 Aug 1999 16:06:04 -0500
Reply-To: [EMAIL PROTECTED]
In article <7of82o$h9q$[EMAIL PROTECTED]>, x256 wrote:
> how can i upgrade my 2.2.5 kernel to 2.2.10 ? ( i have 'patch-2.2.6' - ... -
> 'patch-2.2.10' )
This is described at about line 56 of the README file
(in the top-level kernel source directory).
--
Paul Kimoto <[EMAIL PROTECTED]>
------------------------------
From: Johan Kullstam <[EMAIL PROTECTED]>
Subject: problems with new kernels on redhat 6.0
Date: 06 Aug 1999 15:40:47 -0400
i am having trouble with new kernels on redhat 6.0.
my machine is a alr revolution quad6 (quad ppro-200) with 256M ram,
adaptec 2940uw scsi pci adapter and a 9.1G sca scsi fujitsu drive in
the swap bay.
i've been using fresh egcs and binutils as they've become available.
unless otherwise noted, all kernels are smp. disk i/o speed
measurements are done by bonnie.
redhat 5.2 with glibc-2.0 and glibc-2.1 worked fine with all kernels
from 2.1.124 through 2.2.9.
at that point i installed redhat 6.0. the stock redhat kernel works
fine. i wanted to compile my own kernel. i compile 2.2.5 with
aic7xxxx built into the monolith. i have only one module tulip.o (and
dummy.o but that isn't loaded as far as i can tell). since i put the
scsi driver in the kernel, i am not using initrd. my own compiled
2.2.5 kernel works fine. (after nuking ifup-aliases to shut up
kvetches about not finding lo:1-50 and eth0:1-50)
i upgrade to 2.2.6 and things are still good.
i go to 2.2.7 and my disk access gets *very slow*. running bonnie
shows that char-wise read/write is about 40K/sec (down from 3000K/sec
for working kernel). interestingly, block read/write is nearly the
same as a good kernel. there isn't any disk data corruption, just
slow access. disk access is similarly slow for all of 2.2.8, 2.2.9
and 2.2.10.
i note that the aic7xxx driver is *identitical* in both 2.2.6 and
2.2.7. very little changes wrt smp and disk or file system occur
between these versions.
dmesg looks the same for all the kernels. while some version number
change, there are no errors or warnings printed.
i tried out 2.2.10 in uniprocessor and get good disk performance.
i am suspicious of an irq conflict (this can cause slow modems) since
each scsi adapter and disk access is being punished by a fixed
amount (independent on the size of the data block being moved).
remember, kernel 2.2.7 and 2.2.9 worked fine before (with redhat 5.2
using both glibc-2.0 and glibc-2.1). i suspect something wacky is
happening during the boot sequence (since i can't figure out anything
else to blame).
watching the boot, i notice a slow down right after it talks about
entering run-level 3 and the init script starts its `daemon loading
ok' spew.
has anyone else got this or similar problem? has anyone managed to
fix it?
--
johan kullstam
------------------------------
Crossposted-To: comp.os.linux.development.apps
Date: Fri, 6 Aug 1999 22:51:15 +0200
From: Torbjorn Tallroth <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: GCC byte alignment flag for structures
On Fri, 6 Aug 1999, Matthew Carl Schumaker wrote:
> I'm haveing abit of a problem passing a data structure from a Linux
> machine to an NT machine, it turns out that the NT machine compiles the
> structure using 8 byte alignment while the Linux is using (2/4 ?) I've
> found a couple flags for gcc but they don't seem to change the structure
> size, Anybody know of the flag for this for gcc?
Change the NT machine to use 32 bit alignment instead.
--
tth
------------------------------
From: Matthew Carl Schumaker <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps
Subject: GCC byte alignment flag for structures
Date: Fri, 6 Aug 1999 14:58:58 -0400
I'm haveing abit of a problem passing a data structure from a Linux
machine to an NT machine, it turns out that the NT machine compiles the
structure using 8 byte alignment while the Linux is using (2/4 ?) I've
found a couple flags for gcc but they don't seem to change the structure
size, Anybody know of the flag for this for gcc?
thanks in advance
Matthew Carl Schumaker
UPAC Lights Administrative Chairperson
[EMAIL PROTECTED]
veni, vedi, velcro
I came, I saw, I stuck around
------------------------------
From: [EMAIL PROTECTED] (H. Peter Anvin)
Subject: Re: The beginnings of a protected-mode boot loader
Date: 6 Aug 1999 21:27:13 GMT
Reply-To: [EMAIL PROTECTED] (H. Peter Anvin)
Followup to: <[EMAIL PROTECTED]>
By author: Konrad Mierendorff <[EMAIL PROTECTED]>
In newsgroup: comp.os.linux.development.system
> >
> > It is boring, I do not have extended disk BIOS but have IDE disks
> > with more than 1024 cylinder, even bigger than 8 Gb...
>
> But IMHO your kernel-image has to be below the 1024th cylinder
>
Yes, if you don't have EBIOS then you need to keep all of /boot below
cylinder 1024. lbcon will use EBIOS if it is present, but if it
isn't, there just ain't anything to do.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
------------------------------
From: [EMAIL PROTECTED] (Chris Butler)
Subject: Re: Changing a driver from char to tty?
Date: 5 Aug 1999 22:56:29 +0100
[comp.os.linux.development.system - Tue, 3 Aug 1999 13:28:11 GMT] * Marcus wrote *
> I�m working on a tty driver. I have a char driver that works for
> the card. But I need to make it a tty to be able to use it with ppp. But
> now that I have changed the things I think should be enough, the kernel
> tries to get a NULL pointer when I open the device (fd = open(deviceName,
> O_RDWR ). I haven�t changed the open function except for replacing
> the inode to a tty as argument. I use the same routine to open the device
> in both cases.
> the Oops looks like this if that is any help:
It's no help to us, but it is to you :)
Run it through ksymoops (in the scripts directory of the source, and as a
package if you use Debian).
That'll resolve all of the numeric addresses to function names using the
data in System.map.
--
Chris Butler
<[EMAIL PROTECTED]>
------------------------------
From: "Robert B. Hamilton" <[EMAIL PROTECTED]>
Subject: Re: patching 2.2.x kernels
Date: Fri, 6 Aug 1999 14:57:56 -0500
Reply-To: "Robert B. Hamilton" <[EMAIL PROTECTED]>
On Fri, 6 Aug 1999, x256 wrote:
> hi
> how can i upgrade my 2.2.5 kernel to 2.2.10 ? ( i have 'patch-2.2.6' - ... -
> 'patch-2.2.10' )
Hi.
The easiest way to patch the kernel:
1) make sure you have pristine source for 2.2.5 in /usr/src/linux,
2) change the working directory to your directory containing the patches,
3) then run the script /usr/src/linux/patch-kernel without arguments.
(you can also supply the source directory and patch directory as
the first and second args to patch-kernel)
Since you asked "how do I upgrade", instead of just "how do I patch",
I'll take opportunity to add a couple of helpful steps.
Very important:
4) read carefully /usr/src/linux/README, which gives
instructions for compiling and installing the kernel,
and even more important:
5) read /usr/src/linux/Documentation/Changes to find out
if you need to upgrade any utilities.
For any particular driver you are using, it would also
be a good idea to look for more info about it in
/usr/src/linux/Documentation/
------------------------------
From: [EMAIL PROTECTED] (H. Peter Anvin)
Subject: Re: no-lilo problem
Date: 6 Aug 1999 21:25:47 GMT
Reply-To: [EMAIL PROTECTED] (H. Peter Anvin)
Followup to: <[EMAIL PROTECTED]>
By author: Konrad Mierendorff <[EMAIL PROTECTED]>
In newsgroup: comp.os.linux.development.system
>
> Joe Pfeiffer wrote:
> > You have to have LILO. A bit more precisely, you have to have a boot
> > loader -- something sitting in the boot sector that tells the machine
> > how to load the OS. The normal boot loader for Linux is LILO.
>
> I'm wondering if it's possible to "dd" the kernel-image, like it is
> possible on floppy disks.
>
That works only for floppy disks. On anything but floppies you need
LILO, LOADLIN, or SYSLINUX.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
------------------------------
** 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
******************************
