difference of redhat 6.2 and 7.0

difference of redhat 6.2 and 7.0

[Brent Harding]

				What's really different between redhat 6.2 and 7.0? I've heard of the
problem of kernel 2.4 headers being used with the 2.2 kernels. I'm thinking
of getting a CD of 6.2, as I know there's a speakup image for it. Does
kickstart still work? I read the kickstart howto, but it looks like it
won't set lilo up to dual boot with windows.
 

Re: difference of redhat 6.2 and 7.0

[Ivan Fetch]

Hi,
   In addition to the kernel headers issue you mention, RedHat also
APPEARS to have shipped gcc 2.96 with Redhat 7.0.  The 2.96 version of GCC
was NOT meant for public consumption, and was supposed to be some kind of
beta which was only to be used/tested by Redhat themselves.  As a result
of RedHat releasing 2.96, GNU decided that there new version of GCC (when
it is ready to be released) will be called 2.97.  I have not specifically
asked RedHat nor GNU about this first hand, so if anyone would like to
correct me please feel free...  The bottom line is that some things with
GCC seem to be broken.  I am not sure whether there is a patch yet or some
other meccanism to role back to GCC 2.96.

   There is also some bug in Redhat 7.0 which causes a crash every two
weeks or so - some kind of memory leak.  I am not sure exactly where the
memory leak is - I think there is already an RPM update for it though.

   Depending on what you plan to use this machine for, I would recommend
staying with Redhat 6.2 and installing the RPM updates (for security,
Etc) from support.redhat.com.  I am waiting until RedHat 7.1 or 7.2 comes
out and some more bugs are fixed.  I personally do not like to install the
.0 release of something (especially not in a production environment) but
that's just me.

I hope this helps.  Anyone who cares to discuss the details of these
issues or provide an alternative point of view - I'm open for discussion.

Ivan.


On Sun, 29 Oct 2000, Brent Harding wrote:

> 				What's really different between redhat 6.2 and 7.0? I've heard of the
> problem of kernel 2.4 headers being used with the 2.2 kernels. I'm thinking
> of getting a CD of 6.2, as I know there's a speakup image for it. Does
> kickstart still work? I read the kickstart howto, but it looks like it
> won't set lilo up to dual boot with windows.
>  
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 
> 

Re: difference of redhat 6.2 and 7.0

[xander]

  > 
  > Hi,
  >    In addition to the kernel headers issue you mention, RedHat also
  > APPEARS to have shipped gcc 2.96 with Redhat 7.0.  The 2.96 version of GCC
  > was NOT meant for public consumption, and was supposed to be some kind of
  > beta which was only to be used/tested by Redhat themselves.  As a result
  > of RedHat releasing 2.96, GNU decided that there new version of GCC (when
  > it is ready to be released) will be called 2.97.  I have not specifically
  > asked RedHat nor GNU about this first hand, so if anyone would like to
  > correct me please feel free...  The bottom line is that some things with
  > GCC seem to be broken.  I am not sure whether there is a patch yet or some
  > other meccanism to role back to GCC 2.96.
  > 
  >    There is also some bug in Redhat 7.0 which causes a crash every two
  > weeks or so - some kind of memory leak.  I am not sure exactly where the
  > memory leak is - I think there is already an RPM update for it though.

RedHat 7.0 is a bit flaky indeed. 2.2.x kernel sources don't compile
properly. Better wait till 7.1 is out and run 6.2 in the meantime.

Regards,
xander van wiggen

Re: difference of redhat 6.2 and 7.0

[Brent Harding]

Oh, is there a script out that auto-updates things? Do I need a special
access code, I ordered 6.2 from cheapbytes last night. I figured the same
thing.
At 03:11 PM 10/29/00 -0700, you wrote:
>Hi,
>   In addition to the kernel headers issue you mention, RedHat also
>APPEARS to have shipped gcc 2.96 with Redhat 7.0.  The 2.96 version of GCC
>was NOT meant for public consumption, and was supposed to be some kind of
>beta which was only to be used/tested by Redhat themselves.  As a result
>of RedHat releasing 2.96, GNU decided that there new version of GCC (when
>it is ready to be released) will be called 2.97.  I have not specifically
>asked RedHat nor GNU about this first hand, so if anyone would like to
>correct me please feel free...  The bottom line is that some things with
>GCC seem to be broken.  I am not sure whether there is a patch yet or some
>other meccanism to role back to GCC 2.96.
>
>   There is also some bug in Redhat 7.0 which causes a crash every two
>weeks or so - some kind of memory leak.  I am not sure exactly where the
>memory leak is - I think there is already an RPM update for it though.
>
>   Depending on what you plan to use this machine for, I would recommend
>staying with Redhat 6.2 and installing the RPM updates (for security,
>Etc) from support.redhat.com.  I am waiting until RedHat 7.1 or 7.2 comes
>out and some more bugs are fixed.  I personally do not like to install the
>.0 release of something (especially not in a production environment) but
>that's just me.
>
>I hope this helps.  Anyone who cares to discuss the details of these
>issues or provide an alternative point of view - I'm open for discussion.
>
>Ivan.
>
>
>On Sun, 29 Oct 2000, Brent Harding wrote:
>
>> 				What's really different between redhat 6.2 and 7.0? I've heard of the
>> problem of kernel 2.4 headers being used with the 2.2 kernels. I'm thinking
>> of getting a CD of 6.2, as I know there's a speakup image for it. Does
>> kickstart still work? I read the kickstart howto, but it looks like it
>> won't set lilo up to dual boot with windows.
>>  
>> 
>> 
>> 
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>> 
>> 
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>

Re: difference of redhat 6.2 and 7.0

[L. C. Robinson]

According to the RedHat 6.1 reference guide (a chapter of
which, is the real manual for kickstart), if a windows
partition is present, it will automatically be configured
when the lilo directive is used.  The HOWTO is more of an
example guide, which helps, since the manual is lacking in
this area, but it lacks some specific details and options.

LCR

On Sun, 29 Oct 2000, Brent Harding wrote:

> know there's a speakup image for it. Does kickstart still
> work? I read the kickstart howto, but it looks like it
> won't set lilo up to dual boot with windows.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@usurf.com.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: difference of redhat 6.2 and 7.0

[Brent Harding]

What then does the mkkickstart utility do? Does it just make a kickstart
out of your current setup? Is there a way I can get it on zipspeak, so when
the CD comes in, I'm not in for anything too unexpected?
I don't think the howto gave much in the lilo directive. I'm not real sure
how usefull kickstart is, as most providers doing it on servers have to
edit the ip address and hostname in to the config so each server has that
info. Dhcp won't do it where static IP's are needed, or can dhcp allocate
fixed IP's to new machines not yet put online?
I mean, do some setups have a feature that when the IP is assigned on a
kickstart, it is excluded from those dynamically assignable by the server
itself?
At 06:48 PM 10/30/00 -0700, you wrote:
>According to the RedHat 6.1 reference guide (a chapter of
>which, is the real manual for kickstart), if a windows
>partition is present, it will automatically be configured
>when the lilo directive is used.  The HOWTO is more of an
>example guide, which helps, since the manual is lacking in
>this area, but it lacks some specific details and options.
>
>LCR
>
>On Sun, 29 Oct 2000, Brent Harding wrote:
>
>> know there's a speakup image for it. Does kickstart still
>> work? I read the kickstart howto, but it looks like it
>> won't set lilo up to dual boot with windows.
>
>-- 
>L. C. Robinson
>reply to no_spam+munged_lcr@usurf.com.invalid
>
>People buy MicroShaft for compatibility, but get incompatibility and
>instability instead.  This is award winning "innovation".  Find
>out how MS holds your data hostage with "The *Lens*"; see
>"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>

Re: difference of redhat 6.2 and 7.0

[L. C. Robinson]

You might want to take a look at autorpm:

Name: autorpm                      Relocations: (not relocateable)
Version: 1.9.8.4                           Vendor: Kirk Bauer <kirk@kaybee.org>
Size: 209494                           License: GPL
Packager: Kirk Bauer <kirk@kaybee.org>
URL: http://www.kaybee.org/~kirk/html/linux.html
Summary: RPM Auto-Installer or FTP Mirrorer
Description:
AutoRPM is a program that can do any combination of the following: mirror RPMs
from  an  FTP  site,  keep installed RPMs consistent with an FTP site or local
directory, and keep installed RPMs in a cluster or network of systems  consis-
tent.   It  is  highly  flexible  and even contains  a very  nice, menu-driven
Interactive-Install mode.

And it's even completely text based.  There are some other auto update schemes
I've seen, as well.  I didn't like RedHat's scheme, which came later.

LCR

On Mon, 30 Oct 2000, Brent Harding wrote:

> Oh, is there a script out that auto-updates things? Do I need a special
> access code, I ordered 6.2 from cheapbytes last night. I figured the same
> thing.


-- 
L. C. Robinson
reply to no_spam+munged_lcr@usurf.com.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: difference of redhat 6.2 and 7.0

[L. C. Robinson]

The man page says:
"mkkickstart creates a kickstart description file from the
current machine."

I can send you the whole man page, if it will help.  There
are some config option args available.  Seems like this
would be a nice way to get an initial config file ready
for manual editing, saving some work and time.  I'd be
interested to know how it works out for you.

I see no reason why you couldn't put the resulting kickstart
config file on whatever kind of installation disk you wish,
in the standard manner outlined in the HOWTO, and manual.
In a networked situation, such as you are describing,
though, it would seem better to put it on the server you are
installing from (assuming a network install).

I have only toyed with dhcp, but it appears to me that it
is extremely flexible, and can be configured to do anything
you want, including static addresses (using the bootp
protocol, which is included).  This is probably an area more
suited to the linux networking newsgroup.

Kickstart would probably be pretty useless on large
networks, where it is most desirable, if the networking
could not be readily configured via dhcp, using a standard
kickstart config file.

Incidentally, last night when I was updating my blinux
subscription (email address change), I noticed that RedHat
has a kickstart mailing list.

LCR

On Tue, 31 Oct 2000, Brent Harding wrote:

> What then does the mkkickstart utility do? Does it just make a kickstart
> out of your current setup? Is there a way I can get it on zipspeak, so when
> the CD comes in, I'm not in for anything too unexpected?
> I don't think the howto gave much in the lilo directive. I'm not real sure
> how usefull kickstart is, as most providers doing it on servers have to
> edit the ip address and hostname in to the config so each server has that
> info. Dhcp won't do it where static IP's are needed, or can dhcp allocate
> fixed IP's to new machines not yet put online?
> I mean, do some setups have a feature that when the IP is assigned on a
> kickstart, it is excluded from those dynamically assignable by the server
> itself?
> At 06:48 PM 10/30/00 -0700, you wrote:
> >According to the RedHat 6.1 reference guide (a chapter of
> >which, is the real manual for kickstart), if a windows
> >partition is present, it will automatically be configured
> >when the lilo directive is used.  The HOWTO is more of an
> >example guide, which helps, since the manual is lacking in
> >this area, but it lacks some specific details and options.
> >
> >LCR
> >
> >On Sun, 29 Oct 2000, Brent Harding wrote:
> >
> >> know there's a speakup image for it. Does kickstart still
> >> work? I read the kickstart howto, but it looks like it
> >> won't set lilo up to dual boot with windows.

-- 
L. C. Robinson
reply to no_spam+munged_lcr@usurf.com.invalid

Re: difference of redhat 6.2 and 7.0

[Brent Harding]

Wow, what is redhat's approach to autoupdate? I'll be saving this one for
when the CD comes in.
At 11:43 PM 10/31/00 -0700, you wrote:
>You might want to take a look at autorpm:
>
>Name: autorpm                      Relocations: (not relocateable)
>Version: 1.9.8.4                           Vendor: Kirk Bauer
<kirk@kaybee.org>
>Size: 209494                           License: GPL
>Packager: Kirk Bauer <kirk@kaybee.org>
>URL: http://www.kaybee.org/~kirk/html/linux.html
>Summary: RPM Auto-Installer or FTP Mirrorer
>Description:
>AutoRPM is a program that can do any combination of the following: mirror
RPMs
>from  an  FTP  site,  keep installed RPMs consistent with an FTP site or
local
>directory, and keep installed RPMs in a cluster or network of systems
consis-
>tent.   It  is  highly  flexible  and even contains  a very  nice,
menu-driven
>Interactive-Install mode.
>
>And it's even completely text based.  There are some other auto update
schemes
>I've seen, as well.  I didn't like RedHat's scheme, which came later.
>
>LCR
>
>On Mon, 30 Oct 2000, Brent Harding wrote:
>
>> Oh, is there a script out that auto-updates things? Do I need a special
>> access code, I ordered 6.2 from cheapbytes last night. I figured the same
>> thing.
>
>
>-- 
>L. C. Robinson
>reply to no_spam+munged_lcr@usurf.com.invalid
>
>People buy MicroShaft for compatibility, but get incompatibility and
>instability instead.  This is award winning "innovation".  Find
>out how MS holds your data hostage with "The *Lens*"; see
>"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>

Re: difference of redhat 6.2 and 7.0

[Brent Harding]

Wow, sounds cool! Will it work if I ssh in to an already up box and run it,
so I have something local? I mean, cutting the file section out of the
howto is probably not easy.
At 12:53 AM 11/1/00 -0700, you wrote:
>The man page says:
>"mkkickstart creates a kickstart description file from the
>current machine."
>
>I can send you the whole man page, if it will help.  There
>are some config option args available.  Seems like this
>would be a nice way to get an initial config file ready
>for manual editing, saving some work and time.  I'd be
>interested to know how it works out for you.
>
>I see no reason why you couldn't put the resulting kickstart
>config file on whatever kind of installation disk you wish,
>in the standard manner outlined in the HOWTO, and manual.
>In a networked situation, such as you are describing,
>though, it would seem better to put it on the server you are
>installing from (assuming a network install).
>
>I have only toyed with dhcp, but it appears to me that it
>is extremely flexible, and can be configured to do anything
>you want, including static addresses (using the bootp
>protocol, which is included).  This is probably an area more
>suited to the linux networking newsgroup.
>
>Kickstart would probably be pretty useless on large
>networks, where it is most desirable, if the networking
>could not be readily configured via dhcp, using a standard
>kickstart config file.
>
>Incidentally, last night when I was updating my blinux
>subscription (email address change), I noticed that RedHat
>has a kickstart mailing list.
>
>LCR
>
>On Tue, 31 Oct 2000, Brent Harding wrote:
>
>> What then does the mkkickstart utility do? Does it just make a kickstart
>> out of your current setup? Is there a way I can get it on zipspeak, so when
>> the CD comes in, I'm not in for anything too unexpected?
>> I don't think the howto gave much in the lilo directive. I'm not real sure
>> how usefull kickstart is, as most providers doing it on servers have to
>> edit the ip address and hostname in to the config so each server has that
>> info. Dhcp won't do it where static IP's are needed, or can dhcp allocate
>> fixed IP's to new machines not yet put online?
>> I mean, do some setups have a feature that when the IP is assigned on a
>> kickstart, it is excluded from those dynamically assignable by the server
>> itself?
>> At 06:48 PM 10/30/00 -0700, you wrote:
>> >According to the RedHat 6.1 reference guide (a chapter of
>> >which, is the real manual for kickstart), if a windows
>> >partition is present, it will automatically be configured
>> >when the lilo directive is used.  The HOWTO is more of an
>> >example guide, which helps, since the manual is lacking in
>> >this area, but it lacks some specific details and options.
>> >
>> >LCR
>> >
>> >On Sun, 29 Oct 2000, Brent Harding wrote:
>> >
>> >> know there's a speakup image for it. Does kickstart still
>> >> work? I read the kickstart howto, but it looks like it
>> >> won't set lilo up to dual boot with windows.
>
>-- 
>L. C. Robinson
>reply to no_spam+munged_lcr@usurf.com.invalid
>
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>

Re: difference of redhat 6.2 and 7.0

[L. C. Robinson]

Yes, it works as an ordinary user in text mode, such as:

ssh some.machine
/usr/sbin/mkkickstart --nfs some_server.localnet:/mnt/cdrom --dhcp --nox > /tmp/ks.cfg

The result, however, is potentially destructive of existing
data, unless you edit the "zerombr" and "clearpart"
directives, and unless the machine you are cloning is
set up similar to what you want on your target machine, it
might be better to start from a good example kickstart,
since you will still have to do a lot of editing and
checking.  In my case, doing it this way, would be the long
way around.

LCR

On Wed, 1 Nov 2000, Brent Harding wrote:

> Wow, sounds cool! Will it work if I ssh in to an already
> up box and run it, so I have something local? I mean,
> cutting the file section out of the howto is probably not
> easy.

> At 12:53 AM 11/1/00 -0700, you wrote:
> >The man page says:
> >"mkkickstart creates a kickstart description file from the
> >current machine."
> >
> >I can send you the whole man page, if it will help.  There
> >are some config option args available.  Seems like this
> >would be a nice way to get an initial config file ready
> >for manual editing, saving some work and time.  I'd be
> >interested to know how it works out for you.
> >
> >I see no reason why you couldn't put the resulting kickstart
> >config file on whatever kind of installation disk you wish,
> >in the standard manner outlined in the HOWTO, and manual.
> >In a networked situation, such as you are describing,
> >though, it would seem better to put it on the server you are
> >installing from (assuming a network install).
> >
> >I have only toyed with dhcp, but it appears to me that it
> >is extremely flexible, and can be configured to do anything
> >you want, including static addresses (using the bootp
> >protocol, which is included).  This is probably an area more
> >suited to the linux networking newsgroup.
> >
> >Kickstart would probably be pretty useless on large
> >networks, where it is most desirable, if the networking
> >could not be readily configured via dhcp, using a standard
> >kickstart config file.
> >
> >Incidentally, last night when I was updating my blinux
> >subscription (email address change), I noticed that RedHat
> >has a kickstart mailing list.
> >
> >LCR
> >
> >On Tue, 31 Oct 2000, Brent Harding wrote:
> >
> >> What then does the mkkickstart utility do? Does it just make a kickstart
> >> out of your current setup? Is there a way I can get it on zipspeak, so when
> >> the CD comes in, I'm not in for anything too unexpected?
> >> I don't think the howto gave much in the lilo directive. I'm not real sure
> >> how usefull kickstart is, as most providers doing it on servers have to
> >> edit the ip address and hostname in to the config so each server has that
> >> info. Dhcp won't do it where static IP's are needed, or can dhcp allocate
> >> fixed IP's to new machines not yet put online?
> >> I mean, do some setups have a feature that when the IP is assigned on a
> >> kickstart, it is excluded from those dynamically assignable by the server
> >> itself?
> >> At 06:48 PM 10/30/00 -0700, you wrote:
> >> >According to the RedHat 6.1 reference guide (a chapter of
> >> >which, is the real manual for kickstart), if a windows
> >> >partition is present, it will automatically be configured
> >> >when the lilo directive is used.  The HOWTO is more of an
> >> >example guide, which helps, since the manual is lacking in
> >> >this area, but it lacks some specific details and options.
> >> >
> >> >LCR
> >> >
> >> >On Sun, 29 Oct 2000, Brent Harding wrote:
> >> >
> >> >> know there's a speakup image for it. Does kickstart still
> >> >> work? I read the kickstart howto, but it looks like it
> >> >> won't set lilo up to dual boot with windows.
> >
> >-- 
> >L. C. Robinson
> >reply to no_spam+munged_lcr@usurf.com.invalid
> >
> >
> >
> >
> >_______________________________________________
> >Blinux-list mailing list
> >Blinux-list@redhat.com
> >https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> >
> >
> 
> 
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
> 

-- 
L. C. Robinson
reply to no_spam+munged_lcr@usurf.com.invalid

People buy MicroShaft for compatibility, but get incompatibility and
instability instead.  This is award winning "innovation".  Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html

Re: difference of redhat 6.2 and 7.0

[L. C. Robinson]

They ship a package called up2date which is GUI only, and
builds an interactive web page: kinda useless, in my book.

OTOH, autorpm can be configured to run nightly through cron,
without any tending, and to send you email about what it
finds, and if it downloaded anything, and if you gave it
permission, what it installed/updated, all while monitoring
several mirrors.  It will also authenticate packages via
gnugp or pgp automatically, again, emailing you the result.
It does take more effort to set it up, and learn all the
features (but there is a decent example configuration, so
one can shortcut this, if all the features are not needed).
In the long run, it's far less work, even for sighted users.

LCR

On Wed, 1 Nov 2000, Brent Harding wrote:

> Wow, what is redhat's approach to autoupdate? I'll be
> saving this one for when the CD comes in.


-- 
L. C. Robinson
reply to no_spam+munged_lcr@usurf.com.invalid

Re: difference of redhat 6.2 and 7.0

[Brent Harding]

Oh, I was just going to use one of of the free accounts I can get to get
the file, and download it to my machine, and delete the clear partitions
deal, I suppose the mbr can be cleared for a new lilo.
At 12:18 PM 11/2/00 -0700, you wrote:
>Yes, it works as an ordinary user in text mode, such as:
>
>ssh some.machine
>/usr/sbin/mkkickstart --nfs some_server.localnet:/mnt/cdrom --dhcp --nox >
/tmp/ks.cfg
>
>The result, however, is potentially destructive of existing
>data, unless you edit the "zerombr" and "clearpart"
>directives, and unless the machine you are cloning is
>set up similar to what you want on your target machine, it
>might be better to start from a good example kickstart,
>since you will still have to do a lot of editing and
>checking.  In my case, doing it this way, would be the long
>way around.
>
>LCR
>
>On Wed, 1 Nov 2000, Brent Harding wrote:
>
>> Wow, sounds cool! Will it work if I ssh in to an already
>> up box and run it, so I have something local? I mean,
>> cutting the file section out of the howto is probably not
>> easy.
>
>> At 12:53 AM 11/1/00 -0700, you wrote:
>> >The man page says:
>> >"mkkickstart creates a kickstart description file from the
>> >current machine."
>> >
>> >I can send you the whole man page, if it will help.  There
>> >are some config option args available.  Seems like this
>> >would be a nice way to get an initial config file ready
>> >for manual editing, saving some work and time.  I'd be
>> >interested to know how it works out for you.
>> >
>> >I see no reason why you couldn't put the resulting kickstart
>> >config file on whatever kind of installation disk you wish,
>> >in the standard manner outlined in the HOWTO, and manual.
>> >In a networked situation, such as you are describing,
>> >though, it would seem better to put it on the server you are
>> >installing from (assuming a network install).
>> >
>> >I have only toyed with dhcp, but it appears to me that it
>> >is extremely flexible, and can be configured to do anything
>> >you want, including static addresses (using the bootp
>> >protocol, which is included).  This is probably an area more
>> >suited to the linux networking newsgroup.
>> >
>> >Kickstart would probably be pretty useless on large
>> >networks, where it is most desirable, if the networking
>> >could not be readily configured via dhcp, using a standard
>> >kickstart config file.
>> >
>> >Incidentally, last night when I was updating my blinux
>> >subscription (email address change), I noticed that RedHat
>> >has a kickstart mailing list.
>> >
>> >LCR
>> >
>> >On Tue, 31 Oct 2000, Brent Harding wrote:
>> >
>> >> What then does the mkkickstart utility do? Does it just make a kickstart
>> >> out of your current setup? Is there a way I can get it on zipspeak,
so when
>> >> the CD comes in, I'm not in for anything too unexpected?
>> >> I don't think the howto gave much in the lilo directive. I'm not real
sure
>> >> how usefull kickstart is, as most providers doing it on servers have to
>> >> edit the ip address and hostname in to the config so each server has
that
>> >> info. Dhcp won't do it where static IP's are needed, or can dhcp
allocate
>> >> fixed IP's to new machines not yet put online?
>> >> I mean, do some setups have a feature that when the IP is assigned on a
>> >> kickstart, it is excluded from those dynamically assignable by the
server
>> >> itself?
>> >> At 06:48 PM 10/30/00 -0700, you wrote:
>> >> >According to the RedHat 6.1 reference guide (a chapter of
>> >> >which, is the real manual for kickstart), if a windows
>> >> >partition is present, it will automatically be configured
>> >> >when the lilo directive is used.  The HOWTO is more of an
>> >> >example guide, which helps, since the manual is lacking in
>> >> >this area, but it lacks some specific details and options.
>> >> >
>> >> >LCR
>> >> >
>> >> >On Sun, 29 Oct 2000, Brent Harding wrote:
>> >> >
>> >> >> know there's a speakup image for it. Does kickstart still
>> >> >> work? I read the kickstart howto, but it looks like it
>> >> >> won't set lilo up to dual boot with windows.
>> >
>> >-- 
>> >L. C. Robinson
>> >reply to no_spam+munged_lcr@usurf.com.invalid
>> >
>> >
>> >
>> >
>> >_______________________________________________
>> >Blinux-list mailing list
>> >Blinux-list@redhat.com
>> >https://listman.redhat.com/mailman/listinfo/blinux-list
>> >
>> >
>> >
>> 
>> 
>> 
>> _______________________________________________
>> Blinux-list mailing list
>> Blinux-list@redhat.com
>> https://listman.redhat.com/mailman/listinfo/blinux-list
>> 
>
>-- 
>L. C. Robinson
>reply to no_spam+munged_lcr@usurf.com.invalid
>
>People buy MicroShaft for compatibility, but get incompatibility and
>instability instead.  This is award winning "innovation".  Find
>out how MS holds your data hostage with "The *Lens*"; see
>"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
>