VirtualBox in Ubuntu 8.04

When using the default intallation of CentOS i.e. Dynamically expanding disc,
as I did (rather than custom), the filesystem is LVM (Logical Volume Manager).
It seems a lot more flexible than ext3 etc. but difficult for me to understand.

What is your take on this filesystem ? Will it one day replace ext3 etc. ?

 

LVM is not a filesystem, more like filesystem manager.

It allows you to create partitions independent of the physical layout. For example, if you have 2 80GB disks, you can create a 130GB partition.

http://en.wikipedia.org/wiki/Logical_volume_management

Mrk

 

I must say CentOS 5.2 is working more or less perfectly in VB.
After adding rpmforge to the repos. (and setting priorities to a high 11 in order
to avoid any conflicts with the base installs), I can for instance play any
videos/music on or offline from local.
With only 512 MB allocated no prob. streaming from Youtube and Apple
trailers at the same time.
I have a screenshot update to show this. http://files.myopera.com/ocky/files/Multimedia in CentOS 5.2.png

Will definitely try CentOS on wife's laptop. Updates till March 2014 !

 

As you know I am currently running CentOS 5.2 as guest, Ubuntu 8.04 being the
host. The firewall in CentOS was enabled as an install option and also shows
as enabled in services running.
What I find strange is, that running as root, I am unable to use the command
line to check whether it is indeed running. For instance the command
# iptables -L results in "bash: command not found" ; rpm -q iptables shows that
they are installed. Also lsmod | grep ip_tables same story, cmd. not found.
I don't know why this is ?? Edit: am behind a router and using NAT for VB.

(PS - Ubuntu kernel was updated yesterday to 2.6.24-23. I used the
sudo etc/init.d/vboxdrv setup command and all was fine. I only have dkms
package on the host - not on the guest as recommended, because this package
is only available from the Third Party repo. rpmforge, and although I have
added this repo., I thought it better not to install - just in case.)

 

I don't know if you want to, but yesterday I put Virtualbox OSE on 8.10 and it worked fine, I checked and it doesn't require the kernel modules to be rebuilt each time, so if you plan on being a regular user of Virtualbox, I would recommend using 8.10 instead of 8.04.

 

Nah.. I prefer to stick with LTS - conservative I suppose. I will wait a couple of
months when I intend to migrate from desktop to notebook. Then I will try
Jaunty and/or Linux Mint. For the wife, CentOS which I am now 'trialing' in VB, and
provided there will be no unpleasant surprises.

Any ideas re. my query concerning iptables command as per my previous
post ?

 

Installing java for desktop on CentOS 5.2 is a little convoluted (for me). I stumbled across this blog site which explains it nicely :-
http://blog.sixsigns.com/2008/06/26/update-on-installing-jre-6-on-centos/
in case someone is interested. Unfortunately it seems to work best with the
jdk download/install which is rather large.

 

Hello,
Try with service ... as in service iptables ...
Cheers,
Mrk

 

No, I still get command not found. Maybe I am missing one or other package,
or it is a VirtualBox thing. I have copied this from sevices in the menus. The last section is for ip6 -plse. ignore.

Code:

Table: filter
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0           

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         
1    RH-Firewall-1-INPUT  all  --  0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination         

Chain RH-Firewall-1-INPUT (2 references)
num  target     prot opt source               destination         
1    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           
2    ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0           icmp type 255 
3    ACCEPT     esp  --  0.0.0.0/0            0.0.0.0/0           
4    ACCEPT     ah   --  0.0.0.0/0            0.0.0.0/0           
5    ACCEPT     udp  --  0.0.0.0/0            224.0.0.251         udp dpt:5353 
6    ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0           udp dpt:631 
7    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           tcp dpt:631 
8    ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0           state RELATED,ESTABLISHED 
9    REJECT     all  --  0.0.0.0/0            0.0.0.0/0           reject-with icmp-host-prohibited 


***************************************************************************************

Table: filter
Chain INPUT (policy ACCEPT)
num  target     prot opt source               destination         
1    RH-Firewall-1-INPUT  all      ::/0                 ::/0               

Chain FORWARD (policy ACCEPT)
num  target     prot opt source               destination         
1    RH-Firewall-1-INPUT  all      ::/0                 ::/0               

Chain OUTPUT (policy ACCEPT)
num  target     prot opt source               destination         

Chain RH-Firewall-1-INPUT (2 references)
num  target     prot opt source               destination         
1    ACCEPT     all      ::/0                 ::/0               
2    ACCEPT     icmpv6    ::/0                 ::/0               
3    ACCEPT     esp      ::/0                 ::/0               
4    ACCEPT     ah       ::/0                 ::/0               
5    ACCEPT     udp      ::/0                 ff02::fb/128       udp dpt:5353 
6    ACCEPT     udp      ::/0                 ::/0               udp dpt:631 
7    ACCEPT     tcp      ::/0                 ::/0               tcp dpt:631 
8    ACCEPT     udp      ::/0                 ::/0               udp dpts:32768:61000 
9    ACCEPT     tcp      ::/0                 ::/0               tcp dpts:32768:61000 flags:!0x16/0x02 
10   REJECT     all      ::/0                 ::/0               reject-with icmp6-adm-prohibited 

Regards, and thanks for churning out the sizzlers from the Dedoimedo forge !

 

After googling around I found the answer as to why the iptables commands
mentioned by me always resulted in "bash: command not found"

Unlike in Ubuntu, I needed to type su - root in the terminal (not just su, or
sudo as in Ubuntu)
For instance 'service iptables status' gave me the same output as shown in
my previous post. To see whether the iptables modules are loaded :-

[root@localhost ~]# lsmod | grep ip_tables
ip_tables 17029 1 iptable_filter
x_tables 17349 6 xt_state,ip_tables,ipt_REJECT,ip6t_REJECT,xt_tcpudp,ip6_tables
[root@localhost ~]#

I trust that these are the default settings for the firewall in CentOS 5 xx
( I know nothing about iptables and just wanted to be sure that they are loaded
and working).

 

I have spent some time getting CentOS guest running nicely on Ubuntu 8.04
host and would hate to lose my current state when updating from 2.1.0 to
2.1.2. (Sun version)
Going by the manual it seems one can install over the old version as long as
any running VM's are terminated and exiting VB. (2.3.4.4 in the manual).

I have only recently installed 2.1.0 and therefore have never updated, so any
advice would be appreciated .. eg.. will the guest additions need reinstalling etc.

 

Guests might need reinstalling. But that's all. Should be ...
As to iptables, the basic ruleset is the simple default-deny for inbound ... nothing fancy.
Mrk

 

Decided to add the repository and key and downloaded. Everything went
smoothly and I didn't have to re-install the Guest Additions. I don't see any
difference to 2.1.0, except that on start-up from a shutdown state, it uses
the first screen resolution I added to xorg.conf (1280x1024) - previously 800x600.
An improvement. In the VM itself I use 1024x768.

Great stuff !

Edit: Even CentOS can look OK with some different icons/skins for opera/firefox etc.
Screenie>>> CentOS in VB 2.1.2

 

But I think you should. Many changes in newer Virtualbox versions are usually due to improvements in the Guest Additions.

 

OK - I am sure you are right, as I saw an option in the installation to the effect
of More/OK/Exit and I clicked OK which probably loaded the existing Guest
Additions.
Thanks.

Edit: Done - no problems. I think CentOS can only use Guest Additions version 1.3 not 1.4 - maybe that's why
I still am unable to see much difference in settings etc.
Some features may not be available in CentOS 5.2 .. for example...

 

Update:
Thanks to this forum I have recently installed CentOS 5.2 on my wife's old
HP nx6110 laptop. What a pleasure. Only one problem - when the lid is
closed and then opened nothing will get the display going and one
needs to shut down.
(I did google and added some lines to xorg.conf but to no avail).
BUT the good news is that it suspends to RAM perfectly. She just has to remember
Fn+F3 (moon symbol).

Overall I am very impressed and find myself wanting to use this laptop more
and more. ( Hope it lasts till April 2014 when CentOS 5.2 support ends).

I am not sure whether the CentOS kernel will be compatible with newer
hardware.

PS. VirtualBox helped me to thoroughly check/test the CentOS 5.2 distro.
Thanks and regards.

 

well centos 5.3 should be out soon and supports new hardware including the new intel processers. rhel 5.3 is out so you just need to wait until centos build centos 5.3 from the source.

 

Ok, maybe good luck with my small lid closing problem.
yum update glibc (...seems to need updating beforehand)
yum update

 

Try adding the following line to your xorg.conf in the device section:

Option "ForceEnablePipeA" "true"

This is a fix for laptops with intel graphics, which I think yours has.

Cheers, Nick.

 

Will give it a try. Do I need to reboot ?
So far have added the following lines:-

Option "VBERestore" "1" (to the Device section), and new section:-

Section "ServerFlags"
Option "BlankTime" "0"
EndSection

If your solution doesn't do it, it won't be a train smash as the suspend to RAM
works perfectly.
Thanks.

 

Hi,

You will need to restart X for the settings to be reloaded, log out should do it.

No gaurantees it will work, but its quite common bug on the intel Xorg drivers (which are generally good quality).

 

Hi Nick,

Unfortunately no luck. It does seem to be a common problem and your
fix suggestion has done the job for a good number of folks, but there are
other unfortunates like me for whom it didn't help. Some even suggested
uninstalling the gnome screensaver etc.

Thanks anyway - will just use Fn+F3 to supend to RAM. Who knows, maybe
the update to CentOS 5.3 will patch this rather widespread problem.

Regards.