<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: #606420; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=#606420 link=blue>
<DIV dir=ltr align=left><SPAN class=004473617-24032008><FONT face=Arial
color=#0000ff size=2>So in order to not use a ram disk and to still have access
to the files in the chrooted %post, you'd need to copy the files to a
directory beneath /mnt/sysimage during the %pre stage, right? Something
like /mnt/sysimage/var/tmp? This way no ram disk is needed and the data is
written in %pre and readable by %post.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=004473617-24032008></SPAN> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> kickstart-list-bounces@redhat.com
[mailto:kickstart-list-bounces@redhat.com] <B>On Behalf Of </B>Shabazian,
Chip<BR><B>Sent:</B> Monday, March 24, 2008 1:16 PM<BR><B>To:</B> Discussion
list about Kickstart<BR><B>Subject:</B> RE: using /dev/ram devices in RHEL5
kickstarts<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">The important thing to
know about this is that you can run TWO %post sections. In the first, you
can copy whatever you want from /tmp/your_dir to the chrooted /tmp, then you can
use your current %post within a chrooted
environment<o:p></o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
kickstart-list-bounces@redhat.com [mailto:kickstart-list-bounces@redhat.com]
<B><SPAN style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Kent
Baxley<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Monday, March 24,
2008 8:38 AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
kickstart-list@redhat.com<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> using /dev/ram devices in RHEL5
kickstarts</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">I'm researching a kickstart problem that deals with some
of the differences between RHEL4 and RHEL5. In RHEL 4, I could create a
RAM drive and copy files to this RAM drive in the %pre script portion of
kickstart. I would then open the RAM drive in the %post section.
This allowed me to pass information from the Pre to the Post processing
scripts. Because the %pre scripts do not have a local drive to write to at
this time in the installation process the became the easiest way tell the post
process scripts what went on during the pre script installation
choices.<BR><BR>In the past, I was able to use the following code to create a
ram drive during the %pre process of kickstart.<BR><BR>mkdir
/tmp/ramdisk<BR>mke2fs /dev/ram<BR>mount /dev/ram /tmp/ramdisk<BR><BR>This code
is right out of my kickstart.<BR><BR>Once in the %post process<BR><BR>mkdir
/tmp/ramdisk<BR>mount /dev/ram /tmp/ramdisk<BR><BR>Then I copy files from the
/tmp/ramdisk mount point.<BR><BR><BR>The /dev/ram devices seem to be missing
during the installation process, so, the above code snippents don't seem to work
anymore on RHEL5. I've found I can work around this by doing something
like:<BR><BR>mknod /dev/ram b 1 0<BR> <BR>Then continue with the steps
above, however, why is /dev/ram seemingly not created by default anymore in
RHEL5? Should I be using another method from here on out?<BR><BR>Another
possibility for passing data between %pre and %post environments, I've found,
could be:<BR><BR>%pre<BR>Create a tmpfs ram drive<BR>Copy files to
tmpfs<BR><BR>%post --nochroot<BR>copy files from tmpfs ram drive to
/mnt/sysimage/path<BR><BR>%post<BR>.<BR>.<BR><BR>Notice that the first %post
allows for a nochroot flag so I can copy data from the tmpfs. The second and
last %post is where I would run my bash scripts after the data in tmpfs has been
copied to the local hard drive.<BR><BR>So, my question is, will either option
(run mknod to create /dev/ram or use tmpfs) work, and what should I be doing for
RHEL5 installs and beyond? I'm also open to any other suggestions.
<BR><BR>Thanks!<o:p></o:p></SPAN></FONT></P></DIV></BODY></HTML>