*ahem* execustion?

2009-10-20 Diskussionsfäden Thomas Neumann
hiya

lib/fai/subroutines:
  echo "WARNING: Skipping $hfile execustion because it's not executable."
  echo "WARNING: Skipping $hfile.source execustion because it's not
executable."
lib64/fai/subroutines:
  echo "WARNING: Skipping $hfile execustion because it's not executable."
  echo "WARNING: Skipping $hfile.source execustion because it's not
executable."

found in 3.2.16 or 3.2.20


I guess noone besides me has non-executable scripts. ;)
(I use them for documentation purposes.)

tschüß
thomas



Re: *ahem* execustion?

2009-10-20 Diskussionsfäden Henning Sprang
Hi Thomas,

Thomas Neumann wrote:
> lib/fai/subroutines:
>   echo "WARNING: Skipping $hfile execustion because it's not executable."
>   echo "WARNING: Skipping $hfile.source execustion because it's not
> executable."
> lib64/fai/subroutines:
>   echo "WARNING: Skipping $hfile execustion because it's not executable."
>   echo "WARNING: Skipping $hfile.source execustion because it's not
> executable."
> 
> found in 3.2.16 or 3.2.20

O.K., but what do you want tp point us to?
The typo?

yeah, it's wrong, but it's not such a big problem. Even, sometimes,
typos can be good - as Harald Welte when it comes to detect GPL code
pieces in proprietary products :)

> I guess noone besides me has non-executable scripts. ;)

And those people who forget to make their files in scripts executable.
They need to be notified, that's what the warnings ar for (in case
that's your question).


Henning


Re: *ahem* execustion?

2009-10-20 Diskussionsfäden Thomas Neumann
[resend because of wrong sender address -_-;;]

hiya

[execustion]
> O.K., but what do you want tp point us to?
> The typo?

Yes.

tschüß
thomas




Re: setup-storage: error

2009-10-20 Diskussionsfäden Michael Tautschnig
Sorry for this full-quote; I think it might be useful if you could add your
information to the bug reported as #404927 (http://bugs.debian.org/404927) for
udev people to work around this or kernel folks fix this.

Best,
Michael

[...]

> 
> I get the same problem here on an IBM 3950, my sda device belongs to
> group floppy.
> I use a Lenny nfsroot.
> 
> there is something about that in the udev rules : (91-permissions.rules)
> # default permissions for block devices
> SUBSYSTEM=="block", GROUP="disk"
> # the aacraid driver is broken and reports that disks removable (see
> #404927)
> SUBSYSTEM=="block", ATTRS{removable}=="1", \
> DRIVERS!="aacraid", GROUP="floppy"
> 
> but I doesn't seems to work well...
> 
> # udevinfo -a -p `udevinfo -q path -n /dev/sda` |less
> 
> Udevinfo starts with the device specified by the devpath and then
> walks up the chain of parent devices. It prints for every device
> found, all possible attributes in the udev rules key format.
> A rule to match, can be composed by the attributes of the device
> and the attributes from one single parent device.
> 
>   looking at device '/block/sda':
> KERNEL=="sda"
> SUBSYSTEM=="block"
> DRIVER==""
> ATTR{range}=="16"
> ATTR{removable}=="1"
> ATTR{size}=="715776000"
> ATTR{capability}=="13"
> ATTR{stat}=="   18411 848538139 8224 8355   468795
> 2432659   946228013240   954448"
> 
>   looking at parent device
> '/devices/pci:01/:01:02.0/host0/target0:0:0/0:0:0:0':
> KERNELS=="0:0:0:0"
> SUBSYSTEMS=="scsi"
> DRIVERS=="sd"
> ATTRS{device_blocked}=="0"
> ACTION!="add|change", GOTO="permissions_end"
> 
> SUBSYSTEMS=="scsi"
> DRIVERS=="sd"
> ATTRS{device_blocked}=="0"
> ATTRS{type}=="0"
> ATTRS{scsi_level}=="3"
> ATTRS{vendor}=="IBM "
> ATTRS{model}=="A   "
> ATTRS{rev}=="V1.0"
> ATTRS{state}=="running"
> ATTRS{timeout}=="45"
> ATTRS{iocounterbits}=="32"
> ATTRS{iorequest_cnt}=="0x6b48"
> ATTRS{iodone_cnt}=="0x6b48"
> ATTRS{ioerr_cnt}=="0x1"
> ATTRS{modalias}=="scsi:t-0x00"
> ATTRS{evt_media_change}=="0"
> ATTRS{queue_depth}=="256"
> ATTRS{queue_type}=="ordered"
> ATTRS{level}=="RAID5"
> 
>   looking at parent device
> '/devices/pci:01/:01:02.0/host0/target0:0:0':
> KERNELS=="target0:0:0"
> SUBSYSTEMS==""
> DRIVERS==""
> 
>   looking at parent device '/devices/pci:01/:01:02.0/host0':
> KERNELS=="host0"
> SUBSYSTEMS==""
> DRIVERS==""
> 
>   looking at parent device '/devices/pci:01/:01:02.0':
> KERNELS==":01:02.0"
> SUBSYSTEMS=="pci"
> DRIVERS=="aacraid"
> ATTRS{vendor}=="0x9005"
> ATTRS{device}=="0x0285"
> ATTRS{subsystem_vendor}=="0x1014"
> ATTRS{subsystem_device}=="0x02f2"
> ATTRS{class}=="0x010400"
> ATTRS{irq}=="28"
> ATTRS{local_cpus}==""
> ATTRS{local_cpulist}=="0-15"
> 
> ATTRS{modalias}=="pci:v9005d0285sv1014sd02F2bc01sc04i00"
> ATTRS{numa_node}=="0"
> ATTRS{enable}=="1"
> ATTRS{broken_parity_status}=="0"
> ATTRS{msi_bus}==""
> 
>   looking at parent device '/devices/pci:01':
> KERNELS=="pci:01"
> SUBSYSTEMS==""
> DRIVERS==""
> 
> 
> 
> My workaround for now is to accept devices recognised as "floppy"...
> /srv/fai/nfsroot/lenny-i386/live/filesystem.dir/usr/lib/fai/disk-info
> 
> [ `stat -c %G /dev/$device` = "disk" ] || [ `stat -c %G /dev/$device` =
> "floppy" ] || isdisk=0
> 
> It's not the best way, but it do the trick...
> 
> -- 
> Mathieu Alorent
> Shell&Core Sophia-Antipolis
> AUSY
> Pour France Telecom – OPF/PORTAILS/DOP/HEBEX/SOPHIA
> 
> Tél: 04 97 12 6226
> 
> malorent@orange-ftgroup.com
> 
> La signature de ce mail peut être vérifiée en installant les autorités de 
> certifications CAcert suivantes :
> http://www.cacert.org/certs/root.crt
> http://www.cacert.org/certs/class3.crt




pgp2ERXTH9pIx.pgp
Description: PGP signature