If you use an LVM for root ..  I find it's a 'good' thing to have a separate
non-LVM for /boot.  Seems like RH defaults to partitioning a single minidisk
with /boot in dasda1, swap in dasda2, and root LVM on dasda3.  (Or maybe
that's just how the kickstart file I was using did things?)..

Anyway -- as Marcy said - it's also handy to be able to DDR /boot
separately..

Scott

On Wed, Jul 2, 2008 at 10:29 AM, Marcy Cortes <[EMAIL PROTECTED]>
wrote:

> The other advantage to a small /boot minidisk of its own in a VM
> environment is that if you mess it up (like your maintenance to the
> kernel missed doing mkinitrd/zipl) , you can DDR a good one from a
> another server.
>
>
> Marcy
> "This message may contain confidential and/or privileged information. If
> you are not the addressee or authorized to receive this for the
> addressee, you must not use, copy, disclose, or take any action based on
> this message or any information herein. If you have received this
> message in error, please advise the sender immediately by reply e-mail
> and delete this message. Thank you for your cooperation."
>
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Edmund R. MacKenty
> Sent: Wednesday, July 02, 2008 9:22 AM
> To: [email protected]
> Subject: Re: [LINUX-390] Question DASD on CLIENT from Start system
> instructions
>
> On Wednesday 02 July 2008 12:02, Mark Post wrote:
> >Some people like to break /boot out into a separate partition, even on
>
> >System z.  It's not necessary, per se, since mainframe's don't have any
>
> >BIOS limitations to work around.  But, some people feel more
> >comfortable  with it, or want their mainframe systems to look more like
>
> >their midrange  ones.
>
> One reason for having /boot on a separate filesystem is to keep it safe.
> Some distros (Gentoo, perhaps Debian?) default to a separate /boot
> filesystem which is not mounted by default.  This keeps your pesky users
> from mucking with it.  It also ensures that the /boot filesystem is
> never mounted read-write during normal operations, including reboots.
> This pretty much avoids the possibility of filesystem corruption.  The
> only time you mount it read-write is when you have to install a new
> kernel into it.
>
> So a separate /boot is a safety measure.
>        - MacK.
> -----
> Edmund R. MacKenty
> Software Architect
> Rocket Software, Inc.
> Newton, MA USA
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to