Re: mount /proc at boot as read-only

2019-01-06 Thread valdis . kletnieks
On Sun, 06 Jan 2019 21:13:26 +0300, Lev Olshvang said: > I am trying to harden the embedded system. > I have embedded system with systemd . OK, you've already got a problem right there. It's an embedded system. Therefor, you know everything that should be running, and what order it should

mount /proc at boot as read-only

2019-01-06 Thread Lev Olshvang
Hello all, I am trying to harden the embedded system. Is it possible and safe to mount /proc file system in a read-only mode and how to do this? I have embedded system with systemd where /proc is mounted rw. I suspect that systemd mounts it when it bebgns to bootsrtap user space. On my

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Jay Aurabind
On Sun, 6 Jan 2019 at 19:37, Valentin Vidic wrote: > On Sun, Jan 06, 2019 at 06:58:09PM +0530, Jay Aurabind wrote: > > I do not have any /dev/i2c* listings. Besides, these are the only modules > > with i2c in their names: > > If not i2c than it could be this load path: > > modules.alias:alias

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Valentin Vidic
On Sun, Jan 06, 2019 at 06:58:09PM +0530, Jay Aurabind wrote: > I do not have any /dev/i2c* listings. Besides, these are the only modules > with i2c in their names: If not i2c than it could be this load path: modules.alias:alias acpi*:HPQ6007:* hp_accel modules.alias:alias acpi*:HPQ6000:*

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Jay Aurabind
On Sun, 6 Jan 2019 at 18:32, Valentin Vidic wrote: > On Sun, Jan 06, 2019 at 06:17:44PM +0530, Jay Aurabind wrote: > > Apparently it could be both I2C or SPI, as I find lis3lv02d_spi.c as > well. > > I don't really know if this device sits on I2C bus or SPI. > > Yes, but you can check lsmod

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Valentin Vidic
On Sun, Jan 06, 2019 at 06:17:44PM +0530, Jay Aurabind wrote: > Apparently it could be both I2C or SPI, as I find lis3lv02d_spi.c as well. > I don't really know if this device sits on I2C bus or SPI. Yes, but you can check lsmod after boot to see if i2c driver was loaded. Also you can try to list

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Jay Aurabind
On Sun, 6 Jan 2019 at 16:49, Valentin Vidic wrote: > On Sun, Jan 06, 2019 at 02:22:34PM +0530, Jay Aurabind wrote: > > The subject line might be a bit dramatic, but I assure you my question is > > isn't. > > > > I have a 3-axis accelerometer (LIS3LV02DL) in my laptop which shows up as > > an

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Valentin Vidic
On Sun, Jan 06, 2019 at 02:22:34PM +0530, Jay Aurabind wrote: > The subject line might be a bit dramatic, but I assure you my question is > isn't. > > I have a 3-axis accelerometer (LIS3LV02DL) in my laptop which shows up as > an input device. Since its x86, I am assuming the necessary

Re: The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Greg KH
On Sun, Jan 06, 2019 at 02:22:34PM +0530, Jay Aurabind wrote: > Hi, > > The subject line might be a bit dramatic, but I assure you my question is > isn't. > > I have a 3-axis accelerometer (LIS3LV02DL) in my laptop which shows up as > an input device. Since its x86, I am assuming the necessary

The Kernel knows. But how ? Did the acpi make a secret dead drop ?

2019-01-06 Thread Jay Aurabind
Hi, The subject line might be a bit dramatic, but I assure you my question is isn't. I have a 3-axis accelerometer (LIS3LV02DL) in my laptop which shows up as an input device. Since its x86, I am assuming the necessary information was encoded in ACPI Tables. But I cannot find any mention of this