Our efforts so far indicate the answer is no, which baffles us. We want
to send a limited broadcast to 255.255.255.255 but the message never
arrives. The same code works fine under Linux. Is there a trick for
doing this kind of thing under FreeBSD?
What you're trying to do with sending to the all-ones broadcast
address is known as sending a link-local packet. On some systems,
sending a UDP packet to 255.255.255.255 will actually cause a packet
with that destination to be generated from all network interfaces
which are UP. That
I've already looked at the ISC DHCP source code. They use raw sockets
to
send their broadcasts, which seems to us to be a convoluted way of
sending a simple broadcast. I've seen examples of DHCP client/server
code written in Java using standard UDP. Unfortunately, our own system
is already
Did you enable SO_BROADCAST and IP_ONESBCAST on the socket? I remember
needing
this on FreeBSD but not on Linux.
Yes we did, but...
I know UDP broadcasting works fine, but is
somewhat more involved:
addr.sin_family = AF_INET;
addr.sin_addr.s_addr = inet_addr(130.89.191.255);
addr.sin_port =
why 255.255.255.255 not your net broadcast address?
Because the systems we are using do not have IPs assigned and you to
know your subnet before you can use subnet broadcasting. We're
developing our own DHCP-like service to distribute IPs to all of the
systems, and we need limited broadcast to
We have systems setup using geom based mirroring where the drives are
partitioned into three slices, one for the OS, one for the swap
partition, and one for our application data. We have four hot-swappable
SATA drives per system. At present we only have the OS slice mirrored
with geom, and our own
If you don't mirror swap space, and a drive goes out, you're almost
certain to experience a kernel panic and not just application failures
in userland. Unless you have an urgent need for lots of swap space
available, it's much better from the standpoint of system reliability
to mirror
We have systems that upon initial configuration have no IP addresses
assigned. Their rc.conf entries look like this:
ifconfig_nfe0=UP
ifconfig_nfe1=UP
cloned_interfaces=lagg0
ifconfig_lagg0=laggproto failover laggport nfe0 laggport nfe1
defaultrouter=0.0.0.0
The user later runs a tool
We have our systems configured with the watchdog enabled, with
/etc/rc.d/watchdogd defined as
. /etc/rc.subr
name=watchdogd
rcvar=`set_rcvar`
command=/usr/sbin/${name}
command_args=-s 10 -t 300
pidfile=/var/run/${name}.pid
load_rc_config $name
run_rc_command $1
We assumed this would
We want to develop a system imaging process where all we have to do is insert a
USB thumb drive into a system and reboot it, and some time later the system
would be loaded up with whatever FreeBSD software the particular thumb drive
being used is configured. We'd have different thumb drives for
No, meaning, if a system is unresponsive for 300 seconds, action will be
taken. watchdogd will not prevent proper reboots, panics or power failures.
Bad wording on my part. What you said is what I meant, and I assume the default
action is to reboot the system?
Panic, or overheating. Check
Panic, or overheating. Check the dumpdev/dumpdir variables in rc.conf(5).
BTW, what's the difference between setting kern.corefile in /etc/sysctl and
these dumpdev/dumpdir variables?
___
freebsd-questions@freebsd.org mailing list
If -e cmd is not specified, the daemon will
perform a trivial file system check instead.
So -e has to be provided for the system to reboot? That doesn't seem to jive
with our experience. When we first enabled the watchdog, we just went with the
defaults--no -e command. The default for the
Which watchdog are you using?
We are using the default FreeBSD 7.0 watchdog. We've added the line
watchdogd_enable=yes
to rc.conf to enable it and have modified /etc/rc.d/watchdogd to pass -t 300
to the daemon instead of the default 16.
___
The script runs fine, but the resulting USB drive won't boot. It hangs on
Feb 25 19:27:50 kernel: atkbdc0: Keyboard controller (i8042) port 0x60,0x64
irq 1 on acpi0
every time. I tried different systems as well. There is no error, it just
hangs. Any idea what this is about? I did a web
I solved the issue in my case. When I first ran the script I didn't notice that
it created versions of several system config files, including loader.conf and
rc.conf. I modified the script to make versions that matched my requirements
and the keyboard hang problem went away.
- Original
Can I run sysinstall on a live system, booted say from ad0 and use it to
install a new OS onto a second drive, say ad1? I'm trying to do something like
this:
sysinstall configFile=install.cfg loadConfig
where I have the target drive identified in the sysinstall script, but it
doesn't seem
Yes for sure. You can partition secondary drives on a running system as long
as the drive isn't mounted and your kern.securelevel 2.
It's -1, so I assume that's okay.
You will need to define doesn't seem to like what I'm trying to do to get a
more constructive answer.
Yeah, that wasn't
That's my problem in a nutshell ultimately--how do I tell sysinstall where my
target root is? It impacts the whole
session, including packageAdd commands.
I did a bit of snooping around the distribution and I see that each directory
has a simple install script to install base, the kernel,
I've created a USB boot disk that is used to clone itself onto the systems hard
drives, setting up mirrored file systems in the process. The main difficulty
I'm having is reimaging a system with an existing OS whose drives are already
configured in a mirror. I want of course to destroy the
I first wondered why none of my commands in /etc/profile and
~/.profile got executed. Finally, I modified
/usr/src/bin/sh/main.c to trace what files are read, recompiled
the sh command and: the only file that is executed is ~/.shrc.
I just cannot believe that FreeBSD has such a severe bug.
I have a process with creates bootable USB disks with FreeBSD 7.0. The creation
of the USB disks is pretty straightforward. We have a master OS image saved as
a tarball, and when we want to create a new USB disk, we simply create a single
bootable UFS partition on the target USB drive and then
Shot in the dark but are they by any chance U3 devices?
http://en.wikipedia.org/wiki/U3
There is no indication of that. They mount fine and can be formatted as UFS and
have files copied to them. They are just basic 4GB USB flash drives, on sale at
our local Frys. HP brand (but I don't know
from what I understand it's widely known there is not a standard for
implementing USB bios boot.
I can take a flash drive make it bootable with grub4dos and my board will not
see it.
Take that same drive implement normal grub or syslinux and my board will now
boot that flash drive. Take
How do I install the standard boot manager on a disk using a command line tool?
I believe
boot0cfg -B /dev/adN
installs the FreeBSD boot manager, but I want the standard boot manager that
matches the option in sysinstall.
___
I have a process that automates the creation of a master FreeBSD image that we
clone onto mulitple machines. In the latest version of this image I am seeing
the warnings:
warning: KLD '/boot/kernel/linprocfs.ko' is newer than the linker.hints file
warning: KLD '/boot/kernel/linux.ko' is newer
Probably you installed that files _after_ linker.hints is generated,
just make sure that they are still compatible with /boot/kernel/kernel
Perhaps its a matter of the process we're using. I first install the GENERIC
kernel into the image I am creating:
export DESTDIR=${IMAGE_DIR}
export
I want to have a process running on my FreeBSD box that automatically detects
when a USB drive is inserted. What's the easiest way to accomplish this? I know
I could simply monitor /var/log/messages and look for the appropriate events to
appear, but is there a more elegant way?
My question to you would be: What exactly do you mean by
automatically detect? The drive *is* automatically detected.
Should it be mounted afterwards?
Yeah, I guess my wording was a little vague. I know that the system
automatically detects when a USB drive is inserted, and creates the
This looks like it will do exactly what I need. Thanks for the pointer!
- Original Message -
From: Wojciech Puchar woj...@wojtek.tensor.gdynia.pl
To: Peter Steele pste...@maxiscale.com
Cc: questi...@freebsd.org
Sent: Wednesday, March 11, 2009 8:08:20 AM GMT -08:00 US/Canada Pacific
Last week I submitted a patch to get this system and subsystem
documented in the manual page of devd.conf. It should be in CURRENT now,
and will be MFC'd to STABLE in a week or so.
This looks like exactly what we need, except we're using 7.0, and are too close
to releasing 1.0 of our
It's missing the call to devctl_notify in the devfs handling. This was
added to RELENG_7 on the 28th of May 2008. You'll need at least
rev. 1.208.2.4 of /usr/src/sys/kern/kern_conf.c. See:
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/kern_conf.c?f=uonly_with_tag=RELENG_7logsort=date
The scripts are a bit primitive and get totally confused if I insert
more than one USB storage device at a time so would need some
refinement for general use but work OK for me as the only user on this
PC.
Thanks, I'll give this a try and see how it works. We have a very simple
requirement
Then try another solution: a cron job, as explained in another msg.
Yeah, that's probably the simplest approach. This was my first thought, but I
figured there'd be a more elegant way of doing it if I could tie into the drive
insert event
___
I do something like this. Here's the rules I have
in /usr/local/etc/devd.conf
...
attach 10 {
match device-name umass0;
action sleep 2; /root/bin/usbstick_attach /dev/console;
};
I've tried something similar and I'm having good success. I should be able
accomplish what I need with
A typical df command looks like this:
# df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/mirror/gm0a 4.8G 2.0G 2.4G 46% /
devfs 1.0K 1.0K 0B 100% /dev
linprocfs 4.0K 4.0K 0B 100% /proc
/dev/mirror/gm0d 3.9G 88K 3.6G 0% /tmp
/dev/mirror/gm0e 15G 79M 13G 1% /var
/dev/ad4s3e 116G
Line 417 of /usr/src/bin/df/df.c:
used = sfsp-f_blocks - sfsp-f_bfree;
I keep forgetting that I can go directly to the source to answer questions like
this. Thanks muchly; this is exactly what I need.
___
freebsd-questions@freebsd.org mailing
I've created an autorun facility for USB drives using devd. I have the
following addition in devd.conf:
attach 10 {
match device-name umass0;
action /usr/local/bin/autorun /var/log/autorun.log 21 ;
};
This works perfectly except only stderr messages appear in the autorun.log
file; stdout
I've created a GEOM mirrored file system and everything seems to be working,
but I get the warning
WARNING: Expected rawoffset 0, found 63
when the mirror is being created. What is this referring to?
___
freebsd-questions@freebsd.org mailing list
Are you gmirror'ing the BSD slice?
Wrong:
/dev/ad0s1
/dev/ad2s1
Right:
/dev/ad0
/dev/ad2
That's what it sounds like to me.
I don't think that's the issue. I read many articles on how to mirror slices,
including the BSD slice, and in earlier tests I never saw this error.
We've found that FreeBSD 7.0's support for USB disks is pretty unstable. We
have a process that creates a bootable FreeBSD 7.0 image on a USB disk and this
requires writing a fairly large amount of data in one shot to the USB drive.
We've found that there is probably less than a 50% chance of
I wanted to use the kern.disks sysctl variable but it doesn't seem to work the
way I'd expect. When I first inspected this variable it showed the four hard
drives I would expect:
ad4 ad6 ad8 ad10
Then I inserted a USB stick and checked kern.disks again, and this time the new
USB drive was
We had a somewhat startling scenario occur with gmirror. We have systems with
four drives ad4, ad6, ad8, and ad10, with the OS setup on a mirrored slice
across all four drives. The ad4 drive failed at one point, due to a simple bad
connection in its drive bay. While it was offline, the system
This definitely looks like a bug. Try asking again on the freebsd-geom@
list. Provide output of gmirror list.
I'll try that list...
So, your steps were:
1. ad4, ad6, ad8 and ad10 in a 4-way mirror
2. ad4 fails. At this point did you do a gmirror list? I.e. did
gmirror detect it failing?
This only happens with ad4. If ad6 for example goes offline in the same way,
when it is reinserted
it does not become the dominant drive and resync its data with the other
drives. Rather its data
is overwritten with the data from the 3 member mirror, as you'd expect.
looks like very
By kicked out you mean overwritten?
You should definitely look at gmirror list before and after.
Sorry for the confusion. By kicked out, what I meant was as gmirror started
up it took ad4 as the principal member, saw that it was previously part of a
mirror with three other drives and tried
Assuming I have the name of an interface, what's the easiest way
programmatically to get the status of the interface?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
Because we have large drives (2TB) we're switching to gpart to partition our
disks. I had previously been using fdisk/bsdlabel and setting up specially
configured partition tables that would work with gmirror. This involved faking
the size of the c partition to make sure there was space for
I have a BSD 7 system with the full BSD 8 sources loaded on it, and we use this
box to build our custom BSD 8 kernel and tools. We do not install the custom
code on the BSD 7 box but simply collect the artifacts as a basis for our
custom BSD 8 image. I have a standalone tool that has previously
Okay, that looks doable. I'll see how this works out. Thanks very much for the
info!
-Original Message-
From: Pieter de Goeje [mailto:pie...@degoeje.nl]
Sent: Saturday, February 06, 2010 5:28 PM
To: freebsd-questions@freebsd.org
Cc: Peter Steele
Subject: Re: What is easiest way to build
The easiest way would probably be the following.
# SOMEDIR=/path/to/fbsd8buildenv
# mkdir -p ${SOMEDIR}
# cd /path/to/FreeBSD-8.0/src
# make buildworld
# make installworld DESTDIR=${SOMEDIR}
Then adding --sysroot=${SOMEDIR} to all invocations of gcc/ld and/or liberal
use of -I and -L gcc
You could check that the tool is actually linked to the correct libraries with
ldd(1). If all else fails, you could try building a full FreeBSD 8 jail or
chroot.
However running FBSD 8 userland on a 7 kernel is unsupported so I have no idea
if that will actually work well enough to build
I've used the syntax
1:ad(1,a)/boot/loader
in boot.config to specify the boot device. This doesn't work with GPT
partitions. What's the correct syntax in boot.config for GPT partitions?
___
freebsd-questions@freebsd.org mailing list
I've set up a system with gpart and have the swap partition first followed by
root, var, and so on. This works fine but I've seen documents that always have
root first, then swap. Is there any reason that root should be the first
partition or can it follow swap space?
I've used the syntax
1:ad(1,a)/boot/loader
in boot.config to specify the boot device. This doesn't work with GPT
partitions. What's the correct syntax in boot.config for GPT partitions?
I looked at the source code to boot.c and there doesn't seem to be anything
specifically related to GPT
The root partition should always be the 'a' partition, but it doesn't have to
be the first in physical order on the disk (ie. starting at cylinder 0). So
long as partitions don't overlap (with the historical exception of the 'c'
partition, which should cover the whole drive) you can put them
I suspect I know the problem. The tool I'm building links with a bunch of
other libraries we've developed, which I didn't write. I only modified the
makefile of my
own code. I'm going to have to tweak the makefiles of a dozen different
library modules.
Unfortunately the problem isn't quite as
We have an application where the user can change the date/time via a GUI. One
of the options the user has is to specify that the time is to be synced using
ntp. Our coding worked fine under BSD 7 but since we've moved onto BSD 8 we've
encountered a problem where the command that we initiate
ntpq -pc rv localhost
cat /etc/ntp.conf
My ntp.conf looks like this:
# General Configuration
server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org
server 3.us.pool.ntp.org
# Drift file
driftfile /var/db/ntpd.drift
The output from ntpq for the BSD 7 system is this:
Resending this message. For some reason my post never showed up...
-Original Message-
From: Peter Steele
Sent: Wednesday, February 17, 2010 11:51 AM
To: freebsd-questions@freebsd.org
Subject: RE: What would make ntpd hang in BSD 8?
ntpq -pc rv localhost
cat /etc/ntp.conf
My
We boot off USB disks all the time without issues. As long as the disk is
listed first in the BIOS and it's a proper FBSD image, it works fine...
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Fbsd1
Sent: Wednesday,
We've seen this error sporadically when using the gpart command:
gpart: Cannot get GEOM tree: Cannot allocate memory
What would cause this? It does not happen often but I wouldn't think we should
never see it, not with a simple gpart show command.
We use gpart to create GPT style partitions. For example:
# gpart show ad4
= 34 490234685 ad4 GPT (234G)
34 161 freebsd-boot (8.0K)
50 671088642 freebsd-swap (32G)
67108914 671088643 freebsd-swap (32G)
134217778 104857604
What's the proper way to calculate kernel/user/idle time? I know the raw values
come from sysctl kern.cp_time, but these values need to be massaged based on
the number of CPUs and so on. Can someone explain briefly what the algorithm is
calculating the final percentages representing these
They shouldn't need to be massaged. Just sample the values at two intervals,
and your percentages can be calculated by dividing
each delta by the sum of the deltas (since the sum equals the total CPU usage
over the interval, by definition). If you want to
calculate per-cpu usage, use the
Are there any good instructions for creating a customized bootable .iso image?
I've done the work for creating a bootable USB image, but a .iso is a different
beast in that the boot media is read-only and a virtual disk has to be created
as part of the boot process. Any pointers would be
You can do this with the native make release process for freebsd.
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/release-build.html
Is this what you are looking for?
Hmmm. This might very well do what we need. I'll check it out. Thanks.
We have a system controlled through a Java GUI and one of the commands provided
in the GUI is to change the date/time, including the time zone. When the time
zone is changed the FreeBSD system immediately recognizes the change (that is,
the date command from the command line shows the correct
Is there any facility in FreeBSD for generating a random hostname? We have a
template with a fixed hostname that has to be changed after the template is
closed. It would be useful to have a hostname generated randomly.
___
Thinking about this some more, a good trick would be to generate a hostname
from the MAC address of the host, since that is guaranteed to be unique.
In fact, this is what we are currently using. Unfortunately I guess I wasn't
entirely clear. I was looking for a facility that actually *assigns*
I've ended up writing a service that runs after netif is complete and sets the
hostname based on the MAC address and also updates /etc/hosts. It does what I
need...
Thanks for all the replies on this...
___
freebsd-questions@freebsd.org mailing list
We had an app crash and the resulting core dump produced a very
suspicious/confusing stack trace:
#0 0x0008011d438c in thr_kill () from /lib/libc.so.7
#1 0x0008012722bb in abort () from /lib/libc.so.7
#2 0x0008011fb70c in malloc_usable_size () from /lib/libc.so.7
#3
I've moved this to freebsd-hackers...
-Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Peter Steele
Sent: Thursday, March 25, 2010 9:54 PM
To: freebsd-questions@freebsd.org
Subject: Very suspicious stack trace
We had
Does FreeBSD 8 support the Dell H700 RAID controller? We've been using a 3Ware
controller but may need to switch to this controller. What we'd like to have is
a command line interface similar to the tw_cli command so we can create RAID
sets on a booted system instead of doing it in the BIOS.
I see that these PERC controllers are all SAS instead of SATA. What kind of
cost differential is there between SAS and SATA disks?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
Is there some trick to know when the power supply sensor readings returned by
ipmitool actually reflects that there is a power supply issue? Our difficulty
is that no one seems to use the same sensor values when it comes to power
supply reporting, and even if there are two power supplies the
Theoretically, doing a straight dd copy of one disk to another and then
swapping in that disk should work. I've done it, with no other tweaking needed.
I've never done it with mixed OS instances on the same disk, or for that matter
with a solid state drive. You'll lose the trailing 12GB of your
] On Behalf Of Peter Steele
Sent: Tuesday, March 30, 2010 8:42 AM
To: freebsd-questions@freebsd.org
Subject: Making sense out of impitool power supply readings
Is there some trick to know when the power supply sensor readings returned by
ipmitool actually reflects that there is a power supply issue? Our
We clone systems from specially prepared USB flash sticks and this all works
well, except that occasionally the flash stick fails to boot. It fails at the
mount root step, saying that it cannot mount the specified root partition. We
use a labeled partition on the disk to make it device
What's the best what to test the status of an Ethernet interface
programmatically? We've been using this code similar to this:
struct ifmediareq ifmr;
memset(ifmr, 0, sizeof(ifmr));
strcpy(ifmr.ifm_name, nfe0);
ioctl(sockfd, SIOCGIFMEDIA, (caddr_t)ifmr)
and then checking the value of
I was going to suggest that you look at the ifconfig(8) source code, but then
I did so myself - it looks like you're doing it pretty much exactly how they
are. I've never noticed ifconfig(8) returning an incorrect value, not to say
it's not possible.
Are you sure that nothing is causing
You can try to solve the problem by:
-
# echo kern.cam.boot_delay=1 /boot/loader.conf
-
We've put a pretty sizeable delay already directly in the kernel. There is now
a noticeable pause before the mount root step is about to be performed. We
don't see the problem often now, but
One of the distribution sets that comes on a standard release DVD is base.
This includes the core set of binaries as well as the files under /etc and a
few other text files. Running make installworld doesn't collect everything
that's needed. Is there a make option to gather all of the files? I
We have a USB boot stick based cloning process that we're considering porting
to a DVD based media. I'm not sure though that it's possible due to the
restrictions I've seen in the mfsroot environment we'd have to use. For
example, in our USB disk procedure, we create partitions using gpart and
I use make distributionin /usr/src
to create the rest of the /etc files.
That seems to be exactly what I need. Thanks!
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
It sounds like http://mfsbsd.vx.sk/ would be helpful to you.
(I havent used it yet due to lack of time but it looks good.)
Hmmm, that just might do the trick. I'll check it out, thanks.
___
freebsd-questions@freebsd.org mailing list
But ... why are you constricting yourself to use mfs_root? I have many times
ran FreeBSD completely from CDrom, which
will give you all 700 (or a DVD, 4.3G) usable space.
I'd be happy to help, if you have questions. but please direct the questions
to the mailing list.
The reason I was
If FreeBSD cannot write to /tmp or /var on boot, it automatically creates a
MFS filesystems for those mountpoints
and mounts them during boot. You don't need to do anything.
It works as the same readonly compactflash environments out there.
D'oh! Man, wish I had known that. I just tried it and
If FreeBSD cannot write to /tmp or /var on boot, it automatically
creates a MFS filesystems for those mountpoints and mounts them during boot.
You don't need to do anything.
It works as the same readonly compactflash environments out there.
What incidentally does /var get populated with? Our
What incidentally does /var get populated with? Our image has a custom
directory under /var but this did not show up in the MFS versions of this
directory. I can get around this but I wonder what else might not be included?
I found something else that's missing--/var/db/pkg is empty. It looks
Can you write a few shell scripts? You'ld need to create a tarball of the
/var contents you need on the box, and explode it onto
/var at boot time -- if you're using auto-var on MFS all the time, you'll
need to set that up to happen on every reboot.
Obviously I can do that. What I was really
I'm probably missing something here, but I'm not sure that's correct. If the
OP wants his own /var, then diskless(8) describes how
/var can be automagically populated (see also /etc/rc.initdiskless). The
nanobsd.sh script (designed with flash drives in mind) uses
this method. I looked into
Not that I know of, unless you use the advantages of mfs then. Full circle,
bud. Now you're asking for necessities of the mfs or mfsroot systems.
I don't want to go there, and don't need to. I came up with a simple way to
populate /var from the original contents so I'm happy. The CD boots,
You might be able to reduce the iso size some by making a tarball of /var
(using tar -y or tar -z) instead of keeping /var2 as a tree.
Granted you would then need to have tar(1) in the iso, which may cancel out
much of the savings if you would not otherwise have needed it.
Actually, /var is
i think it's a bug but only happens with such massive mirror. very few
people do more than 2-way mirrors that's probably it wasn't catched.
please do report the bug - it's critical.
In fact I just confirmed that if we reduce our mirror to just two members the
problem does not occur. The
Has anyone successfully used the wake-on-LAN tool wol to wake-up a FreeBSD
system? If yes, what NICs did you need to use to get this to work?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
Long story short: Wake-on-LAN requires OS/NIC driver support. The OS puts the
NIC in a mode at shutdown that allows Wake-on-LAN to work. FreeBSD has no
Wake-on-LAN driver support, hence, no host running FreeBSD has Wake-on-LAN
capabilities.
I'm shocked that the Intel NICs don't have
Tim, I know nothing about WOL on FreeBSD, but according to the wiki,
development just started in 8 CURRENT:
http://wiki.freebsd.org/WakeOnLan
I came across that same reference. Unfortunately we're stuck on 7.0. I take it
the point of the wol command that available in the ports collection is
FUD, read ifconfig(8)
There is no mention of wake-on-LAN in the man page for ifconfig in 7.0. I'd be
interested in seeing if the 8.0 man page has added anything.
___
freebsd-questions@freebsd.org mailing list
In some cases (depending on the NIC and the BIOS) WOL works even without
OS support. It might be worth testing before you do anything else.
I've tried various experiments with the wol command to try to wake up one of
our boxes with no luck. We're using the stock nVidia driver. There is also no
1 - 100 of 176 matches
Mail list logo
