Re: where would i find the header file for ext4 and inode layout?
On 13 Mar 2011, at 22:16, Robert P. J. Day wrote:
On Sun, 13 Mar 2011, Matt Willsher wrote:
On Mar 13, 2011 8:50 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Sun, 13 Mar 2011, Matt Willsher wrote:
On 13 March 2011 20:30, Robert P. J. Day rpj...@crashcourse.ca wrote:
as part of my sys admin course this week, i'd like to show the
students the actual header file that displays the structure of the
ext4 filesystem (inode, superblock, that sort of thing). but i'm
not
sure where that header file is.
i have the kernel-devel and kernel-headers packages installed and
i
would have assumed the file (or files) would be somewhere under
/usr/include/{linux,sys} but i'm just not seeing it. help?
It seems to be called ext4.h. Does find /usr/include -name ext4.h
-print find it?
i'm just reinstalling in prep for class so i'll check it as soon as
my system is up again. i swear i searched for the pattern *ext4*, so
let's see if it's different this time. thanks.
Was that *ext4* single quoted? If not bash seems to grab that glob
and find the doesn't get passed what you want (at least I think that
is what happens). If you're not too fussy about the source of the
file, Google shows up a ext4.h with a search for the same.
currently, i have no ext4.h header file anywhere under /usr/include,
and i have both packages kernel-devel and kernel-headers installed.
i'm sure i'm doing something stupid.
Sorry, I replied off list before. I've put it back on in case anyone else can
help.
What about the kernel SRPM? In the SL6 kernel SRPM there is a tar.bz2 file
which contains the full source including fs/ext4/ext4.h and a bunch of other
related headers. SL5 will be similar I would think.
gnome desktop with garbled letters and glibc problems
Hi,
I'm trying 6.0 version out if it is a good choice for production servers. This
is not an major issue, just a pain in the ass. All the letters on the Gnome
Desktop (i think) are all garbled. Tried looking language packs with no luck.
i18n is configured to use en.US utf-8. There isnt a xorg.conf to configure the
language. Maybe its deprecated. Anybody have a solution for this one? Maybe it
works after selecting during install, but I tried the minimal install to see
just how minimal it is. Another problem, there seem to be 2 glibc packages with
different versions and I cant delete either of them. Had to exclude glibc* in
yum.conf in order to update recent packages. We wont be using them as desktops,
I have Ubuntu for that. But this should work out of the box in my opinion.
Glibc
is a far more serious issue. I want the newest version, of course. Anyways keep
up the good work. Thinking about changing from CentOS to SL but I am not so
sure
anymore.
-- Running transaction check
-- Processing Dependency: glibc-common = 2.12-1.7.el6 for package:
glibc-2.12-1.7.el6.i686
--- Package glibc-common.i686 0:2.12-1.7.el6_0.3 set to be updated
-- Finished Dependency Resolution
Error: Package: glibc-2.12-1.7.el6.i686
(@anaconda-ScientificLinux-201103021620.i386/6)
Requires: glibc-common = 2.12-1.7.el6
Removing: glibc-common-2.12-1.7.el6.i686
(@anaconda-ScientificLinux-201103021620.i386/6)
glibc-common = 2.12-1.7.el6
Updated By: glibc-common-2.12-1.7.el6_0.3.i686 (sl-security)
glibc-common = 2.12-1.7.el6_0.3
You could try using --skip-broken to work around the problem
glibc-2.12-1.7.el6_0.3.i686 is a duplicate with glibc-2.12-1.7.el6.i686
glibc-2.12-1.7.el6_0.3.i686 has missing requires of glibc-common = ('0',
'2.12',
'1.7.el6_0.3')
tzdata-2010o-1.el6.noarch is a duplicate with tzdata-2010l-1.el6.noarch
Bestu kveðjur/Best regards,
Sigurður Jónsson
Re: SL6 livecd and md RAID partitions - danger
On Sunday 13 March 2011 3:16 pm, Urs Beyerle wrote: On 03/13/2011 07:46 PM, Tom H wrote: On Sun, Mar 13, 2011 at 1:33 PM, Urs Beyerleurs.beye...@env.ethz.ch wrote: As part of upgrade planning for my main workstation at home (an updated SL 5.2 system), I booted from the live CD just to see if all the major devices worked. Everything worked :). Unfortunately, that act rendered my existing system unbootable. When I booted from the live CD it found and started my md RAID1 partitions, including my system root partition. Nice, I had all my data there to play with. I noticed that where I had previously used /dev/md0, /dev/md1, etc..., the live CD system had created them as /dev/md122, /dev/md123, and so on, and not in the original order. I didn't think much of this, figuring my regular system would start them back in the original configuration, but apparently some metadata somewhere got changed by the live CD system and now the original system would not get past switching to the root file system with a 'no such device' error. I could see, just before going off the screen, where it had started my root partition as /dev/md125 rather than /dev/md0. I tried a couple of things to recover from this: I tried stopping and reassembling the RAID sets with the desired device names from the live CD system, and repackaging my initrd with device files for the /dev/md12* devices, but no luck. At that point I decided that, since I had already done my backups and was planning on eventually going to SL6, that I'd just push forward with a fresh install of SL6. It took a few hours that I hadn't planned on to get everything back up to speed, and I have one issue yet to work and a couple of minor things to configure. I have another retired box with the same RAID setup and it too, got hosed by the live CD. I'm going to play with this box to see if I can find a way to recover from this. Beware. Thanks for letting us know! I would be very interesting in a recovery procedure. I guess that it should be possible to re-assemble the raid device. So in case /dev/md0 was renamed to /dev/125 and was setup with /dev/sda1 /dev/sdb1, you may get /dev/md0 back, if you do mdadm --stop /dev/125 mdadm --assemble /dev/md0 /dev/sda1 /dev/sdb1 Are your raid partition of the type 0xfd (Linux RAID autodetect) or 0x83 (Linux)? If this is a general problem with the LiveCD and software raids, I would like to fix it on the LiveCD. Usually md devices are renamed/renumbered when /etc/mdadm.conf has HOMEHOSTsystem set and the metadata in the superblock has a different homehost value. The file /etc/mdadm.conf does not exist on the LiveCD. Therefore the md devices should not be renamed...? Bluejay, do you see /etc/mdadm.conf, if you boot your system with the LiveCD? I had a similar problem with disks when I lost a system disk and needed to rebuild the file system. Thank god I had a hard copy of print out of df before it crashed. This is crude but effective. I used the install disks - got to the area that allowed me to set up and format hard disks. I named them correctly, and organized the data as on hard copy. The data is still there but the install program plays dumb but will allow you to rename everything - set do not format. Continue and when it gets to asking for application - bail out. (reboot) and you are there. Now you have to work on /etc/fstab to make all drives physical mounts. (get rid of logical drive names). Once this is done you should be able to reboot and recover you old data. You will notice that you have a new fstab. After you have everyting saved to a back up. Then you can replace disks / rename them and use the same scheme to restore you system to use LVM. A hard way around the apple tree but sometimes it's desperate measures by desperate men. Its crude / rude but effective. A very usefull utility would be a partial install disk that allows you to do disk management and quit the install. Larry Linder
Re: gnome desktop with garbled letters and glibc problems
All the letters on the Gnome Desktop (i think) are all garbled. Tried looking language packs with no luck. i18n is configured to use en.US utf-8. There isnt a xorg.conf to configure the language. Maybe its deprecated. Anybody have a solution for this one? Maybe it works after selecting during install, but I tried the minimal install to see just how minimal it is. Try yum groupinstall Fonts I ran into something like that after a minimal install and installing the desktop stuff manually. All the characters appeared as little blocks. - Bluejay Adametz First things first -- but not necessarily in that order - The Doctor NOTICE: This message, including any attachments, is only for the use of the intended recipient(s) and may contain confidential and privileged information, or information otherwise protected from disclosure by law. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, copying, dissemination or distribution of this message or any of its attachments is strictly prohibited. If you received this message in error, please contact the sender immediately by reply email and destroy this message, including all attachments, and any copies thereof.
Re: where would i find the header file for ext4 and inode layout?
On 13 March 2011 20:50, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Sun, 13 Mar 2011, Matt Willsher wrote:
On 13 March 2011 20:30, Robert P. J. Day rpj...@crashcourse.ca wrote:
as part of my sys admin course this week, i'd like to show the
students the actual header file that displays the structure of the
ext4 filesystem (inode, superblock, that sort of thing). but i'm
not
sure where that header file is.
i have the kernel-devel and kernel-headers packages installed and
i
would have assumed the file (or files) would be somewhere under
/usr/include/{linux,sys} but i'm just not seeing it. help?
It seems to be called ext4.h. Does find /usr/include -name ext4.h
-print find it?
i'm just reinstalling in prep for class so i'll check it as soon as
my system is up again. i swear i searched for the pattern *ext4*, so
let's see if it's different this time. thanks.
Robert,
Are you asking wrt SL 5 or SL 6 ? If you would please clarify, I'll
then have a poke about on my systems. :-)
Alan.
Re: where would i find the header file for ext4 and inode layout?
On 03/13/2011 03:50 PM, Robert P. J. Day wrote:
On Sun, 13 Mar 2011, Matt Willsher wrote:
On 13 March 2011 20:30, Robert P. J. Dayrpj...@crashcourse.ca wrote:
as part of my sys admin course this week, i'd like to show the
students the actual header file that displays the structure of the
ext4 filesystem (inode, superblock, that sort of thing). but i'm
not
sure where that header file is.
i have the kernel-devel and kernel-headers packages installed and
i
would have assumed the file (or files) would be somewhere under
/usr/include/{linux,sys} but i'm just not seeing it. help?
It seems to be called ext4.h. Does find /usr/include -name ext4.h
-print find it?
i'm just reinstalling in prep for class so i'll check it as soon as
my system is up again. i swear i searched for the pattern *ext4*, so
let's see if it's different this time. thanks.
rday
For SL6
# locate ext4.h
/usr/src/kernels/2.6.32-71.14.1.el6.x86_64/include/trace/events/ext4.h
/usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h
/usr/src/kernels/2.6.32-71.el6.x86_64/include/trace/events/ext4.h
# rpm -qf
/usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h
kernel-devel-2.6.32-71.18.2.el6.x86_64
#
Troy
--
__
Troy Dawson daw...@fnal.gov (630)840-6468
Fermilab ComputingDivision/SCF/FEF/SLSMS Group
__
Change of email.
Hi, I want to change my email, from: pcav...@gmail.com to pcavero.scienti...@gmail.com. How to I can do this?? or if I need to unsubscribe the first account, and then subscribe the another, How to I can do. Best Regards, Pablo Cavero Systems Engineer 568 - 920 9509
Re: Change of email.
On 03/14/2011 09:01 AM, Pablo Cavero wrote: Hi, I want to change my email, from: pcav...@gmail.com mailto:pcav...@gmail.com to pcavero.scienti...@gmail.com mailto:pcavero.scienti...@gmail.com. How to I can do this?? or if I need to unsubscribe the first account, and then subscribe the another, How to I can do. Best Regards, Pablo Cavero Systems Engineer 568 - 920 9509 Generally, yes, that is usually the easiest way. Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/SCF/FEF/SLSMS Group __
Re: where would i find the header file for ext4 and inode layout?
On Mon, 14 Mar 2011, Alan Bartlett wrote:
On 13 March 2011 20:50, Robert P. J. Day rpj...@crashcourse.ca wrote:
On Sun, 13 Mar 2011, Matt Willsher wrote:
On 13 March 2011 20:30, Robert P. J. Day rpj...@crashcourse.ca wrote:
as part of my sys admin course this week, i'd like to show the
students the actual header file that displays the structure of the
ext4 filesystem (inode, superblock, that sort of thing). but i'm
not
sure where that header file is.
i have the kernel-devel and kernel-headers packages installed and
i
would have assumed the file (or files) would be somewhere under
/usr/include/{linux,sys} but i'm just not seeing it. help?
It seems to be called ext4.h. Does find /usr/include -name ext4.h
-print find it?
i'm just reinstalling in prep for class so i'll check it as soon as
my system is up again. i swear i searched for the pattern *ext4*, so
let's see if it's different this time. thanks.
Robert,
Are you asking wrt SL 5 or SL 6 ? If you would please clarify, I'll
then have a poke about on my systems. :-)
SL 6. i can't believe i'm having trouble tracking it down.
rday
--
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
Re: a few questions about SL admin best practises
On Sat, Mar 12, 2011 at 12:06:56AM -0800, Garrett Holmstrom wrote: gholms@luna ~ % mount | grep ext /dev/sda1 on /boot type ext4 (rw) In the LVM way of things, if I connect this disk to another computer, would these /boot partitions collide and prevent the computer from booting? (I guess one can hot-plug this disk to avoid the boot problem) (in the md world, separate unmanaged /boot partitions are not required) -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: where would i find the header file for ext4 and inode layout?
On 14 March 2011 14:40, Robert P. J. Day rpj...@crashcourse.ca wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: Are you asking wrt SL 5 or SL 6 ? If you would please clarify, I'll then have a poke about on my systems. :-) SL 6. i can't believe i'm having trouble tracking it down. The ext4.h file is exactly were Troy said it would be -- [quote] # rpm -qf /usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h kernel-devel-2.6.32-71.18.2.el6.x86_64 # [/quote] Unless, of course, that is not what you need? Alan.
Re: where would i find the header file for ext4 and inode layout?
On Mon, 14 Mar 2011, Alan Bartlett wrote: On 14 March 2011 14:40, Robert P. J. Day rpj...@crashcourse.ca wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: Are you asking wrt SL 5 or SL 6 ? If you would please clarify, I'll then have a poke about on my systems. :-) SL 6. i can't believe i'm having trouble tracking it down. The ext4.h file is exactly were Troy said it would be -- [quote] # rpm -qf /usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h kernel-devel-2.6.32-71.18.2.el6.x86_64 # [/quote] Unless, of course, that is not what you need? but the fact that that's under /usr/src/kernels suggests (normally) that that's part of a kernel *source* package. i'm pretty sure i've previously seen it as part of something like kernel-headers -- i should not have to download the kernel source to get kernel structure header files. i'll poke around some more. rday -- Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday
Re: where would i find the header file for ext4 and inode layout?
On 14 March 2011 16:39, Robert P. J. Day rpj...@crashcourse.ca wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: The ext4.h file is exactly were Troy said it would be -- [quote] # rpm -qf /usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h kernel-devel-2.6.32-71.18.2.el6.x86_64 # [/quote] Unless, of course, that is not what you need? but the fact that that's under /usr/src/kernels suggests (normally) that that's part of a kernel *source* package. Nooo. You've missed the subtlety of Troy's post. Take another look at what I quoted. The file come from the kernel-devel package. So just -- sudo yum install kernel-devel -- and you will have the file. :-) Alan.
Re: where would i find the header file for ext4 and inode layout?
On 14 Mar 2011, at 16:43, Alan Bartlett a...@elrepo.org wrote: On 14 March 2011 16:39, Robert P. J. Day rpj...@crashcourse.ca wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: The ext4.h file is exactly were Troy said it would be -- [quote] # rpm -qf /usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4.h kernel-devel-2.6.32-71.18.2.el6.x86_64 # [/quote] Unless, of course, that is not what you need? but the fact that that's under /usr/src/kernels suggests (normally) that that's part of a kernel *source* package. Nooo. You've missed the subtlety of Troy's post. Take another look at what I quoted. The file come from the kernel-devel package. So just -- sudo yum install kernel-devel They don't appear to be what was being looked for - those files look like they are for diags and tracing (systap stuff?) rather than the actual inode structs etc.
Re: where would i find the header file for ext4 and inode layout?
On Monday, March 14, 2011 17:51:46 Robert P. J. Day wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: On 14 March 2011 16:39, Robert P. J. Day rpj...@crashcourse.ca wrote: On Mon, 14 Mar 2011, Alan Bartlett wrote: The ext4.h file is exactly were Troy said it would be -- [quote] # rpm -qf /usr/src/kernels/2.6.32-71.18.2.el6.x86_64/include/trace/events/ext4. h kernel-devel-2.6.32-71.18.2.el6.x86_64 # [/quote] Unless, of course, that is not what you need? but the fact that that's under /usr/src/kernels suggests (normally) that that's part of a kernel *source* package. Nooo. You've missed the subtlety of Troy's post. Take another look at what I quoted. The file come from the kernel-devel package. So just -- sudo yum install kernel-devel -- and you will have the file. :-) i'm fairly familiar with the layout of the kernel source and i can assure you that that ext4.h file above doesn't represent the layout of the ext4 filesystem. it's under the include/trace/events directory so it's clearly related to system tracing, not filesystem structure. let's just put all this on hold until i have the time this evening to do a more thorough search. just try yum whatprovides */ext4.h to find out what rpms contain that file. Cheers, Andreas
Re: SL6 livecd and md RAID partitions - danger
On Sun, Mar 13, 2011 at 3:16 PM, Urs Beyerle urs.beye...@env.ethz.ch wrote: On 03/13/2011 07:46 PM, Tom H wrote: Usually md devices are renamed/renumbered when /etc/mdadm.conf has HOMEHOSTsystem set and the metadata in the superblock has a different homehost value. The file /etc/mdadm.conf does not exist on the LiveCD. Therefore the md devices should not be renamed...? Bluejay, do you see /etc/mdadm.conf, if you boot your system with the LiveCD? I've checked the Live CD that I have and it doesn't have /etc/mdadm.conf. The install that I made with the Live CD does have one though, which I find confusing because I thought (incorrectly it seems) that a Live CD install is made from the same image as the Live CD itself. It doesn't have HOMEHOSTsystem but it is set to automount some arrays. I don't know through what mechanism arrays are renamed when they are assembled on a foreign box and *stay*renamed* when are re-assembled on the home box. I know that it's happened to me and others with more than one distribution and that the resolution is to boot from a rescue disk, run hostname host, and assemble the array(s) with --update=homehost.
Scientific Linux ALPHA 2 SL 5.6 for x86_64
Available from ftp://ftp.scientificlinux.org/linux/scientific/5rolling/x86_64/ Scientific Linux ALPHA 2 SL 5.6 for x86_64 March 14, 2011 Updated to latest kernel so needed new kernel-modules kernel-module-aufs-2.6.18-238.5.1.el5-0.20090202.cvs-6.sl5.x86_64.rpm kernel-module-aufs-2.6.18-238.5.1.el5xen-0.20090202.cvs-6.sl5.x86_64.rpm kernel-module-ndiswrapper-2.6.18-238.5.1.el5-1.55-1.SL.x86_64.rpm kernel-module-ndiswrapper-2.6.18-238.5.1.el5xen-1.55-1.SL.x86_64.rpm kernel-module-openafs-2.6.18-238.5.1.el5-1.4.14-80.sl5.x86_64.rpm kernel-module-openafs-2.6.18-238.5.1.el5xen-1.4.14-80.sl5.x86_64.rpm OpenAFS Updated to version 1.4.14 openafs-1.4.14-80.sl5.x86_64.rpm openafs-authlibs-1.4.14-80.sl5.x86_64.rpm openafs-authlibs-devel-1.4.14-80.sl5.x86_64.rpm openafs-client-1.4.14-80.sl5.x86_64.rpm openafs-compat-1.4.14-80.sl5.x86_64.rpm openafs-debug-1.4.14-80.sl5.x86_64.rpm openafs-devel-1.4.14-80.sl5.x86_64.rpm openafs-kernel-source-1.4.14-80.sl5.x86_64.rpm openafs-kpasswd-1.4.14-80.sl5.x86_64.rpm openafs-krb5-1.4.14-80.sl5.x86_64.rpm openafs-server-1.4.14-80.sl5.x86_64.rpm Updated to latest anaconda(installer) anaconda-11.1.2.224-2.SL.x86_64.rpm anaconda-runtime-11.1.2.224-2.SL.x86_64.rpm The anaconda option --noeject is not available. Apache httpd-2.2.3-43.sl5.3.x86_64.rpm httpd-devel-2.2.3-43.sl5.3.i386.rpm httpd-devel-2.2.3-43.sl5.3.x86_64.rpm httpd-manual-2.2.3-43.sl5.3.x86_64.rpm mod_ssl-2.2.3-43.sl5.3.x86_64.rpm ERRATA that were released after SL ALPHA 1 5.6 were incorporated firefox-3.6.14-4.el5_6.i386.rpm firefox-3.6.14-4.el5_6.x86_64.rpm java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5.x86_64.rpm java-1.6.0-openjdk-demo-1.6.0.0-1.20.b17.el5.x86_64.rpm java-1.6.0-openjdk-devel-1.6.0.0-1.20.b17.el5.x86_64.rpm java-1.6.0-openjdk-javadoc-1.6.0.0-1.20.b17.el5.x86_64.rpm java-1.6.0-openjdk-src-1.6.0.0-1.20.b17.el5.x86_64.rpm kernel-2.6.18-238.5.1.el5.x86_64.rpm kernel-debug-2.6.18-238.5.1.el5.x86_64.rpm kernel-debug-devel-2.6.18-238.5.1.el5.x86_64.rpm kernel-devel-2.6.18-238.5.1.el5.x86_64.rpm kernel-doc-2.6.18-238.5.1.el5.noarch.rpm kernel-headers-2.6.18-238.5.1.el5.x86_64.rpm kernel-xen-2.6.18-238.5.1.el5.x86_64.rpm kernel-xen-devel-2.6.18-238.5.1.el5.x86_64.rpm libsmbclient-3.0.33-3.29.el5_6.2.i386.rpm libsmbclient-3.0.33-3.29.el5_6.2.x86_64.rpm libsmbclient-devel-3.0.33-3.29.el5_6.2.i386.rpm libsmbclient-devel-3.0.33-3.29.el5_6.2.x86_64.rpm libtiff-3.8.2-7.el5_6.6.i386.rpm libtiff-3.8.2-7.el5_6.6.x86_64.rpm libtiff-devel-3.8.2-7.el5_6.6.i386.rpm libtiff-devel-3.8.2-7.el5_6.6.x86_64.rpm logwatch-7.3-9.el5_6.noarch.rpm mailman-2.1.9-6.el5_6.1.x86_64.rpm mod_dav_svn-1.6.11-7.el5_6.1.x86_64.rpm samba-3.0.33-3.29.el5_6.2.x86_64.rpm samba3x-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-client-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-common-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-doc-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-domainjoin-gui-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-swat-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-winbind-3.5.4-0.70.el5_6.1.i386.rpm samba3x-winbind-3.5.4-0.70.el5_6.1.x86_64.rpm samba3x-winbind-devel-3.5.4-0.70.el5_6.1.i386.rpm samba3x-winbind-devel-3.5.4-0.70.el5_6.1.x86_64.rpm samba-client-3.0.33-3.29.el5_6.2.x86_64.rpm samba-client-3.0.33-3.29.el5_6.2.x86_64.rpm samba-common-3.0.33-3.29.el5_6.2.i386.rpm samba-common-3.0.33-3.29.el5_6.2.x86_64.rpm samba-swat-3.0.33-3.29.el5_6.2.x86_64.rpm subversion-1.6.11-7.el5_6.1.i386.rpm subversion-1.6.11-7.el5_6.1.x86_64.rpm subversion-devel-1.6.11-7.el5_6.1.i386.rpm subversion-devel-1.6.11-7.el5_6.1.x86_64.rpm subversion-javahl-1.6.11-7.el5_6.1.x86_64.rpm subversion-perl-1.6.11-7.el5_6.1.x86_64.rpm subversion-ruby-1.6.11-7.el5_6.1.x86_64.rpm thunderbird-2.0.0.24-14.el5_6.x86_64.rpm xulrunner-1.9.2.14-4.el5_6.i386.rpm xulrunner-1.9.2.14-4.el5_6.x86_64.rpm xulrunner-devel-1.9.2.14-4.el5_6.i386.rpm xulrunner-devel-1.9.2.14-4.el5_6.x86_64.rpm mod_dav_svn-1.6.11-7.el5_6.3.x86_64.rpm subversion-1.6.11-7.el5_6.3.i386.rpm subversion-1.6.11-7.el5_6.3.x86_64.rpm subversion-devel-1.6.11-7.el5_6.3.i386.rpm subversion-devel-1.6.11-7.el5_6.3.x86_64.rpm subversion-javahl-1.6.11-7.el5_6.3.x86_64.rpm subversion-perl-1.6.11-7.el5_6.3.x86_64.rpm subversion-ruby-1.6.11-7.el5_6.3.x86_64.rpm
Scientific Linux ALPHA 2 SL 5.6 for i386
Available from ftp://ftp.scientificlinux.org/linux/scientific/5rolling/i386/ - Scientific Linux ALPHA 2 SL 5.6 for i386March 14,2011 Updated Kernel to latest because of security update, so need new kernel modules kernel-module-aufs-2.6.18-238.5.1.el5-0.20090202.cvs-6.sl5.i686.rpm kernel-module-aufs-2.6.18-238.5.1.el5PAE-0.20090202.cvs-6.sl5.i686.rpm kernel-module-aufs-2.6.18-238.5.1.el5xen-0.20090202.cvs-6.sl5.i686.rpm kernel-module-ndiswrapper-2.6.18-238.5.1.el5-1.55-1.SL.i686.rpm kernel-module-ndiswrapper-2.6.18-238.5.1.el5PAE-1.55-1.SL.i686.rpm kernel-module-ndiswrapper-2.6.18-238.5.1.el5xen-1.55-1.SL.i686.rpm kernel-module-openafs-2.6.18-238.5.1.el5-1.4.14-80.sl5.i686.rpm kernel-module-openafs-2.6.18-238.5.1.el5PAE-1.4.14-80.sl5.i686.rpm kernel-module-openafs-2.6.18-238.5.1.el5xen-1.4.14-80.sl5.i686.rpm kernel-module-xfs-2.6.18-238.5.1.el5-0.4-2.sl5.i686.rpm kernel-module-xfs-2.6.18-238.5.1.el5PAE-0.4-2.sl5.i686.rpm kernel-module-xfs-2.6.18-238.5.1.el5xen-0.4-2.sl5.i686.rpm OpenAFS Updated to the 1.4.14 release of openafs openafs-1.4.14-80.sl5.i686.rpm openafs-authlibs-1.4.14-80.sl5.i686.rpm openafs-authlibs-devel-1.4.14-80.sl5.i686.rpm openafs-client-1.4.14-80.sl5.i686.rpm openafs-compat-1.4.14-80.sl5.i686.rpm openafs-debug-1.4.14-80.sl5.i686.rpm openafs-devel-1.4.14-80.sl5.i686.rpm openafs-kernel-source-1.4.14-80.sl5.i686.rpm openafs-kpasswd-1.4.14-80.sl5.i686.rpm openafs-krb5-1.4.14-80.sl5.i686.rpm openafs-server-1.4.14-80.sl5.i686.rpm Installer(anaconda) Updated to latest version anaconda-11.1.2.224-2.SL.i386.rpm anaconda-runtime-11.1.2.224-2.SL.i386.rpm The anaconda option --noeject is not available. Apache Changed index.html to not have Upstream Vendor info but to have SL info. Updated via security update . httpd-2.2.3-43.sl5.3.i386.rpm httpd-manual-2.2.3-43.sl5.3.i386.rpm httpd-devel-2.2.3-43.sl5.3.i386.rpm mod_ssl-2.2.3-43.sl5.3.i386.rpm ERRATA released after SL ALPHA 1 5.6 incorporated into this release subversion-1.6.11-7.el5_6.1.i386.rpm subversion-devel-1.6.11-7.el5_6.1.i386.rpm subversion-javahl-1.6.11-7.el5_6.1.i386.rpm subversion-perl-1.6.11-7.el5_6.1.i386.rpm subversion-ruby-1.6.11-7.el5_6.1.i386.rpm firefox-3.6.14-4.el5_6.i386.rpm java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5.i386.rpm java-1.6.0-openjdk-demo-1.6.0.0-1.20.b17.el5.i386.rpm java-1.6.0-openjdk-devel-1.6.0.0-1.20.b17.el5.i386.rpm java-1.6.0-openjdk-javadoc-1.6.0.0-1.20.b17.el5.i386.rpm java-1.6.0-openjdk-src-1.6.0.0-1.20.b17.el5.i386.rpm kernel-2.6.18-238.5.1.el5.i686.rpm kernel-debug-2.6.18-238.5.1.el5.i686.rpm kernel-debug-devel-2.6.18-238.5.1.el5.i686.rpm kernel-devel-2.6.18-238.5.1.el5.i686.rpm kernel-doc-2.6.18-238.5.1.el5.noarch.rpm kernel-headers-2.6.18-238.5.1.el5.i386.rpm kernel-PAE-2.6.18-238.5.1.el5.i686.rpm kernel-PAE-devel-2.6.18-238.5.1.el5.i686.rpm kernel-xen-2.6.18-238.5.1.el5.i686.rpm kernel-xen-devel-2.6.18-238.5.1.el5.i686.rpm libsmbclient-3.0.33-3.29.el5_6.2.i386.rpm libsmbclient-devel-3.0.33-3.29.el5_6.2.i386.rpm libtiff-3.8.2-7.el5_6.6.i386.rpm libtiff-devel-3.8.2-7.el5_6.6.i386.rpm logwatch-7.3-9.el5_6.noarch.rpm mailman-2.1.9-6.el5_6.1.i386.rpm mod_dav_svn-1.6.11-7.el5_6.1.i386.rpm samba-3.0.33-3.29.el5_6.2.i386.rpm samba-client-3.0.33-3.29.el5_6.2.i386.rpm samba-common-3.0.33-3.29.el5_6.2.i386.rpm samba-swat-3.0.33-3.29.el5_6.2.i386.rpm samba3x-3.5.4-0.70.el5_6.1.i386.rpm samba3x-client-3.5.4-0.70.el5_6.1.i386.rpm samba3x-common-3.5.4-0.70.el5_6.1.i386.rpm samba3x-doc-3.5.4-0.70.el5_6.1.i386.rpm samba3x-domainjoin-gui-3.5.4-0.70.el5_6.1.i386.rpm samba3x-swat-3.5.4-0.70.el5_6.1.i386.rpm samba3x-winbind-3.5.4-0.70.el5_6.1.i386.rpm samba3x-winbind-devel-3.5.4-0.70.el5_6.1.i386.rpm thunderbird-2.0.0.24-14.el5_6.i386.rpm xulrunner-1.9.2.14-4.el5_6.i386.rpm xulrunner-devel-1.9.2.14-4.el5_6.i386.rpm mod_dav_svn-1.6.11-7.el5_6.3.i386.rpm subversion-1.6.11-7.el5_6.3.i386.rpm subversion-devel-1.6.11-7.el5_6.3.i386.rpm subversion-javahl-1.6.11-7.el5_6.3.i386.rpm subversion-perl-1.6.11-7.el5_6.3.i386.rpm subversion-ruby-1.6.11-7.el5_6.3.i386.rpm device-mapper-multipath-0.4.7-42.el5_6.1.i386.rpm gnome-screensaver-2.16.1-8.el5_6.3.i386.rpm kpartx-0.4.7-42.el5_6.1.i386.rpm scsi-target-utils-1.0.8-0.el5_6.1.i386.rpm
Debuginfo repositories
Hello, I am wondering why Scientific Linux doesn't support debuginfo repositories in the same way as Red Hat does (disabled in *.repo files, distributed directly in the directory with binaries). I found some debug information 'hidden' in the directory /linux/scientific/6rolling/archive/debuginfo/, however I am not sure if it contains all debuginfo from all other binary directories and is already in sync. There are two reasons, why we shall care about debuginfo as a first class citizen: 1) ABRT (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/ch-abrt.html;) 2) SystemTap (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/SystemTap_Beginners_Guide/index.html;) Without debuginfo it is difficult to generate a sensible crash log (ABRT) and it helps [Red Hat] developers a lot. If one wants to analyse and tune the performance of the system, the SystemTap is absolutely essential and it needs debuginfo as well. Best Regards Vaclav M.
Re: a few questions about SL admin best practises
On 3/14/2011 9:15, Konstantin Olchanski wrote: On Sat, Mar 12, 2011 at 12:06:56AM -0800, Garrett Holmstrom wrote: gholms@luna ~ % mount | grep ext /dev/sda1 on /boot type ext4 (rw) In the LVM way of things, if I connect this disk to another computer, would these /boot partitions collide and prevent the computer from booting? That volume is just a regular partition since /boot can't reside on a LV. -- Garrett Holmstrom
