VirtualBox

Ticket #697 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

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

Reported by: trixon Owned by:
Priority: major Component: installer
Version: VirtualBox 3.0.0 Keywords:
Cc: Guest type: other
Host type: Linux

Description

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.

Change History

comment:1 Changed 7 years ago by michael

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!

comment:2 follow-ups: ↓ 3 ↓ 4 Changed 7 years ago by trixon

  1. cat /etc/pardus-release
  1. 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

comment:3 in reply to: ↑ 2 ; follow-up: ↓ 5 Changed 7 years ago by 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?

comment:4 in reply to: ↑ 2 ; follow-up: ↓ 6 Changed 7 years ago by 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.

comment:5 in reply to: ↑ 3 Changed 7 years ago by 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

comment:6 in reply to: ↑ 4 Changed 7 years ago by 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.

comment:7 Changed 6 years ago by frank

  • Host type changed from other to Linux

comment:8 Changed 6 years ago by frank

  • Component changed from other to installer

comment:9 Changed 5 years ago by ozan.caglayan

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

comment:10 Changed 5 years ago by michael

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!

comment:11 Changed 5 years ago by michael

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.

comment:12 Changed 5 years ago by michael

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?

comment:13 Changed 5 years ago by michael

  • Version changed from VirtualBox 1.5.0 to VirtualBox 2.2.4

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

comment:15 Changed 5 years ago by michael

  • Status changed from new to closed
  • Version changed from VirtualBox 2.2.4 to VirtualBox 3.0.0
  • Resolution set to fixed
  • Summary changed from Pardus Linux: "As our installer does not recognize your Linux distribution..." to Pardus Linux: "As our installer does not recognize your Linux distribution..." -> fixed in 3.0.2

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.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use