RE: FreeBSD
Пользователи, просматривающие топик: none
|
Зашли как: Guest
|
Имя  |
| Сообщение |
<< Старые топики Новые топики >> |
|
|
RE: FreeBSD - 2009-07-14 14:44:58.843333
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
quote:
Теперь вообще нечего, не ставится.
У меня всего только, не грузились пакеты.
cd /usr/ports/x11-servers/xorg-server && make install clean Так?
|
|
|
|
|
RE: FreeBSD - 2009-07-14 18:24:07.100000
|
|
|
ArtDDSS
Сообщений: 493
Оценки: 0
Присоединился: 2008-09-20 16:51:15.550000
|
пишет нет такой деректорий.
|
|
|
|
|
RE: FreeBSD - 2009-07-19 20:50:51.473333
|
|
|
ArtDDSS
Сообщений: 493
Оценки: 0
Присоединился: 2008-09-20 16:51:15.550000
|
У меня были проблемы с инетом теперь все а норме скачалось=)
|
|
|
|
|
Как запустить Gnome на Free BSD 7.2 - 2009-07-22 18:59:11.846666
|
|
|
Ufogen
Сообщений: 20
Оценки: 0
Присоединился: 2009-03-11 11:37:37.370000
|
В файле /etc/rc.conf
прописал gdm_enable="YES"
После чего перезагружаюсь, ничего неполучается.
Подскажите как запустить Gnome на Free BSD 7.2 ?
|
|
|
|
|
RE: FreeBSD - 2009-07-22 19:05:45.180000
|
|
|
Анон
Сообщений: 632
Оценки: 0
Присоединился: 2008-07-21 22:14:59.233333
|
# /etc/rc.d/gdm start ну или
$ echo "exec gnome-session" > ~/.xinitrc && startx
Дуй хендбук читать.
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-07-22 19:08:01.850000
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
Еще
ee /etc/rc.conf
hald_enable='"YES"
gnome_enable="YES"
dbus_enable="YES"
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-07-22 22:34:58.950000
|
|
|
Ufogen
Сообщений: 20
Оценки: 0
Присоединился: 2009-03-11 11:37:37.370000
|
Где какчнуть руссифицированый порт для Gnome 2.26? И есть ли он?
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-07-23 00:10:44.093333
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
Плохая новость - такого порта еще нет.
Хорошая - ты можешь создать его сам.(/usr/ports/russian/gnome). Хы-хы-хы-хы-хы
А пока что, можно настроить локаль:
ee ~/.login_conf
# $FreeBSD: src/share/skel/dot.login_conf,v 1.3.34.1 2009/04/15 03:14:26 kensmith Exp $
#
# see login.conf(5)
#
#me:\
# :charset=iso-8859-1:\
# :lang=de_DE.ISO8859-1:
me:ufogen:\
:charset=KOI8-R:\
:lang=ru_RU.KOI8-R:
Этим ты добъешся локализации на русском языке.
Вопрос: а для чего тебе это? man pages на английском языке ведь. И документация исходных текстов тоже …
Руссификация Гнома тебе сильно не поможет в освоении FreeBSD.
Я так думаю.
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 01:17:23.586666
|
|
|
sergeiprog
Сообщений: 302
Оценки: 0
Присоединился: 2007-04-24 10:02:27.956666
|
ребята выручайте!!!!!!!!!!!!!
не как не могу запустить KDE на freeBSD 7.2
установил все что требуется, запускаю startx, startkde результате зависают спасение только ctrl+alt+del
запускается kdm появляется окно ввода, но не работает ни клава ни мышь ((((((((
вот что пишет
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "vmware" (module does no exist, 0)
(EE) Failed to load module "fbdevhw" (module does no exist, 0)
что делать????????
при попытке создать конфиг Xorg -configure, ругается на fbdevhw(на отсутствие)[&:]
конфиги пустые!!!
что делать?!?? где брать?!?!?
читал и хэндбук и гуглил и чатился, осталось НАДЕЖДА ТОЛЬКО НА ВАС
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 10:12:07.076666
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
cd /usr/ports/x11-drivers/xf86-video-fbdev/ && make install clean
cd /usr/ports/x11-drivers/xf86-video-vmware/ && make install clean Для xorg.conf смотри здесь
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 11:17:43.403333
|
|
|
sergeiprog
Сообщений: 302
Оценки: 0
Присоединился: 2007-04-24 10:02:27.956666
|
quote:
ORIGINAL: mobydick
cd /usr/ports/x11-drivers/xf86-video-fbdev/ && make install clean
cd /usr/ports/x11-drivers/xf86-video-vmware/ && make install clean Для xorg.conf смотри здесь
с начало он требовал fbdev, тогда установка xf86-video-fbdev помогла теперь требует fbdevhw
после установки vmware
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "fbdevhw" (module does not exist, 0)
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 11:23:47.200000
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
ee /etc/rc.conf
hald_enable="YES"
dbus_enable="YES"
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 11:56:02.673333
|
|
|
sergeiprog
Сообщений: 302
Оценки: 0
Присоединился: 2007-04-24 10:02:27.956666
|
теперь выскакивает сообщение при загрузки
login: acd0: FAILURE -unknown CMD (0x03) ILLEGAL REQUEST asc=0x24 ascq=0x0
acd0: FAILURE -unknown CMD (0x03) ILLEGAL REQUEST asc=0x24 ascq=0x0
acd0: FAILURE -unknown CMD (0x03) ILLEGAL REQUEST asc=0x24 ascq=0x0
acd0: FAILURE -unknown CMD (0x03) ILLEGAL REQUEST asc=0x24 ascq=0x0
хотя диск я отключил ?!?!?
но мышь и клава заработала!!!!!!!!!
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 12:23:27.636666
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
Не обращай внимания на эти сообщения! Это у всех так.
Xorg работает сейчас?
Если нужен GNOME, пропиши
gnome_enable="YES" в /etc/rc.conf.
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 13:05:21.406666
|
|
|
sergeiprog
Сообщений: 302
Оценки: 0
Присоединился: 2007-04-24 10:02:27.956666
|
да, я kdm запускаю
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-10 17:17:59.373333
|
|
|
sergeiprog
Сообщений: 302
Оценки: 0
Присоединился: 2007-04-24 10:02:27.956666
|
блин теперь KDE не хочет поменять разрешение экрана на 1024х768.
при запуске X -config xorg.config.new пишет
(II) Loading extension MIT-SCREEN-SAVER
(EE) XKB: No components provided for device Virtual core keyboard
|
|
|
|
|
RE: Как запустить Gnome на Free BSD 7.2 - 2009-08-22 00:03:57.643333
|
|
|
benkor
Сообщений: 154
Оценки: 0
Присоединился: 2007-11-25 20:12:53.990000
|
quote:
(EE) XKB: No components provided for device Virtual core keyboard
# portupgrade x11/xkeyboard-config
|
|
|
|
|
2 сетевых подключения. - 2009-08-31 16:22:06.373333
|
|
|
cry1ngw0lf
Сообщений: 4
Оценки: 0
Присоединился: 2009-08-31 16:13:48.476666
|
Помогите пожалуйста определится с направлением в какую сторону копать.
Есть веб сервер и два сетевых интерфейса ( и два интернета ) нужно настроить FreeBSD Таким образом что бы каждому сетевому интерфейсу соответсвовал свой defaultrouter.
Заранее спасибо.
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-09-02 06:59:21.340000
|
|
|
scsport
Сообщений: 2
Оценки: 0
Присоединился: 2009-05-01 15:36:59.773333
|
копай на оффсайте! в разделе route!
http://www.freebsd.org/doc/ru/books/handbook/network-routing.html
чтобы долго не парился - вот пример двух подсетей
#/etc/rc.conf
static_routes="net1 net2"
route_net1="-net 192.168.0.0/24 192.168.0.1"
route_net2="-net 192.168.1.0/24 192.168.1.1"
**********************************************
#/etc/resolv.conf
nameserver 214.55.64.7
nameserver 1.5.63.2
думаю тут понятно примерно:) ты бы хоть конфигурацию описал или ещё там чё:)…зачем два интернета….одна как правило внутрення сетка
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-09-02 14:49:58.403333
|
|
|
cry1ngw0lf
Сообщений: 4
Оценки: 0
Присоединился: 2009-08-31 16:13:48.476666
|
У меня просто свой web сервер и к нему подведено два канала от разных провайдеров. Тем самым я пытаюсь увеличить отказоустойчивость.
То есть если запросы приходят на интерфейс номер 1 то ответ должен идти тоже с него. Для второго соответственно.
Так как у меня в #/etc/rc.conf записан defaultrouter … то интернет работает только по одному каналу.
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-09-10 16:56:02.983333
|
|
|
cry1ngw0lf
Сообщений: 4
Оценки: 0
Присоединился: 2009-08-31 16:13:48.476666
|
Нашел следующее решение если вдруг кому-то понадобится.
1. Пересобрал ядро с опциями подержки ipfw и нескольких таблиц маршрутизации.
2. Указал в первой таблице 1 гейтвей. для второй другой (setfib)
3. Правилами ipfw разруливаю когда какую из таблиц маршрутизации использовать
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-09-15 10:47:49.066666
|
|
|
cry1ngw0lf
Сообщений: 4
Оценки: 0
Присоединился: 2009-08-31 16:13:48.476666
|
К сожалению это заработало только на тестовой машине … продолжаю копать в этом направлении.
Видимо не хватает еще чего то.
Если у кого то получалось настроить на FreeBSD 2 инета .. отпишитесь пожалуйста.
|
|
|
|
|
Запуск скрипта из rc.d - 2009-09-16 12:51:26.290000
|
|
|
motorola
Сообщений: 64
Оценки: 0
Присоединился: 2007-11-13 19:44:42.273333
|
Привет, подскажите хочу запустить консольный скрипт после старта системы, пишу
создаю скриптик в /usr/local/etc/rc.d/runs
#!/bin/sh
/home/public/script.php
ставлю chmod 775 на ./usr/local/etc/rc.d/runs и на /home/public/script.php
запускаю ./usr/local/etc/rc.d/runs
php скрипт успешно отрабатываеться
но после перезагрузки системы из rc.d автоматом не запускаеться, подскажите что делаю неправильно
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-11-16 14:32:22.910000
|
|
|
kenpa
Сообщений: 8
Оценки: 0
Присоединился: 2008-12-04 19:12:51.073333
|
quote:
ORIGINAL: cry1ngw0lf
К сожалению это заработало только на тестовой машине … продолжаю копать в этом направлении.
Видимо не хватает еще чего то.
Если у кого то получалось настроить на FreeBSD 2 инета .. отпишитесь пожалуйста.
Для этих задач можно использовать функцию reply-to из pf. На ipfw такое реализуется из конструкций skipto tag fwd.
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-11-16 14:37:55.333333
|
|
|
kenpa
Сообщений: 8
Оценки: 0
Присоединился: 2008-12-04 19:12:51.073333
|
quote:
ORIGINAL: cry1ngw0lf
У меня просто свой web сервер и к нему подведено два канала от разных провайдеров. Тем самым я пытаюсь увеличить отказоустойчивость.
То есть если запросы приходят на интерфейс номер 1 то ответ должен идти тоже с него. Для второго соответственно.
Так как у меня в #/etc/rc.conf записан defaultrouter … то интернет работает только по одному каналу.
Выбирай из двух вариантов:
1. Собственная AS + BGP.
2. Исходящий: менять дефолт по факту падения линка. Входящий: заводить свою зону, выставлять маленький TTL, выдавать в ответ на запросы только те адреса, которые в настоящий момент живые.
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-11-23 05:53:29.603333
|
|
|
AloneHate
Сообщений: 76
Оценки: 0
Присоединился: 2008-01-13 07:36:57.400000
|
Народ на хорошую(на мой взгляд!!!) книжку нарвался по бсдям, стараниц почти 1К, кому интересно ссылка
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-11-25 12:58:32.123333
|
|
|
WinLinux
Сообщений: 491
Оценки: 0
Присоединился: 2008-07-18 14:06:33.563333
|
Хорошая книга только для начинающих + не много староватая уже…
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-12-07 18:05:28.153333
|
|
|
CASPER2
Сообщений: 46
Оценки: 0
Присоединился: 2007-02-22 15:48:33.700000
|
Ктонибуть может подсказать как на FreeNas создать потключение к инету по PPPoE? Гдето читал что можно интегрировать некоторые фаилы и ядро из FreeBSD! Может кто-то подскажет?
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-12-08 20:39:37.113333
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
Авось поможет?
# $FreeBSD: src/sys/conf/NOTES,v 1.1553.2.4 2009/11/15 11:30:59 stas Exp $
#
# NOTES -- Lines that can be cut/pasted into kernel and hints configs.
#
# Lines that begin with 'device', 'options', 'machine', 'ident', 'maxusers',
# 'makeoptions', 'hints', etc. go into the kernel configuration that you
# run config(8) with.
#
# Lines that begin with 'hint.' are NOT for config(8), they go into your
# hints file. See /boot/device.hints and/or the 'hints' config(8) directive.
#
# Please use ``make LINT'' to create an old-style LINT file if you want to
# do kernel test-builds.
#
# This file contains machine independent kernel configuration notes. For
# machine dependent notes, look in /sys/<arch>/conf/NOTES.
#
#
# NOTES conventions and style guide:
#
# Large block comments should begin and end with a line containing only a
# comment character.
#
# To describe a particular object, a block comment (if it exists) should
# come first. Next should come device, options, and hints lines in that
# order. All device and option lines must be described by a comment that
# doesn't just expand the device or option name. Use only a concise
# comment on the same line if possible. Very detailed desсriрtions of
# devices and subsystems belong in man pages.
#
# A space followed by a tab separates 'options' from an option name. Two
# spaces followed by a tab separate 'device' from a device name. Comments
# after an option or device should use one space after the comment character.
# To comment out a negative option that disables code and thus should not be
# enabled for LINT builds, precede 'options' with "#!".
#
#
# This is the ``identification'' of the kernel. Usually this should
# be the same as the name of your kernel.
#
ident LINT
#
# The `maxusers' parameter controls the static sizing of a number of
# internal system tables by a formula defined in subr_param.c.
# Omitting this parameter or setting it to 0 will cause the system to
# auto-size based on physical memory.
#
maxusers 10
#
# The `makeoptions' parameter allows variables to be passed to the
# generated Makefile in the build area.
#
# CONF_CFLAGS gives some extra compiler flags that are added to ${CFLAGS}
# after most other flags. Here we use it to inhibit use of non-optimal
# gcc built-in functions (e.g., memcmp).
#
# DEBUG happens to be magic.
# The following is equivalent to 'config -g KERNELNAME' and creates
# 'kernel.debug' compiled with -g debugging as well as a normal
# 'kernel'. Use 'make install.debug' to install the debug kernel
# but that isn't normally necessary as the debug symbols are not loaded
# by the kernel and are not useful there anyway.
#
# KERNEL can be overridden so that you can change the default name of your
# kernel.
#
# MODULES_OVERRIDE can be used to limit modules built to a specific list.
#
makeoptions CONF_CFLAGS=-fno-builtin #Don't allow use of memcmp, etc.
#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
#makeoptions KERNEL=foo #Build kernel "foo" and install "/foo"
# Only build ext2fs module plus those parts of the sound system I need.
#makeoptions MODULES_OVERRIDE="ext2fs sound/sound sound/driver/maestro3"
makeoptions DESTDIR=/tmp
#
# FreeBSD processes are subject to certain limits to their consumption
# of system resources. See getrlimit(2) for more details. Each
# resource limit has two values, a "soft" limit and a "hard" limit.
# The soft limits can be modified during normal system operation, but
# the hard limits are set at boot time. Their default values are
# in sys/<arch>/include/vmparam.h. There are two ways to change them:
#
# 1. Set the values at kernel build time. The options below are one
# way to allow that limit to grow to 1GB. They can be increased
# further by changing the parameters:
#
# 2. In /boot/loader.conf, set the tunables kern.maxswzone,
# kern.maxbcache, kern.maxtsiz, kern.dfldsiz, kern.maxdsiz,
# kern.dflssiz, kern.maxssiz and kern.sgrowsiz.
#
# The options in /boot/loader.conf override anything in the kernel
# configuration file. See the function init_param1 in
# sys/kern/subr_param.c for more details.
#
options MAXDSIZ=(1024UL*1024*1024)
options MAXSSIZ=(128UL*1024*1024)
options DFLDSIZ=(1024UL*1024*1024)
#
# BLKDEV_IOSIZE sets the default block size used in user block
# device I/O. Note that this value will be overridden by the label
# when specifying a block device from a label with a non-0
# partition blocksize. The default is PAGE_SIZE.
#
options BLKDEV_IOSIZE=8192
#
# MAXPHYS and DFLTPHYS
#
# These are the max and default 'raw' I/O block device access sizes.
# Reads and writes will be split into DFLTPHYS chunks. Some applications
# have better performance with larger raw I/O access sizes. Typically
# MAXPHYS should be twice the size of DFLTPHYS. Note that certain VM
# parameters are derived from these values and making them too large
# can make an an unbootable kernel.
#
# The defaults are 64K and 128K respectively.
options DFLTPHYS=(64*1024)
options MAXPHYS=(128*1024)
# This allows you to actually store this configuration file into
# the kernel binary itself. See config(8) for more details.
#
options INCLUDE_CONFIG_FILE # Include this file in kernel
options GEOM_AES # Don't use, use GEOM_BDE
options GEOM_BDE # Disk encryption.
options GEOM_BSD # BSD disklabels
options GEOM_CACHE # Disk cache.
options GEOM_CONCAT # Disk concatenation.
options GEOM_ELI # Disk encryption.
options GEOM_FOX # Redundant path mitigation
options GEOM_GATE # Userland services.
options GEOM_JOURNAL # Journaling.
options GEOM_LABEL # Providers labelization.
options GEOM_LINUX_LVM # Linux LVM2 volumes
options GEOM_MBR # DOS/MBR partitioning
options GEOM_MIRROR # Disk mirroring.
options GEOM_MULTIPATH # Disk multipath
options GEOM_NOP # Test class.
options GEOM_PART_APM # Apple partitioning
options GEOM_PART_BSD # BSD disklabel
options GEOM_PART_EBR # Extended Boot Records
options GEOM_PART_EBR_COMPAT # Backward compatible partition names
options GEOM_PART_GPT # GPT partitioning
options GEOM_PART_MBR # MBR partitioning
options GEOM_PART_PC98 # PC-9800 disk partitioning
options GEOM_PART_VTOC8 # SMI VTOC8 disk label
options GEOM_PC98 # NEC PC9800 partitioning
options GEOM_RAID3 # RAID3 functionality.
options GEOM_SHSEC # Shared secret.
options GEOM_STRIPE # Disk striping.
options GEOM_SUNLABEL # Sun/Solaris partitioning
options GEOM_UZIP # Read-only compressed disks
options GEOM_VIRSTOR # Virtual storage.
options GEOM_VOL # Volume names from UFS superblock
options GEOM_ZERO # Performance testing helper.
#
# The root device and filesystem type can be compiled in;
# this provides a fallback option if the root device cannot
# be correctly guessed by the bootstrap code, or an override if
# the RB_DFLTROOT flag (-r) is specified when booting the kernel.
#
options ROOTDEVNAME=\"ufs:da0s2e\"
#####################################################################
# Scheduler options:
#
# Specifying one of SCHED_4BSD or SCHED_ULE is mandatory. These options
# select which scheduler is compiled in.
#
# SCHED_4BSD is the historical, proven, BSD scheduler. It has a global run
# queue and no CPU affinity which makes it suboptimal for SMP. It has very
# good interactivity and priority selection.
#
# SCHED_ULE provides significant performance advantages over 4BSD on many
# workloads on SMP machines. It supports cpu-affinity, per-cpu runqueues
# and scheduler locks. It also has a stronger notion of interactivity
# which leads to better responsiveness even on uniprocessor machines. This
# will eventually become the default scheduler.
#
# SCHED_STATS is a debugging option which keeps some stats in the sysctl
# tree at 'kern.sched.stats' and is useful for debugging scheduling decisions.
#
options SCHED_4BSD
options SCHED_STATS
#options SCHED_ULE
#####################################################################
# SMP OPTIONS:
#
# SMP enables building of a Symmetric MultiProcessor Kernel.
# Mandatory:
options SMP # Symmetric MultiProcessor Kernel
# ADAPTIVE_MUTEXES changes the behavior of blocking mutexes to spin
# if the thread that currently owns the mutex is executing on another
# CPU. This behaviour is enabled by default, so this option can be used
# to disable it.
options NO_ADAPTIVE_MUTEXES
# ADAPTIVE_RWLOCKS changes the behavior of reader/writer locks to spin
# if the thread that currently owns the rwlock is executing on another
# CPU. This behaviour is enabled by default, so this option can be used
# to disable it.
options NO_ADAPTIVE_RWLOCKS
# ADAPTIVE_SX changes the behavior of sx locks to spin if the thread that
# currently owns the sx lock is executing on another CPU.
# This behaviour is enabled by default, so this option can be used to
# disable it.
options NO_ADAPTIVE_SX
# MUTEX_NOINLINE forces mutex operations to call functions to perform each
# operation rather than inlining the simple cases. This can be used to
# shrink the size of the kernel text segment. Note that this behavior is
# already implied by the INVARIANT_SUPPORT, INVARIANTS, KTR, LOCK_PROFILING,
# and WITNESS options.
options MUTEX_NOINLINE
# RWLOCK_NOINLINE forces rwlock operations to call functions to perform each
# operation rather than inlining the simple cases. This can be used to
# shrink the size of the kernel text segment. Note that this behavior is
# already implied by the INVARIANT_SUPPORT, INVARIANTS, KTR, LOCK_PROFILING,
# and WITNESS options.
options RWLOCK_NOINLINE
# SX_NOINLINE forces sx lock operations to call functions to perform each
# operation rather than inlining the simple cases. This can be used to
# shrink the size of the kernel text segment. Note that this behavior is
# already implied by the INVARIANT_SUPPORT, INVARIANTS, KTR, LOCK_PROFILING,
# and WITNESS options.
options SX_NOINLINE
# SMP Debugging Options:
#
# PREEMPTION allows the threads that are in the kernel to be preempted by
# higher priority [interrupt] threads. It helps with interactivity
# and allows interrupt threads to run sooner rather than waiting.
# WARNING! Only tested on amd64 and i386.
# FULL_PREEMPTION instructs the kernel to preempt non-realtime kernel
# threads. Its sole use is to expose race conditions and other
# bugs during development. Enabling this option will reduce
# performance and increase the frequency of kernel panics by
# design. If you aren't sure that you need it then you don't.
# Relies on the PREEMPTION option. DON'T TURN THIS ON.
# MUTEX_DEBUG enables various extra assertions in the mutex code.
# SLEEPQUEUE_PROFILING enables rudimentary profiling of the hash table
# used to hold active sleep queues as well as sleep wait message
# frequency.
# TURNSTILE_PROFILING enables rudimentary profiling of the hash table
# used to hold active lock queues.
# WITNESS enables the witness code which detects deadlocks and cycles
# during locking operations.
# WITNESS_KDB causes the witness code to drop into the kernel debugger if
# a lock hierarchy violation occurs or if locks are held when going to
# sleep.
# WITNESS_SKIPSPIN disables the witness checks on spin mutexes.
options PREEMPTION
options FULL_PREEMPTION
options MUTEX_DEBUG
options WITNESS
options WITNESS_KDB
options WITNESS_SKIPSPIN
# LOCK_PROFILING - Profiling locks. See LOCK_PROFILING(9) for details.
options LOCK_PROFILING
# Set the number of buffers and the hash size. The hash size MUST be larger
# than the number of buffers. Hash size should be prime.
options MPROF_BUFFERS="1536"
options MPROF_HASH_SIZE="1543"
# Profiling for internal hash tables.
options SLEEPQUEUE_PROFILING
options TURNSTILE_PROFILING
#####################################################################
# COMPATIBILITY OPTIONS
#
# Implement system calls compatible with 4.3BSD and older versions of
# FreeBSD. You probably do NOT want to remove this as much current code
# still relies on the 4.3 emulation. Note that some architectures that
# are supported by FreeBSD do not include support for certain important
# aspects of this compatibility option, namely those related to the
# signal delivery mechanism.
#
options COMPAT_43
# Old tty interface.
options COMPAT_43TTY
# Note that as a general rule, COMPAT_FREEBSD<n> depends on
# COMPAT_FREEBSD<n+1>, COMPAT_FREEBSD<n+2>, etc.
# Enable FreeBSD4 compatibility syscalls
options COMPAT_FREEBSD4
# Enable FreeBSD5 compatibility syscalls
options COMPAT_FREEBSD5
# Enable FreeBSD6 compatibility syscalls
options COMPAT_FREEBSD6
# Enable FreeBSD7 compatibility syscalls
options COMPAT_FREEBSD7
#
# These three options provide support for System V Interface
# Definition-style interprocess communication, in the form of shared
# memory, semaphores, and message queues, respectively.
#
options SYSVSHM
options SYSVSEM
options SYSVMSG
#####################################################################
# DEBUGGING OPTIONS
#
# Compile with kernel debugger related code.
#
options KDB
#
# Print a stack trace of the current thread on the console for a panic.
#
options KDB_TRACE
#
# Don't enter the debugger for a panic. Intended for unattended operation
# where you may want to enter the debugger from the console, but still want
# the machine to recover from a panic.
#
options KDB_UNATTENDED
#
# Enable the ddb debugger backend.
#
options DDB
#
# Print the numerical value of symbols in addition to the symbolic
# representation.
#
options DDB_NUMSYM
#
# Enable the remote gdb debugger backend.
#
options GDB
#
# Enable the kernel DTrace hooks which are required to load the DTrace
# kernel modules.
#
options KDTRACE_HOOKS
#
# SYSCTL_DEBUG enables a 'sysctl' debug tree that can be used to dump the
# contents of the registered sysctl nodes on the console. It is disabled by
# default because it generates excessively verbose console output that can
# interfere with serial console operation.
#
options SYSCTL_DEBUG
#
# DEBUG_MEMGUARD builds and enables memguard(9), a replacement allocator
# for the kernel used to detect modify-after-free scenarios. See the
# memguard(9) man page for more information on usage.
#
options DEBUG_MEMGUARD
#
# DEBUG_REDZONE enables buffer underflows and buffer overflows detection for
# malloc(9).
#
options DEBUG_REDZONE
#
# KTRACE enables the system-call tracing facility ktrace(2). To be more
# SMP-friendly, KTRACE uses a worker thread to process most trace events
# asynchronously to the thread generating the event. This requires a
# pre-allocated store of objects representing trace events. The
# KTRACE_REQUEST_POOL option specifies the initial size of this store.
# The size of the pool can be adjusted both at boottime and runtime via
# the kern.ktrace_request_pool tunable and sysctl.
#
options KTRACE #kernel tracing
options KTRACE_REQUEST_POOL=101
#
# KTR is a kernel tracing mechanism imported from BSD/OS. Currently
# it has no userland interface aside from a few sysctl's. It is
# enabled with the KTR option. KTR_ENTRIES defines the number of
# entries in the circular trace buffer; it must be a power of two.
# KTR_COMPILE defines the mask of events to compile into the kernel as
# defined by the KTR_* constants in <sys/ktr.h>. KTR_MASK defines the
# initial value of the ktr_mask variable which determines at runtime
# what events to trace. KTR_CPUMASK determines which CPU's log
# events, with bit X corresponding to CPU X. KTR_VERBOSE enables
# dumping of KTR events to the console by default. This functionality
# can be toggled via the debug.ktr_verbose sysctl and defaults to off
# if KTR_VERBOSE is not defined.
#
options KTR
options KTR_ENTRIES=1024
options KTR_COMPILE=(KTR_INTR|KTR_PROC)
options KTR_MASK=KTR_INTR
options KTR_CPUMASK=0x3
options KTR_VERBOSE
#
# ALQ(9) is a facility for the asynchronous queuing of records from the kernel
# to a vnode, and is employed by services such as KTR(4) to produce trace
# files based on a kernel event stream. Records are written asynchronously
# in a worker thread.
#
options ALQ
options KTR_ALQ
#
# The INVARIANTS option is used in a number of source files to enable
# extra sanity checking of internal structures. This support is not
# enabled by default because of the extra time it would take to check
# for these conditions, which can only occur as a result of
# programming errors.
#
options INVARIANTS
#
# The INVARIANT_SUPPORT option makes us compile in support for
# verifying some of the internal structures. It is a prerequisite for
# 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be
# called. The intent is that you can set 'INVARIANTS' for single
# source files (by changing the source file or specifying it on the
# command line) if you have 'INVARIANT_SUPPORT' enabled. Also, if you
# wish to build a kernel module with 'INVARIANTS', then adding
# 'INVARIANT_SUPPORT' to your kernel will provide all the necessary
# infrastructure without the added overhead.
#
options INVARIANT_SUPPORT
#
# The DIAGNOSTIC option is used to enable extra debugging information
# from some parts of the kernel. As this makes everything more noisy,
# it is disabled by default.
#
options DIAGNOSTIC
#
# REGRESSION causes optional kernel interfaces necessary only for regression
# testing to be enabled. These interfaces may constitute security risks
# when enabled, as they permit processes to easily modify aspects of the
# run-time environment to reproduce unlikely or unusual (possibly normally
# impossible) scenarios.
#
options REGRESSION
#
# RESTARTABLE_PANICS allows one to continue from a panic as if it were
# a call to the debugger to continue from a panic as instead. It is only
# useful if a kernel debugger is present. To restart from a panic, reset
# the panicstr variable to NULL and continue execution. This option is
# for development use only and should NOT be used in production systems
# to "workaround" a panic.
#
#options RESTARTABLE_PANICS
#
# This option let some drivers co-exist that can't co-exist in a running
# system. This is used to be able to compile all kernel code in one go for
# quality assurance purposes (like this file, which the option takes it name
# from.)
#
options COMPILING_LINT
#
# STACK enables the stack(9) facility, allowing the capture of kernel stack
# for the purpose of procinfo(1), etc. stack(9) will also be compiled in
# automatically if DDB(4) is compiled into the kernel.
#
options STACK
#####################################################################
# PERFORMANCE MONITORING OPTIONS
#
# The hwpmc driver that allows the use of in-CPU performance monitoring
# counters for performance monitoring. The base kernel needs to configured
# with the 'options' line, while the hwpmc device can be either compiled
# in or loaded as a loadable kernel module.
#
# Additional configuration options may be required on specific architectures,
# please see hwpmc(4).
device hwpmc # Driver (also a loadable module)
options HWPMC_HOOKS # Other necessary kernel hooks
#####################################################################
# NETWORKING OPTIONS
#
# Protocol families
#
options INET #Internet communications protocols
options INET6 #IPv6 communications protocols
options ROUTETABLES=2 # max 16. 1 is back compatible.
# In order to enable IPSEC you MUST also add device crypto to
# your kernel configuration
options IPSEC #IP security (requires device crypto)
#options IPSEC_DEBUG #debug for IP security
#
# #DEPRECATED#
# Set IPSEC_FILTERTUNNEL to change the default of the sysctl to force packets
# coming through a tunnel to be processed by any configured packet filtering
# twice. The default is that packets coming out of a tunnel are _not_ processed;
# they are assumed trusted.
#
# IPSEC history is preserved for such packets, and can be filtered
# using ipfw(8)'s 'ipsec' keyword, when this option is enabled.
#
#options IPSEC_FILTERTUNNEL #filter ipsec packets from a tunnel
#
# Set IPSEC_NAT_T to enable NAT-Traversal support. This enables
# optional UDP encapsulation of ESP packets.
#
options IPSEC_NAT_T #NAT-T support, UDP encap of ESP
options IPX #IPX/SPX communications protocols
options NCP #NetWare Core protocol
options NETATALK #Appletalk communications protocols
options NETATALKDEBUG #Appletalk debugging
#
# SMB/CIFS requester
# NETSMB enables support for SMB protocol, it requires LIBMCHAIN and LIBICONV
# options.
options NETSMB #SMB/CIFS requester
# mchain library. It can be either loaded as KLD or compiled into kernel
options LIBMCHAIN
# libalias library, performing NAT
options LIBALIAS
# flowtable cache
options FLOWTABLE
#
# SCTP is a NEW transport protocol defined by
# RFC2960 updаtеd by RFC3309 and RFC3758.. and
# soon to have a new base RFC and many many more
# extensions. This release supports all the extensions
# including many drafts (most about to become RFC's).
# It is the premeier SCTP implementation in the NET
# and is quite well tested.
#
# Note YOU MUST have both INET and INET6 defined.
# you don't have to enable V6, but SCTP is
# dual stacked and so far we have not teased apart
# the V6 and V4.. since an association can span
# both a V6 and V4 address at the SAME time :-)
#
options SCTP
# There are bunches of options:
# this one turns on all sorts of
# nastly printing that you can
# do. Its all controled by a
# bit mask (settable by socket opt and
# by sysctl). Including will not cause
# logging until you set the bits.. but it
# can be quite verbose.. so without this
# option we don't do any of the tests for
# bits and prints.. which makes the code run
# faster.. if you are not debugging don't use.
options SCTP_DEBUG
#
# This option turns off the CRC32c checksum. Basically
# You will not be able to talk to anyone else that
# has not done this. Its more for expermentation to
# see how much CPU the CRC32c really takes. Most new
# cards for TCP support checksum offload.. so this
# option gives you a "view" into what SCTP would be
# like with such an offload (which only exists in
# high in iSCSI boards so far). With the new
# splitting 8's algorithm its not as bad as it used
# to be.. but it does speed things up try only
# for in a captured lab environment :-)
options SCTP_WITH_NO_CSUM
#
#
# All that options after that turn on specific types of
# logging. You can monitor CWND growth, flight size
# and all sorts of things. Go look at the code and
# see. I have used this to produce interesting
# charts and graphs as well :->
#
# I have not yet commited the tools to get and print
# the logs, I will do that eventually .. before then
# if you want them send me an email rrs@freebsd.org
# You basically must have KTR enabled for these
# and you then set the sysctl to turn on/off various
# logging bits. Use ktrdump to pull the log and run
# it through a dispaly program.. and graphs and other
# things too.
#
options SCTP_LOCK_LOGGING
options SCTP_MBUF_LOGGING
options SCTP_MBCNT_LOGGING
options SCTP_PACKET_LOGGING
options SCTP_LTRACE_CHUNKS
options SCTP_LTRACE_ERRORS
# altq(9). Enable the base part of the hooks with the ALTQ option.
# Individual disciplines must be built into the base system and can not be
# loaded as modules at this point. ALTQ requires a stable TSC so if yours is
# broken or changes with CPU throttling then you must also have the ALTQ_NOPCC
# option.
options ALTQ
options ALTQ_CBQ # Class Based Queueing
options ALTQ_RED # Random Early Detection
options ALTQ_RIO # RED In/Out
options ALTQ_HFSC # Hierarchical Packet Scheduler
options ALTQ_CDNR # Traffic conditioner
options ALTQ_PRIQ # Priority Queueing
options ALTQ_NOPCC # Required if the TSC is unusable
options ALTQ_DEBUG
# netgraph(4). Enable the base netgraph code with the NETGRAPH option.
# Individual node types can be enabled with the corresponding option
# listed below; however, this is not strictly necessary as netgraph
# will automatically load the corresponding KLD module if the node type
# is not already compiled into the kernel. Each type below has a
# corresponding man page, e.g., ng_async(8).
options NETGRAPH # netgraph(4) system
options NETGRAPH_DEBUG # enable extra debugging, this
# affects netgraph(4) and nodes
# Node types
options NETGRAPH_ASYNC
options NETGRAPH_ATMLLC
options NETGRAPH_ATM_ATMPIF
options NETGRAPH_BLUETOOTH # ng_bluetooth(4)
options NETGRAPH_BLUETOOTH_BT3C # ng_bt3c(4)
options NETGRAPH_BLUETOOTH_HCI # ng_hci(4)
options NETGRAPH_BLUETOOTH_L2CAP # ng_l2cap(4)
options NETGRAPH_BLUETOOTH_SOCKET # ng_btsocket(4)
options NETGRAPH_BLUETOOTH_UBT # ng_ubt(4)
options NETGRAPH_BLUETOOTH_UBTBCMFW # ubtbcmfw(4)
options NETGRAPH_BPF
options NETGRAPH_BRIDGE
options NETGRAPH_CAR
options NETGRAPH_CISCO
options NETGRAPH_DEFLATE
options NETGRAPH_DEVICE
options NETGRAPH_ECHO
options NETGRAPH_EIFACE
options NETGRAPH_ETHER
options NETGRAPH_FEC
options NETGRAPH_FRAME_RELAY
options NETGRAPH_GIF
options NETGRAPH_GIF_DEMUX
options NETGRAPH_HOLE
options NETGRAPH_IFACE
options NETGRAPH_IP_INPUT
options NETGRAPH_IPFW
options NETGRAPH_KSOCKET
options NETGRAPH_L2TP
options NETGRAPH_LMI
# MPPC compression requires proprietary files (not included)
#options NETGRAPH_MPPC_COMPRESSION
options NETGRAPH_MPPC_ENCRYPTION
options NETGRAPH_NETFLOW
options NETGRAPH_NAT
options NETGRAPH_ONE2MANY
options NETGRAPH_PIPE
options NETGRAPH_PPP
options NETGRAPH_PPPOE
options NETGRAPH_PPTPGRE
options NETGRAPH_PRED1
options NETGRAPH_RFC1490
options NETGRAPH_SOCKET
options NETGRAPH_SPLIT
options NETGRAPH_SPPP
options NETGRAPH_TAG
options NETGRAPH_TCPMSS
options NETGRAPH_TEE
options NETGRAPH_UI
options NETGRAPH_VJC
# NgATM - Netgraph ATM
options NGATM_ATM
options NGATM_ATMBASE
options NGATM_SSCOP
options NGATM_SSCFU
options NGATM_UNI
options NGATM_CCATM
device mn # Munich32x/Falc54 Nx64kbit/sec cards.
#
# Network interfaces:
# The `loop' device is MANDATORY when networking is enabled.
device loop
# The `ether' device provides generic code to handle
# Ethernets; it is MANDATORY when an Ethernet device driver is
# configured or token-ring is enabled.
device ether
# The `vlan' device implements the VLAN tagging of Ethernet frames
# according to IEEE 802.1Q.
device vlan
# The `wlan' device provides generic code to support 802.11
# drivers, including host AP mode; it is MANDATORY for the wi,
# and ath drivers and will eventually be required by all 802.11 drivers.
device wlan
options IEEE80211_DEBUG #enable debugging msgs
options IEEE80211_AMPDU_AGE #age frames in AMPDU reorder q's
options IEEE80211_SUPPORT_MESH #enable 802.11s D3.0 support
options IEEE80211_SUPPORT_TDMA #enable TDMA support
# The `wlan_wep', `wlan_tkip', and `wlan_ccmp' devices provide
# support for WEP, TKIP, and AES-CCMP crypto protocols optionally
# used with 802.11 devices that depend on the `wlan' module.
device wlan_wep
device wlan_ccmp
device wlan_tkip
# The `wlan_xauth' device provides support for external (i.e. user-mode)
# authenticators for use with 802.11 drivers that use the `wlan'
# module and support 802.1x and/or WPA security protocols.
device wlan_xauth
# The `wlan_acl' device provides a MAC-based access control mechanism
# for use with 802.11 drivers operating in ap mode and using the
# `wlan' module.
# The 'wlan_amrr' device provides AMRR transmit rate control algorithm
device wlan_acl
device wlan_amrr
# Generic TokenRing
device token
# The `fddi' device provides generic code to support FDDI.
device fddi
# The `arcnet' device provides generic code to support Arcnet.
device arcnet
# The `sppp' device serves a similar role for certain types
# of synchronous PPP links (like `cx', `ar').
device sppp
# The `bpf' device enables the Berkeley Packet Filter. Be
# aware of the legal and administrative consequences of enabling this
# option. The number of devices determines the maximum number of
# simultaneous BPF clients programs runnable. DHCP requires bpf.
device bpf
# The `disc' device implements a minimal network interface,
# which throws away all packets sent and never receives any. It is
# included for testing and benchmarking purposes.
device disc
# The `epair' device implements a virtual back-to-back connected Ethernet
# like interface pair.
device epair
# The `edsc' device implements a minimal Ethernet interface,
# which discards all packets sent and receives none.
device edsc
# The `tap' device is a pty-like virtual Ethernet interface
device tap
# The `tun' device implements (user-)ppp and nos-tun(8)
device tun
# The `gif' device implements IPv6 over IP4 tunneling,
# IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling and
# IPv6 over IPv6 tunneling.
# The `gre' device implements two types of IP4 over IP4 tunneling:
# GRE and MOBILE, as specified in the RFC1701 and RFC2004.
# The XBONEHACK option allows the same pair of addresses to be configured on
# multiple gif interfaces.
device gif
device gre
options XBONEHACK
# The `faith' device captures packets sent to it and diverts them
# to the IPv4/IPv6 translation daemon.
# The `stf' device implements 6to4 encapsulation.
device faith
device stf
# The `ef' device provides support for multiple ethernet frame types
# specified via ETHER_* options. See ef(4) for details.
device ef
options ETHER_II # enable Ethernet_II frame
options ETHER_8023 # enable Ethernet_802.3 (Novell) frame
options ETHER_8022 # enable Ethernet_802.2 frame
options ETHER_SNAP # enable Ethernet_802.2/SNAP frame
# The pf packet filter consists of three devices:
# The `pf' device provides /dev/pf and the firewall code itself.
# The `pflog' device provides the pflog0 interface which logs packets.
# The `pfsync' device provides the pfsync0 interface used for
# synchronization of firewall state tables (over the net).
device pf
device pflog
device pfsync
# Bridge interface.
device if_bridge
# Common Address Redundancy Protocol. See carp(4) for more details.
device carp
# IPsec interface.
device enc
# Link aggregation interface.
device lagg
#
# Internet family options:
#
# MROUTING enables the kernel multicast packet forwarder, which works
# with mrouted and XORP.
#
# IPFIREWALL enables support for IP firewall construction, in
# conjunction with the `ipfw' program. IPFIREWALL_VERBOSE sends
# logged packe
|
|
|
|
|
RE: 2 сетевых подключения. - 2009-12-08 20:50:19.936666
|
|
|
CASPER2
Сообщений: 46
Оценки: 0
Присоединился: 2007-02-22 15:48:33.700000
|
еще было бы не плохо где эти фаилы взять и куда закинуть! И потом проверить на работоспособность! Просто весь инет облазил ничего толком не объясняют все по научному!
|
|
|
|
|
ПОМОГИТЕ - 2010-02-12 17:57:51.686666
|
|
|
pomazanik
Сообщений: 1
Оценки: 0
Присоединился: 2010-02-12 17:51:53.766666
|
Подскажите где мне найти человека который мог бы подкорректировать сайт,очень нужно, Pomazanik@list.ru-буду ждать ваших писем
|
|
|
|
|
wi fi - 2010-03-06 23:56:24.650000
|
|
|
:.XuMuK.:
Сообщений: 4
Оценки: 0
Присоединился: 2010-03-06 19:12:37.770000
|
кто нить на acer'овских ноутах вай фай настраивал? при первой загрузке в логах про мой интерфейс ни буквы (wlan0)… ethernet адаптер видит, но инета всё равно нет… [sm=aq.gif]
|
|
|
|
|
RE: wi fi - 2010-03-07 02:42:18.030000
|
|
|
:.XuMuK.:
Сообщений: 4
Оценки: 0
Присоединился: 2010-03-06 19:12:37.770000
|
всё)) главное вопрос правильно сформулировать))*
|
|
|
|
|
RE: 2 сетевых подключения. - 2010-03-07 02:44:34.593333
|
|
|
:.XuMuK.:
Сообщений: 4
Оценки: 0
Присоединился: 2010-03-06 19:12:37.770000
|
надо перекомпилить ядро с нужными тебе параметрами
|
|
|
|
|
RE: FreeBSD - 2010-06-17 08:46:38.683333
|
|
|
alex117
Сообщений: 424
Оценки: 0
Присоединился: 2010-02-09 10:54:42.646666
|
У меня вопрос - чтобы установить какую-то программу в FreeBSD обязательно нужен интернет?Если нет,то как отключить,чтобы он не лез обновлять порты и ставил все с диска?
|
|
|
|
|
RE: FreeBSD - 2010-06-19 23:32:13.840000
|
|
|
mobydick
Сообщений: 354
Оценки: 0
Присоединился: 2008-08-08 01:16:49.146666
|
Не обязательно.
Если программа есть на диске с дистрибутивом,
тогда DVD в дисковод и
sysinstall
Configure
Packages
CD/DVD
Дальше разберешься сам.
В этом случае порты не будут обновлятся
|
|
|
|
|
RE: FreeBSD - 2010-06-21 20:55:21.246666
|
|
|
WinLinux
Сообщений: 491
Оценки: 0
Присоединился: 2008-07-18 14:06:33.563333
|
quote:
ORIGINAL: alex117
У меня вопрос - чтобы установить какую-то программу в FreeBSD обязательно нужен интернет?Если нет,то как отключить,чтобы он не лез обновлять порты и ставил все с диска?
А также FreeBSD как и любой другой Unix работает с пакетами, который изначально являются скомпилированными и распостраняются в виде пакета формата .pkg, устанавливается легко и просто с помощью команды pkg_add имя_пакета, а также есть пакеты, которые необходимо скомпилировать. Посети сайт www.lissyara.su
|
|
|
|
|
RE: FreeBSD - 2010-06-26 05:07:32.856666
|
|
|
Abrasive
Сообщений: 42
Оценки: 0
Присоединился: 2010-06-22 02:34:35.530000
|
Товарищи, помогите разобраться с VPN…
Есть сервак в другом городе, задача - поднять на нем VPN и, соответственно, ходить в нет через него. Оговорюсь сразу: искал, читал, вникал. Но дело в том, что с Фряхой до этого не сталкивался вообще, с vpn - только под виндой, и то пару раз. Все найденные маны предполагают, что машина с фряхой использует минимум два сетевых интерфейса: один смотрит в инет, другой - в локалку, и vpn нужен локальным машинам для доступа в интернет. В моем случае, интерфейс однин - тот, которым сервер смотрит в инет. Как это разрулить на одном интерфейсе я так и не понял…
|
|
|
|
|
RE: FreeBSD - 2010-07-03 10:00:22.860000
|
|
|
Abrasive
Сообщений: 42
Оценки: 0
Присоединился: 2010-06-22 02:34:35.530000
|
И еще проблемка…
Поставил Фрю на домашний комп, все вроде нормально, все работает как положено. Накатил KDE - не работает мышь и клава. Без иксов - все пучком. Посмотрел по форумам - советуют в /etc/rc.conf прописать hal_enable="YES", прописал - не помогло… Больше дельных ответов на эту тему не видел.
Кто сталкивался - подскажите, в чем может быть дело?
|
|
|
|
|
|
