kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/sysutils/hal/files/hal.sh

28 lines
463 B
Bash
Raw Normal View History

Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
#!@RCD_SCRIPTS_SHELL@
#
Update hal with a SMF manifest and method and a correction for PKG_HOME.haldaemon to default to /var/run/hald instead of /var/run/hal The init script hardcoded /var/run/hald so now use the corrected variable. Also, use OPSYSVARS for BUILDLINK_TRANSFORMS adding one for SunOS -z.ignore bump PKGREVISION
2015-09-25 18:26:15 +02:00
# $NetBSD: hal.sh,v 1.3 2015/09/25 16:26:16 richard Exp $
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
#
# PROVIDE: hal
# REQUIRE: DAEMON dbus
# KEYWORD: shutdown
. /etc/rc.subr
name="hal"
rcvar=$name
command="@PREFIX@/sbin/hald"
start_precmd=hal_prestart
hal_prestart() {
Update hal with a SMF manifest and method and a correction for PKG_HOME.haldaemon to default to /var/run/hald instead of /var/run/hal The init script hardcoded /var/run/hald so now use the corrected variable. Also, use OPSYSVARS for BUILDLINK_TRANSFORMS adding one for SunOS -z.ignore bump PKGREVISION
2015-09-25 18:26:15 +02:00
dir="@PKG_HOME.haldaemon@"
Import hal version 0.5.11. Uses the 'dummy' backend on NetBSD for now, more to come soon. What is the point of HAL? To merge information from various sources such that desktop applications can locate and use hardware devices. The point is that the exact set of information to merge varies by device and bus type. In order to do this, we need to define a format for the information, hence the HAL specification. We may read some stuff from the hardware itself, then add some info provided by the kernel, then add some metadata from some systemwide files, then add some data that has been obtained by the desktop and stored per-user, then look at some blacklist, and finally we have a complete picture of everything known about that particular device. An extra value is that we can do this in an operating system independent way. Stuff like this is important to the major desktop environments.
2008-11-22 16:20:51 +01:00
if @TEST@ ! -d $dir; then
@MKDIR@ $dir
@CHMOD@ 0755 $dir
@CHOWN@ @HAL_USER@:@HAL_GROUP@ $dir
fi
@CHMOD@ 0755 "@VARBASE@/cache"
}
load_rc_config $name
run_rc_command "$1"
Reference in a new issue Copy permalink