Re: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
Quoting Shad L. Lords [EMAIL PROTECTED]: kernel. I went back to 2.4.7 in order to keep the smp, BOOT, and regular kernel the same version. SMP, BOOT, and regular kernels are all available for 2.4.9-21 (wish I'd noticed that before I spent all night building them). Check your local RedHat mirror. Of course, there's no smp for i386; you'd need to look in i586 or i686. -- Dan Brown, KE6MKS, [EMAIL PROTECTED] Since all the world is but a story, it were well for thee to buy the more enduring story rather than the story that is less enduring. -- The Judgment of St. Colum Cille -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
David Brown [EMAIL PROTECTED] said: I used the following procedure to upgrade my SME v5.1.2 *test*server to a 2.4.9-21 RedHat kernel: David, many thanks for taking the time to put this mini-Howto together. I might have some time over the weekend to give it a try myself. I do have a general question though that maybe you or other devinfo members might be able to answer. The question is far reaching but simply stated would read: 'is this the _best_ way to go?' Should we simply add a new kernel on top of SME or would it be better to add SME on top of a complete RedHat 7.2 distro? I'm thinking about all the modules and rpm dependencies that are kernel specific. I'm also thinking about ext3 file system. Going the 'adding SME to a distro' route would I think make it easier as everything we need is there, we are simply added SME as well. Please do not missunderstand. I tremendously appreciate your HowTo contrib and will take the time myself to give it a go and see if this is just as easy. Simply wanting to hear your opinion and others on the above as well. Regards, -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
This is my first attempt as well at messing with kernel and stuff. But
thanks to a great starting point by David Brown and a little bit of spare
time I have enhanced the howto for Upgrading the kernel to a 2.4 kernel. I
went back to 2.4.7 in order to keep the smp, BOOT, and regular kernel the
same version. I have also added a few things to get the main filesystem
converted to ext3 and added ipchain support so that the masq stuff still
works. There still seems to be a problem with PPTP. I have not had a
chance to test diald, pppoe or dhcpd stuff yet. It appears that dhcpd at
least starts but that is as far as I have gotten.
do the following as root to update to 2.4.7 kernel with quota support and ext3
==
cd /root
mkdir rpms
cd rpms
mkdir done
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/kudzu-0.99.23-1.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/mkinitrd-3.2.6-1.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/modutils-2.4.6-4.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/filesystem-2.1.6-2.noarch.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/setup-2.5.7-1.noarch.rpm
wget ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/bash-2.05-8.i386.rpm
rpm -Uvh *.rpm
mv * done
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/kernel-2.4.7-10.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/kernel-BOOT-2.4.7-10.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/kernel-pcmcia-cs-3.1.27-10.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/kernel-smp-2.4.7-10.i586.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/hotplug-2001_04_24-11.i386.rpm
rpm -e kernel-pcmcia-cs
rpm -ivh *.rpm
mv * done
pico /etc/lilo.conf
--
copy 'image=/boot/vmlinuz-2.2.19-7.0.8' line and all indented lines under it
change 'label=esmith' to 'label=esmith22'
copy 'image=/boot/vmlinuz-2.2.19-7.0.8smp' line if exists and all indented lines under
it
if smp kernel exists change 'label=esmith-up' to 'label=esmith22-up'
on copies have have 'label=esmith' change all occurences of '2.2.19-7.0.8' to
'2.4.7-10'
on copies have have 'label=esmith-up' if exists change all occurences of
'2.2.19-7.0.8smp' to '2.4.7-10smp'
--
/sbin/e-smith/expand-template /etc/lilo.conf
lilo
reboot
if 'esmith-up' exists pick this
depmod -a
reboot
pick 'esmith'
depmod -a
reboot
cd rpms
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/quota-3.01pre9-3.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/initscripts-6.40-1.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/mount-2.11g-5.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/iputils-20001110-6.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/e2fsprogs-1.23-2.i386.rpm
wget
ftp://ftp.rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/ipchains-1.3.10-10.i386.rpm
rpm -Uvh *.rpm
mv * done
convertquota -u /
convertquota -g /
/etc/e-smith/events/actions/enable-quotas
tune2fs -j /dev/hda6
tune2fs -j /dev/hda1
pico /etc/fstab
---
change ext2 to ext3 on first 2 lines (Label=/ and Label=/boot)
---
/sbin/e-smith/expand-template /etc/fstab
/sbin/e-smith/config set ipchains service InitscriptOrder 06 status enabled
ln -s /etc/rc.d/init.d/e-smith/service /etc/rc.d/rc7.d/S06ipchains
touch /etc/sysconfig/ipchains
reboot
pico /etc/rc.d/init.d/functions
---
insert following below echo_passed() function (~line 332):
echo_disabled() {
[ $BOOTUP = color ] $MOVE_TO_COL
echo -n [
[ $BOOTUP = color ] $SETCOLOR_WARNING
echo -n DISABLED
[ $BOOTUP = color ] $SETCOLOR_NORMAL
echo -n ]
echo -ne \r
return 1
}
insert following below passed() function (~line 385)
# Log that something passed, but is disabled in this configuration
disabled() {
rc=$?
if [ -z $IN_INITLOG ]; then
initlog $INITLOG_ARGS -n $0 -s $1 -e 1
else
trap SIGPIPE
echo $INITLOG_ARGS -n $0 -s \$1\ -e 1 21
trap - SIGPIPE
fi
[ $BOOTUP != verbose ] echo_disabled
return $rc
}
change following 2 lines (~line 404)
initlog $INITLOG_ARGS -c $* success $$STRING || failure $$STRING
rc=$?
to
# initlog $INITLOG_ARGS -c $* success $$STRING || failure $$STRING
initlog $INITLOG_ARGS -c $*
rc=$?
case $rc in
0) success $STRING ;;
99) disabled $STRING
rc=0 ;;
*) failure $STRING ;;
esac
# rc=$?
---
reboot
Still have to fix/test PPTP. Appears that ppp.o and ppp_mppp.o in the
/lib/modules/2.2.19-7.0.8/net may be needed for PPTP to work. May need to recompile
these for the newer kernel.
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL
Re: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
Shad L. Lords [EMAIL PROTECTED] said: This is my first attempt as well at messing with kernel and stuff. Looks like a fabulous first attempt to me Shad. Great job! I just wish I had time to try this. Maybe by the weekend. Regards, -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
On Thursday, February 07, 2002, Darrell May wrote: David, many thanks for taking the time to put this mini-Howto together. I might have some time over the weekend to give it a try myself. No problem at all. I'd appreciate it if other people would try this out and verify that it works for them. I forgot to mention that I did this on a SME v5.1.2 server, upgraded from several 5.1 betas, just in case it matters. I chose the RedHat 2.4.9-21 kernel because it is the latest 2.4.x series that RedHat has released (I think) and there has been some discussion that this is one of the most stable kernels in the 2.4.x series. I do have a general question though that maybe you or other devinfo members might be able to answer. The question is far reaching but simply stated would read: 'is this the _best_ way to go?' Don't take this the wrong way, but who cares? Now let me qualify that. :) I think we will only find the _best_ way by testing several methods of upgrading to a 2.4.x kernel to see what works best. After seeing that, Mitel management may decide that it really isn't that hard after all ... or they may not. Either way, we as developers will have tracked down some of the issues that need to be considered. Should we simply add a new kernel on top of SME or would it be better to add SME on top of a complete RedHat 7.2 distro? I'm thinking about all the modules and rpm dependencies that are kernel specific. I'm also thinking about ext3 file system. Going the 'adding SME to a distro' route would I think make it easier as everything we need is there, we are simply added SME as well. Well, I'm going to mess with taking the latest RedHat 7.2 versions of all the packages on the SME v5.1.2 disk and make a custom iso to install a system with SME on top of RedHat 7.2. I'll start this tonight and see how it goes. Here's the biggest problem (as has already been stated several times): even if we get all the latest up to date RedHat 7.2 packages up and running. David M. Brown Frick, Frick Jetté Architects [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
David Brown [EMAIL PROTECTED] said: Don't take this the wrong way, but who cares? Now let me qualify that. :) No worries. Your point is an excellent one. We might have to try both ways. I was only hoping to seek advice from those that have already gone there before to share with us their wisdom. For all onlist that may not be aware, there is a tremendous amount of development activity which happens offlist. There are some incredible projects already underway that I am aware of and I'm sure there are hundreds more I do not even know about. So, you may find some of my questions are geered to trying to get these people to speak up and share with the devinfo community. Sometimes they do, mostly they reply to me directly. Ultimately it is their choice to choose whom they reply to. I always ask if I may share back their comments to devinfo and this is where many of my posts originate. Latest example was my 'krud' post which spurred this new activity ;- Regards, -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
Re: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
From the work I have done trying to get PPTP working with the 2.4 kernel I think that the ppp.o and ppp_mppe.o modules that exist in the /lib/modules/2.2.19-7.0.8-e-smith/net directory are going to need to be recompiled for the new version of the kernel (2.4.7 or 2.4.9). Is there anyone out there that is willing to help in recompiling these modules (I would prefer to start with the 2.4.7-10 kernel). If possible it would be nice to have both the smp and normal versions. I have machines that fit both configurations that I can test with. If someone could recompile these modules and send them here then I will report back success or failure. Thanks everyone, -Shad -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
Well, I'm going to mess with taking the latest RedHat 7.2 versions of all the packages on the SME v5.1.2 disk and make a custom iso to install a To give you a heads up, I tried to build a custom iso cd of the 5..2 release and had lots of problems. First, the RedHat directory generally in the RedHat cd was rename to e-smith and so the stock genhdlist from the 7.1 cd will not work. I recompiled the genhdlist with references to RedHat change to e-smith and the genhdlist ran without errors. Unfortunately, when I try to install off the cd, the installer croaked when it got to installing the rpm packages By the way, anyone find the src.rpm for the anacronda that was used to build the cd? edward [EMAIL PROTECTED] on 02/07/2002 12:03:00 PM To: [EMAIL PROTECTED]@Internet, [EMAIL PROTECTED]@Internet, [EMAIL PROTECTED]@Internet cc:(bcc: Edward Tak/CA/KAIPERM) Subject: RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo On Thursday, February 07, 2002, Darrell May wrote: David, many thanks for taking the time to put this mini-Howto together. I might have some time over the weekend to give it a try myself. No problem at all. I'd appreciate it if other people would try this out and verify that it works for them. I forgot to mention that I did this on a SME v5.1.2 server, upgraded from several 5.1 betas, just in case it matters. I chose the RedHat 2.4.9-21 kernel because it is the latest 2.4.x series that RedHat has released (I think) and there has been some discussion that this is one of the most stable kernels in the 2.4.x series. I do have a general question though that maybe you or other devinfo members might be able to answer. The question is far reaching but simply stated would read: 'is this the _best_ way to go?' Don't take this the wrong way, but who cares? Now let me qualify that. :) I think we will only find the _best_ way by testing several methods of upgrading to a 2.4.x kernel to see what works best. After seeing that, Mitel management may decide that it really isn't that hard after all ... or they may not. Either way, we as developers will have tracked down some of the issues that need to be considered. Should we simply add a new kernel on top of SME or would it be better to add SME on top of a complete RedHat 7.2 distro? I'm thinking about all the modules and rpm dependencies that are kernel specific. I'm also thinking about ext3 file system. Going the 'adding SME to a distro' route would I think make it easier as everything we need is there, we are simply added SME as well. Well, I'm going to mess with taking the latest RedHat 7.2 versions of all the packages on the SME v5.1.2 disk and make a custom iso to install a system with SME on top of RedHat 7.2. I'll start this tonight and see how it goes. Here's the biggest problem (as has already been stated several times): even if we get all the latest up to date RedHat 7.2 packages up and running. David M. Brown Frick, Frick Jetté Architects [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 From: Darrell May [mailto:[EMAIL PROTECTED]] 'is this the _best_ way to go?' Best in the sense of being the most comprehensive, complete, compatible way of doing things? Probably not. From that perspective, it's probably better to start with the RH7.2 versions of all the relevant packages--or install versions which were designed to be RH7.1 updates (there's a 2.4.9-21 kernel distributed as a RH7.1 update, as well as the RH7.2 one that David used). However, David's suggestion may be the best in the sense of being quite functional and less work to implement than replacing all the packages, even when there isn't an obvious reason to do so. Ease of implementation is also an important consideration, of course. - -- Dan Brown, KE6MKS, [EMAIL PROTECTED] Since all the world is but a story, it were well for thee to buy the more enduring story rather than the story that is less enduring. -- The Judgment of St. Colum Cille -BEGIN PGP SIGNATURE- Version: PGP 7.0.4 iQA/AwUBPGLzMH6CI7gsQbX8EQI6mwCfVTDr0G71YalrLNGL9euJKQ/OxOkAn1eh yCW74OA0pvlvd6Lmh9aYAESu =YKGK -END PGP SIGNATURE- -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
[EMAIL PROTECTED] said: First, the RedHat directory generally in the RedHat cd was rename to e-smith That one is easy. I build custom isos daily. When I give you the answer don't scream too loud Change to the base directory of your iso copy. Let's say if your copy is located at /root/sme512 cd /root/sme512 ln -s e-smith RedHat After that you'll find the standard RedHat anaconda-runtime rpm and genhdlist and all the other iso build tools work just fine. Regards, -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
On Thu, 7 Feb 2002, David Brown wrote: Here's the biggest problem (as has already been stated several times): even if we get all the latest up to date RedHat 7.2 packages up and running. I guess I should read what I post before I post it. :) What I meant to say was: Here's the biggest problem (as has already been stated several times): even if we get all the latest up to date RedHat 7.2 packages up and running, we still need masq modules for pptp, ipsec, realaudio, h323, icq, and possibly more that will work with the 2.4.x kernel. This is a much bigger challenge IMHO than simply upgrading SME to a 2.4.x series kernel. I'm looking into this, but I've never looked into programming kernel modules, so I assume a steep learning curve. David M. Brown Frick, Frick Jetté Architects [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
David Brown [EMAIL PROTECTED] said: we still need masq modules for pptp, ipsec, realaudio, h323, icq, and Agreed, they are extremely valuable to those that do use and need them. However, from another viewpoint, many small business SME users don't use them, don't need them and therfore won't even miss them. Regards -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
On Thu, 7 Feb 2002, Darrell May wrote: However, from another viewpoint, many small business SME users don't use them, don't need them and therfore won't even miss them. This is especially true for servers running in serveronly mode. -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
-Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 3:43 PM To: David Brown; [EMAIL PROTECTED] Subject: RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo David Brown [EMAIL PROTECTED] said: we still need masq modules for pptp, ipsec, realaudio, h323, icq, and Agreed, they are extremely valuable to those that do use and need them. However, from another viewpoint, many small business SME users don't use them, don't need them and therfore won't even miss them. True, but the only way Mitel as a company is going to make the move to a 2.4 kernel IMHO is if these modules are available and working properly. If we are looking for the _best_ solution, we must consider this issue. Upgrading the kernel seems almost trivial at this point, since it involves putting together pre-made pieces in a defined sequence. Masq modules, OTOH seem to be far more daunting, as they involve actual coding. Anyone truly interested in this thread should look into the status of masq modules for the 2.4 kernel to see if they can help port the ones we need from the 2.2 kernel series. Not only would this help your favorite Linux distro, it would benefit the Linux community at large. David M. Brown Frick, Frick Jetté Architects [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
Charlie Brady [EMAIL PROTECTED] said: This is especially true for servers running in serveronly mode. Absolutely, ... how did I miss that great example! Definitely not needed there and that takes care of most of the larger SME corporate clients where corporate firewalls/VPN are already in place doing their thing. I'm even sitting at a client now that has a Nortel Extranet in place. Just taking a time out and checking e-mails. Thanks Charlie, -- Darrell May DMC Netsourced.com http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
-Original Message- From: Darrell May [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 07, 2002 4:01 PM To: Charlie Brady; Darrell May Cc: [EMAIL PROTECTED] Subject: RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo Charlie Brady [EMAIL PROTECTED] said: This is especially true for servers running in serveronly mode. Absolutely, ... how did I miss that great example! Definitely not needed there and that takes care of most of the larger SME corporate clients where corporate firewalls/VPN are already in place doing their thing. I understand this, since you only implement masq in gateway mode, but I left that fact out of my previous post because I don't see it as being very feasible to have serveronly mode based on a 2.4.x kernel and server and gateway mode dependent on modules that force a 2.2.x kernel. How do you ship a product like that? David M. Brown Frick, Frick Jetté Architects [EMAIL PROTECTED] -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
On Thu, 7 Feb 2002, David Brown wrote: Charlie Brady [EMAIL PROTECTED] said: This is especially true for servers running in serveronly mode. Absolutely, ... how did I miss that great example! Definitely not needed there and that takes care of most of the larger SME corporate clients where corporate firewalls/VPN are already in place doing their thing. I understand this, since you only implement masq in gateway mode, but I left that fact out of my previous post because I don't see it as being very feasible to have serveronly mode based on a 2.4.x kernel and server and gateway mode dependent on modules that force a 2.2.x kernel. How do you ship a product like that? You (probably) don't. But that's a marketing problem not a development one. :-) -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
RE: [e-smith-devinfo] 2.4.x Kernel Upgrade Mini-HowTo
On Thu, 7 Feb 2002 [EMAIL PROTECTED] wrote: By the way, anyone find the src.rpm for the anacronda that was used to build the cd? It'll soon show up with all the other src.rpms from the 5.1.2 distribution. It was omitted because it's not in the RPMS directory, so was missing from my list. Good luck with it - anaconda is no fun to play with. -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Grouphttp://www.e-smith.com/ Mitel Networks Corporationhttp://www.mitel.com/ Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
