Bug#65933: Setting clock to UTC sometimes doesn't work

[Niccolo Rigacci]

Package: boot-floppies
Version: 2.2.15
Subject: Setting


When dbootstrap executes "Configure the Base System", if you
choose to set the clock to local time, the string "UTC=no" is
placed in /etc/default/rcS. This is OK.

But if you re-execute "Configure the Base System" and choose to
set the clock to UTC, the value in /etc/default/rcS is not
updated.

I suggest to place an "else" clause in configure_timezone_step2()
function in boot-floppies/utilities/dbootstrap/tzconfig.c



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[Hartmut Koptein]

> > > How and Interim filesystem might work (as i see it)
> > 
> > Why have an interim fs?

And what about raiserfs or better jfs ?


Hartmut


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[bug1]

Hartmut Koptein wrote:
> 
> > > > How and Interim filesystem might work (as i see it)
> > >
> > > Why have an interim fs?
> 
> And what about raiserfs or better jfs ?
> 

I havent tried reiserfs yet, from what i know it save us a bit of space
with small files wouldnt it, does it have nay other advantages ?

Whats jfs?


Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[Hartmut Koptein]

> > And what about raiserfs or better jfs ?
> > 
> 
> I havent tried reiserfs yet, from what i know it save us a bit of space
> with small files wouldnt it, does it have nay other advantages ?
> 
> Whats jfs?

jfs is the journaling-file-system from ibm -- the aix filesystem without
the LVM. 

We have  ext3, raiserfs, xfs and jfs.

disadvantages: 
   ext3 isn't a real journalingfs or better: it hasen't the ful
power. Forget ext3.
   xfs  is non-free stuff

So we have two important fs: raiser and jfs. Both uses b-trees. But 
raiserfs is (currently) only for ia32. 

jfs is gpl, supports other archs then ia32 (powerpc, ...) and also
64bit archs (ia64); jfs for ia32-smp is also possible.

raiserfs is more tested then jfs. But i personally like jfs more then
raiserfs. 


jfs url: 

  http://www10.software.ibm.com/developerworks/opensource/jfs/


Thanks,


  Hartmut


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[Bruce Sass]

On Tue, 20 Jun 2000, bug1 wrote:
> Bruce Sass wrote:
> > > Bruce Sass wrote:
> > > > On Sun, 18 Jun 2000, bug1 wrote:
> > > > > How and Interim filesystem might work (as i see it)
> > > >
> > > > Why have an interim fs?
> > >
> > > 1) To get around any space limitations presented by the boot medium, or
> > > ramdisk.
> > >   It is delaying the partitioning process till later on after we have
> > > lots on space available to us.
> > >   There are lots of different things we can consider doing if space isnt
> > > the primary limitation.
> > 
> > What is the advantage to delaying partitioning, get it out of the way
> > fast and you have the whole harddrive to play with.
> > 
> If you get it out the way first, then you limit how powerfull it can be.
<...>
> If we have lots of space we can use full libraries
> 
> Having LVM, RAID and Resizing tools available when doing the
> partitioning would mean there are no limits to how you choose to
> partition your system, and you could most likely install without having
> to first backup the contents of a partition prior to the install which
> destroys it.

You could do that now, and it is just as good an idea with the existing
system as it is with the one you have in mind.  :)

> Where im coming from is that i consider partitioning to be (probably)
> the most important part of the installation, its much harder to
> repartition after the install than it do any other configuration.

No argument here.

I think you are forgetting about something...
how is partitioning going to be accomplished without user interaction. 

I'm not aware of any tools that can take a description of a filesystem
then partition and setup a harddrive(s) accordingly, that seems to be a
task necessary for unattended (auto-pilot mode) installations.  If you
have such a program then it doesn't make much sense to use the manual
tools in the archive, give the user a more flexible and natural UI
instead.  May as well aim for the target instead of below it, if you
fall short and need to resort to the manual tools then so be it, they
can always be an option loaded off of a floppy, the HD, a CD, or a
network.  You already have at least a read-only filesystem available,
that is all you really need for providing extra tools required before
the target system has storage space available. 

I'm not saying, `forget about an interim fs', just that it is an extra
hassle to setup, has overhead, and it should not be necessary, try to
avoid it... a primitive RAM disk used as a scratchpad, yes, a full blown
fs, no. 

> Thats my experience anyway.  

Mine also

> > I was thinking of a monolithic installer core, modularized like the
> > kernel is for `maybe needed' functions... very small footprint, maybe
> > even totally in memory.
> > 
> If we can have LVM, RAID and Filesystem resizing tools available for
> partitioning using this methods i would be just as happy.

I don't really see what you can do with an installation before the
harddrive(s) are partitioned, this functionality will need to be
available near the start of the process.


later,

Bruce


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bf-utf, gnewt

[Taketoshi Sano]

Hi.

In article <[EMAIL PROTECTED]>,
  at 18 Jun 2000 23:39:34 -0700,
on bf-utf, gnewt,
 [EMAIL PROTECTED] (Karl M. Hegbloom) writes:

>  I started trying to port the patches I found in the bf-utf repository
>  over to the `slang' Newt (snewt) in the `gnewt' module.

Thanks for working on bf-utf.

>  Are those changes backwards compatible?  I know nothing about that.
>  Note that there is a `minislang' in `gnewt' that I think we can
>  use... I did not apply any patches to it.

What do you mean with "backward compatible" ?  I think the back-porting
of the patch (created with slang 1.4.0) for older 1.3 series is really
hard because of many difference between 1.3 and 1.4, but you can try it
anyway.  If you get success, then we can use it happily.

Do you think that `minislang' is usable for us in bf-utf for potato ?

>  If it's backwards compatible, we should switch to the `gnewt' tree
>  rather than the `bf-utf' one for Newt and Slang.

I will checkout that gnewt modules from cvs.debian.org.

Regards.
-- 
  Taketoshi Sano: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[bug1]

Bruce Sass wrote:
> I think you are forgetting about something...
> how is partitioning going to be accomplished without user interaction.
> 
> I'm not aware of any tools that can take a description of a filesystem
> then partition and setup a harddrive(s) accordingly, that seems to be a
> task necessary for unattended (auto-pilot mode) installations.  If you
> have such a program then it doesn't make much sense to use the manual
> tools in the archive, give the user a more flexible and natural UI
> instead.  May as well aim for the target instead of below it, if you
> fall short and need to resort to the manual tools then so be it, they
> can always be an option loaded off of a floppy, the HD, a CD, or a
> network.  You already have at least a read-only filesystem available,
> that is all you really need for providing extra tools required before
> the target system has storage space available.
> 

What if the partitioner was just a GUI, didnt have any tools itself, it
just interfaced to external command line tools. 

Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

potato boot-floppies

[Anthony Towns]

Hello world,

Congratulations guys: -testing seems to hold nothing but praise for potato
upgrades, looks good.

Is there anything more you're intending to do to b-f for potato,
beyond 2.2.15? Alternately, do whatever changes you already have in CVS
account for:

critical bugs - outstanding
 * #64371: Smart Array RAID Compaq do not see at boot; 31 days old
 * #64823: incorrect LILO automatic placement on i386; 22 days old
 * #65515: boot-floppies: update-modules requires /bin/bash; 8 days old

important bugs - outstanding
 * #64500: subject boot-floppies don't want to install kernel &
   modules on ppc/apus.; 28 days old

? Or are these not really RC? (If the latter, please downgrade them
appropriately)

Basically, what I'm asking is, as far as source is concerned, are you
ready to go? I realise you need to wait for updated base packages before
you update all the arch dependent bf stuff. If you're not ready to go,
you really really need to get that way in the next day or two.

Feel free to reply to this list; I'm on it, I just don't follow it
too carefully most of the time.

Cheers,
aj (acting release manager)

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
 We believe in: rough consensus and working code.''
  -- Dave Clark

 PGP signature

Re: potato boot-floppies

[Petr Cech]

On Tue, Jun 20, 2000 at 09:55:31PM +1000 , Anthony Towns wrote:
> Hello world,
> 
> Congratulations guys: -testing seems to hold nothing but praise for potato
> upgrades, looks good.

cool

> Is there anything more you're intending to do to b-f for potato,
> beyond 2.2.15? Alternately, do whatever changes you already have in CVS

I think m68k people wanted to do a release and there are some minor
enhacements and mostly doc updates.

> account for:
> 
> critical bugs - outstanding
>  * #64371: Smart Array RAID Compaq do not see at boot; 31 days old

1) I don't see, why it's critical
2) the -compact flavour should solve this

>  * #64823: incorrect LILO automatic placement on i386; 22 days old

I think the subject is missleading. It only doesn't want to put LILO into
extended partition. Let's call it a feature :)

>  * #65515: boot-floppies: update-modules requires /bin/bash; 8 days old

fixed modutils are in Incoming

> ? Or are these not really RC? (If the latter, please downgrade them
> appropriately)
> 
> Basically, what I'm asking is, as far as source is concerned, are you
> ready to go? I realise you need to wait for updated base packages before
> you update all the arch dependent bf stuff. If you're not ready to go,
> you really really need to get that way in the next day or two.

I think we wait to tausq to upload -compact and -idepci flavor and for
corresponding pcmcia packages. And b-f has to be updatet for 2.2.16

> Feel free to reply to this list; I'm on it, I just don't follow it
> too carefully most of the time.
> 
> Cheers,
> aj (acting release manager)

Petr Cech
-- 
Debian GNU/Linux maintainer - www.debian.{org,cz}
   [EMAIL PROTECTED]

Resistance is futile. You all will be packaged


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: potato boot-floppies

[Christian T. Steigies]

On Tue, Jun 20, 2000 at 09:55:31PM +1000, Anthony Towns wrote:
> ? Or are these not really RC? (If the latter, please downgrade them
> appropriately)
> 
> Basically, what I'm asking is, as far as source is concerned, are you
> ready to go? I realise you need to wait for updated base packages before
> you update all the arch dependent bf stuff. If you're not ready to go,
> you really really need to get that way in the next day or two.
Do you mean, there will be a newer boot-floppies version used for the potato
CDs? I'm in favour of this, not excatly sure if m68k is hit by these RC
bugs, but there are a few simple changes for m68k, which are in CVS but not
yet in 2.2.15. One way to get this right, would be a new bf version.

Please give a warning before a new bf is tagged, I still have some further
(text) updates for m68k, and I am still waiting for further user input.
(I do not really want to tag myself, but if there is no other way...)

Christian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: bf-utf, gnewt

[Karl M. Hegbloom]

> "Taketoshi" == Taketoshi Sano <[EMAIL PROTECTED]> writes:

Taketoshi>  [EMAIL PROTECTED] (Karl M. Hegbloom) writes:

>> I started trying to port the patches I found in the bf-utf repository
>> over to the `slang' Newt (snewt) in the `gnewt' module.

Taketoshi> Thanks for working on bf-utf.

>> Are those changes backwards compatible?  I know nothing about that.
>> Note that there is a `minislang' in `gnewt' that I think we can
>> use... I did not apply any patches to it.

Taketoshi> What do you mean with "backward compatible" ?  I think the back-porting
Taketoshi> of the patch (created with slang 1.4.0) for older 1.3 series is really
Taketoshi> hard because of many difference between 1.3 and 1.4, but you can try it
Taketoshi> anyway.  If you get success, then we can use it happily.

 I'm concerned with whether, after patching it to work with utf8 wide
 characters, it will still function as before, with standard ascii?
 Will I be able to use it still, or will it only work for asian text,
 after the patches?

Taketoshi> Do you think that `minislang' is usable for us in bf-utf for potato ?

 I hope so.  The patches from the other libslang will need to be
 ported to it.  Again, will that be compatible with standard ASCII
 still??

>> If it's backwards compatible, we should switch to the `gnewt' tree
>> rather than the `bf-utf' one for Newt and Slang.

Taketoshi> I will checkout that gnewt modules from cvs.debian.org.

 Ok, good.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[Erik Andersen]

On Tue Jun 20, 2000 at 03:37:17AM -0600, Bruce Sass wrote:
> No argument here.
> 
> I think you are forgetting about something...
> how is partitioning going to be accomplished without user interaction. 
> 
> I'm not aware of any tools that can take a description of a filesystem
> then partition and setup a harddrive(s) accordingly, that seems to be a
> task necessary for unattended (auto-pilot mode) installations. 

sfdisk can do this (but it is much buggier then fdisk and
has endianness problems).

 -Erik

--
Erik B. Andersen   Web:http://www.xmission.com/~andersen/ 
   email:  [EMAIL PROTECTED]
--This message was written using 73% post-consumer electrons--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: woody installation system

[Adam Di Carlo]

Joey Hess <[EMAIL PROTECTED]> writes:

> Ok, let's just call it debian-installer. Adam, please make a new
> module with that name in the debian-boot cvs repository.

Done.  I set g+ws on the dir which I think is the right thing.

-- 
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: potato boot-floppies

[Anthony Towns]

On Tue, Jun 20, 2000 at 03:39:34PM +0200, Petr Cech wrote:
> I think we wait to tausq to upload -compact and -idepci flavor and for
> corresponding pcmcia packages. And b-f has to be updatet for 2.2.16

Okay, assuming all that was pretty much correct and indicative, we
should have all the source updates done and in the archives in the next
52 hours or so, so committing and tagging 2.2.16 around then or maybe
a day or two later should work okay, as far as my schedule's concerned.

I'm okay with being a little laggy with boot-floppies, especially if m68k
is okay for release, since I'm working on the assumption that m68k'll
take the most time to build and upload.

Cheers,
aj (acting release manager)

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
 We believe in: rough consensus and working code.''
  -- Dave Clark

 PGP signature

Re: [woody,debinst] Interim filesystem

[Bruce Sass]

On Tue, 20 Jun 2000, bug1 wrote:
> Bruce Sass wrote:
> > I think you are forgetting about something...
> > how is partitioning going to be accomplished without user interaction.
> > 
> > I'm not aware of any tools that can take a description of a filesystem
> > then partition and setup a harddrive(s) accordingly, that seems to be a
> > task necessary for unattended (auto-pilot mode) installations.  If you
> > have such a program then it doesn't make much sense to use the manual
> > tools in the archive, give the user a more flexible and natural UI
> > instead.  May as well aim for the target instead of below it, if you
> > fall short and need to resort to the manual tools then so be it, they
> > can always be an option loaded off of a floppy, the HD, a CD, or a
> > network.  You already have at least a read-only filesystem available,
> > that is all you really need for providing extra tools required before
> > the target system has storage space available.
> > 
> 
> What if the partitioner was just a GUI, didnt have any tools itself, it
> just interfaced to external command line tools. 

I would expect a debian-installer partitioning program to be a
collaboration of (G)UI, core, and cmdline tools (or at least the bits
from them that are needed).  I guess what it boils down to is if the
necessary functions can be incorporated into the installer, the core of 
the partitioner, or would need to be stand-alone; the latter would
probably necessitate an interim fs, the first two mean more work.


later,

Bruce


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [woody,debinst] Interim filesystem

[Bruce Sass]

On Tue, 20 Jun 2000, Erik Andersen wrote:
> On Tue Jun 20, 2000 at 03:37:17AM -0600, Bruce Sass wrote:
> > I think you are forgetting about something...
> > how is partitioning going to be accomplished without user interaction. 
> > 
> > I'm not aware of any tools that can take a description of a filesystem
> > then partition and setup a harddrive(s) accordingly, that seems to be a
> > task necessary for unattended (auto-pilot mode) installations. 
> 
> sfdisk can do this (but it is much buggier then fdisk and
> has endianness problems).

It can do part of it (setting up the partition table), but there is
still the task of translating what the user wants for a fs into
partition tables and creating the actual fs on the drive(s).

[If I could get the seagate driver working with this Future Domain 
TMC-881 SCSI controller I would start seriously playing around with this
concept. :( ]


later,

Bruce


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: potato boot-floppies

[Joerg Friedrich]

On Tue, 20 Jun 2000, Petr Cech wrote:

> >  * #64823: incorrect LILO automatic placement on i386; 22 days old
> 
> I think the subject is missleading. It only doesn't want to put LILO into
> extended partition. Let's call it a feature :)
But this leeds into serious problems if a third party bootloader is used,
i.e. IBM (OS/2) Bootloader, Powerquest Bootmagic (comes with Partition
Magic)

there should be an option to allow installing lilo into an extended
partition, maybe with a warning.



-- 
Heute ist nicht alle Tage, ich komme wieder, keine Frage!!!

   Joerg


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#65988: modules unavailable because of wierd symlink

[kbullock]

Package: boot-floppies
Version: N/A;
Severity: grave

Using the potato boot-floppied version 2.2.15-2000-06-07, I installed my
system from five floppies and the Internet. After the driver disks had been
loaded into the ramdisk, I went to install modules, but there were none in
the list. After poking around I discovered that /lib/modules was a symlink
to itself, and /lib/modules.old contained the modules. 'rm modules; mv
modules.old modules' took care of the problem.

-- System Information
Debian Release: 2.2
Architecture: i386
Kernel: Linux belter 2.2.16 #1 Fri Jun 9 16:16:20 CDT 2000 i586



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#65991: boot-floppies: module params STILL not passed correctly; can't install ne or adlib_card

[J.A. Bezemer]

Package: boot-floppies
Version: 2.2.15-2000-06-07
Severity: critical

The modutils stuff in dbootstrap ("Configure device drivers") still does not
pass options to the modprobe call. I can't install `ne' or `adlib_card' from
the "GUI". Especially `adlib_card' is nice because it explicitly says it
doesn't get the parameter that I'm trying to pass to it; a "modprobe
adlib_card" (i.e. without params) from tty2 gives exactly that error. (a
modprobe _with_ params gives a normal "device not found"-type of error)

System: Pentium 166 MHz, booted from official non-US test-cycle-2 i386
Binary-1 CD (which is supposed to use images-2.88/rescue.bin).


Regards,
  Anne Bezemer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#65991: boot-floppies: module params STILL not passed correctly; can't install ne or adlib_card

[Randolph Chung]

This is a modutils bug and has been filed many times. it has been fixed
already.

randolph
-- 
Debian Developer <[EMAIL PROTECTED]>
http://www.TauSq.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: potato boot-floppies

[Randolph Chung]

> I think we wait to tausq to upload -compact and -idepci flavor and for
> corresponding pcmcia packages. And b-f has to be updatet for 2.2.16

i'll do that in the next couple of days.

i think it's kinda poetic that we have 2.2.16 b-f and 2.2.16
boot-floppies... :-)

randolph
-- 
Debian Developer <[EMAIL PROTECTED]>
http://www.TauSq.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#65991: boot-floppies: module params STILL not passed correctly; can't install ne or adlib_card

[J.A. Bezemer]

On Tue, 20 Jun 2000, Randolph Chung wrote:

> This is a modutils bug and has been filed many times. it has been fixed
> already.

It was supposed to be fixed in 2.2.15. It is _not_.

And if it's fixed (really??) in some upcoming 2.2.16, then go tell the Acting
RM _quickly_, otherwise he'll start test-cycle-3 without 2.2.16.


Regards,
  Anne Bezemer



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#66003: Boot Floppy Problems using PCMCIA Network Card

[Steven Elling]

Package: boot-floppies
Version: 2.1.12

Following Section 7 (Using dbootstrap for Initial System Configuration) of the 
"Installing
Debian GNU/Linux 2.1 For Intel x86" document, I tried to install Debian on a Toshiba 
Tecra
8000 with a PCMCIA 3Com 3c589D-TP NIC over NFS.  It looked good until I got to 7.14
``Install the Base System''.  The laptop would fail to contact the NFS server and the 
link
light on the network switch was not lit.


At the console, running 'ifconfig eth0 up' produces:

eth0: unknown interface


Running 'ifconfig -a' only shows:

loLink encap:Local Loopback
  inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
  UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  Collisions:0


Running 'lsmod' shows that the pcmcia and network modules loaded:

Module PagesUsed by
3c589_cs   20
psaux  10
smbfs  60
nfs   124
cdrom  10
ds 2[3c589_cs]  2
i82365 52
pcmcia_core9[3c589_cs ds i82365]0


Running 'ps' shows card manager is running:

1   (init)
19  (dbootstrap)
2   (kflushd)
20  (sh)
2459(cardmgr)
2494(ps)
3   (kswapd)
4   (md_thread)
5   (md_thread)
820 (nfsiod)
821 (nfsiod)
822 (nfsiod)
823 (nfsiod)


Running '/target/etc/init.d/pcmcia restart' shows the following:

Shutting down PCMCIA services:start-stop-daemon: not found
 cardmgrstart-stop-daemon: not found
.
Starting PCMCIA services: modules/lib/modules/2.0.38/pcmcia/pcmcia_core.o: a module 
named
pcmcia_core already exists
/lib/modules/2.0.38/pcmcia/i82365.o: a module named i82365 already exists
/lib/modules/2.0.38/pcmcia/ds.o: a module named ds already exists
start-stop-daemon: not found
 cardmgr.
start-stop-daemon: not found


This very same laptop had RedHat Linux 6.2 running on it without any network problems
before it got blown away for Debian.

-- 

Steven Elling - [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]