Bug #7490 “/sys not mounted at boot on a 2.6 kernel” : Bugs : sysvinit package : Ubuntu

Revision history for this message

In Debian Bug tracker #266361, Aurelien Jarno (aurelien-aurel32) wrote on 2004-08-17: Re: Bug#266227: lm-sensors doesn't start and doesn't provide any information how to solve this problem

#1

Download full text (5.4 KiB)

clone 266227
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 26627 minor
thanks

[ For the initscripts maintainer, in short the problem is that
/sys is not mounted at boot time in a system using a 2.6 kernel. ]

On Tue, Aug 17, 2004 at 07:01:16AM +0300, Mantas Kriaučiūnas wrote:
> Package: lm-sensors
> Version: 2.8.7-2
> Severity: grave
> Justification: renders package unusable
>
> I'm trying to get working lm-sensors on debian:
>
> dubrava:/home/mantas# apt-get install lm-sensors
>
> [...]
>
> Setting up lm-sensors (2.8.7-2) ...
>
> Gtk-WARNING **: cannot open display:
> debconf: unable to initialize frontend: Gnome
> debconf: (DISPLAY problem?)
> debconf: falling back to frontend: Dialog
>
> Creating config file /etc/sensors.conf with new version
> cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
> cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> done.
>
>
> As I don't know what is sysfs (procfs is mountend automatically on my
> system by discover) and didn't got any debconf prompts about mounting
> sysfs, so I did 'modprobe i2c_sensor' and then did:
sysfs should be mounted on a 2.6 kernel. It is the jobs of initscripts,
and it is surprising that it is not mounted at boot time.

> dubrava:/home/mantas# /etc/init.d/lm-sensors restart
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> done.
>
> It seems same shit again :(
>
> Then I've read in /usr/share/doc/lm-sensors/README.Debian this:
>
> 2.6 kernels
>
> Once you have your kernel properly configured, you need to probe for the
> sensors available on your system. You can use the sensors-detect program to
> do this.
>
> Hehe, if it's so simple, why don't offer debconf prompt for user about this?
Simply because the Debian Policy forbids to do that. Moreover, the "Once
you have your kernel properly configured" is important there, it means
that need to have the drivers built as modules or built into the kernel.
And it could a lot more complicated with 2.4 kernels than with 2.6
kernels.

> OK, then I started sensors-detect program pressed Enter several times and
> got this info in terminal:
>
> To make the sensors modules behave correctly, add these lines to
> /etc/mo...

clone 266227
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 26627 minor
thanks

[ For the initscripts maintainer, in short the problem is that
  /sys is not mounted at boot time in a system using a 2.6 kernel. ]

On Tue, Aug 17, 2004 at 07:01:16AM +0300, Mantas Kriaučiūnas wrote:
> Package: lm-sensors
> Version: 2.8.7-2
> Severity: grave
> Justification: renders package unusable
> 
> I'm trying to get working lm-sensors on debian:
> 
> dubrava:/home/mantas# apt-get install lm-sensors
> 
> [...]
> 
> Setting up lm-sensors (2.8.7-2) ...
> 
> Gtk-WARNING **: cannot open display:
> debconf: unable to initialize frontend: Gnome
> debconf: (DISPLAY problem?)
> debconf: falling back to frontend: Dialog
> 
> Creating config file /etc/sensors.conf with new version
>  cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
>  cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
>  done.
> 
> 
> As I don't know what is sysfs (procfs is mountend automatically on my
> system by discover) and didn't got any debconf prompts about mounting
> sysfs, so I did 'modprobe i2c_sensor' and then did:
sysfs should be mounted on a 2.6 kernel. It is the jobs of initscripts,
and it is surprising that it is not mounted at boot time.

> dubrava:/home/mantas# /etc/init.d/lm-sensors restart
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
>  done.
> 
> It seems same shit again :(
>   
> Then I've read in /usr/share/doc/lm-sensors/README.Debian this:
> 
> 2.6 kernels
> 
> Once you have your kernel properly configured, you need to probe for the
> sensors available on your system. You can use the sensors-detect program to
> do this.
> 
> Hehe, if it's so simple, why don't offer debconf prompt for user about this?
Simply because the Debian Policy forbids to do that. Moreover, the "Once
you have your kernel properly configured" is important there, it means
that need to have the drivers built as modules or built into the kernel. 
And it could a lot more complicated with 2.4 kernels than with 2.6 
kernels.

> OK, then I started sensors-detect program pressed Enter several times and
> got this info in terminal:
> 
> To make the sensors modules behave correctly, add these lines to
> /etc/modules:
> 
> #----cut here----
> # I2C adapter drivers
> i2c-isa
> # I2C chip drivers
> w83627hf
> #----cut here----
> 
> Then, run /etc/init.d/module-init-tools
> 
> 
> To make the sensors modules behave correctly, add these lines to
> /etc/modprobe.d/local and run update-modules:
> 
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
> 
> 
> I copied info into /etc/modules, then copied another part into 
> /etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases
> and found, that the same alias is in /etc/modprobe.d/aliases already !!!
You're right, that alias is already present for 2.6 kernels.
And for 2.4 kernels, the alias is automatically added by the package.

> One more bug :( Also I think it's not hard to make script, which adds needed
> lines automatically, why user should manually to do this ?
Because some users prefer to build the driver in hard in their kernel, 
some others prefers to load them manually, and moreover, they maybe more
than one module possible for the same device.

[...]

> So,
>  - why  sensors-detect isn't started automatically (after debconf prompt)
> about this ?
Explained before. However, I'll add a debconf note to explain how to
configure the kernel modules, though it is already explained in
/usr/share/doc/lm-sensors/README.Debian.

>  - why output of sensors-detect isn't copied to /etc/modules automatically ?
Explained before. It's better to let the users decide, and copy/paste is
not a very difficult thing.

>  - why sysfs isn't mounted in /etc/init.d/lm-sensors or in some other place
>  automatically ?
As said, it is not the job of lm-sensors. I have reassigned a copy of
this bug to initscripts.

> It seems lm-sensors will be usable for simple users only, when these problems
> will be solved (not even advanced users can't get lmsensors working :( )
I don't want to feed the troll, but I know a lot people that can be
defined as "simple users" using lm-sensors. Without the problem of sysfs
(which I repeat doesn't come from lm-sensors), you would have configured
it easilly.

Bye,
Aurélien

-- 
  .''`.  Aurelien Jarno	              GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Revision history for this message

In Debian Bug tracker #266361, Aurelien Jarno (aurelien-aurel32) wrote on 2004-08-17: Re: Processed: Re: Bug#266227: lm-sensors doesn't start and doesn't provide any information how to solve this problem

#2

clone 266227 -1
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 266227 minor
thanks

--
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' <email address hidden> | <email address hidden>
`- people.debian.org/~aurel32 | www.aurel32.net

Revision history for this message

In Debian Bug tracker #266361, Thomas Hood (jdthood-yahoo) wrote on 2004-08-17: severity of 266361 is important

#3

severity 266361 important

Revision history for this message

In Debian Bug tracker #266361, Thomas Hood (jdthood-aglu) wrote on 2004-08-17: sysfs is mounted by current initscripts

#4

The current initscripts does mount sysfs on /sys.

The user should upgrade his initscripts package.
--
Thomas Hood

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-17:

#5

Automatically imported from Debian bug report #266361 http://bugs.debian.org/266361

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-17:

#6

Download full text (5.4 KiB)

Message-Id: <email address hidden>
Date: Tue, 17 Aug 2004 07:01:16 +0300
From: =?iso-8859-13?q?Mantas_Kriau=E8i=FBnas?= <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: lm-sensors doesn't start and doesn't provide any information how to solve
this problem

Package: lm-sensors
Version: 2.8.7-2
Severity: grave
Justification: renders package unusable

I'm trying to get working lm-sensors on debian:

dubrava:/home/mantas# apt-get install lm-sensors

[...]

Setting up lm-sensors (2.8.7-2) ...

Gtk-WARNING **: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog

Creating config file /etc/sensors.conf with new version
cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

As I don't know what is sysfs (procfs is mountend automatically on my
system by discover) and didn't got any debconf prompts about mounting
sysfs, so I did 'modprobe i2c_sensor' and then did:

dubrava:/home/mantas# /etc/init.d/lm-sensors restart
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

It seems same shit again :(

Then I've read in /usr/share/doc/lm-sensors/README.Debian this:

2.6 kernels

Once you have your kernel properly configured, you need to probe for the
sensors available on your system. You can use the sensors-detect program to
do this.

Hehe, if it's so simple, why don't offer debconf prompt for user about this?

OK, then I started sensors-detect program pressed Enter several times and
got this info in terminal:

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
#----cut here----

Then, run /etc/init.d/module-init-tools

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.d/local and run update-modules:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

I copied info into /etc/modules, then copied another part into
/etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases
and found, that the same alias is in /etc/modprobe.d/aliases already !!!

One more bug :( Also I think it's not hard to mak...

Message-ID: <20040817173731.GA23186@bode.aurel32.lan>
Date: Tue, 17 Aug 2004 19:37:32 +0200
From: Aurelien Jarno <aurelien@aurel32.net>
To: Mantas =?utf-8?B?S3JpYXXEjWnFq25hcw==?= <mantas@akl.lt>,
	266227@bugs.debian.org
Cc: Miquel van Smoorenburg <miquels@cistron.nl>
Subject: Re: Bug#266227: lm-sensors doesn't start and doesn't provide any information how to solve
	this problem

clone 266227
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 26627 minor
thanks

[ For the initscripts maintainer, in short the problem is that
  /sys is not mounted at boot time in a system using a 2.6 kernel. ]

On Tue, Aug 17, 2004 at 07:01:16AM +0300, Mantas Kriaučiūnas wrote:
> Package: lm-sensors
> Version: 2.8.7-2
> Severity: grave
> Justification: renders package unusable
> 
> I'm trying to get working lm-sensors on debian:
> 
> dubrava:/home/mantas# apt-get install lm-sensors
> 
> [...]
> 
> Setting up lm-sensors (2.8.7-2) ...
> 
> Gtk-WARNING **: cannot open display:
> debconf: unable to initialize frontend: Gnome
> debconf: (DISPLAY problem?)
> debconf: falling back to frontend: Dialog
> 
> Creating config file /etc/sensors.conf with new version
>  cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
>  cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
>  done.
> 
> 
> As I don't know what is sysfs (procfs is mountend automatically on my
> system by discover) and didn't got any debconf prompts about mounting
> sysfs, so I did 'modprobe i2c_sensor' and then did:
sysfs should be mounted on a 2.6 kernel. It is the jobs of initscripts,
and it is surprising that it is not mounted at boot time.

> dubrava:/home/mantas# /etc/init.d/lm-sensors restart
> Setting sensors limits:Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
> Can't access procfs/sysfs file
> Unable to find i2c bus information;
> For 2.6 kernels, make sure you have mounted sysfs and done
> 'modprobe i2c_sensor'!
> For older kernels, make sure you have done 'modprobe i2c-proc'!
>  done.
> 
> It seems same shit again :(
>   
> Then I've read in /usr/share/doc/lm-sensors/README.Debian this:
> 
> 2.6 kernels
> 
> Once you have your kernel properly configured, you need to probe for the
> sensors available on your system. You can use the sensors-detect program to
> do this.
> 
> Hehe, if it's so simple, why don't offer debconf prompt for user about this?
Simply because the Debian Policy forbids to do that. Moreover, the "Once
you have your kernel properly configured" is important there, it means
that need to have the drivers built as modules or built into the kernel. 
And it could a lot more complicated with 2.4 kernels than with 2.6 
kernels.

> OK, then I started sensors-detect program pressed Enter several times and
> got this info in terminal:
> 
> To make the sensors modules behave correctly, add these lines to
> /etc/modules:
> 
> #----cut here----
> # I2C adapter drivers
> i2c-isa
> # I2C chip drivers
> w83627hf
> #----cut here----
> 
> Then, run /etc/init.d/module-init-tools
> 
> 
> To make the sensors modules behave correctly, add these lines to
> /etc/modprobe.d/local and run update-modules:
> 
> #----cut here----
> # I2C module options
> alias char-major-89 i2c-dev
> #----cut here----
> 
> 
> I copied info into /etc/modules, then copied another part into 
> /etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases
> and found, that the same alias is in /etc/modprobe.d/aliases already !!!
You're right, that alias is already present for 2.6 kernels.
And for 2.4 kernels, the alias is automatically added by the package.

> One more bug :( Also I think it's not hard to make script, which adds needed
> lines automatically, why user should manually to do this ?
Because some users prefer to build the driver in hard in their kernel, 
some others prefers to load them manually, and moreover, they maybe more
than one module possible for the same device.

[...]

> So,
>  - why  sensors-detect isn't started automatically (after debconf prompt)
> about this ?
Explained before. However, I'll add a debconf note to explain how to
configure the kernel modules, though it is already explained in
/usr/share/doc/lm-sensors/README.Debian.

>  - why output of sensors-detect isn't copied to /etc/modules automatically ?
Explained before. It's better to let the users decide, and copy/paste is
not a very difficult thing.

>  - why sysfs isn't mounted in /etc/init.d/lm-sensors or in some other place
>  automatically ?
As said, it is not the job of lm-sensors. I have reassigned a copy of
this bug to initscripts.

> It seems lm-sensors will be usable for simple users only, when these problems
> will be solved (not even advanced users can't get lmsensors working :( )
I don't want to feed the troll, but I know a lot people that can be
defined as "simple users" using lm-sensors. Without the problem of sysfs
(which I repeat doesn't come from lm-sensors), you would have configured
it easilly.

Bye,
Aurélien

-- 
  .''`.  Aurelien Jarno	              GPG: 1024D/F1BCDB73
 : :' :  Debian GNU/Linux developer | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-17:

#8

Message-ID: <email address hidden>
Date: Tue, 17 Aug 2004 20:06:03 +0200
From: Aurelien Jarno <email address hidden>
To: <email address hidden>
Subject: Re: Processed: Re: Bug#266227: lm-sensors doesn't start and doesn't provide any information
how to solve this problem

clone 266227 -1
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 266227 minor
thanks

--
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' <email address hidden> | <email address hidden>
`- people.debian.org/~aurel32 | www.aurel32.net

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-17:

#9

Message-Id: <20040817185921.7364310D6D2@localhost>
Date: Tue, 17 Aug 2004 20:59:21 +0200 (CEST)
From: <email address hidden> (Thomas Hood)
To: <email address hidden>
Subject: severity of 266361 is important

severity 266361 important

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-08-17:

#10

Message-Id: <email address hidden>
Date: Tue, 17 Aug 2004 21:03:18 +0200
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: sysfs is mounted by current initscripts

The current initscripts does mount sysfs on /sys.

The user should upgrade his initscripts package.
--
Thomas Hood

Revision history for this message

Matt Zimmerman (mdz) wrote on 2004-08-26:

#11

Likewise for Warty

Revision history for this message

In Debian Bug tracker #266361, Mantas Kriaučiūnas (mantas) wrote on 2004-09-13: reopen 266361

#12

reopen 266361

Revision history for this message

In Debian Bug tracker #266361, Mantas Kriaučiūnas (mantas) wrote on 2004-09-13: /sys isn't mounted after installing new initscripts

#13

It seems initscripts has problems with mounting /sys :

----- Forwarded message from Aurelien Jarno <email address hidden> -----

From: Aurelien Jarno <email address hidden>

On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
[...]
> I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> emply in my system. I'm using 2.6.5-1-k7 kernel image.
> Maybe problem is in initscripts (version 2.86-1) package, I think
> postinst of sysvinit and initscripts should check if /sys is mounted and
> if not - then call "/etc/init.d/mountvirtfs start", because I got
> working /sys and lm-sensors when I did:
>
> dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> dubrava:/home/mantas# ls /sys/
> block bus class devices firmware power
> dubrava:/home/mantas# /etc/init.d/lm-sensors start
> Setting sensors limits: done.
>
> Should I report bug agains sysvinit and/or initscripts ?
When you first reported the bug, I clone that bug to initscripts.
However, as you don't answer, the maintainer of initscripts has close
it. So, please reopen bug #266361 and don't complain to lm-sensors.

----- End forwarded message -----

--
Good luck,
Mantas Kriaučiūnas <email address hidden> Jabber ID: <email address hidden>
Public organization "Open Source for Lithuania" - www.akl.lt

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-09-13:

#14

Message-ID: <email address hidden>
Date: Mon, 13 Sep 2004 15:49:44 +0300
From: "AKL. Mantas Kriauciunas" <email address hidden>
To: <email address hidden>
Subject: /sys isn't mounted after installing new initscripts

It seems initscripts has problems with mounting /sys :

----- Forwarded message from Aurelien Jarno <email address hidden> -----

From: Aurelien Jarno <email address hidden>

On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
[...]
> I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> emply in my system. I'm using 2.6.5-1-k7 kernel image.
> Maybe problem is in initscripts (version 2.86-1) package, I think
> postinst of sysvinit and initscripts should check if /sys is mounted an=
d
> if not - then call "/etc/init.d/mountvirtfs start", because I got
> working /sys and lm-sensors when I did:
>=20
> dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> dubrava:/home/mantas# ls /sys/
> block bus class devices firmware power
> dubrava:/home/mantas# /etc/init.d/lm-sensors start
> Setting sensors limits: done.
>=20
> Should I report bug agains sysvinit and/or initscripts ?
When you first reported the bug, I clone that bug to initscripts.
However, as you don't answer, the maintainer of initscripts has close
it. So, please reopen bug #266361 and don't complain to lm-sensors.

----- End forwarded message -----

--=20
Good luck,
Mantas Kriau=C4=8Di=C5=ABnas <email address hidden> Jabber ID: <email address hidden>=
t
Public organization "Open Source for Lithuania" - www.akl.lt

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-09-13:

#15

Message-ID: <email address hidden>
Date: Mon, 13 Sep 2004 15:45:54 +0300
From: "AKL. Mantas Kriauciunas" <email address hidden>
To: <email address hidden>
Subject: reopen 266361

reopen 266361

Revision history for this message

In Debian Bug tracker #266361, Miquel van Smoorenburg (miquels) wrote on 2004-09-13: Re: Bug#266361: /sys isn't mounted after installing new initscripts

#16

severity 266361 minor
tags 266361 +moreinfo
thanks

On 2004.09.13 14:49, AKL. Mantas Kriauciunas wrote:
> It seems initscripts has problems with mounting /sys :

It doesn't AFAIK. The user must have changed something locally
on his system - initscripts DOES correctly mount /sys at
startup. It does on all systems I'm using here, and there have
been no other complaints ....

Please check if /etc/rcS.d/S02mountvirtfs is present, points
to /etc/init.d/mountvirtfs, and that mountvirtfs is at least
version 2.85-23.

Or maybe I misunderstand and the user upgraded from a broken
initscripts that apparently didn't mount /sys to a fixed one,
without rebooting ? In that case, stuff like that happens when
running "unstable". That's why it's called that. Things break
now and then .. all versions in "stable" and "testing" are OK.

> ----- Forwarded message from Aurelien Jarno <email address hidden> -----
>
> From: Aurelien Jarno <email address hidden>
>
> On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
> [...]
> > I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> > emply in my system. I'm using 2.6.5-1-k7 kernel image.
> > Maybe problem is in initscripts (version 2.86-1) package, I think
> > postinst of sysvinit and initscripts should check if /sys is mounted and
> > if not - then call "/etc/init.d/mountvirtfs start", because I got
> > working /sys and lm-sensors when I did:

No it shouldn't just go out and mount /sys without asking.

> > dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> > dubrava:/home/mantas# ls /sys/
> > block bus class devices firmware power
> > dubrava:/home/mantas# /etc/init.d/lm-sensors start
> > Setting sensors limits: done.
> >
> > Should I report bug agains sysvinit and/or initscripts ?
> When you first reported the bug, I clone that bug to initscripts.
> However, as you don't answer, the maintainer of initscripts has close
> it. So, please reopen bug #266361 and don't complain to lm-sensors.
>
> ----- End forwarded message -----
>
> --
> Good luck,
> Mantas Kriaučiūnas <email address hidden> Jabber ID: <email address hidden>
> Public organization "Open Source for Lithuania" - www.akl.lt
>
>
>

severity 266361 minor
tags 266361 +moreinfo
thanks

On 2004.09.13 14:49, AKL. Mantas Kriauciunas wrote:
> It seems initscripts has problems with mounting /sys :

It doesn't AFAIK. The user must have changed something locally
on his system - initscripts DOES correctly mount /sys at
startup. It does on all systems I'm using here, and there have
been no other complaints ....

Please check if /etc/rcS.d/S02mountvirtfs is present, points
to /etc/init.d/mountvirtfs, and that mountvirtfs is at least
version 2.85-23.

Or maybe I misunderstand and the user upgraded from a broken
initscripts that apparently didn't mount /sys to a fixed one,
without rebooting ? In that case, stuff like that happens when
running "unstable". That's why it's called that. Things break
now and then .. all versions in "stable" and "testing" are OK.

> ----- Forwarded message from Aurelien Jarno <aurelien@aurel32.net> -----
> 
> From: Aurelien Jarno <aurelien@aurel32.net>
> 
> On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
> [...]
> > I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> > emply in my system. I'm using 2.6.5-1-k7 kernel image.
> > Maybe problem is in initscripts (version 2.86-1) package, I think
> > postinst of sysvinit and initscripts should check if /sys is mounted and
> > if not - then call "/etc/init.d/mountvirtfs start", because I got
> > working /sys and lm-sensors when I did:

No it shouldn't just go out and mount /sys without asking.

> > dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> > dubrava:/home/mantas# ls /sys/
> > block  bus  class  devices  firmware  power
> > dubrava:/home/mantas# /etc/init.d/lm-sensors start
> > Setting sensors limits: done.
> > 
> > Should I report bug agains sysvinit and/or initscripts ?
> When you first reported the bug, I clone that bug to initscripts.
> However, as you don't answer, the maintainer of initscripts has close
> it. So, please reopen bug #266361 and don't complain to lm-sensors.
> 
> ----- End forwarded message -----
> 
> -- 
> Good luck,
> Mantas Kriaučiūnas <mantas@akl.lt>      Jabber ID: mantas@akl.lt
> Public organization "Open Source for Lithuania" - www.akl.lt
> 
> 
>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-09-13:

#17

Message-Id: <1095087866l.13569l.2l@traveler>
Date: Mon, 13 Sep 2004 15:04:26 +0000
From: Miquel van Smoorenburg <email address hidden>
To: "AKL. Mantas Kriauciunas" <email address hidden>
Cc: <email address hidden>, <email address hidden>, Aurelien Jarno
<email address hidden>, <email address hidden>
Subject: Re: Bug#266361: /sys isn't mounted after installing new initscripts

severity 266361 minor
tags 266361 +moreinfo
thanks

On 2004.09.13 14:49, AKL. Mantas Kriauciunas wrote:
> It seems initscripts has problems with mounting /sys :

It doesn't AFAIK. The user must have changed something locally
on his system - initscripts DOES correctly mount /sys at
startup. It does on all systems I'm using here, and there have
been no other complaints ....

Please check if /etc/rcS.d/S02mountvirtfs is present, points
to /etc/init.d/mountvirtfs, and that mountvirtfs is at least
version 2.85-23.

Or maybe I misunderstand and the user upgraded from a broken
initscripts that apparently didn't mount /sys to a fixed one,
without rebooting ? In that case, stuff like that happens when
running "unstable". That's why it's called that. Things break
now and then .. all versions in "stable" and "testing" are OK.

> ----- Forwarded message from Aurelien Jarno <email address hidden> -----
>=20
> From: Aurelien Jarno <email address hidden>
>=20
> On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
> [...]
> > I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> > emply in my system. I'm using 2.6.5-1-k7 kernel image.
> > Maybe problem is in initscripts (version 2.86-1) package, I think
> > postinst of sysvinit and initscripts should check if /sys is mounted an=
d
> > if not - then call "/etc/init.d/mountvirtfs start", because I got
> > working /sys and lm-sensors when I did:

No it shouldn't just go out and mount /sys without asking.

> > dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> > dubrava:/home/mantas# ls /sys/
> > block bus class devices firmware power
> > dubrava:/home/mantas# /etc/init.d/lm-sensors start
> > Setting sensors limits: done.
> >=20
> > Should I report bug agains sysvinit and/or initscripts ?
> When you first reported the bug, I clone that bug to initscripts.
> However, as you don't answer, the maintainer of initscripts has close
> it. So, please reopen bug #266361 and don't complain to lm-sensors.
>=20
> ----- End forwarded message -----
>=20
> --=20
> Good luck,
> Mantas Kriau=C4=8Di=C5=ABnas <email address hidden> Jabber ID: <email address hidden>=
t
> Public organization "Open Source for Lithuania" - www.akl.lt
>=20
>=20
>=20

Message-Id: <1095087866l.13569l.2l@traveler>
Date: Mon, 13 Sep 2004 15:04:26 +0000
From: Miquel van Smoorenburg <miquels@cistron.nl>
To: "AKL. Mantas Kriauciunas" <mantas@akl.lt>
Cc: 266361@bugs.debian.org, control@bugs.debian.org, Aurelien Jarno
	<aurelien@aurel32.net>, miquels@cistron.nl
Subject: Re: Bug#266361: /sys isn't mounted after installing new initscripts

severity 266361 minor
tags 266361 +moreinfo
thanks

On 2004.09.13 14:49, AKL. Mantas Kriauciunas wrote:
> It seems initscripts has problems with mounting /sys :

It doesn't AFAIK. The user must have changed something locally
on his system - initscripts DOES correctly mount /sys at
startup. It does on all systems I'm using here, and there have
been no other complaints ....

Please check if /etc/rcS.d/S02mountvirtfs is present, points
to /etc/init.d/mountvirtfs, and that mountvirtfs is at least
version 2.85-23.

Or maybe I misunderstand and the user upgraded from a broken
initscripts that apparently didn't mount /sys to a fixed one,
without rebooting ? In that case, stuff like that happens when
running "unstable". That's why it's called that. Things break
now and then .. all versions in "stable" and "testing" are OK.

> ----- Forwarded message from Aurelien Jarno <aurelien@aurel32.net> -----
>=20
> From: Aurelien Jarno <aurelien@aurel32.net>
>=20
> On Fri, Sep 03, 2004 at 02:43:45PM +0300, AKL. Mantas Kriauciunas wrote:
> [...]
> > I have sysvinit version 2.86-1 installed, but /sys dicectory is still
> > emply in my system. I'm using 2.6.5-1-k7 kernel image.
> > Maybe problem is in initscripts (version 2.86-1) package, I think
> > postinst of sysvinit and initscripts should check if /sys is mounted an=
d
> > if not - then call "/etc/init.d/mountvirtfs start", because I got
> > working /sys and lm-sensors when I did:

No it shouldn't just go out and mount /sys without asking.

> > dubrava:/home/mantas# /etc/init.d/mountvirtfs start
> > dubrava:/home/mantas# ls /sys/
> > block  bus  class  devices  firmware  power
> > dubrava:/home/mantas# /etc/init.d/lm-sensors start
> > Setting sensors limits: done.
> >=20
> > Should I report bug agains sysvinit and/or initscripts ?
> When you first reported the bug, I clone that bug to initscripts.
> However, as you don't answer, the maintainer of initscripts has close
> it. So, please reopen bug #266361 and don't complain to lm-sensors.
>=20
> ----- End forwarded message -----
>=20
> --=20
> Good luck,
> Mantas Kriau=C4=8Di=C5=ABnas <mantas@akl.lt>      Jabber ID: mantas@akl.l=
t
> Public organization "Open Source for Lithuania" - www.akl.lt
>=20
>=20
>=20

Revision history for this message

In Debian Bug tracker #266361, Thomas Hood (jdthood-aglu) wrote on 2004-11-18: no moreinfo

#18

No more info being forthcoming, we'll assume that this bug resulted from
misconfiguration of some sort (perhaps due to the chaotic history of
mountvirtfs in unstable). Closing.

--
Thomas Hood

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-11-18:

#19

Message-Id: <1100789200.5732.6.camel@thanatos>
Date: Thu, 18 Nov 2004 15:46:41 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: no moreinfo

No more info being forthcoming, we'll assume that this bug resulted from
misconfiguration of some sort (perhaps due to the chaotic history of
mountvirtfs in unstable). Closing.

--
Thomas Hood

Bug Watch Updater (bug-watch-updater) on 2006-09-27

Changed in sysvinit:
status:	Unknown → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	sysvinit (Debian)	Fix Released	Unknown	debbugs #266361
	sysvinit (Ubuntu)	Fix Released	High	Unassigned

Ubuntu
sysvinit package

/sys not mounted at boot on a 2.6 kernel

Bug Description

Other bug subscribers

Remote bug watches

Ubuntusysvinit package

/sys not mounted at boot on a 2.6 kernel

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
sysvinit package