Re: [Cooker] Theregister 8.2 review
I've actually been looking for the name of that simple firewall wizard package since I reinstalled Mandrake 8.2 (really not the OS's fault, I had a family member decide it was a good idea to unplug the server between the box and it's UPS which resulted in the HDD spraying garbage all over the drive). Anyhow, would anyone happen to remember the name of that RPM? Mandrake comes with a LOT and I've looked through the Well the one I was using was Bastille but it seems to have fallen out of favour these days. -- Sitsofe | http://sucs.org/~sits/
Re: [Cooker] Theregister 8.2 review
On Friday August 16 2002 05:21 am, Sitsofe Wheeler wrote: I've actually been looking for the name of that simple firewall wizard package since I reinstalled Mandrake 8.2 (really not the OS's fault, I had a family member decide it was a good idea to unplug the server between the box and it's UPS which resulted in the HDD spraying garbage all over the drive). Anyhow, would anyone happen to remember the name of that RPM? Mandrake comes with a LOT and I've looked through the Well the one I was using was Bastille but it seems to have fallen out of favour these days. I believe he might be asking about /usr/sbin/tinyfirewall It starts a simple GUI conf for Bastille. It's been there all along, but since 8.2 the icon for running it was removed from MCC. It's provided with drakxtools-newt and also requires iptables and a Bastille rpm or two. Really only a suitable firewall conf for a desktop with a dialup tho. -- Tom Brinkman Corpus Christi, Texas
Re: [Cooker] Theregister 8.2 review
On Thu, Aug 15, 2002 at 09:34:53AM +0100, Sitsofe Wheeler wrote: Sorry to dredge this up but as Mandrake 9 is still in beta I'm reminded of few points in theregister review of Mandrake 8.2 (http://www.theregister.co.uk/content/4/25160.html). In it the reviewer which mentioned how a reinstallation was necessary after a failed kernel compile. I had my own little spin on this myself when I downloaded the stock kernel and compiled my own bad kernel. If this has changed in 9 then my apologies but in 8.2 the entries in lilo.conf for the mandrake kernels all used the vmlinuz symlink which is libel to change if a new (non mandrake kernel) is compiled thus causing grief if this kernel compile goes wrong. I really feel that the entries in lilo.conf should use the full kernel image name to guard against this (or perhaps some special mandrake kernel link). Concerning the .config file complaint (The config file had almost no relationship to the previously installed system.) - since I don't recompile the mandrake kernel I can't really comment on this. Yeah it's like that so kernel upgrades take effect without editing lilo.conf. If you compile a bad kernel and don't know how to use the rescue disk then you probably shouldn't be compiling the kernel. And nothing is stoping you from editing the lilo.conf. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org If your love has no hope of being welcomed do not voice it; for if it be silent it can endure, a guarded flame, within you. - The Wisdom of the Sands
Re: [Cooker] Theregister 8.2 review
On Thu, 2002-08-15 at 09:59, Ben Reser wrote: If this has changed in 9 then my apologies but in 8.2 the entries in lilo.conf for the mandrake kernels all used the vmlinuz symlink which is libel to change if a new (non mandrake kernel) is compiled thus causing grief if this kernel compile goes wrong. I really feel that the entries in lilo.conf should use the full kernel image name to guard against this (or perhaps some special mandrake kernel link). Yeah it's like that so kernel upgrades take effect without editing lilo.conf. If you compile a bad kernel and don't know how to use the rescue disk then you probably shouldn't be compiling the kernel. And nothing is stoping you from editing the lilo.conf. Um...but kernel upgrades change lilo.conf *anyway*. (They put a specifically directed entry for themselves, labelled with their kernel version and revision number, at the bottom of the menu - e.g. 2419-1 , pointing to -2.4.19.1mdk and not just the symlink). If they're going to do that I don't see what's to stop them editing something else in there. -- adamw
Re: [Cooker] Theregister 8.2 review
On Thu, Aug 15, 2002 at 09:34:53AM +0100, Sitsofe Wheeler wrote: Sorry to dredge this up but as Mandrake 9 is still in beta I'm reminded of few points in theregister review of Mandrake 8.2 (http://www.theregister.co.uk/content/4/25160.html). In it the reviewer which mentioned how a reinstallation was necessary after a failed kernel compile. I had my own little spin on this myself when I downloaded the stock kernel and compiled my own bad kernel. If this has changed in 9 then my apologies but in 8.2 the entries in lilo.conf for the mandrake kernels all used the vmlinuz symlink which is libel to change if a new (non mandrake kernel) is compiled thus causing grief if this kernel compile goes wrong. I really feel that the entries in lilo.conf should use the full kernel image name to guard against this (or perhaps some special mandrake kernel link). Concerning the .config file complaint (The config file had almost no relationship to the previously installed system.) - since I don't recompile the mandrake kernel I can't really comment on this. Yeah it's like that so kernel upgrades take effect without editing lilo.conf. If you compile a bad kernel and don't know how to use the rescue disk then you probably shouldn't be compiling the kernel. And nothing is stoping you from editing the lilo.conf. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org If your love has no hope of being welcomed do not voice it; for if it be silent it can endure, a guarded flame, within you. - The Wisdom of the Sands Or using grub, which allows you to type in the specific kernel, parameters and initrd you wish to use. It's saved me a few times when i built a bad kernel. Also, never delete the good kernel before testing the newly built one. Scott
Re: [Cooker] Theregister 8.2 review
1. Huh ? There is a way to make your own kernel according to some mandrake concept of what you're supposed to do ? 2. I have always gone and done everything after getting kernel source, lilo, System.map, etc., etc., etc., Like, I do hereby assume full responsibility... And I have not done that with 9B2 yet because it is 9B2 and deserves kicking around to see if it breaks. I feel like it is a given that no kernel will come perfectly out of the box... any comments appreciated here. 3. I have never seen any Mandrake says step 1 should be... Readme.txt or something please, or pointer to existing... ? -AEF On Thursday 15 August 2002 08:10 am, [EMAIL PROTECTED] wrote: On Thu, Aug 15, 2002 at 09:34:53AM +0100, Sitsofe Wheeler wrote: Sorry to dredge this up but as Mandrake 9 is still in beta I'm reminded of few points in theregister review of Mandrake 8.2 (http://www.theregister.co.uk/content/4/25160.html). Yeah it's like that so kernel upgrades take effect without editing lilo.conf. If you compile a bad kernel and don't know how to use the Ben Reser [EMAIL PROTECTED] Or using grub, which allows you to type in the specific kernel, parameters and initrd you wish to use. It's saved me a few times when i built a bad kernel. Also, never delete the good kernel before testing the newly built one.
Re: [Cooker] Theregister 8.2 review
On Thu, Aug 15, 2002 at 12:02:58PM +0100, Adam Williamson wrote: Um...but kernel upgrades change lilo.conf *anyway*. (They put a specifically directed entry for themselves, labelled with their kernel version and revision number, at the bottom of the menu - e.g. 2419-1 , pointing to -2.4.19.1mdk and not just the symlink). If they're going to do that I don't see what's to stop them editing something else in there. That's just cated on the end. And you're expecting users to be smart enough to know that their kernel is now 2419-1 instead of just linux... -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org If your love has no hope of being welcomed do not voice it; for if it be silent it can endure, a guarded flame, within you. - The Wisdom of the Sands
Re: [Cooker] Theregister 8.2 review
On Thu, 2002-08-15 at 09:26, allen wrote: 1. Huh ? There is a way to make your own kernel according to some mandrake concept of what you're supposed to do ? 2. I have always gone and done everything after getting kernel source, lilo, System.map, etc., etc., etc., Like, I do hereby assume full responsibility... And I have not done that with 9B2 yet because it is 9B2 and deserves kicking around to see if it breaks. I feel like it is a given that no kernel will come perfectly out of the box... any comments appreciated here. 3. I have never seen any Mandrake says step 1 should be... Readme.txt or something please, or pointer to existing... I beleive there is a Mandrake Kernel HOWTO at mandrakeuser.org that walks you thorugh a mdk rpm kernel upgrade, a mandrake kernel source (install src.rpm and compile) upgrade, and IIRC a get your source from kernel.org upgrade. If it no longer exists please contact me directly, I'd be interested in helping to write up a new one. ? -AEF On Thursday 15 August 2002 08:10 am, [EMAIL PROTECTED] wrote: On Thu, Aug 15, 2002 at 09:34:53AM +0100, Sitsofe Wheeler wrote: Sorry to dredge this up but as Mandrake 9 is still in beta I'm reminded of few points in theregister review of Mandrake 8.2 (http://www.theregister.co.uk/content/4/25160.html). Yeah it's like that so kernel upgrades take effect without editing lilo.conf. If you compile a bad kernel and don't know how to use the Ben Reser [EMAIL PROTECTED] Or using grub, which allows you to type in the specific kernel, parameters and initrd you wish to use. It's saved me a few times when i built a bad kernel. Also, never delete the good kernel before testing the newly built one.
Re: [Cooker] Theregister 8.2 review
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've actually been looking for the name of that simple firewall wizard package since I reinstalled Mandrake 8.2 (really not the OS's fault, I had a family member decide it was a good idea to unplug the server between the box and it's UPS which resulted in the HDD spraying garbage all over the drive). Anyhow, would anyone happen to remember the name of that RPM? Mandrake comes with a LOT and I've looked through the list a couple times now and still can't seem to find it. I'm looking for the graphical wizard that allows you to set the allowed services in the firewall config for incomming, yet retain all outgoing ports through the NAT. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj1cijkACgkQUMkt1ZRwL1OnXQCfQPZQrDoRTWA6MVX57UO9Z4k+ HRoAoLNrpeT/Avriz8Ar4cWTinAAFOV/ =LH8S -END PGP SIGNATURE-
Re: [Cooker] Theregister 8.2 review
snf? --- Richard G. Houser [EMAIL PROTECTED] wrote: I've actually been looking for the name of that simple firewall wizard package since I reinstalled Mandrake 8.2 (really not the OS's fault, I had a family member decide it was a good idea to unplug the server between the box and it's UPS which resulted in the HDD spraying garbage all over the drive). Anyhow, would anyone happen to remember the name of that RPM? Mandrake comes with a LOT and I've looked through the list a couple times now and still can't seem to find it. I'm looking for the graphical wizard that allows you to set the allowed services in the firewall config for incomming, yet retain all outgoing ports through the NAT. __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com
