I find it interesting that there were more responses on the topic of email
threading than there were for the original question.
I'll bet we get about 4 more posts because I top-posted. Can't we cut each
other some slack?
On Saturday 19 January 2008 10:10:32 am Carlos E. R. wrote:
> The Saturday 2008-01-19 at 08:48 -0800, PerfectReign wrote:
> > On Sat, January 19, 2008 7:11 am, Philipp Thomas wrote:
> >> On Sat, 19 Jan 2008 06:18:51 -0800 (PST), PerfectReign wrote:
> >>> This is email. There is no thread.
> >>
> >> Either you simply forgot a smiley or I don't get it. Of cause there
> >> are
> >> mail threads. What do you think In-Reply-To and References in the mail
> >> header were invented for?
> >>
> >> Yes, there are those wannabe MUAs such as Outlook, Groupwise and Notes
> >> that constantly ignore the existence of In-Reply-To, but that's a
> >> different story.
> >
> > My apologies. I forgot that you can thread emails on KMail.
>
> All decent mail programs do thread. Thunderbird, Mozilla, Kmail, even text
> only clients like Pine or mutt. Gmail web client does thread, but it calls
> it "conversations".
>
> And the archive is threaded.
>
> Even Outlook does thread:
>
>X-Mailer: Microsoft Office Outlook 12.0
> Thread-Index: AchZxUFbeX4hpExoQh2zru0l/TqnbgAAC2AA
>
> Although being Microsoft, it uses something else instead of the standard.
>
>
>
> --
> Cheers,
> Carlos E. R.
--
Mike Diehl
---
--
Mike Diehl
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm needing to upgrade the kernel on a SLES10 server. I've done kernel
upgrades before so this shouldn't be a problem.
However, when I reboot, I get:
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2--1 pin2=-1
And then the machine hangs. With the factory kernel, this system boots and
runs fine.
Anyone know how to fix this?
TIA,
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, this did fix my problem. I'd been stareing at this for so long, I'd
never have spotted it.
Thanx,
On Tuesday 13 November 2007 12:48:00 pm Anders Johansson wrote:
> On Tuesday 13 November 2007 20:30:33 Mike Diehl wrote:
> > Hi all,
> >
> > I'm trying to get nic bonding to work in active-backup mode, or mode 1
> > and what I seem to be getting is round-robin.
> >
> > I'm seeing traffic on both of the connected nics.
> >
> > Here is my configuration for the bond0 interface.:
> >
> > BOOTPROTO='static'
> > BROADCAST='173.173.37.255'
> > IPADDR='173.173.37.120'
> > NETMASK='255.255.255.0'
> > NETWORK='173.173.37.0'
> > STARTMODE='onboot'
> > BONDING_MASTER='yes'
> > BONDING_MODULE_OPS='mode=active-backup use_carrier=0 miimon=100
>
> ^
>
> That's misspelled. It should read BONDING_MODULE_OPTS
>
> That would explain why the bonding options don't take effect
>
> Anders
>
> --
> Madness takes its toll
--
Mike Diehl
---
--
Mike Diehl
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
I'm trying to get nic bonding to work in active-backup mode, or mode 1 and
what I seem to be getting is round-robin.
I'm seeing traffic on both of the connected nics.
Here is my configuration for the bond0 interface.:
BOOTPROTO='static'
BROADCAST='173.173.37.255'
IPADDR='173.173.37.120'
NETMASK='255.255.255.0'
NETWORK='173.173.37.0'
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPS='mode=active-backup use_carrier=0 miimon=100 primary=eth3'
BONDING_SLAVE0='bus-pci-:0a:03.0'
BONDING_SLAVE1='bus-pci-:07:08.0'
BONDING_SLAVE2='bus-pci-:06:07.0'
BONDING_SLAVE3='bus-pci-:09:04.0'
As you can see, I'm using active-backup mode. However, here is
what /proc/net/bonding/bond0 says:
Ethernet Channel Bonding Driver: v2.6.5 (November 4, 2005)
Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:0e:0c:b0:eb:21
Slave Interface: eth1
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:13:72:55:d2:5e
Slave Interface: eth0
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:13:72:55:d2:5d
Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:0e
Any ideas as to how to fix this?
TIA,
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm trying to install APC UPS agent on SLES9 and I'm getting the following
dependancy failure:
libcrypto.so.4 is needed by apcupsd-3.14.1-1
However, I've looked at all 4 of my CD's and I don't have libcrypto.
Can anyone tell me where to get it?
TIA,
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I submitted bug report number 275431.
Thank you.
On Wednesday 16 May 2007 05:07, Ladislav Slezak wrote:
> Mike Diehl wrote:
> [...]
>
> > Then I get a box that says:
> >
> > Errror
> > Error while writing settings.
> >
> > Once again, the error message is worthless and there doesn't seem to be a
> > log file to be had anywhere...
>
> You can find the log in /var/log/YaST2/y2log
>
> > Any ideas about how to proceede? This is getting very frustrating!
>
> I have no idea, it sounds like a bug in yast2-cd-creator.
>
> I'm unable to help without more information. Please, report the problem
> into bugzilla and attach the yast logs (use 'save_y2logs' command).
>
>
> Ladislav
>
>
> --
>
> Best Regards
>
> Ladislav Slezák
> Yast Developer
>
> SUSE LINUX, s.r.o. e-mail: [EMAIL PROTECTED]
> Lihovarská 1060/12 tel: +420 284 028 960
> 190 00 Prague 9 fax: +420 284 028 951
> Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all,
Well, I've revisited my auto-install CD and I'm having more difficulties.
I've created a control file using the auto install tool in yast2. I've
configured a local installation source.
Now I'm trying to use the CD Creator tool to create a disk image.
Once I get through all of the configuration choices, (install source, profile,
etc.) I get a screen entitled "Saving CD Creator Configuration."
Followed by "=> Write the settings" as the progress indication.
Then I get a box that says:
Errror
Error while writing settings.
Once again, the error message is worthless and there doesn't seem to be a log
file to be had anywhere...
Any ideas about how to proceede? This is getting very frustrating!
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm still trying to get my auto-install CD to work. At least now it boots...
But when it fails during the installation.
I put:
autoyast=file:\\\control.xml install=cd
on the kernal parameter line and autoyast starts the installation process.
Then I get a screen with a "An error occured during the installation." error
message. There doesn't appear that there is any way to diagnose this and the
error message is certainly useless. I've checked that my control.xml file is
valid XML. The log files under /var/log didn't give any hints either.
So, how does one approach this problem?
I've attached the control.xml file, if it makes it through the listserv.
Thanx,
Mike.
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>/root/install
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>eth1
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>yes
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>yes
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>yes
http://www.suse.com/1.0/yast2ns";>no
http://www.suse.com/1.0/yast2ns";>http https ssh
http://www.suse.com/1.0/yast2ns"; type="boolean" >false
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>video
http://www.suse.com/1.0/yast2ns";>username
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>audio
http://www.suse.com/1.0/yast2ns";>username
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>dialout
http://www.suse.com/1.0/yast2ns";>username
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>uucp
http://www.suse.com/1.0/yast2ns";>username
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns"; type="list" />
http://www.suse.com/1.0/yast2ns"; type="boolean" >false
http://www.suse.com/1.0/yast2ns"/>
http://www.suse.com/1.0/yast2ns"; type="list" />
http://www.suse.com/1.0/yast2ns"; type="boolean" >true
http://www.suse.com/1.0/yast2ns";>2.9
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns"; type="boolean" >false
http://www.suse.com/1.0/yast2ns"; type="boolean" >false
http://www.suse.com/1.0/yast2ns";>example.com
http://www.suse.com/1.0/yast2ns";>hostname
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>173.173.88.110
http://www.suse.com/1.0/yast2ns";>173.173.188.120
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>static
http://www.suse.com/1.0/yast2ns";>173.173.88.255
http://www.suse.com/1.0/yast2ns";>eth1
http://www.suse.com/1.0/yast2ns";>173.173.88.120
http://www.suse.com/1.0/yast2ns";>255.255.255.0
http://www.suse.com/1.0/yast2ns";>173.173.88.0
http://www.suse.com/1.0/yast2ns";>onboot
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>static-1
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns"; type="boolean" >false
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>default
http://www.suse.com/1.0/yast2ns";>-
http://www.suse.com/1.0/yast2ns";>173.173.88.254
http://www.suse.com/1.0/yast2ns";>255.255.255.0
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns"; type="list" >
http://www.suse.com/1.0/yast2ns";>
http://www.suse.com/1.0/yast2ns";>/mnt/archiver/post.shhttp://www.suse.com/1.0/yast2ns";>shellhttp://www.suse.com/1.0/yast2ns"/>
http://www.suse.com/1.0/yast2ns";>
http://www.s
On Tuesday 24 April 2007 17:51, David Bolt wrote:
> On Mon, 23 Apr 2007, Mike Diehl <[EMAIL PROTECTED]> wrote:-
> >Anyway, this begs the question as to why the command below doesn't work.
> >
> >When I run it, I get:
> >genisoimage: Uh oh, I cant find the boot catalog directory
> > './raw/boot/loader'!
>
> I don't have genisoimage installed, so have no idea why it's coming up
> with that error.
>
> >Of course, the directory does exist and gnisoimage even scans it! I'm
> > really getting desparate here!
I finally got this working. The file was exactly where I said it was. The
problem was that genisoimage was looking for it relative to the CD's root,
not the current directory. GRr.
Thanx for the help, though.
Mike Diehl.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I was quite impressed! When I took the test, the program indicated that
Gentoo would be the best distribution for me. That's pretty good since I use
Gentoo at home and at work, almost exclusively. I am using Suse for the
first time since it is specified by one of our vendors. In the past, I've
used RedHat, Slackware, Mandrake, Knoppix, Yellow Dog, and Caldera.
The other neat thing was that the program indicated that my second choice
would be Slackware, which is the first distro that I ever used!
I was intrigued by the fact that the program also indicated why it thought a
given distro would be less than optimum for me. In the case of Gentoo, it
indicated the lack of application library would make it less than optimum.
However, I have to take issue with the lack of applications.
Anyway, here is a single point sample that indicates that your program works
well.
Mike Diehl.
On Tuesday 24 April 2007 09:47, Randall R Schulz wrote:
> On Tuesday 24 April 2007 08:11, Dick Turpin wrote:
> > Hi All
> >
> > Every Forum and mailing list gets the same question from potential
> > Linux users every now and again "Which one should I use?" they
> > generally get inundated with the members personal choice rather than
> > the one suited to them.
> >
> > Some of you may have seen this before but there is a site that hosts
> > a test which, based on your answers, will give you the Linux
> > Distributions that are best suited to you I've been given permission
> > to link to it check it out at my site under the heading Linux Chooser
> > http://cannon-linux.co.uk/my-linux-stuff.html?Itemid=27
>
> That's not too bad. A few observations:
>
> It would be nice to be able to back up and change some of your answers.
>
> As is typical with this sort of approach, if you answers don't fit the
> options offered (e.g., I run a workstation that also functions as a
> server), you may not get optimum recommendations.
>
> I liked the offer to teach me about alternate package management
> schemes. I'm aware of the Debian system, of course, but know nothing
> about it. Now I have a Web page open that will give me some basic
> information about it.
>
>
> Anyway, from my first pass through the advisor, I was recommended these
> three distributions:
>
> - Debian
> - OpenSuSE (sic)
> - Mandriva
>
> > --
> > Regards
> > Dick Turpin
>
> Randall Schulz
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thursday 19 April 2007 16:35, David Bolt wrote:
> On Tue, 17 Apr 2007, Mike Diehl <[EMAIL PROTECTED]> wrote:-
>
> >I agree. So, I've fallen back to cdrecord. Since I'm mastering this
> >disk on a non-SUSE machine, I
> >don't have makeSUSEdvd and downloading it led to some dependancy
> > issues.
>
> From the spec file for the RPM, the only dependency is the requirement
> that mkisofs be installed[0]. What dependency problems did you have?
When I run the script, I get:
==
Starting makeSUSEdvd version 0.35
/tmp/CD_DIR already exists. Using /tmp/CD_DIR.12920 instead
You seem to not have create_package_descr installed.
You can install the current version with the command :
rpm -Uvh autoyast2-utils-2.13.56-3.noarch.rpm after getting it from
https://sourceforge.net/projects/makesusedvd. Would you like to install"
automagically with RPM? [n/Y] :
==
Not particularly interested in finding out what autoyast will do to my Gentoo
workstation.
Anyway, this begs the question as to why the command below doesn't work.
When I run it, I get:
genisoimage: Uh oh, I cant find the boot catalog directory './raw/boot/loader'!
Of course, the directory does exist and gnisoimage even scans it! I'm really
getting desparate here!
Any help would be appreciated.
Mike
>
>
> >export BOOT_IMAGE=/home/mdiehl/newstart/raw/boot/loader
> >
> >mkisofs -v -V "SNL INSTALLER" -r -J -l -L -b "$BOOT_IMAGE/isolinux.bin"
> >-c $BOOT_IMAGE/boot.cat \
> >-no-emul-boot -boot-load-size 4 -boot-info-table -graft-points -iso-
> >level 4 -pad -allow-leading-dots -o b.iso ./raw
> >===
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tuesday 17 April 2007 13:08, David Bolt wrote:
> On Tue, 17 Apr 2007, Mike Diehl <[EMAIL PROTECTED]> wrote:-
> >I'm trying to build a custom install CD, but I just can't get the
> > resulting disk to boot. I want to be able to put a disk in a system,
> > boot the system and come back to a fully configured machine.
>
> Does it have to be a CD, or would you be able to work with a DVD
> instead? A DVD would be much more in keeping with the "insert disc, walk
> away, come back to fully working system" desire so, if you can use a
> DVD, check out makeSUSEdvd.
No, eventually, it WILL be a DVD. But if I can't get a CD to work, there's no
point in burning a DVD, just yet.
> My guess would be that kiso doesn't know how to recreate the necessary
> bits to make the resultant image bootable.
I agree. So, I've fallen back to cdrecord. Since I'm mastering this disk on a
non-SUSE machine, I
don't have makeSUSEdvd and downloading it led to some dependancy issues.
So, I extracted the "guts" of the script and continued on.
So, here is the script I'm using:
===
export BOOT_IMAGE=/home/mdiehl/newstart/raw/boot/loader
mkisofs -v -V "SNL INSTALLER" -r -J -l -L -b "$BOOT_IMAGE/isolinux.bin" -c
$BOOT_IMAGE/boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table -graft-points -iso-level 4
-pad -allow-leading-dots -o b.iso ./raw
===
I've extracted the original CD into ./raw and I'm expecting to build a file
called b.iso. (this is plan B, right?)
When I run this script I get:
===
Warning: creating filesystem that does not conform to ISO-9660.
Warning: Creating ISO-9660:1999 (version 2) filesystem.
Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS.
genisoimage 1.1.2 (Linux)
Scanning ./raw
Scanning ./raw/SLES-LICENSE
Scanning ./raw/SLES-LICENSE/it
Scanning ./raw/SLES-LICENSE/nl
... snip ...
Scanning ./raw/yast/core9/suse
Scanning ./raw/yast/core9/suse/setup
Scanning ./raw/yast/core9/suse/setup/descr
genisoimage: Uh oh, I cant find the boot catalog directory './raw/boot/loader'!
===
So it's complaining that it can't find the ./raw/boot/loader directory!
But *I* can:
workstation newstart # ls -la ./raw/boot/loader/
total 7056
dr-xr-xr-x 2 root root4096 Jul 2 2004 .
dr-xr-xr-x 3 root root4096 Jul 2 2004 ..
-r--r--r-- 1 root root 33043 Jul 2 2004 06400480.spl
-r--r--r-- 1 root root 46989 Jul 2 2004 08000600.spl
-r--r--r-- 1 root root 63015 Jul 2 2004 10240768.spl
-r--r--r-- 1 root root 69943 Jul 2 2004 12801024.spl
-r--r--r-- 1 root root 99571 Jul 2 2004 14001050.spl
-r--r--r-- 1 root root 120205 Jul 2 2004 16001200.spl
-r--r--r-- 1 root root 230400 Jul 2 2004 bootlogo
-r--r--r-- 1 root root 4885034 Jul 2 2004 initrd
-r--r--r-- 1 root root 15340 Jul 2 2004 isolinux.bin
-r--r--r-- 1 root root 824 Jul 2 2004 isolinux.cfg
-r--r--r-- 1 root root 1503455 Jul 2 2004 linux
-r--r--r-- 1 root root 71744 Jul 2 2004 memtest
-r--r--r-- 1 root root 510 Jul 2 2004 message
So what am I doing wrong? Also, the command line above refers to a boot.cat
file,
but I've not been able to find one and don't know how to produce it. I've
studied the makeSUSEdvd
script and can't see how it creates this file, either.
HELP!
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm re-posting this since I'm still spinning my wheels trying to get it to
work.
I'm trying to build a custom install CD, but I just can't get the resulting
disk to boot. I want to be able to put a disk in a system, boot the system
and come back to a fully configured machine.
This is what I'm doing:
I'm using k3b to build an image file from the original install media.
Then I'm using kiso to make the changes to the files that I need to make.
After saving the new .iso file, I burn with it with k3b.
The resulting CD won't boot.
Now, when I burn the iso image without making any changes, that CD will boot.
But as soon as I make a change, to control.xml for example, the resulting CD
won't boot.
Any ideas?
TIA,
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm trying to build a custom install CD, but I just can't get the resulting
disk to boot. I want to be able to put a disk in a system, boot the system
and come back to a fully configured machine.
This is what I'm doing:
I'm using k3b to build an image file from the original install media.
Then I'm using kiso to extract the files from the image into a directory. In
hind sight, I guess I could have simply copied the files, but what can I say?
Then I'm making the changes to the files that I need to make.
I use kiso to package the resulting files into an iso image which I burn with
k3b. Before burning, I use kiso to add a boot image to the iso.
The resulting CD won't boot. I'm getting my isolinux.bin file from
http://syslinux.zytor.com/iso.php and renaming it to isolinux.img so that
kiso will recognize it. I'm sure this is where I'm messed up, so what is the
RIGHT way to do this?
TIA,
Mike.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, there is. Our final deployment will be in limited rack space on a
stand-alone network. We have the additional need to manage complexity since
we won't be managing the server(s) directly.
On Tuesday 03 April 2007 15:31, Magnus Boman wrote:
> Mike,
>
> On Tue, 2007-04-03 at 15:30 -0600, Mike Diehl wrote:
> > Hi all.
> >
> > I'm needing to create a single CD/DVD that will automatically install and
> > configure a stripped down SLES9 server. I've got an autoyast control.xml
> > file created that works from my pen drive just fine.
> >
> > But I'd like to see if I can minimize the amount of media swapping
> > involved by putting all of the needed .rpm files on one disk. If I do
> > that, how do I tell the installer to not ask for the additional media?
>
> Is there a reason why you can't use an installation server?
> I'm sure there are ways to combine those CD's to a single DVD, but I
> doubt that it's supported by Novell/SUSE. If you still want to go ahead,
> have a look at http://en.opensuse.org/Making_a_DVD_from_CDs
>
> > TIA,
> >
> > --
> > Mike Diehl,
>
> Cheers,
> Magnus
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm needing to create a single CD/DVD that will automatically install and
configure a stripped down SLES9 server. I've got an autoyast control.xml
file created that works from my pen drive just fine.
But I'd like to see if I can minimize the amount of media swapping involved by
putting all of the needed .rpm files on one disk. If I do that, how do I
tell the installer to not ask for the additional media?
TIA,
--
Mike Diehl,
Network Management Tool Devl.
Sandia National Laboratories.
(505) 284-3137
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi all.
I'm a new SLES9 user but I've been using Linux for some time.
I'm trying to upgrade the kernel on a SLES9 server and am having problems.
I've compiled the kernel and copied it to /boot/bzImage. I've created an
entry in /boot/grub/menu.lst.
The problem is that no matter what I do, it seems to load the same (factory)
version of the kernal.
So what is the prescribed method of upgrading the kernel under SLES9?
TIA,
--
Mike Diehl
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
