Linux-Development-Sys Digest #336, Volume #6     Wed, 27 Jan 99 08:14:09 EST

Contents:
  Re: Kernel 2.2 Stable Problem with RealTek 8129/8139 ethernet  (Tim Moore)
  KERNEL PANIC! on 2.2.0 final (Ricardo Manuel Pacheco Salgado)
  Re: xosview and 2.2.0 (Lars Hofhansl)
  Re: sendmail-8.9.2 claims that "seteuid" is broken - True? (Villy Kruse)
  Re: Why I'm dumping Linux, going back to Windblows (Peter Samuelson)
  Re: how the future of Linux will go (John Cumming)
  Re: 2.2.0-final  <->  2.2.0 can't compile new kernel!! (bill davidsen)
  Re: 2.2.0-final  <->  2.2.0 can't compile new kernel!! (Michael Powe)
  Re: Internal PCI modem (Peter Samuelson)
  Re: Why I'm dumping Linux, going back to Windblows (Christopher Browne)
  Re: how the future of Linux will go (Christopher Browne)
  Linux 2.2.0 final won't compile. (Mark Swanson)
  Root RAID different from Boot RAID? and other RAID issues (A James Lewis)
  Re: PROPOSAL: comp.unix.year-2038 (WAS: 2038 and Linux) (Bloody Viking)

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

Date: Wed, 27 Jan 1999 00:42:21 -0800
From: Tim Moore <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux.networking,comp.os.linux.setup,comp.os.linux.misc,comp.os.linux.development,comp.os.linux.help
Subject: Re: Kernel 2.2 Stable Problem with RealTek 8129/8139 ethernet 

Haven't compiled yet but remember seeing a suggestion to use something
besides xconfig.  Or just manually set the config to =m or =y.

Several upgrade guides on http://www.linuxhq.com/
-- 
[Replies: remove the dot(s)]

"Everything is permitted.  Nothing is forbidden."
                                   WS Burroughs.

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

From: [EMAIL PROTECTED] (Ricardo Manuel Pacheco Salgado)
Subject: KERNEL PANIC! on 2.2.0 final
Date: 27 Jan 1999 00:23:30 GMT

I'm getting kernel panics every time I want use callback on ISDN subsystem 

What's wrong? Is it a bug?

Using driver for PCBIT-D as module.
version 2.2.0 final. Also occurs on v2.1, but not on v2.0.

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

From: Lars Hofhansl <[EMAIL PROTECTED]>
Subject: Re: xosview and 2.2.0
Date: Wed, 27 Jan 1999 10:46:48 +0100

Andreas Heiss wrote:
> 
> Hi folks,
> I just installed 2.2.0 final.
> When running xosview, I see strange network traffic all time.
> The 'netmeter' doesn't work at all. Real network traffic isn't displayed.
> I guess, the reason are the changes in the /proc.
> But how can I fix it ? /proc backward compatibilty is enabled in the
> kernel config.
> 
> Andreas
> 

Hi,

may I suggest the documentation that comes with the kernel source?!
Especially the changes file. xosview is explicitly mentioned there.

Cheers,

        Lars

-- 
Legal Warning: Anyone sending me unsolicited/commercial email
WILL be charged a $100 proof-reading fee. See US Code Title 47,
Sec.227(a)(2)(B), Sec.227(b)(1)(C) and Sec.227(b)(3)(C).
Linux grows, see http://counter.li.org/ and register.


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

From: [EMAIL PROTECTED] (Villy Kruse)
Subject: Re: sendmail-8.9.2 claims that "seteuid" is broken - True?
Date: 27 Jan 1999 09:48:01 +0100

In article <pK_q2.2484$[EMAIL PROTECTED]>,
Chris Rankin  <net.bellsouth@{no.spam}rankinc> wrote:
>Mike Dowling wrote:
>> What error messages do you get?
>> 
>> $ll /usr/sbin/sendmail
>> -r-sr-xr-x   1 root     mem        291420 Jan  4 15:16 /usr/sbin/sendmail
>> 
>> It installs correctly for me.
>
>It's not an error message; it's a comment in the src/conf.h file. If you
>examine the configuration options you will see that sendmail for Linux
>doesn't use the "seteuid" system call because it claims that it's
>broken. If this is true then it would be good to fix before 2.2.0 is
>released.
>
>Chris.

Anyone run the test program to verify that seteuid is still broken?

This program should (or used to) be part of the standard sendmail source
distribution.


Villy

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

From: [EMAIL PROTECTED] (Peter Samuelson)
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Date: 26 Jan 1999 18:15:33 -0600
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>

  [Gordon Scott]
> > Hm, files (on x86s anyway) are limited to 2Gb -- memory might also
> > be.  I don't think it'll be *too* long before a 64bit system
> > addresses that -- there are already a few protests at the 2Gb file
> > limit.
[Todd Ostermeier <[EMAIL PROTECTED]>]
> This is probably way off topic, but

This is actually much more on-topic than most of the "Why I'm dumping
Linux, doing back to Windblows" thead....

> why is that?  32 bit pointers w/ signed magnitude?  (effectively, 31
> bits of addressable memory space)

For files, I think you're right.  The lseek() system call takes a
32-bit signed integer for its argument, since it's possible to use
negative offsets in SEEK_CUR ("seek from current position") mode.

For process address space: x86 before (I think) Pentium Pro has a 4GB
address space.  (PPro/PII can have 36-bit addressing, or 16GB of
addressing, but Linux doesn't use it.)  This space in Linux is divided
into virtual memory and running-process address space.  The default is
a 2GB-2GB split, so that any single process can have 2GB of address
space, as can the system as a whole.

If you want more virtual memory you can change the split to 3GB-1GB in
some header file somewhere in the kernel tree.  Then any single process
can only be 1GB big.

> I'm assuming here that we're talking about 32-bit x86 architectures.

Yes.  64-bit architectures can have both larger files and larger
address spaces.  64-bit file sizes for 32-bit arch's is rumored to be
in the works for Linux 2.3.x.

-- 
Peter Samuelson
<sampo.creighton.edu!psamuels>

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

From: John Cumming <[EMAIL PROTECTED]>
Subject: Re: how the future of Linux will go
Date: Wed, 27 Jan 1999 10:05:27 +0000

steve mcadams wrote:

> I was somewhat concerned after reading Halloween I because it
> (correctly, it seems to me) pointed out that Linux development is
> interest-based.
>
> That is, people don't work on Linux for money (primarily anyway), so
> if it gets boring, they'll go off and work on something else.

Well I develop on Linux, we develop high end financial systems for stock
markets on Linux and deliver via the web on our own  internet based linux
servers. Linux is a fantastic system for commercial development and I am
sure it is only going to gain in popularity as people realise its both
cheap and stable as well as on par with commercial unices in most
important areas................But perhaps I should read the rest of your
messgae first ;-)

>
> Frankly this makes sense to me, and since I'm just getting involved
> with my latest adventure in computing (ie, Linux) I'd really prefer
> not to see it get boring enough that developers drift away.
>
> What also occurred to me is that I have been seeing quite a few
> threads in the past couple weeks about making Linux a really
> competitive system from an installability / usability perspective, in
> addition to its already robust server personna.
>
> I think there's a shift in interest already, and as a result, a shift
> in the people who are going to be most active in Linux development in
> the future.
>
> So I'm going to put on my Nostradamus hat and make a prediction and
> see what level of flames it draws.
>
> My prediction is as follows, (1) there will be fairly massive
> development efforts within the next 6 months that will result in a new
> Linux distribution that is more installable than MS platforms,

What's wrong with Redhat and Suse at present, they offer far better
install routines than MS software. IMHO

> (2) we
> are going to see more GUI toolkits and RAD GUI-Builders on Linux
> within the next year, and

Possibly, but most commercial developers that I know, probably wouldn't
use GUI builders, but would rather stick with a decent text editor.

As for more GUI toolkits:

Qt (and KDE) (commercially available for windows)
Gtk (and Gtk++ C++ wrappers)
wxWindows (for Unix _AND_ MSwindows)
motif (OK it's commercial - but standard)
lesstif (but this isn't)
Tk
Xaw (in its various forms - Xaw, Xaw95, Xaw3d, neXtaw.....and probably
more)

I'm sure there are many more I've not mentioned...........PLEASE NO MORE
GUI TOOLKITS!


> (3) some of this functionality will make its
> way into all the standard distributions and the kernel itself within
> the next 18 months.  -steve

Install routines and GUI toolkits in the kernel ...... EH????

>
> --------------------------------------------------------
> so what?  -  http://www.codetools.com/showcase

--

==================================================================
John Cumming
Senior Software Engineer, Innovative Software Ltd
==================================================================
Innovative Software Ltd         tel: +44 (0)1242 545080
1 Crescent Terrace              fax: +44 (0)1242 545081
Cheltenham
Gloucestershire
United Kingdom                  http://www.innovative-software.com
==================================================================




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

From: [EMAIL PROTECTED] (bill davidsen)
Subject: Re: 2.2.0-final  <->  2.2.0 can't compile new kernel!!
Date: 27 Jan 1999 00:56:54 GMT

In article <[EMAIL PROTECTED]>,
Michael Powe  <[EMAIL PROTECTED]> wrote:

| I got exactly this error trying to build tonight.  I compiled
| 2.2.0-pre8 w/o problem, but using the same config I tried the new
| 2.2.0 and I got the linker error at the same place.

We have had both a patch and advice to build as a module. I will add
that whenever I get a new version, bu download or patch, before doing
the build I do a 'make menuconfig' even if I don't change anything.
There seem to be cases where it is or isn't needed, but I do it as a
matter of faith, and it has eliminated some similar problems.

Of course with a new version I always do a make dep and clean before
starting, builds don't take that long (at least on my machines they
don't).

-- 
  bill davidsen <[EMAIL PROTECTED]>  CTO, TMR Associates, Inc
"Too soon we grow old, and too late we grow smart" -Arthur Godfrey


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

Subject: Re: 2.2.0-final  <->  2.2.0 can't compile new kernel!!
From: Michael Powe <[EMAIL PROTECTED]>
Date: 27 Jan 1999 03:52:56 -0800

=====BEGIN PGP SIGNED MESSAGE=====
Hash: SHA1

>>>>> "Eric" == Eric Valette <[EMAIL PROTECTED]> writes:

>>>>> "Michael" == Michael Powe <[EMAIL PROTECTED]> writes:
    Michael> However, I did not use the same config file, I remade
    Michael> mine from scratch -- twice, to make sure that the first
    Michael> time wasn't a fluke.

    Eric> This patch fixes the problem

Okay, I finally got around to applying the patch.  I got an error --
first 'hunk' succeeded, second 'hunk' failed.  However, I recompiled
and the compile worked.  Installed the new kernel et voil�� -- sound.

Linux trollope 2.2.0 #1 Wed Jan 27 03:05:18 PST 1999 i586 unknown

Thanks again for the help.

mp

8<---------------how-easy-is-it-to-demunge-an-address?------------------->8
#! /usr/bin/perl # if you are [EMAIL PROTECTED] (Another Luser):
while ($line = <>){ if ($line =~ m/^\s*$/ ){ last; }
if ($line =~ m/^From: (\S+) \(([^()]*)\)/){ $from_address = $1; } }
if ($from_address =~ m/\S+NOSPAM\S+/){ $x = index($from_address, NOSPAM);
substr($from_address, $x, 6+1) = ""; printf("The real address is %s\n",
$from_address);}else { printf("No munge, just plain %s\n",$from_address);}
printf("\nBrought to you by the Truth In Mail Headers Foundation\n");
8<-----------------------here's-one-example------------------------------>8

- --
                             Michael Powe
            [EMAIL PROTECTED]   http://www.trollope.org
                         Portland, Oregon USA

=====BEGIN PGP SIGNATURE=====
Version: GnuPG v0.9.0 (GNU/Linux)
Comment: Encrypted with Mailcrypt 3.5.1 and GNU Privacy Guard

iD8DBQE2rv3q755rgEMD+T8RAqxfAJ41ea0CYy9Gd/cl/YaTmF11v95W6wCgk00V
VW8pZiA4+6Ra7WzBsh6129Y=
=UPHo
=====END PGP SIGNATURE=====

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

From: [EMAIL PROTECTED] (Peter Samuelson)
Crossposted-To: comp.os.linux.setup
Subject: Re: Internal PCI modem
Date: 26 Jan 1999 19:36:18 -0600
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>

[Rod Roark <[EMAIL PROTECTED]>]
> Most PCI modems don't work with Linux.  Send it back.  External is
> best, but many ISA models are OK (don't get one that lists MS Windows
> as a requirement,

The other day a friend of mine asked my advice on buying a modem.
Number one rule, I said, don't get a Winmodem.  OK, he said.  At the
store, he tells the guy: say, this looks like a good deal ... this
better not be a Winmodem.  Store guy said no, it's a regular one.
Turns out it's PCI and Win98 reports a Winmodem.

My friend was pissed.  The box didn't say anything except for the fine
print that it didn't work with Win3.1 (I guess that is supposed to tip
you off) and of course the brand is something you've never heard of.  I
assume the salesman was just stupid, not malicious, but next time I'm
at that particular store I am *not* trusting anything they say....

-- 
Peter Samuelson
<sampo.creighton.edu!psamuels>

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

From: [EMAIL PROTECTED] (Christopher Browne)
Crossposted-To: alt.os.linux,comp.os.linux.development.apps,comp.os.linux.setup
Subject: Re: Why I'm dumping Linux, going back to Windblows
Reply-To: [EMAIL PROTECTED]
Date: Wed, 27 Jan 1999 01:59:43 GMT

On Tue, 26 Jan 1999 16:06:57 -0600, Todd Ostermeier
<[EMAIL PROTECTED]> wrote: 
>On 25 Jan 1999, Gordon Scott wrote:
>
>: Hm, files (on x86s anyway) are limited to 2Gb -- memory might also be.
>: I don't think it'll be *too* long before a 64bit system addresses that --
>: there are already a few protests at the 2Gb file limit.
>
>This is probably way off topic, but why is that?  32 bit pointers w/
>signed magnitude?  (effectively, 31 bits of addressable memory space)

There are protests because there are databases out there that are larger
than 2GB in size.  (I work with one database at work that, today, is
57GB in size.)

The average *disk* sold these days is larger than 2GB, after all, and
ext2fs supports partition sizes of on the order of 2TB, so limiting file
size to 2GB seems a mite unreasonable. 
-- 
"I've discovered that P=NP, but the proof is too long to fit within the
confines of this signature..."
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/lsf.html>

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

From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: how the future of Linux will go
Reply-To: [EMAIL PROTECTED]
Date: Wed, 27 Jan 1999 01:59:46 GMT

On Tue, 26 Jan 1999 23:08:45 GMT, steve mcadams <[EMAIL PROTECTED]>
wrote: 
>I was somewhat concerned after reading Halloween I because it
>(correctly, it seems to me) pointed out that Linux development is
>interest-based.
>
>That is, people don't work on Linux for money (primarily anyway), so
>if it gets boring, they'll go off and work on something else.
>
>Frankly this makes sense to me, and since I'm just getting involved
>with my latest adventure in computing (ie, Linux) I'd really prefer
>not to see it get boring enough that developers drift away.

What is liable to happen is *not* simply that "developers drift away."

More likely is that there will be an overall shift in *interests.* There
will be application areas that will attract new developers.  And others
that will shed developers, supposing more intereting things come along.

>What also occurred to me is that I have been seeing quite a few
>threads in the past couple weeks about making Linux a really
>competitive system from an installability / usability perspective, in
>addition to its already robust server personna.
>
>I think there's a shift in interest already, and as a result, a shift
>in the people who are going to be most active in Linux development in
>the future.
>
>So I'm going to put on my Nostradamus hat and make a prediction and
>see what level of flames it draws.
>
>My prediction is as follows, (1) there will be fairly massive
>development efforts within the next 6 months that will result in a new
>Linux distribution that is more installable than MS platforms

Isn't this already true :-).

>(2) we are going to see more GUI toolkits and RAD GUI-Builders on
>Linux within the next year

Whoever can come up with a GUI Builder that is about equivalent in
functionality to Microsoft Access will "become king." 

A commercial package that costs $100 and provides a combination form
builder / report writer / database access tool that can be used by
relatively unsophisticated folk to build moderately sophisticated apps,
ala Access, has the potential to do very well.  Since they'll be able to
avoid the robustness problems by starting with a real DB from the word
"go," the issues will be of usability and keeping the GUI robust. 

See: <http://www.hex.net/~cbbrowne/framewrk.html> for some thoughts.

The problem with this area is that there will be mass rejection and
flamage of non-free choices.  Debian will reject such.  Red Hat may
reject such.  SuSE won't.  In any case, this sort of package, unless
"libre," won't be able to be shipped with the $2 CDs. 

>(3) some of this functionality will make its way into all the standard
>distributions and the kernel itself within the next 18 months.  -steve

Neither GUI nor installation have very much to do with the kernel, so I
don't expect there to be effects there from what you describe.

The critical question is whether or not there is anyone working on such
"application framework" stuff in conjunction with GNOME or KDE.  

Both have some bits of report-writer stuff on the go, but both are thus
far oriented towards basic infrastructure, and haven't yet *really*
started making powerful scripting tools, which is probably the way to
build really dynamic GUIed applications. 

-- 
"I've discovered that P=NP, but the proof is too long to fit within the
confines of this signature..."
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/lsf.html>

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

From: Mark Swanson <[EMAIL PROTECTED]>
Subject: Linux 2.2.0 final won't compile.
Date: Wed, 27 Jan 1999 03:45:48 GMT

The error I get is:

net/network.a(sock_n_syms.o)(__ksymtab+0x288): undefined reference to
`csum_part
ial'
net/network.a(core.o): In function `csum_partial_copy_fromiovecend':
core.o(.text+0x17db): undefined reference to `csum_partial'
core.o(.text+0x181d): undefined reference to `csum_partial'
core.o(.text+0x189c): undefined reference to `csum_partial_copy_generic'

net/network.a(ipv4.o): In function `ip_fw_masquerade':
ipv4.o(.text+0xdba): undefined reference to `csum_partial'
ipv4.o(.text+0xdd5): undefined reference to `csum_partial'
ipv4.o(.text+0x105d): undefined reference to `csum_partial'
ipv4.o(.text+0x10a5): undefined reference to `csum_partial'
ipv4.o(.text+0x1115): undefined reference to `csum_partial'
net/network.a(ipv4.o)(.text+0x1333): more undefined references to
`csum_partial'
 follow
net/network.a(ipv4.o): In function `ip_reply_glue_bits':
ipv4.o(.text+0x9796): undefined reference to `csum_partial_copy_generic'

ipv4.o(.text+0x97c1): undefined reference to `csum_partial_copy_generic'

net/network.a(ipv4.o): In function `tcp_do_sendmsg':
ipv4.o(.text+0xb3a4): undefined reference to `csum_partial'
ipv4.o(.text+0xb422): undefined reference to `csum_partial_copy_generic'

ipv4.o(.text+0xb65b): undefined reference to `csum_partial_copy_generic'

net/network.a(ipv4.o): In function `tcp_fragment':
ipv4.o(.text+0xf5c1): undefined reference to `csum_partial'
net/network.a(ipv4.o): In function `tcp_retrans_try_collapse':
ipv4.o(.text+0xf9d2): undefined reference to `csum_partial'
net/network.a(ipv4.o): In function `tcp_v4_send_check':
ipv4.o(.text+0x125b3): undefined reference to `csum_partial'
net/network.a(ipv4.o): In function `tcp_v4_send_synack':
ipv4.o(.text+0x12a34): undefined reference to `csum_partial'
net/network.a(ipv4.o): In function `tcp_v4_rcv':
ipv4.o(.text+0x1367b): undefined reference to `csum_partial'
net/network.a(ipv4.o)(.text+0x150e0): more undefined references to
`csum_partial
' follow
/mnt/usr/src/linux/arch/i386/lib/lib.a(old-checksum.o): In function
`csum_partia
l_copy':
old-checksum.o(.text+0x2e): undefined reference to
`csum_partial_copy_generic'
make: *** [vmlinux] Error 1

Does anyone know what ipv4 features I shouldn't use? My .config file:
(network options)

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
# CONFIG_NETLINK_DEV is not set
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
# CONFIG_IP_ROUTE_VERBOSE is not set
CONFIG_IP_ROUTE_LARGE_TABLES=y
CONFIG_IP_ROUTE_NAT=y
# CONFIG_IP_PNP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_ALWAYS_DEFRAG=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y

#
# Protocol-specific masquerading support will be built as modules.
#
CONFIG_IP_MASQUERADE_ICMP=y

#
# Protocol-specific masquerading support will be built as modules.
#
CONFIG_IP_MASQUERADE_MOD=y
CONFIG_IP_MASQUERADE_IPAUTOFW=y
CONFIG_IP_MASQUERADE_IPPORTFW=y
CONFIG_IP_MASQUERADE_MFW=y
# CONFIG_IP_ROUTER is not set
CONFIG_NET_IPIP=m
# CONFIG_NET_IPGRE is not set
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_RARP is not set
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
CONFIG_IPV6=m
# CONFIG_IPV6_EUI64 is not set
CONFIG_IPX=m
# CONFIG_IPX_INTERN is not set
CONFIG_SPX=m
CONFIG_ATALK=m
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
# CONFIG_CPU_IS_SLOW is not set




--
1999 - The year of the penguin.



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

From: A James Lewis <[EMAIL PROTECTED]>
Subject: Root RAID different from Boot RAID? and other RAID issues
Date: Wed, 27 Jan 1999 02:03:46 +0000


Hi,

I'm reading the Documentation/md.txt and it states that booting from a
mirror (Raid-1) is not possible only concat/stripe (raid-0)

But there is a Root-RAID howto that gives an example of RAID5....   Can
anyone tell me if md.txt is out of date and I can boot a mirror in
2.2.0... OR does the initrd method essentially allow any raid level to be / ?

Would it be possible to load initrd from a small partition, or some other
way rather than from a DOS partition?  mabe I can make a 16meg partition
to hold the initrd stuff?  mabe then I could mount it and even mirror? it
after the system is no-longer relying on it?

Perhaps I have mis-understood the whole process!

Does anyone know a good place for documentation on this, because nowhere
does it say what happens if a disk dies and how the system behaves under
fault conditions... what if one of the devices disappears and hence the
/dev/sda1 becomes /dev/sda0 and is in the wrong place in the raid?

Is there device specific device nameing like solaris in 2.2.0.... having
the /dev/sdaX stuff is nice for booting in a mirrored config because it
should boot off the mirror, but for setting up the raid it's bad...
mabe...  What happens if a device for mdadd doesn't exist any more... can
the raid still start?

Please CC by email any suggestions because this list is high volume....

All in all though... 2.2.0 works swimingly... I've seen an ac1 patch
already so it looks like we're in for some tidying up and a 2.2.1 after
Linus' well deserved holiday....  

I may have mis-understood the kmod stuff, but bear with me....

If I do:-

mount -t msdos /dev/fd0 /mnt then kmod loads fat.o and msdos.o...

but if I load xawtv, which accesses /dev/video, it doesn't load bttv....
is there a generic alias it calls? would this me in /etc/conf.modules or
somewhere else?

basically, somthing should be triggered when /dev/video is accessed?

James ([EMAIL PROTECTED])
My operating system unders~1 long filena~1, and yours?


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

From: Bloody Viking <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.advocacy,comp.software.year-2000
Subject: Re: PROPOSAL: comp.unix.year-2038 (WAS: 2038 and Linux)
Date: 27 Jan 1999 00:53:04 GMT

In comp.os.linux.advocacy [EMAIL PROTECTED] wrote:

: Now, why didn't the y2k'ers think of that when they created the group? Cripes,
: it was only four years in the fut... oh, never mind.

Becuse they made the same mistake as the original coders who coded in the
Y2K bugs! It's called shortsightedness! 

-- 
CAUTION: Email Spam Killer in use. Leave this line in your reply! 152680
   T-minus 339 Days, 5 Hours, and 1 Minutes until Y2K and counting.

3434298 bytes of spam mail deleted.           http://www.wwa.com/~nospam/

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


** 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