Re: Init takes long time and what is lspci?

1999-08-02 Thread Stephen Pitts
On Sun, Aug 01, 1999 at 02:31:15PM +0200, Jonas Steverud wrote:
 
 Debian Potato.
 
 When I boot, init prints out INIT 2.74 (?) and then it stops for
 10-20 seconds and then continues with NET4: Unix domain sockets 1.0
 for Linux NET4.0. which takes another 5-10 seconds. Anyone who knows
 why this happens? Is it trying to get some information from somewhere
 or what? Before I changed to the 2.2.10-kernel (see other thread) this
 did not happen. Or is it perfectly normal?
 

Unix domain sockets are a special type of file that can be read and
written to, to gain all of the advantages of sockets without the
overhead of TCP/IP. X and its font servers use them, as well as
xmms and mysql (right off the top of my head..probably lots
of others). In the Debian kernel_image_2.2.10, unix domain sockets 
are compiled in  as a module and kmod is loading them as a module 
because some daemon that is starting needs them. On my system, I see 
that 108 things are using unix domain sockets.

My smallest system here is a P-150, but I'll agree that there is a
noticable boot-time delay when loading this module. In discussion
right now on debian-devel is the idea of using ash instead of
bash for /bin/sh. Since ash is faster/uses less memory than bash,
it could significantly decrease the bootup time of your system.
-- 
Stephen Pitts
[EMAIL PROTECTED]
webmaster - http://www.mschess.org


Re: Init takes long time and what is lspci?

1999-08-01 Thread Jor-el
-BEGIN PGP SIGNED MESSAGE-

Jonas,

'lspci' is not needed and will not work on the 2.0.x kernels. They
need a file in the /proc heirarchy which was introduced in the 2.2.x
kernels.

Cant answer your INIT question.

Regards,
Jor-el

Human cardiac catheterization was introduced by Werner Forssman in 1929.
Ignoring his department chief, and tying his assistant to an operating
table to prevent her interference, he placed a ureteral catheter into
a vein in his arm, advanced it to the right atrium [of his heart], and
walked upstairs to the x-ray department where he took the confirmatory
x-ray film.  In 1956, Dr. Forssman was awarded the Nobel Prize.

On 1 Aug 1999, Jonas Steverud wrote:

 
 Debian Potato.
 
 Last queation first: what's lspci? I get the message that lspci is not
 found so no PCI conflicts are calculated when I boot. I presume it's
 in pciutils but who do I know if I need it or not? I bought the
 computer in november '96 and I really don't know/remember what's in
 it. (I gave up keeping track of all new standards when SVGA meant
 better then 640x480x16 and the i486 came.)
 
 When I boot, init prints out INIT 2.74 (?) and then it stops for
 10-20 seconds and then continues with NET4: Unix domain sockets 1.0
 for Linux NET4.0. which takes another 5-10 seconds. Anyone who knows
 why this happens? Is it trying to get some information from somewhere
 or what? Before I changed to the 2.2.10-kernel (see other thread) this
 did not happen. Or is it perfectly normal?
 
 -- 
 ( Jonas Steverud  @  www.dtek.chalmers.se/~d4jonas/ !Wei Wu Wei)
 ( U2MoL, Roleplaying, LaTeX, Emacs/Gnus, SCWM, etc. ! To Do Without Do )
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 
 

-BEGIN PGP SIGNATURE-
Version: 2.6.3a
Charset: noconv

iQCVAwUBN6RPxvrE9j2ZpWNBAQFsbwQAwo8kz62RAhgvBSQ3SptxOlVtXGhWCusR
0opRaAqUaybZEAHXhuYE3K6+d4RRzvP9esmcmvDINXLAq0OntKjE15N9ckVBe8xY
TmihHYrbS6QI/+zgofe8Xw+s6Ti0VHbItE1+HIGgp5u9MCv0iy2yWLtfuRMJvROJ
nhXbdvmC19Q=
=Mijy
-END PGP SIGNATURE-


Re: Init takes long time and what is lspci?

1999-08-01 Thread Robert Vollmert
On Sun, Aug 01, 1999 at 02:31:15PM +0200, Jonas Steverud wrote:
 When I boot, init prints out INIT 2.74 (?) and then it stops for
 10-20 seconds and then continues with NET4: Unix domain sockets 1.0
 for Linux NET4.0. which takes another 5-10 seconds. Anyone who knows
 why this happens? Is it trying to get some information from somewhere
 or what? Before I changed to the 2.2.10-kernel (see other thread) this
 did not happen. Or is it perfectly normal?

I had this problem, too, after a partial upgrade to potato. After
upgrading a few more packages, it worked again. I can't remember
which packages exactly, but I think sysvinit was among them.

-- 
Robert Vollmert  [EMAIL PROTECTED]