Linux-Development-Sys Digest #663, Volume #7 Wed, 8 Mar 00 18:13:17 EST
Contents:
Re: Why a file system ? ("Peter T. Breuer")
Question about long dates (Andre Charbonneau)
Re: Tape Driver EOF ("anonymous")
Re: Installing glibc (Please Help!) (Martin Wackenhut)
Re: Installing glibc (Please Help!) (Andreas Jaeger)
Re: Lexmark1100 printer driver for 2.2.12-20 ("Joao")
writing a module to implement a firewall ([EMAIL PROTECTED])
Re: Impasse with 2 SCSI controllers, kernel mods required? (Marc SCHAEFER)
Linkable executables? (Brian Chin)
Re: Tape Driver EOF (Jamey Kirby)
pci questions (Russell Suter)
Questions on kernel code (Jon Becker)
Re: Questions on kernel code (Alexander Viro)
Re: Creating VB RAD Style Application to Linux (Chris J/#6)
Re: Struct size and allocate problem! need help. ("Anthony W. Youngman")
----------------------------------------------------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Why a file system ?
Date: 8 Mar 2000 16:02:25 GMT
d wrote:
: You are right, a database would be a big improvement over the current
: organization. Consider that in a Unix heirarchical file system each
: file is identified by a pathname. In database parlance, this is an
: ordered collection of boolean attributes. In a system designed in the
: `database style' those attributes would be unordered, and the file
: /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/cc1
: would be the same file as
: /gcc-lib/egcs-2.91.66/lib/i386-redhat-linux/usr/cc1
Well, one is its primary key, and the other is a secondary key or
perhaps a query. There is nothing to stop you changing "cd" to something
which looks up all possible perms of the path components. Of course,
you have to change mkdir, too, to stop ypu making two distinct
directories with overlapping sets of components.
peter
------------------------------
Date: Wed, 08 Mar 2000 11:39:11 -0800
From: Andre Charbonneau <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development
Subject: Question about long dates
Hello,
I've been looking at l10n stuff under Linux and I'm a bit confused about
date and time localization. In system locale source files there are
fields to specify the following:
- d_t_fmt : The 'concatenated' date and time format
- d_fmt : the date format
- t_fmt : the time format
- t_fmt_ampm : the time format in am/pm style
When you look at the above, there is nothing related to 'short' or
'long' date. You either display the date in short format (by setting
d_fmt to "%y/%m/%d"), or in a long format (by setting d_fmt to "%a %d %b
%Y"). To my understanding (and correct me if I'm wrong), either the
system is set to display a date in a short way, or it is set to display
a date in a long way, but not both at the same time. For example, if
d_fmt is set in a 'short' style, then to display a long date you would
have to use the following call:
strftime(buf, "%a %d %b %Y",...);
Does this means that in Linux, there is no such thing as a 'long' date
or 'short' date? Therefore, it depends on the application who calls the
strftime function to determine if it needs a date formatted in a way
other than the one offered by the current locale setting?
Any clarifications would be appreciated,
Thanks,
--
Andre Charbonneau
Software Engineer
Corel Corporation
728-0826 x5612
------------------------------
From: "anonymous" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.apps,comp.os.ms-windows.programmer.nt.kernel-mode,comp.unix.programmer,microsoft.public.win32.programmer.kernel
Subject: Re: Tape Driver EOF
Date: Thu, 9 Mar 2000 00:42:23 +0800
Hi,
As title above,
I'm facing problem integrating storage on tape drive NT and Unix,
my application data is written into the tape from NT 4.0, then it is read by
the the same type of tape drive on Unix OS.
On Unix, we are using the "dd" command to read/write to the tape, and
On NT4.0, we are using the tape driver API.
However, the problem is that the Unix "dd" cannot find the EOF marker
and continue to read through the files until physical tape-end.
What is the EOF code that should be wrote to the tape in order for the Unix
application
recognize it ? or any other step I have missed ?
Thank in advance
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dear Spammer : Whatever reason is - no junk mail.
For auto email retrieve program, some free email for u.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
------------------------------
From: Martin Wackenhut <[EMAIL PROTECTED]>
Subject: Re: Installing glibc (Please Help!)
Date: Wed, 08 Mar 2000 18:13:03 +0100
Thomas Zajic wrote:
>
> On 08 Mar 2000 08:13:44 +0100, Andreas Jaeger wrote:
>
> > >>>>> Nix writes:
> >
> > Nix> Andreas Jaeger <[EMAIL PROTECTED]> writes:
> > >> The glibc comes with enough documention already. Please read the FAQ,
> > >> INSTALL and README files.
> >
> > Nix> Is there some kind of tailored virus or something in the glibc that
> > Nix> prevents all those who try to build it from reading its FAQ?
> >
> > [ ... ]
> >
> > Any idea what we can do about this? Shall I stop writing FAQ entries
> > since nobody (except the two of us;-) reads them?
> ^^^
> Make that three, and no, don't stop. ;-)
>
> > I do like the conspiracy theory.;-)
>
> See headers. ;-)
>
> Thomas
It's not the FAQ.
If I would install it on my running system there would be no problem.
Greetings
> --
> =-------------------------------------------------------------------------=
> - Thomas "ZlatkO" Zajic <[EMAIL PROTECTED]> Linux-2.0.38/slrn-0.9.6.2 -
> - "It is not easy to cut through a human head with a hacksaw." (M. C.) -
> =-------------------------------------------------------------------------=
------------------------------
From: Andreas Jaeger <[EMAIL PROTECTED]>
Subject: Re: Installing glibc (Please Help!)
Date: 08 Mar 2000 18:51:52 +0100
>>>>> Martin Wackenhut writes:
Martin> It's not the FAQ.
Might be in the INSTALL or README document? ;-)
Martin> If I would install it on my running system there would be no problem.
Then tell us what's exactly what your problem is - and what you need
besides install_root (documented in the INSTALL document)?
Andreas
--
Andreas Jaeger
SuSE Labs [EMAIL PROTECTED]
private [EMAIL PROTECTED]
------------------------------
From: "Joao" <[EMAIL PROTECTED]>
Subject: Re: Lexmark1100 printer driver for 2.2.12-20
Date: Wed, 8 Mar 2000 18:58:01 +0200
kiwa macey <[EMAIL PROTECTED]> schreef in artikel
<89sard$717$[EMAIL PROTECTED]>...
> I have just started learning linux on my home computer and was unable to
> find any printer drivers for my Lexmark 1100 el'cheapo printer.
>
> I was wondering if anyone knows of anywhere or anything that will do the
> job??
>
>
>
Try a search for 'lm1100' at http://www.freshmeat.net . This program works
for 300x300 color and B/W on Lexmark 1100/1000 series..
Greets joey
------------------------------
From: [EMAIL PROTECTED]
Subject: writing a module to implement a firewall
Date: Wed, 08 Mar 2000 19:10:25 +0200
Hi
i am trying to write some sort of a packet filter/firewall for linux.
I am running RH6.1
i have tried doing so using dev_add_pack and register my handling
function.
I do get the chance to see both incoming and outgoing packets,
however, i can only alter incoming packets.
looking at the kernel source showed me that the packet i get on the
incoming side (sent to me by dev_queue_xmit_nit) are only a clone, and
i have no way of returning an answer about any changes i have made to
the packet.
can any help me take control over outgoing packets ?
10x
Hilik
------------------------------
From: Marc SCHAEFER <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup,alt.os.linux.caldera
Subject: Re: Impasse with 2 SCSI controllers, kernel mods required?
Date: 8 Mar 2000 14:35:58 GMT
In comp.os.linux.development.system teri <[EMAIL PROTECTED]> wrote:
: Kernel recompile, this time with no 1542CF driver built-in. It is now
: impossible to load the driver (Device or resource busy). I have read
Any message issued by the dmesg command ? if it says something like
`cannot allocate IRQ', reserve that IRQ in the PCI/PNP BIOS
configuration as used by ISA/Legacy.
------------------------------
From: Brian Chin <[EMAIL PROTECTED]>
Subject: Linkable executables?
Date: Wed, 08 Mar 2000 22:41:00 -0800
I was wondering if there currently is anyway that you can create a .so
which can be executed, or an executable which can be linked to.
Basically, I want a program which will work one way, but other programs
can link and use procedures from inside it. Is this possible, and if
not, is there an alternative (other than splitting the executable into
to files), or is there something I can work on to make it possible?
------------------------------
From: [EMAIL PROTECTED] (Jamey Kirby)
Crossposted-To:
comp.os.linux.development.apps,comp.os.ms-windows.programmer.nt.kernel-mode,comp.unix.programmer,microsoft.public.win32.programmer.kernel
Subject: Re: Tape Driver EOF
Date: Wed, 08 Mar 2000 18:41:39 GMT
There should be an EOD written to the tape by the drive.
Are you using marks? If so, are you using setmarks or filemarks?
Jamey Kirby
[EMAIL PROTECTED]
On Thu, 9 Mar 2000 00:42:23 +0800, "anonymous" <[EMAIL PROTECTED]>
wrote:
>
>Hi,
>
>As title above,
>
>I'm facing problem integrating storage on tape drive NT and Unix,
>my application data is written into the tape from NT 4.0, then it is read by
>the the same type of tape drive on Unix OS.
>
>On Unix, we are using the "dd" command to read/write to the tape, and
>On NT4.0, we are using the tape driver API.
>
>However, the problem is that the Unix "dd" cannot find the EOF marker
>and continue to read through the files until physical tape-end.
>
>What is the EOF code that should be wrote to the tape in order for the Unix
>application
>recognize it ? or any other step I have missed ?
>
>Thank in advance
>
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Dear Spammer : Whatever reason is - no junk mail.
>For auto email retrieve program, some free email for u.
>[EMAIL PROTECTED]
>[EMAIL PROTECTED]
>[EMAIL PROTECTED]
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>
>
>
------------------------------
From: Russell Suter <[EMAIL PROTECTED]>
Subject: pci questions
Date: Wed, 08 Mar 2000 14:46:07 -0700
Hey,
Is there any documentation on the pci driver in the 2.2.* kernel? And, I'm
curious what's the difference between the sibling and next in the pci_dev
struct?
TIA
--
Russ
------------------------------
From: [EMAIL PROTECTED] (Jon Becker)
Subject: Questions on kernel code
Date: 8 Mar 2000 21:44:47 GMT
I'm a newbie to the Linux kernel, so please forgive me if these are
silly or obvious questions. Also, please let me know if there's a
better newsgroup in which I can pose general questions about the
operation of the kernel. These questions are based on the 2.2.14
kernel.
1) Is the task array really necessary? I can see how it's maintained,
how it interacts with task structs, and how tarray_freelist is
maintained. However, I don't see how the task array is really useful.
Any time the kernel needs to index over all tasks, it just uses the
task list itself (via for_each_task).
Such an array could be useful for mapping a task index to the task
struct itself. However this mapping seems to be done rarely, except
for the idle task, which could be handled using a single global
instead of an array for all tasks.
Additionally, it is used to associate a unique number with each task
(its index in the array). But couldn't such a mapping be done without
having the overhead of the task array? (Yeah, I know it's only 2K,
but it also requires a little extra time in various places to maintain
it correctly.) Perhaps the answer is no, since quickly finding a new
unallocated task number will require something similar to
tarray_freelist anyway, but I'd like to know for sure.
2) There is a comment in sched.c which indicates that the scheduler
cannot be called at interrupt time. And indeed one of the first
things done in schedule() is to check and make sure it's not running
in an interrupt context. However, I have a problem with this for two
reasons: first, I don't see how the code bears this out; second, if
the scheduler cannot be called at interrupt time then I don't see how
timesharing can be guaranteed.
As to the first, when an interrupt occurs it invokes a handler and
then bottom halves are run. Then the code jumps to ret_from_intr
(assuming the 386 version). This tests to see whether the code being
returned to was in user mode when the interrupt came in. If so, it
checks to see if the current task has its need_resched flag set. If
so, it calls schedule().
So if a timer interrupt comes in, then it will be handled, which among
other things activates the TIMER_BH bottom half. That bottom half
will then be run, which sets the current task's need_resched flag if
its quantum has expired. Then it'll go to ret_from_intr. Why does
this not result in schedule() being called?
As for timesharing, if schedule can't be called at interrupt time,
then it can only be done when the current task goes into kernel mode
(right?). What if the current task is sitting in an infinite loop
that doesn't involve any system calls? The need_resched will be set
when a timer interrupt comes in., but how can schedule() be called to
kick out the current task?
Now obviously my analysis is incorrect, since things really do work.
But I'd like someone to explain what I got wrong.
Thanks for any help you can give.
-Jon
------------------------------
From: [EMAIL PROTECTED] (Alexander Viro)
Subject: Re: Questions on kernel code
Date: 8 Mar 2000 17:18:07 -0500
In article <8a6hkf$e4r$[EMAIL PROTECTED]>,
Jon Becker <[EMAIL PROTECTED]> wrote:
>So if a timer interrupt comes in, then it will be handled, which among
>other things activates the TIMER_BH bottom half. That bottom half
>will then be run, which sets the current task's need_resched flag if
>its quantum has expired. Then it'll go to ret_from_intr. Why does
>this not result in schedule() being called?
It does. However, at that moment you are not within the interrupt - you
are in the glue, heading out of the kernel. The critical thing about
schedule() is that _all_ code in the upper half is guaranteed that no context
switches will happen unless we explicitly ask for them. Control may be
taken out (interrupt may happen and bottom half code will be executed),
but it will return to the same process. If you are heading to the user
mode - that's it, we can call schedule() without breaking this warranty.
>As for timesharing, if schedule can't be called at interrupt time,
>then it can only be done when the current task goes into kernel mode
>(right?). What if the current task is sitting in an infinite loop
>that doesn't involve any system calls? The need_resched will be set
>when a timer interrupt comes in., but how can schedule() be called to
>kick out the current task?
See above.
>Now obviously my analysis is incorrect, since things really do work.
>But I'd like someone to explain what I got wrong.
>Thanks for any help you can give.
Take the Daemon Book - the things you are asking are not Linux-specific,
it's generic UNIX stuff. Read it ("4.4BSD Design and Implementation") -
it's well-written and in the basic areas like that our kernels are pretty
close.
--
"You're one of those condescending Unix computer users!"
"Here's a nickel, kid. Get yourself a better computer" - Dilbert.
------------------------------
From: [EMAIL PROTECTED] (Chris J/#6)
Subject: Re: Creating VB RAD Style Application to Linux
Date: 8 Mar 2000 21:57:19 -0000
Reply-To: [EMAIL PROTECTED]
IIRC, Borland are porting Delphi, C++ Builder and J-Builder to Linux...in
fact I have a copy of J-Builder Foundation right here in front of me. Once
I get Sun's JDK 1.2 working, I'll be able to get the thing to install as
well. :)
Chris...
In article <8a0f7b$fk8$[EMAIL PROTECTED]>, EiNet <[EMAIL PROTECTED]> wrote:
>Hi dear Linux Developers,
>
>I come from MS Windows and when I started long time ago we can only develop
>to windows with complicated languages like C. And there were not so much
>developers for MS Windows. Then one day Microsoft had the great idea of
>developing a really simple environment using a easy to understand and low
>learning curve language called Visual Basic.
>
--
@}-,'-------------------------------------------------- Chris Johnson --'-{@
/ "(it is) crucial that we learn the difference / [EMAIL PROTECTED] \
/ between Sex and Gender. Therein lies the key / \
/ to our freedom" -- LB / www.nccnet.co.uk/~sixie \
------------------------------
From: "Anthony W. Youngman" <[EMAIL PROTECTED]>
Crossposted-To:
alt.os.linux,comp.os.linux.development.apps,comp.unix.sco.misc,comp.unix.sco.programmer,comp.unix.unixware.misc,tw.bbs.comp.linux
Subject: Re: Struct size and allocate problem! need help.
Date: Tue, 7 Mar 2000 00:13:51 +0000
Reply-To: "Anthony W. Youngman" <[EMAIL PROTECTED]>
In article <8a10um$i8qui$[EMAIL PROTECTED]>, Scott Lurndal
<[EMAIL PROTECTED]> writes
>In article <[EMAIL PROTECTED]>, "Jaron" <[EMAIL PROTECTED]>
>writes:
>|> ThankX all for suggestions.
>|>
>|> At this point. what I worry about is the portability ?
>|> Because I want this program works for many UNIX environment like
>|> SCO UNIX, UnixWare, UNIX SVR4.2 and Linux...
>
>For Unixware, Solaris, SVR4.* and Linux - look at
>
>$ man -k xdr
>
>for information about external-data-representation (as used by
>SUN RPC).
>
>No structure definition will be binary compatible between
>dissimilar architectures (e.g. mips vs. ia32 vs. sparc vs. alpha),
>so XDR was developed to provide an architecture independent data
>representation. 'tis a bit verbose, but useful.
>
>Alternative to xdr is simply to use ISO-8859-1 octets
>to represent the data (and convert back to binary with the
>appropriate conversion function - e.g. strtoul, strtod, et. al.)
>
I do something similar ...
But. I assume the reason you need it to be 10 bytes is because you're
writing to a file? Just create two macros. The first takes a 10-byte
buffer and loads your structure. The second takes your structure and
loads the 10-byte buffer. Makes it slightly more long-winded, but the
result is that your program is optimised for speed - the structure is at
its most optimum form, and yet your file layout is constant. NB - if
you're doing that, use functions like ntohs and htons etc on your
integers. One, it makes debugging a damn sight easier if your file is
little-endian, and secondly it means files are portable between
different-endian computers.
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
Trousers with a single hole in their waistband are topologically equivalent
to a doughnut. These sugarcoated trousers have yet to catch on at fast-food
outlets! (SuperStrings by F. David Peat)
------------------------------
** 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
******************************
