Pardus Linux: "As our installer does not recognize your Linux distribution..." -> fixed in 3.0.2

[trixon]

As our installer does not recognize your Linux distribution, we were unable to set up the initialization script vboxnet correctly. The script has been copied copied to the /etc/init.d directory. You should set up your system to start it at system start, or start it manually before using VirtualBox.

If you would like to help us add support for your distribution, please open a new ticket on ​http://www.virtualbox.org/wiki/Bugtracker. VirtualBox has been installed successfully.

[Michael Thayer]

If you would like to help us add support for Pardus to VirtualBox, the following information would help us greatly:

• how to detect Pardus (probably a file called /etc/pardus-version or similar)
• how to add an init script which we have placed in /etc/init.d to the default runlevel
• how to remove an init script from the default runlevel

Thanks a lot!

[trixon]

1. cat /etc/pardus-release

2. You can start your own scripts automatically by putting them in the file /etc/conf.d/local.start

To see the currently running services that are handled by Pardus (mudur / comar) in the default runlevel:

service list

To start such a service:

service servicename start

To add it to the default runlevel so that it will start automatically the next time the system boots:

service servicename on

[Frank Mehnert]

Replying to trixon:

1. cat /etc/pardus-release

That means that the file exists but does not have any content, right? That is, ls -l /etc/pardus-release shows you a file size of 0?

[Michael Thayer]

Replying to trixon: Just to clarify that - could we setup our vboxdrv service by copying the script to /etc/init.d/vboxdrv and executing:

service vboxdrv on

And presumably stop it again with:

service vboxdrv off

Changing /etc/conf.d/local.start from inside a script is not something that we will do, as the danger of getting something wrong and messing up the script is too great.

[trixon]

Replying to frank:

Replying to trixon:

1. cat /etc/pardus-release

That means that the file exists but does not have any content, right? That is, ls -l /etc/pardus-release shows you a file size of 0?

No, the file has contents, in my case:
Pardus 2007.2

ls -l /etc/pardus-release
-rw-r--r-- 1 root root 14 24 aug 11.38 /etc/pardus-release

[trixon]

Replying to michael:

Replying to trixon: Just to clarify that - could we setup our vboxdrv service by copying the script to /etc/init.d/vboxdrv and executing:

service vboxdrv on

And presumably stop it again with:

service vboxdrv off

Changing /etc/conf.d/local.start from inside a script is not something that we will do, as the danger of getting something wrong and messing up the script is too great.

No, that will not work. Im sory that I cant tell you any ore since Im new to Pardus.

[Ozan Çağlayan]

Hi,

Starting from the beginning, here are the informations that you asked:

Detecting Pardus

Pardus release information is hold in a file called /etc/pardus-release. It's a one-line text file containing for example such version information:

ozan@cyclope pardus $ cat /etc/pardus-release
Pardus 2008.1 Hyaena hyaena

How to add/remove an init script placed in /etc/init.d to the default runlevel

Well it's a little bit tricky in here. We have /etc/init.d but it is not related at all to our init system and thus to the runlevels. We're using pythonized init system, every service is represented by a well defined python script. You can take a look at the script written for microcode-ctl package:

​http://svn.pardus.org.tr/pardus/devel/applications/hardware/microcode-ctl/comar/service.py

After writing the related script(Let's call it vbox-pardus.py), all you have to do is to call hav for registering/unregistering the script to the init system:

# hav register vboxdrv System.Service vbox-pardus.py (For registering)
# hav remove vboxdrv (For unregistering)

Now let's see an example output of /bin/service which lists the current services:

# LC_ALL=C service
     Service       |  Status |  Autostart  | Description
--------------------------------------------------------
acpid              | running |     yes     | ACPI Daemon
...
...
vboxdrv            |         |     yes     | VirtualBox Kernel Driver

If you're willing to support us, we can help writing the service script.

Regards,

---

For more information about writing service scripts for Pardus, you can look at: ​http://developer.pardus.org.tr/Service_Scripts

[Michael Thayer]

Sorry that I haven't got around to this yet. If you can hang on a bit longer, I will do it at some point!

[Michael Thayer]

Update: I have (finally!) added experimental support for Pardus locally to our host installer, but it won't make it into 3.0 anymore. If you can hang on a bit longer I can provide you with a test build to try out.

[Michael Thayer]

My current, rather hackish solution, uses a Pardus python script wrapper (not quite correct from the looks of it, but correct enough to do the job) around an init script which I install to /usr/sbin (I never really liked software automatically putting things in /etc anyway, as that is supposed to be a place for manual user configuration). It would make more sense to me to auto-generate the python wrapper. Does Pardus have anything like that now which works with lsb init scripts?

[Michael Thayer]

By the way, is there any information available in English about the format of Pardus (Pisi?) packages?

[trixon]

Hi, here are some links

​http://developer.pardus.org.tr/pisi/index.html
​http://en.pardus-wiki.org/Actions_API
​http://en.pardus-wiki.org/Building_Packages

There is a package here
​http://svn.pardus.org.tr/pardus/2009/devel/hardware/virtualization/virtualbox/

[Michael Thayer]

Our installer should now support Pardus. The Additions installer does not, as Pardus comes with pre-installed Additions, and I don't like having our installer mess about too much with the installed system.