Re: [revisor-users] [Revisor-users] custom Fedora install with drivers

[Jeroen van Meeuwen]

On 05/13/2009 05:28 PM, Brandon Blackmoor wrote:
>  Hello. New revisor/livecd-tools user here. Although I have
> recompiled
>  kernels and compiled a variety of software, I have never "spun" my own
>  linux distribution. So, please forgive the lengthy first post, but I
>  want to make sure I do not leave anything out before I ask my questions
>  at the end.
>
>  I have been asked to create a turnkey Linux install which will meet the
>  following requirements:
>
>  * After installation, the system will boot up in "kiosk" mode: no login
>  (at most, a "Guest" login), directly to a web browser, which loads
>  full-screen (no menu bar or address bar), directly to a specified web
>  page.
>
>  * The Linux installation needs to include some proprietary touch screen
>  drivers (eGalax), and the xorg.conf needs to be modified, too.
>
>  * The installation should require little or no user intervention: plug
>  in the USB drive, boot the machine, and hit "Enter" on the keyboard.
>
>  I can set up a machine that meets these requirements manually.
>
>  * I have the touchscreen drivers and the xorg.conf changes.
>
>  * I am told (although I have not yet tested it) that the xguest package
>  will enable a "kiosk" style desktop.
>
>  * I have a Firefox plugin to lock the web browser down.
>
>  Can Revisor allow me to turn this manual installation into a turnkey
>  custom installation, which does not require the user to manually install
>  drivers or edit xorg.conf?
>  
I think Revisor can, yes. If all these actions you perform can be 
performed using just the shell, then all commands needed to make it so 
will need to go into a %post section of the kickstart file.

Also note that with the copy_dir setting, Revisor allows you to specify 
the root of a directory tree on the composing host's filesystem that'll 
be copied over the root directory of the soon-to-be live system. This 
way you can copy in the files (such as drivers, new xorg.conf and the FF 
plugin).

The %post script in kickstart is supposed to be executed *after* the 
copying of files from the host composing the image onto the filesystem 
of the image, and so in %post you should be able to use the files you 
copied in.

>  If so... where do I start? Do I need to make a custom repository
> with
>  these touchscreen drivers? I have created a custom repo in the past (for
>  systems behind a firewall), but I have never created a RPM from scratch.
>  
I would recommend creating an RPM package for the touchscreen drivers, 
yes, but it's not an absolute requirement.

Kind regards,

Jeroen van Meeuwen
-kanarip

[Revisor-users] custom Fedora install with drivers

[Lars Bjørndal]

Jeroen van Meeuwen <kanarip(a)kanarip.com&gt; writes:

>  On 05/13/2009 05:28 PM, Brandon Blackmoor wrote: 
...
>  I think Revisor can, yes. If all these actions you perform can be 
>  performed using just the shell, then all commands needed to make it so 
>  will need to go into a %post section of the kickstart file.
>
>  Also note that with the copy_dir setting, Revisor allows you to specify 
>  the root of a directory tree on the composing host's filesystem that'll 
>  be copied over the root directory of the soon-to-be live system. This 
>  way you can copy in the files (such as drivers, new xorg.conf and the FF 
>  plugin).
>
>  The %post script in kickstart is supposed to be executed *after* the 
>  copying of files from the host composing the image onto the filesystem 
>  of the image, and so in %post you should be able to use the files you 
>  copied in. 
I tried copy_dir some months ago, but didn't get it working for some
reason. Should the copy_dir statement go in the %post section, or
somewhere before that. Could you please point me to an example spec
file where it's used?

Thanks and regards,
Lars

[Revisor-users] custom Fedora install with drivers

[Jeroen van Meeuwen]

On 05/16/2009 09:39 PM, Lars Bjørndal wrote:
>  Jeroen van Meeuwen<kanarip(a)kanarip.com>  writes:
>
> > On 05/13/2009 05:28 PM, Brandon Blackmoor wrote:
>  ...
> > I think Revisor can, yes. If all these actions you perform can be
> > performed using just the shell, then all commands needed to make it so
> > will need to go into a %post section of the kickstart file.
> >
> > Also note that with the copy_dir setting, Revisor allows you to specify
> > the root of a directory tree on the composing host's filesystem that'll
> > be copied over the root directory of the soon-to-be live system. This
> > way you can copy in the files (such as drivers, new xorg.conf and the FF
> > plugin).
> >
> > The %post script in kickstart is supposed to be executed *after* the
> > copying of files from the host composing the image onto the filesystem
> > of the image, and so in %post you should be able to use the files you
> > copied in.
>
>  I tried copy_dir some months ago, but didn't get it working for some
>  reason. Should the copy_dir statement go in the %post section, or
>  somewhere before that. Could you please point me to an example spec
>  file where it's used?
>  
copy_dir is a setting provided to Revisor using it's configuration files 
in /etc/revisor/revisor.conf. You can either specify copy_dir on the 
global level (the [revisor] section in /etc/revisor/revisor.conf) so it 
applies to all models, or per-model (for example, the [f10-i386] section 
in /etc/revisor/revisor.conf).

See also: 
https://fedorahosted.org/revisor/wiki/ConfigurationReference/copy_dir

Kind regards,

Jeroen van Meeuwen
-kanarip