Send CentOS-announce mailing list submissions to
centos-announce(a)centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request(a)centos.org
You can reach the person managing the list at
centos-announce-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
…
[View More]Today's Topics:
1. CESA-2013:1292 Moderate CentOS 5 kernel Update (Karanbir Singh)
----------------------------------------------------------------------
Message: 1
Date: Fri, 27 Sep 2013 13:27:33 +0000
From: Karanbir Singh <kbsingh(a)centos.org>
Subject: [CentOS-announce] CESA-2013:1292 Moderate CentOS 5 kernel
Update
To: centos-announce(a)centos.org
Message-ID: <20130927132733.GA6657(a)chakra.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2013:1292 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1292.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
a7e10caacf1fdd1e08e144495e71fe0e94f2310999603a90b89468e95bc84378 kernel-2.6.18-348.18.1.el5.i686.rpm
1b7276db4b4052672e8e02180c34547443ef98ef8fa7e1201ab65097c95133b1 kernel-debug-2.6.18-348.18.1.el5.i686.rpm
a7d7519839ea65828797fd5952bdb57d618ce4cedc8426af71c1c7609efe9db5 kernel-debug-devel-2.6.18-348.18.1.el5.i686.rpm
a5b4abe506beec8c7d273ff6a7eb1f0e902b5c4bd5bb71c0f46f1f8b3a38e7bb kernel-devel-2.6.18-348.18.1.el5.i686.rpm
79a4d84b1bba491e30e2c328a8369b5cb47ed0fd3cade4b895df8f33f940feac kernel-doc-2.6.18-348.18.1.el5.noarch.rpm
78908ea2f130e05f3eb374035b64f1f7fb094ec5d5d0c534981e3c1e041c3c03 kernel-headers-2.6.18-348.18.1.el5.i386.rpm
5e3b1755b02ee7f592908f85219d74f56d1d15690c8d8f16efcfef6f7356d410 kernel-PAE-2.6.18-348.18.1.el5.i686.rpm
61a8ad1bc7bd51e3de4564907ec8b5e0827bed7caed0280eeb4971affa6b1b27 kernel-PAE-devel-2.6.18-348.18.1.el5.i686.rpm
4c62299cf2b2f40ec498a8c6205627512a807c44c17be16748a328b9908e3b23 kernel-xen-2.6.18-348.18.1.el5.i686.rpm
8bf1ba60e90222113cf2599fe7a16a9125817231319cfbc4e26a5174af0c6e76 kernel-xen-devel-2.6.18-348.18.1.el5.i686.rpm
x86_64:
3de38207deb3d1a3ffb4320f1306c0600c3d00ea30ec60a18ad2651020b5b9cb kernel-2.6.18-348.18.1.el5.x86_64.rpm
183f34a264e9901700dd89521c891c14dbd45d9aa5ce3e2597df324006281bf2 kernel-debug-2.6.18-348.18.1.el5.x86_64.rpm
8944b1d2d73d91964dca2a80d84f17e1cc88b0e645d51e4c8159bdaa95d4f2a3 kernel-debug-devel-2.6.18-348.18.1.el5.x86_64.rpm
567c562993a1a9419d476267d7bf64471748219d6f13687b850f1b89b842772d kernel-devel-2.6.18-348.18.1.el5.x86_64.rpm
79a4d84b1bba491e30e2c328a8369b5cb47ed0fd3cade4b895df8f33f940feac kernel-doc-2.6.18-348.18.1.el5.noarch.rpm
9fca88447fd4e506e468d331a57dd04e9294757bf31ae7e6fe2d676605fa4540 kernel-headers-2.6.18-348.18.1.el5.x86_64.rpm
d3c98ef6884f552336fbea906e17478a612dbd63d521460f6acd8618b7c3e85b kernel-xen-2.6.18-348.18.1.el5.x86_64.rpm
902f0e407a109476bafcb412a3f59dcfe44c73d353188eec6c9debaece519105 kernel-xen-devel-2.6.18-348.18.1.el5.x86_64.rpm
Source:
a0d99df8dfcbcb99a9480c785716304671c0b63de2b9018c9eba21e277ae38c0 kernel-2.6.18-348.18.1.el5.src.rpm
--
Karanbir Singh
CentOS Project { http://www.centos.org/ }
irc: z00dax, #centos(a)irc.freenode.net
------------------------------
_______________________________________________
CentOS-announce mailing list
CentOS-announce(a)centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 103, Issue 17
************************************************
[View Less]
Hi,
I was wondering, why/when it is useful or when should I avoid to use LVM.
I think the big advantage of LVMing is if you modify (rezising, ...)
disk and filesystem layouts "a lot".
Are there any real pros or cons for following situations regarding e.g.
management and speed?
e.g.:
I do have a server system raid for which the disk layout will not
change; e.g. /var /usr /home will not change much in size.
OR
I do have some file storage shares (iscsi raids) up to some TB each on
one big …
[View More]storage device.
Sometimes (e.g. after a server crash) it is useful to remount the
storage to a different server.
Should I use LVM on the iscsi storage volumes?
Any suggestion and comment is welcome . Regards . Götz
--
Götz Reinicke
IT-Koordinator
Tel. +49 7141 969 82 420
Fax +49 7141 969 55 420
E-Mail goetz.reinicke(a)filmakademie.de
Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de
Eintragung Amtsgericht Stuttgart HRB 205016
Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg
Geschäftsführer: Prof. Thomas Schadt
[View Less]
On Thu, 26 Sep 2013, Robert Heller wrote:
> OK, this is what you need to do:
>
> Create a file named /lib/udev/rules.d/90-local.rules containing this line:
>
> SUBSYSTEMS=="usb", ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="5611", GROUP="scanner", MODE="0660"
>
>
> (This means: on the USB subsystem, for a device with vendor id 03f0 (HP), and
> product id 5611 (Photosmart C3180), change its group to 'scanner', and its
> mode to 0660.)
>
> then execute this …
[View More]command (probably not needed, but can't hurt):
>
> udevadm control --reload-rules
>
> make sure there is a group named 'scanner' and that you are a member of it
> (yes, you have to logout/login again to get the group update).
>
> unplug and re plug in the device. The device file fill now be in group scanner
> with group rw permission and anyone in the scanner group can run hp-scan and
> access the scanner (note it probably won't be /dev/bus/usb/001/006, but
> something else (/dev/bus/usb/001/007 probably and /dev/bus/usb/001/006 will vanish).
That did the trick.
I used lp instead of scanner because I'd already made myself a member of lp.
Thanks.
> I don't know if this will bork things if you plan to use this thing as a
> printer under CentOS (I am not sure what user the CUPS daemon runs as). If
> necessary, you might need to tweek the rules file to be compatible with CUPS
> or add the UID used by the CUPS daemon to 'scanner'.
Printing works fine.
The only issue I've noticed is that if I leave paper in the all-in-one,
it wants to copy, not just scan.
I'm not sure whether that is a change.
It's been an OS ago since I wanted to scan.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
[View Less]
greetings list,
i am creating a new thread because of comment made by;
From: Nicolas Thierry-Mieg <Nicolas.Thierry-Mieg(a)imag.fr>
in thread "Subject: [CentOS] erase disk".
in past readings about;
erasing an hdd, forensics of hard disk drives, dban, destroying hdd
i submit these links for those who may wish to further their
knowledge on primaries of hdd forensics;
hard disk drive forensics - Ixquick Web Search
https://ixquick.com/do/search?q=%22hard+disk+drive+forensics%22&…
[View More]amp;lui=english
About 28 results
hdd forensics - Ixquick Web Search
https://ixquick.com/do/search?q=%22hdd+forensics%22&lui=english
About 8,410 results
forensics of hard disk drive - Ixquick Web Search
https://ixquick.com/do/search?q=%22forensics+of+hard+disk+drive%22&lui=engl…
About 5 results [actually, 1]
forensics of hdd - Ixquick Web Search
https://ixquick.com/do/search?q=forensics+of+hdd&lui=english
About 819,695 results
of the above, #3 relates to a book;
Spin-stand Microscopy of Hard Disk Data
(Elsevier Series in Electromagnetism) [Hardcover]
which is available thru "amazon.com" and i would imagine other good
book supplies.
at amazon, there is;
/*quote
Book Description
Publication Date: April 11, 2007 | ISBN-10: 0080444652 |
ISBN-13: 978-0080444659 | Edition: 1
This book provides an in-depth exposition of spin-stand microscopy
of hard disk data which is a new technique recently developed and
extensively tested by the authors of the book. Spin-stand microscopy
is the first magnetic imaging technique where imaging is performed
ex-situ on a rotating disk mounted on a spin-stand. This technique
is one of the fastest scanning-based microscopy techniques. It is
non-invasive and has nano-scale resolution. For these reasons, it
provides unique capabilities for the visualization of magnetization
patterns recorded on hard disks.
/*etouq
i do not have book, tho if i have $237.50 and nothing better to
spend it on, i may purchase it.
as can be seen by "results" of above links, there is a lot of
information available related to "Subject:".
something that, in my current and passed readings, many do not
seem aware of is that even tho 'dban' can be use to remove data,
it _does_not_ guarantee removing, beyond recovery, data on a hard
disk.
head gap wear and bearing wear factor in highly as to whether or
not data can be readily recovered, and to a greater factor, if
hdd is mounted vertical or horizontal.
if one wishes, as mentioned in two of post, "sledge hammer" and
"hydraulic wedge", are good ways.
much better, and more assured is 'degaussing' disk platters, even
which will leave a small bias.
best way, of insuring data removal is to scrape disks clean of
coating, or to burn off coating. i have used latter.
--
peace out.
in a world with out fences, who needs gates.
tc.hago.
g
.
[View Less]
mkfs.ext4 fails to create 38TB file system on CentOS 6.4 64bit with this
error:
mkfs.ext4: Size of device /dev/vg02/vtapes too big to be expressed in 32
bits
using a blocksize of 4096.
More details follow:
# uname -a
Linux tzbackup 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
# fdisk -l /dev/sdc
Disk /dev/sdc: 41996.7 GB, 41996727091200 bytes
255 heads, 63 sectors/track, 5105811 cylinders
Units = cylinders of 16065 * 512 = 8225280 …
[View More]bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
# pvdisplay /dev/sdc
--- Physical volume ---
PV Name /dev/sdc
VG Name vg02
PV Size 38.20 TiB / not usable 4.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 10012799
Free PE 0
Allocated PE 10012799
PV UUID qGIgYy-Q8N2-xUjM-58Zb-uEnu-qFNY-NGjkhx
# vgdisplay /dev/vg02
--- Volume group ---
VG Name vg02
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 0
Max PV 0
Cur PV 1
Act PV 1
VG Size 38.20 TiB
PE Size 4.00 MiB
Total PE 10012799
Alloc PE / Size 10012799 / 38.20 TiB
Free PE / Size 0 / 0
VG UUID T1jUYU-wBTG-u0aN-AtYV-iFf8-S6Hw-zMuacu
# lvdisplay /dev/vg02/vtapes
--- Logical volume ---
LV Path /dev/vg02/vtapes
LV Name vtapes
VG Name vg02
LV UUID 6cktBz-ayFL-5XVp-kVEp-4giU-A1Kc-Jjf2UV
LV Write Access read/write
LV Creation host, time tzbackup, 2013-09-20 13:29:30 -0700
LV Status available
# open 0
LV Size 38.20 TiB
Current LE 10012799
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:8
# mkfs.ext4 -b 4096 /dev/vg02/vtapes
mke2fs 1.41.12 (17-May-2010)
mkfs.ext4: Size of device /dev/vg02/vtapes too big to be expressed in 32
bits
using a blocksize of 4096.
Any idea?
Thanks,
-- Peter
[View Less]
Michael Hennebry wrote:
> On Thu, 26 Sep 2013, Robert Heller wrote:
>
>> It looks like to use the scanner you need to edit your /etc/group file
or use the user manager to add yourself to the lp group.
>
> That did not work.
> I ran a separate login to get one that admitted I was in the lp group.
Applying strace to hp-scan told me that it could not open
> /dev/bus/usb/001/006 for writing.
> Its owner and group are both root.
I'll try again.
google for centos 6 …
[View More]scanner ownership permissions
The first hit I got is a thread on this list from '11 or last year. The
last post in the thread ends with:
Excerpt:
Actual fix:
1) # scanimage -L
device `epkowa:interpreter:001:005' is a Epson (unknown model) flatbed
scanner
to get the bus and the device (in the above, bus = 001; device = 005)
2) "lsusb" to get the ID
# lsusb | grep -i "bus 001" | grep -i "device 005"
Bus 001 Device 005: ID 04b8:0131 Seiko Epson Corp.
3) cd to the udev "sane" directory
# cd /etc/udev/rules.d
4) find the "sane" configuration file.
# ls | grep -i sane
60-libsane.rules
5) add an entry into the sane configuration file for your scanner.
Note: the ATTRS{idVendor} is the first half of your ID above (04b8)
the ATTRS{idProduct} is the second half of your ID above (0131)
the name in the comments you make up yourself
if you put all your users into group "users", then use "users" for the
group below. If you use a different group for each user, then create a
group called "scanners" (groupadd scanners), use "scanners" for
the group below, and add each user to the "scanners" group
# Epkowa Epson Perfection V300
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0131",
ENV{libsane_matched}="yes", MODE="0664", OWNER="root", GROUP="users" ---
end excerpt ---
Modify to fit your system and device.
mark
[View Less]
On Thu, 26 Sep 2013, Robert Heller wrote:
> It looks like to use the scanner you need to edit your /etc/group file or use
> the user manager to add yourself to the lp group.
That did not work.
I ran a separate login to get one that admitted I was in the lp group.
Applying strace to hp-scan told me that it could not open
/dev/bus/usb/001/006 for writing.
Its owner and group are both root.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten …
[View More]class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
[View Less]
On Wed, 25 Sep 2013, Robert Heller wrote:
> At Wed, 25 Sep 2013 13:34:51 -0600 CentOS mailing list <centos(a)centos.org> wrote:
> The proper cure for this is to add yourself to the group that udev puts the
> device in. Look in /etc/udev/rules.d. Under CentOS 5 with hplip3-common
> installed, this would be 55-hpmud.rules.
I'm running centos 6.
Googling tells me the corresponding centos 6 directory is /lib/udev/rules.d .
There are no files with 55 or hp in their names,
but …
[View More]there are 39 with the string usb .
Where should I be looking?
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"On Monday, I'm gonna have to tell my kindergarten class,
whom I teach not to run with scissors,
that my fiance ran me through with a broadsword." -- Lily
[View Less]