* I incorporated Regular Expressions for get the information of the package name.
* To find out the source of a package, I’m consulting the local database, if the file is not in the local database then I using yumloader .
* The program is retrieving a txt file to the user, detailing about the packages included in the .iso, this file will detail this kind of situations:
for example you asked for this package:
ruby-gtksourceview-0.18.0-1.fc10
And the program is retrieving this one to you instead:
ruby-gnome2-0.18.1-5.fc10
Because the source of ruby-gtksourceview is ruby-gnome2, so this file would for information purposes.

* I’m checking if two files came from the same source, the source is just downloaded once.
* Some other small changes in the code.

although I have some issues like the text file has some content at the end of the program execution, but when is included into the iso image the content is lost partially (need to dig into it).
Another issue is when I’m working with this particular package: ruby-gtksourceview-0.18.0-1.fc10 during the execution several lines like this appear:
sh: ruby: command not found
I don’t think is related to the program, although can be, I’m not sure.

I need to incorporate a way to read any kind of CD/DVD’s, for now my code reads just Live CD’s, that is part of the improves for coming releases, among with validations in several points.

For take a look in my project click here.

I appreciate suggestions and comments.

Install the next packages:

ypbind

ypserv

yp-tools

Setting up NIS Server:

Set the domainname in the master server by the command domainname, example:

#domainname nad810.org

Until this moment in /var/yp/ directory, there is two elements:

1. bindings directory (which is empty) and
2. nicknames file, which has this content:

• passwd passwd.byname
• group group.byname
• networks networks.byaddr
• hosts hosts.byname
• protocols protocols.bynumber
• services services.byname
• aliases mail.aliases
• ethers ethers.byname

Modify the Makefile to support:

• • Minimum UID 5000

  • Minimum GID 5000

  • Enable slave servers

  • Merge user password and group password

  • map files for passwd, group, hosts, rpc, and services

Run the command ypinit -m

* perhaps is neccesary to give the entire path for ypinit command and run it like this:

#/usr/lib/yp/ypinit -m

You will be prompt by this command to notify the names of any NIS servers. (important don’t get confuse in between server’s host name and domain name). So when the name of the server is in the list press Ctrl + D for finish.

Edit the files:

• securenets

  In this file we specified which clients are valid for the server respond to. If nothing is specified in this file, the access is given to everyone. For security reasons is recommended specify the IP address or the networks allowed to use NIS.

  Note: In my case I have this file in /usr/share/doc/ypserv-2.19/securenets, and I configured it to allow any host in the network 192.168.7.0/24.

• /etc/ypserv.conf

  This file is the configuration file for the ypserv daemon. It also may be used to control the behavior of the rpc.ypxfrd daemon if is being used.

  I decided leave the file without any change.

If there is any slave server:

# /etc/rc.d/init.d/ypxfrd start

Start the NIS server:

# /etc/rc.d/init.d/ypserv start

Initialize the rpc.yppasswdd daemon if you want to handle NIS passwords:

# /etc/rc.d/init.d/yppasswdd start

Initialize the maps files:

# /etc/rc.d/init.d/ypbind start

Now is necessary edit /etc/nsswitch.conf, this file tells the system where to look for database files.

I added “nis” to this entries in that file:

passwd files nis

shadow files nis

group: files nis

hosts: files dns nis

Setup a NIS client

Set the same domain name that the NIS server:

#domainname nad810.org

Edit the /etc/yp.conf file and add:

ypserver <NIS server IP> (or any other option explained in the file)

This file is used to control the behaviour of the client daemon. You are allowed to specify domains and/or servers in this file.

After that:

#service ypbind start

or

# /etc/rc.d/init.d/ypbind start

Setting NFS:

In the Server:

Modify the file /etc/exports/ adding this line:

/home 192.168.7.0/24(rw,sync)

Where 192.168.122.0/24 is my network.

In the Client:

Install autofs package

Edit the /etc/auto.master file and add this entry:

/home /etc/auto.home –timeout 600

Edit the /etc/auto.home file adding this entry:

* -fstype=nfs,soft,intr 192.168.7.33:/home/&

Edit the /etc/exports file adding:

/home *(rw, sync)

Restart the autofs service:

service autofs start

If you want to keep after reboot do:

service autofs start

How it works?

When configured for network booting (PXE is not the only way, there is some more like Etherboot or NetBoot) the client first requests an IP address from the LTSP Server (which has a DHCP server running).

Once the IP has been gotten, the Linux kernel is transfer to the client by TFTP protocol, which is another server running in the LTSP server.

Then, the client mounts its root filesystem, by the NFS server running in the LTSP Server. After that loads Linux and starts the X window system. The client connects to the XDMCP login manager on the LTSP server.

I installed ltsp version 5.1, so in this version (and any newer that 5) the client first builds an SSH tunnel to the LTSP server’s X environment, through which it will start the LDM login manager (on the LTSP server). From this point forward, all programs are started on the LTSP server, but displayed and operated from the client.

………………………………………………………………………………………………………………………………………………………………………………………………………………………

To try this package I used my Laptop which have Fedora 10, following the steps that the guys from “K12Linux” (LTSP for Fedora) recommend in their Install Guide.

So, I installed the ltsp-server package:

# yum install ltsp-server

And since I want to test the client in the same machine but I can’t use KVM (my Laptop does not support virtualization very well) I don’t need to install ltsp-lvclient, instead of that, I will use a virtual machine on VirtualBox.

- This entry should have to be added to /etc/exports file:

/opt/ltsp *(ro,async,no_root_squash)

That will mount the files within ‘/opt/ltsp’ (server) into the client root filesystem with read-only permissions.

- We need a interface for handle the LTSP as well, we can use the ifup command for that:

# ifup ltspbr0

- This will bring this new interface up, run ifconfig command and the new interface will be there:

if you want to have it even after rebooting, need to have networking running (chkconfig network on)

- We need to turn on and start (by using ‘chkconfig servicename on’ and ‘service servicename start’) the next services:

xinetd

ltsp-dhcpd

rpcbind

nfs

sshd

And then, put the next servers on:

ldminfod

nbdrootd

nbdswapd

tftp

- Now the next step will take time (believe me, better do something else meanwhile….), execute this command to build the client:

# ltsp-build-client

When that be finish, you will see the next message:

In my case I had some troubles with my machine so I had to do it twice, if that  happen to you, you have to erase the content of /opt/ltsp/ file before try to build the client again, otherwise it won’t let you do it.

Now is time to test it, open you VirtualBox (I assume that you have already one machine on it). Select the machine’s settings (because we need to specify that the interface used by our vm is ltspbr0) and in the Network tab change the interface like this:

Specifying the interface for Virtual the machine.

Then, start the machine and press F12 to enable PXE (stand for Preboot eXecution Environment, also know as “pixie”). Through that we won’t let the system start the boot process from the local hard drive, but from the network interface.

If everything goes right, the authentication screen will appear:

So you can authenticate with any valid user name in your machine.

I found this project useful since I have an extra machine at home, kind of old, but which can be useful for this purpose, so if I’m using my desktop computer, somebody else could use the old pc to connect as client of it and both work at the same time, nice…!, don’t you think?

Very long night, but with good results…

This is my code:  CorrespondingSource0.9

I tested it with a Fedora 10 Live CD, what it does is find the file system, mount it (for all the ones who knows how is a Live CD and all that mess with the images: yeah, was fun!), then access the rpm database of the CD and give a list of all the packages that are including in the disk.

I plan to merge this with the code that I already have done and hopefully be able to add more features to this project.

(I’m a Python newbie so, welcome any suggestion).

To see the script click HERE

Komodo Editor has other capabilities like multi-language file support (Perl, PHP, Python, CSS, HTML, JavaScript, XML… etc),  Vi emulation among some others things (that I guess will be able to discover very soon).

So, I downloaded it from:  http://www.activestate.com/komodo_edit/

I got the tarball, unzipped it, run the install.sh script… but I got this message:

chcon: unrecognized option ‘–quiet’
Try `chcon –help’ for more information.
chcon: unrecognized option ‘–quiet’
Try `chcon –help’ for more information.
chcon: unrecognized option ‘–quiet’
Try `chcon –help’ for more information.
chcon: unrecognized option ‘–quiet’
Try `chcon –help’ for more information.
install: error: could not set SELinux security context for ‘/home/Patty/Komodo-Edit-5/lib/python/lib/libpython2.6.so’: ‘texrel_shlib_t’, ‘textrel_shlib_t’, ‘shlib_t’, ‘s0′ contexts failed

To fix the problem it necessary  just make a small change in the file: selinuxlib.py (which is in the installation package directory, inside of “support” directory) in this line:

cmd = ‘chcon -t %s –quiet “%s”‘ % (context, path)

to make it like this:

cmd = ‘chcon -t %s “%s”‘ % (context, path)

and it will works without any problems.

So if somebody want to try it and get same trouble, just need to try this.

* Loop through the files in your home directory, and for each readable file, ask whether the file should be printed, mailed to you, or ignored (P/M/I) and then take the appropriate action.

*Count the number of files in the user’s home directory which are not readable.

Kino is a video editor software which has options for cut scenes, apply some special effects, export video to a different formats and some other features. The help manual is short but a lot clear and you can see example images.

For apply special effects for example you can just click on FX Icon (ubicated in the right side panel) and specify the time that the effect should start and finish:

and apply either Audio or Video filters that you prefer:

Example of Soft Focus Video Filter

The list of Audio effects includes: Dub, Fade In, Fade Out, Gain, Mix and Silence.

Options for Video filters include: Blur, Charcoal, Colour Average, Colour Hold, Flip, Jerky, Kaleidoscope, Levels, Mirror, Pan and Zoom, Pixelate, Soft Focus, Superimpose, Titler and some others…

Video with Pixelate and Titler effects...

I used Pixelate and Titler video filters, and fade out and silence audio filters for the closing part of my video; I cut just a small piece from the video where the effects can be appreciated, so if you want to take a look and see how this effects look like click here.

Also this software is capable to export video to different formats such as: DVD, Flash, H.264 MP4, MP3, MPEG-4 3GPP, MPEG-4 AVI, OGG, VCD and some others… (the videos in the link are in OGG and Flash formats).

Kino works good with videos not too big, and editing is relatively easy, it has a very simple graphic interface and exporting files to other formats is fast and works very well.

The tricky part is make a kickstart file, to see more information about how create kickstart files visit this link: http://fedoraproject.org/wiki/Anaconda/Kickstart#Creating_the_Kickstart_File.

This a example of one:

repo –name=release –mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9&arch=$basearch
repo –name=updates –mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f9&arch=$basearch

%packages –nobase
bash
kernel
passwd
policycoreutils
chkconfig
authconfig
rootfiles
anaconda-runtime
isomaster
pingus

%end

To tell Pungi to make a spin out of that file, type this command in the shell window:
#pungi -c <kickstartfile.cfg> –nosource –force –ver=<DestinyDirectory>

You will get a Directory, with a iso image inside, next thing is burn it or use the qemu tool to try it (to a view of its use check “Using Fedora livecd-tools” post).

A live CD or DVD is designed in a special way that when is run, the system contained on it appears in the screen as similar as possible to the standard system with all the features that can be possible included, and when the the CD/DVD is ejected from the computer (reboot may be necessary) the original system is returned as usual.

The term “live” derives from the fact that these CDs each contain a complete, functioning and operational operating system. There are also Live USB flash drives which are similar to live CDs, but often have the added functionality of automatically and transparently writing changes back to their bootable medium.

So in this post I will talk about how to generate live CDs or DVD’s on Fedora based systems, giving an example procedure. Here the steps:

* Login as root in a Machine with Fedora Operative System.

* Install Live cd tools by typing in the command line:
# yum install livecd-tools

This will install some kickstarts files in this location: /usr/share/livecd-tools, the files generated will depend of with version of Fedora you are working with, I’m using Fedora 9 (then it created files from all the Fedora previous versions until the one that I’m using), these are the list of files that I got in my machine:

livecd-fedora-7-desktop.ks
livecd-fedora-7-kde.ks
livecd-fedora-8-base-desktop.ks
livecd-fedora-8-desktop.ks
livecd-fedora-8-developer.ks
livecd-fedora-8-electronic-lab.ks
livecd-fedora-8-games.ks
livecd-fedora-8-kde.ks
livecd-fedora-9-base-desktop.ks
livecd-fedora-9-desktop.ks
livecd-fedora-9-kde.ks
livecd-fedora-base-desktop.ks
livecd-fedora-desktop.ks
livecd-fedora-developer.ks
livecd-fedora-electronic-lab.ks
livecd-fedora-games.ks
livecd-fedora-kde.ks
livecd-fedora-minimal.ks
livedvd-fedora-kde.ks

* Pick one of them (I used: livecd-fedora-9-base-desktop.ks).

* For avoid problems related to selinux, I disabled it, by editing the file and changing the correspondent line, like this:
…
selinux –disabled
…

* Saved your changes and in the command line type:
# livecd-creator -c livecd-fedora-9-base-desktop.ks

This will generate a iso image with your chosen live CD option. This may take some time so… you might have enough time for a cup of tea (I was working with a wireless connection so I could have the entire dinner!).

When it finished, you will have a new file, this is the one that I got: livecd-fedora-9-base-desktop-200812061928.iso

Now you can either burn it or use tools like qemu  and kvm to try it out. If you choose the second option, you should install those packages, in the command line type:
# yum install kvm qemu

Once it finish, type:
# qemu-kvm -m 512 -cdrom livecd-fedora-9-base-desktop-200812061928.iso

and if everything is correct then you will be able to see a screen like this:

QEMU running a Live CD iso image

References:
1. http://fedoraproject.org/wiki/How_to_create_and_use_Fedora_LiveCD
2. http://en.wikipedia.org/wiki/Live_CD