[RIJEŠENO] Arch Linux-vmware daemon, start on boot

[glaskoncILLa]

khm, rekao bih da nije ni tu, treba naci na koji nacin napravi onaj $daemon array i na koji nacin odluci o redoslijedu.. sto je mozda u /etc/sysctl.conf, mozda u sumi, a mozda bi bilo brze procitati dokumenataciju ili ga smjesiti u rc.local.

[Lutherus]

jel treba nekome još i gentoo raskopati i složiti dok sam tu ??

šalim se , naravno.uvjek ga može smjestiti u rc.local

[pingu]

Nema druge majstori. /etc/rc.local je najjednostavnije i najbrže rješenje.

To su te sitnice koje volim kod Archa i BSD inita. KISS - Keep It Short and Simple.

A ja nepotrebno kompliciram.

[glaskoncILLa]

tu ipak fali malo detalja, mislim da je sysv daleko skalabilniji i "upravljiviji" pristup..

[simke]

jedna od uputa.

Run sudo mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d to create VMware runlevel directories.
Run sudo ln -s /bin/lsmod /sbin/ to create symlink for lsmod.
Extract VMware server tarball somewhere... i.e. /tmp/.
Run cd /tmp/vmware-server-distrib;sudo ./vmware-install.pl. I used /home/vmware/bin for installation.
When it asks where the directories for rc0.d thru rc6.d are, use /etc/rc.d/vmware.d.
When it asks where the init directory is, use /etc/rc.d.

[pingu]

tu ipak fali malo detalja, mislim da je sysv daleko skalabilniji i "upravljiviji" pristup..

Nemam znanja i iskustva da bi mogao primjetiti te razlike kao sysadmini u nekom produkcijskom okruženju, serveri i slično, SysV vs BSD init, ali kao početniku, ovaj BSD pristup mi je dobro sjeo i intuitivno mogu rješavati probleme.

@simke
Nije potrebno sve to raditi za VMware Player 3.0, možda je potrebno za stariji 2.5.

VMWare Player >= 2.5

Download the VMware-Player-xxx-xxx.<architecture>.bundle file from the VMWare Website and save it in any directory you like. Then, you need to create the same directories as you need installing VMWare Server. As root:

# mkdir -p /etc/rc.d/vmware.d/rc{0,1,2,3,4,5,6}.d

Then execute (as root) the installation binary:

# ./VMware-Player-xxx-xxx.<architecture>.bundle

When it promts for System Service Runlevels answer:

/etc/rc.d/vmware.d/

If you get told that "/etc/rc.d/vmware.d is not an init directory", create some dummy directories:

cd /etc/rc.d/vmware.d
mkdir rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d init.d

For System Service Scripts use:

/etc/rc.d

You do not need to manually reconfigure the kernel modules each time you perform a kernel update. VMPlayer will do this for you when you start it up.

Infact, vmware-config.pl is gone. If you need to manually reconfigure your kernel modules do (as root):

/usr/bin/vmware-modconfig --console --install-all

[glaskoncILLa]

tu ipak fali malo detalja, mislim da je sysv daleko skalabilniji i "upravljiviji" pristup..

Nemam znanja i iskustva da bi mogao primjetiti te razlike kao sysadmini u nekom produkcijskom okruženju, serveri i slično, SysV vs BSD init, ali kao početniku, ovaj BSD pristup mi je dobro sjeo i intuitivno mogu rješavati probleme.

ne treba ti znanje ni iskustvo, samo razmisli.
dakle, sad ti pase da se virtualka digne nakon svega ostalog i rc.local ( koji postoji valjda na svakoj i sysv oriented distri osim sisea ) je ok rjesenje, ali sto da zelis da se to digne kao prvi servis ili 7edmi?

ne kazem da se to ne moze, ali ipak nije toliko intinuitivno..

[pingu]

ne treba ti znanje ni iskustvo, samo razmisli.
dakle, sad ti pase da se virtualka digne nakon svega ostalog i rc.local ( koji postoji valjda na svakoj i sysv oriented distri osim sisea ) je ok rjesenje, ali sto da zelis da se to digne kao prvi servis ili 7edmi?

ne kazem da se to ne moze, ali ipak nije toliko intinuitivno..

Možda sam krivo shvatio pitanje, ali redoslijed podizanja demona u Arch linuxu (vjerovatno slično ide u Slackwareu, Frugalwareu, za gentoo i FreeBSD nisam siguran, ali mi Arch ima najbolje posloženu konfiguracijsku strukturu u odnosu na Slack, Frugal i slične BSD init distre, imho) ide onim redoslijedom kako je napisano u demon sekciji rc.conf file-a. Npr.

Kod: Označi sve

DAEMONS=(syslog-ng @network @netfs @crond @alsa @cpufreq dbus hal)

Kada bi želio da mi se podigne GDM ili KDM login manager kao daemon (a ne preko /etc/inittab metode), onda bi ga nakon hal-a stavio zadnjeg na listu, što je razumljivo, jer ga nema smisla stavljati prije nego se ostali ključni servisi uključe a prouzrokovalo bi probleme prilikom podizanja grafičkog sučelja.

[glaskoncILLa]

khm, malo me zbunio odinov, bilo mi je cudno da unutra ima samo wicd i hal i bla..?

[pingu]

khm, malo me zbunio odinov, bilo mi je cudno da unutra ima samo wicd i hal i bla..?

Mislim da je odinov, od njegovog Arch live projekta.

Ovako izgleda generički Arch Linux rc.conf:

Kod: Označi sve

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
#
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NET_PROFILES=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)