How to make the boot menu just like I want?
Dear FreeBSD Team: This is Frederick. Is there any table to list the partition number(subtype) or sysid? I have two hard disks. The first one install windows, and the second one install freebsd. I first install windows, then install freebsd. I use boot manager to manage my boot. The menu shows: F1: DOS F5: Drive 1 I want the menu to show like: F1: Windows F5 Drive 1 I did something. I changed the subtype in the fdisk, 6, 7, 12, 13, 14... but I can't make my menu just like I want. So please help me to find the partition number(subtype), or tell me how to do that to make the change. Please reply me to the following mail address: [EMAIL PROTECTED] Thanks for your help! Frederick. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
via vt1616 ac97 onboard sound
shalom, I haven't found any docs to tell me how to get this up and running yet. I have a Abit VA-10 mobo with via graphics and sound onboard. I found that Xfree86.org had updated to 4.4.0 and was able to install binaries without too much trouble, so I have X/Kde up. So does anyone know how I can do this? I found this viacombo/rpm package on the viaarena website. It has support for multiple linux's... it that an option? Just point me in the right direction. thanks nikita - Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
natd translating ip and udp packets but not tcp..
Greetings and salutations; I am having a puzzling issue with natd under FreeBSD 5.2, in which it will translate icmp and udp packets just fine, but tcp connections from the inside network to the outside world cannot be established. I can lookup hostnames, ping etc. from the internal client box, but cannot establish a connection to any tcp-based service. Consider my configuration, with addresses changed to implicate the guilty: Gateway internal interface: xl1 Gateway internal ip: 192.168.0.1/24 Client internal ip: 192.168.0.2 Gateway external interface: xl0 Gateway external ip: 131.107.3.124 Proper kernel options in place. ipfw configuration (more or less): 050 divert 8668 ip from any to any via xl0 100 allow ip from any to any natd running properly against xl0 I can provide more detailed information (tcpdumps, etc) if requested. Thanks. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Pentium 120 reboots after loading mfsroot floppy.
Hi, I was hoping to try out FreeBSD on an old machine I have been given (Pentium 120, 514MB HD, 8mb ram) and it reboots after loading the mfsroot floppy disk. You insert the disk, it goes /|\|/ for a while then reboots. What might cause this problem? Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Pentium 120 reboots after loading mfsroot floppy.
Thanks all for your replies, For future peoples reference. I managed to scrounge some more ram so it had 16 instead of 8 meg, and it boots prpoerly now. I had forgotten sysinstall needed more than 8MB of ram. I thrown off because it was just rebooting instead of printing an error. - Fred Frederick Bowes [EMAIL PROTECTED] writes: I was hoping to try out FreeBSD on an old machine I have been given (Pentium 120, 514MB HD, 8mb ram) and it reboots after loading the mfsroot floppy disk. You insert the disk, it goes /|\|/ for a while then reboots. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd 5.1 and devfs
shalom, I read the manpage on devfs and can't make heads or tails of it. I've a cs4236 onboard pnp sound card that took 2 months to finally get running and I'm gonna wait that long this time. My box is a dell optiplex gx1 and using old school rules catted dmesg.boot and found pcm0my card but when I tried to run sh MAKEDEV snd0 I find that makedev is now deprecated. please assist in my using devfs to make device nodes please reply to address above. Thanks nikita - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
regarding devfs ...
Hi, is there anyone who has documentation other than the manpage for freebsd's implementation of devfs? I have researched all the websites that I know of and have been unable to find any comprehensive doc on the subject. I've been trying to set a pnp onboard soundcard cs4236 crystal and other than getting the pcm0 message in the dmesg.boot I've haven't got a clue. Any salient help would be appreciated. Thanks nikita - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
hello again, devfs, hello
hi I just wondering if anyone is still out there who cn actually help me with the problem I'm having with devfs and my sound card. devfs did'nt automatically create any node I would normally expect to find , [/dev/snd/;/dev/dsp(although it did create dsp0.0 and 0.1); /dev/audio(for the sparc);and /dev/mixer]. now I know that people are busy, getting their own sh*t together, however I have been looking for any documetation other than the manpage for the last 3 hours on the web and haven't found a thing. I have an old dell optiplex gx1 with onboard sound that worked fine under freebsd 4.8. I see pcm0 in dmegboot, and catting sndstat gives me my card.I just want to know what to do to create the necessary nodes step by step... thanks nikita - Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Formatting an email for this list using vi
Hi, I have just started learning to use vi, and remember someone posting something a while ago about how to re-format an email reply to have proper 60 character width or something like that, does anyone remember how that is done? Thanks, Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using freebsd to analyse ip usage?
Hello Everyone, At work there are some unused ip addresses but we dont know which ones they are (because there are alot of computers) is there a port which could be used to ping the subnet over a few days to work out which ip addresses are actually coming online? Thanks Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw log popup in X
This is slightly off topic, but I have just setup ipfw and was wondering if there was a way to get the log messgaes popup in a window (ie so if someone attempts to connect, you get notified)? Some /usr/ports perhaps? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Hard drive geometry headache (slightly off topic)
Hello! I have a problem which i cannot seem to fix no matter what I do! I have a 120GB disk, which had windows XP/FreeBSD partions working fine on one computer. Now I had to move it to a new computer in which the bios detects a certian geometry, but then the system wont boot. No matter what I do now, i cant get the system to boot off the disk, i have even tried eraseing it with fdisk (freebsd and dos versions). Does anyone know how I can save it? I have tried everything and dont know where else to ask. Frederick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hard drive geometry headache (slightly off topic)
Now I had to move it to a new computer in which the bios detects a certian geometry, but then the system wont boot. No matter what I do now, i cant get the system to boot off the disk, i have even tried eraseing it with fdisk (freebsd and dos versions). Does anyone know how I can save it? I have tried everything and dont know where else to ask. Check to see that the BIOS is using the same addressing mode as the old board. I had a somewhat similar problem and it turned out the BIOS was in Large mode. Switching to LBA solved the problem. Also, if you've fdisk'ed the drive, chances are you've hosed the installations. I stopped caring about the data on the disk (which is backed up, so just an inconvenience. I have tried setting LBA/Large/CHS and booting and installing freebsd. Under each type, fdisk always reports that the geometry is incorect. Each time the install works fine but then when trying to boot, it cant read the hard disk! I am guessing freebsd works out the correct drive geometry, but the bios is not! Interestingly though, when set to LBA, the head/cyl/sector count is equal to what the freebsd fdisk detects it to be. (This is a new motherboard which works when booting/installing FreeBSD on an old 2G hd i have lying around) the problem is only with the 80G drive Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Hard drive geometry headache (slightly off topic)
Now I had to move it to a new computer in which the bios detects a certian geometry, but then the system wont boot. No matter what I do I had the same problem back in 4.5. I worked around the problem by formating the hard drive with a Win98(Oh Boy) recovery floppy then ... Formatting/fdisking under windows 98 or xp cd's didnt work for me, caused the same trouble. I've solved the problem and repreat it here for future generations reference (: It appears that the MBR was infact corrupt, causing fdisk to get confused... the following command made the hd appear blank and let it all work again: dd if=/dev/zero of=/dev/ad0 count=2000 (Yes i lost my data but the drive now works!) Thanks for ur help (: Fred ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cs4236b crystal onboard sound help
Shalom, I have been trying to avoid contacting you since I know that your engaged, however I have come to the end of my resources. I have a dual boot with win98 and freebsd 4.8 on a Dell Optiplex GX1(tower). I have attempted to configure the sound [crystalcs4236b onboard audio controller] for the past two months and have had no success. I even tried installing the open sound system, [which found the card, but couldn't get the audio test to work]. I've ran pnpinfo and it finds it as well, but I still can't get the bloody thing to work... So now all I can do is ask for HEELLP sincerely yours, [EMAIL PROTECTED] - Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
trouble installing rpm-4.0.4.tar.gz
shalom, I have a question which I hope that you can help me with. I just tried to intstall rpm-4.0.4.tar.gz on my system[freebsd 4.8] and have not been able to get it to ./configure let alone make. Is there a special dir, ( /usr/compat/linux?), or dependencies that are required to compile the tarball? My main reason for trying top install a package manager is that I've had problems with gmetadom[lastest] and various other tarballs with limited success. I am attempting to teach myself about unix and could just use a pointer in the right direction. Thank you for your time... [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Photos - Get your photo on the big screen in Times Square ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
once again rpm-4.0.4.tar.gz
Hello, I'm trying to get some help installing the tarball in the subject line because I do not have an internet connection at home, and every time I have tried to build a binary from source I've have been unable to because of some missing dependencies. I'm new to asking for help but I would like some guidance simply to be able to start developing my own apps and to be able to help some other poor slub who doesn't have a clue. So, I have freebsd 4.8 with linux compat enabled and I can't get the package to configure because it needs autoconf. So if anyone has an answer for me it would be a blessing. Happy New Year! nikita - Do you Yahoo!? Yahoo! Photos - Get your photo on the big screen in Times Square ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
I'm attempting to remove a number of old files within a directory that was rsynced over from another box. However a number of files (old symlinks and regular files in this instance) cause a kernel panic when attempting to remove them using rm or unlink. This is the panic message output: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x160 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81476306 stack pointer = 0x28:0xff811aacf880 frame pointer = 0x28:0xff811aacf940 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4729 (rm) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80b7d694 at VOP_REMOVE_APV+0x34 #7 0x808cb4fd at kern_unlinkat+0x32d #8 0x80b17cf0 at amd64_syscall+0x450 #9 0x80b03427 at Xfast_syscall+0xf7 And this is the backtrace from kgdb: #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808327f5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:442 #2 0x80832ca1 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:607 #3 0x80b18400 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:819 #4 0x80b18749 in trap_pfault (frame=0xff811aacf7d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735 #5 0x80b18c0f in trap (frame=0xff811aacf7d0) at /usr/src/sys/amd64/amd64/trap.c:474 #6 0x80b0313f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x81476306 in zfs_freebsd_remove (ap=Variable ap is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842 #8 0x80b7d694 in VOP_REMOVE_APV (vop=Variable vop is not available. ) at vnode_if.c:1333 #9 0x808cb4fd in kern_unlinkat (td=0xfe00046cb8c0, fd=-100, path=0x7fffdd73 Address 0x7fffdd73 out of bounds, pathseg=UIO_USERSPACE, oldinum=0) at vnode_if.h:575 #10 0x80b17cf0 in amd64_syscall (td=0xfe00046cb8c0, traced=0) at subr_syscall.c:131 #11 0x80b03427 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #12 0x0008009315fc in ?? () This particular system is a VM running on a VMWare ESXi hypervisor. So far I haven't had any luck in finding a cause. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel Panic on 9.0-RELEASE When Attempting to Remove Files
In response to the related thread started by Martin McCormick we did run a `zpool scrub` on the zpool, and the scrub completed successfully with no repairs performed. I successfully tried importing the zpool in Linux using the native Linux ZFS module. However attempting to remove the files via Linux results in `rm` either being killed or hanging. Ryan On 02/10/2012 10:43 AM, Ryan Frederick wrote: I'm attempting to remove a number of old files within a directory that was rsynced over from another box. However a number of files (old symlinks and regular files in this instance) cause a kernel panic when attempting to remove them using rm or unlink. This is the panic message output: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x160 fault code = supervisor read data, page not present instruction pointer = 0x20:0x81476306 stack pointer = 0x28:0xff811aacf880 frame pointer = 0x28:0xff811aacf940 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 4729 (rm) trap number = 12 panic: page fault cpuid = 1 KDB: stack backtrace: #0 0x808680fe at kdb_backtrace+0x5e #1 0x80832cb7 at panic+0x187 #2 0x80b18400 at trap_fatal+0x290 #3 0x80b18749 at trap_pfault+0x1f9 #4 0x80b18c0f at trap+0x3df #5 0x80b0313f at calltrap+0x8 #6 0x80b7d694 at VOP_REMOVE_APV+0x34 #7 0x808cb4fd at kern_unlinkat+0x32d #8 0x80b17cf0 at amd64_syscall+0x450 #9 0x80b03427 at Xfast_syscall+0xf7 And this is the backtrace from kgdb: #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x808327f5 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:442 #2 0x80832ca1 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:607 #3 0x80b18400 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:819 #4 0x80b18749 in trap_pfault (frame=0xff811aacf7d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:735 #5 0x80b18c0f in trap (frame=0xff811aacf7d0) at /usr/src/sys/amd64/amd64/trap.c:474 #6 0x80b0313f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x81476306 in zfs_freebsd_remove (ap=Variable ap is not available. ) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c:1842 #8 0x80b7d694 in VOP_REMOVE_APV (vop=Variable vop is not available. ) at vnode_if.c:1333 #9 0x808cb4fd in kern_unlinkat (td=0xfe00046cb8c0, fd=-100, path=0x7fffdd73 Address 0x7fffdd73 out of bounds, pathseg=UIO_USERSPACE, oldinum=0) at vnode_if.h:575 #10 0x80b17cf0 in amd64_syscall (td=0xfe00046cb8c0, traced=0) at subr_syscall.c:131 #11 0x80b03427 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #12 0x0008009315fc in ?? () This particular system is a VM running on a VMWare ESXi hypervisor. So far I haven't had any luck in finding a cause. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
You can recompile all ports that depend on pcre so that they'll use the new shared library. You can do so with: # portmaster -r pcre-8.30 Ryan On 02/15/2012 08:42 PM, Antonio Olivares wrote: Dear folks, I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING and I followed advice there to run # portmaster -w devel/pcre and I did this, and now machine won't get X. How can I bypass this mistake? I am now hesitant to update the other machines :(, I will get into problems starting X because of some update of a certain lib. Any thoughts, ideas or suggestions? Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /lib/exec/ld-elf.so.1: Shared object libpcre.so.0 not found, required by libxfsm-4.6.so.0 amd64 FreeBSD 8.2
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
should take care of the compilation failure. Afterward you should be
able to run portmaster as shown in the error message (minus
'net/avahi-app') to finish recompiling the ports that depend on pcre.
Ryan
On 02/15/2012 10:55 PM, Antonio Olivares wrote:
On Wed, Feb 15, 2012 at 9:33 PM, Robert Bonomibon...@mail.r-bonomi.com wrote:
Antonio Olivaresolivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7 (0x800647000)
There are two of them :( Should there be only one?
This is _normal_. The .so (with no further sufix), is generally just a link
to the 'latest' .so *with* a numeric suffix.
I am in a not good state now. I broke two machines by updating to
latest and get the same error on both machines.
I get the /libexec/ld-elf.so.1: Shared object libpcre.so.0 is needed
by * and nothing works, I run
# portmaster -r pcre-8.30
and it bombs out with the following:
signals-marshal.c:186: warning: ISO C forbids conversion of object
pointer to function pointer type
CC libavahi_gobject_la-ga-client-enumtypes.lo
CC libavahi_gobject_la-ga-entry-group-enumtypes.lo
CC libavahi_gobject_la-ga-enums-enumtypes.lo
CCLD libavahi-gobject.la
GISCAN Avahi-0.6.gir
g-ir-scanner: warning: Option --strip-prefix has been deprecated;
see --identifier-prefix and --symbol-prefix.
/usr/include/machine/endian.h:123: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:123: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint64_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/usr/include/machine/endian.h:130: syntax error, unexpected '{' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at '{'
/usr/include/machine/endian.h:130: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/types.txt,/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/dump.xml']'
returned non-zero exit status 1
gmake[3]: *** [Avahi-0.6.gir] Error 1
gmake[3]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory
`/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/net/avahi-app/work/avahi-0.6.29'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/net/avahi-app.
=== make failed for net/avahi-app
=== Aborting update
=== Update for avahi-app-0.6.29_1 failed
=== Aborting update
=== Update for gvfs-1.6.6_2 failed
=== Aborting update
=== Update for Thunar-1.3.0 failed
=== Aborting update
Terminated
=== There are messages from installed ports to display,
but first take a moment to review the error messages
above. Then press Enter when ready to proceed.
=== pkg-message for gamin-0.1.10_4
===
Gamin will only provide realtime notification of changes for at most n files,
where n is the minimum value between (kern.maxfiles * 0.7) and
(kern.maxfilesperproc - 200). Beyond that limit, files will be polled.
If you often open several large folders with Nautilus, you might want to
increase the kern.maxfiles tunable (you do not need to set
kern.maxfilesperproc, since it is computed at boot time from kern.maxfiles).
For a typical desktop, add the following line to /boot/loader.conf, then
reboot the system:
kern.maxfiles=25000
The behavior of gamin can be controlled via the various gaminrc files.
See http://www.gnome.org/~veillard/gamin/config.html on how to create
these files. In particular, if you find gam_server is taking up too much
CPU time polling for changes, something like the following may help
in one of the gaminrc files:
# reduce polling frequency to once per 10 seconds
# for UFS file systems in order to lower CPU load
fsset ufs poll 10
===
=== pkg-message for liblqr-1-0.4.1_2
==
unable to mount secondary hard disks now
Im running FreeBSD 5.3, its an almost fresh install. Its been running for about 7 days now. I have an internal IDE drive that the OS runs from, then I have two external firewire drives (da0, da1) that are only used as Samba shares. This morning i found that one of the firewire drives are no longer mounted (da1), this might have happened when I uninstalled Samba 2.x and installed 3.x yesterday, then rebooted. but im not sure, because i didnt check to see if the drive was still mounted after the reboot. So i figured i would just mount it again (even though da1 in the fstab) FileServer# mount /dev/da1s1c /mnt/jabba mount: /dev/da1s1c on /mnt/jabba: incorrect super block So now im not realy sure what to do, this drive was working perfectly before the reboot. someone told me to run fsck on the drive, but that gives me the following error. FileServer# fsck /dev/da1s1c ** /dev/da1s1c Cannot find file system superblock /dev/da1s1c: NOT LABELED AS A BSD FILE SYSTEM (unused) here is what fdisk returns... FileServer# fdisk /dev/da1s1c *** Working on device /dev/da1s1c *** parameters extracted from in-core disklabel are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=9728 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 0, size 5 (24 Meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end: cyl 1023/ head 254/ sector 63 Here are the relevant lines from my fstab... /dev/da0c /mnt/yoda ufs rw 2 2 /dev/da1s1c /mnt/jabba ufs rw 2 2 Thanks in advance -Shea ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd-update Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update Not Recognizing Updated Custom Kernel for 9.0-RELEASE-p3
I realized I made a couple of wording/clarification errors in my original message. First just about all of these kernels are not custom but simply locally compiled with no custom modifications. Second the locally compiled kernels are all named GENERIC (no custom name). Ryan On 6/12/12 2:29 PM, Ryan Frederick wrote: I have several FreeBSD 9 systems with custom compiled kernels. After using freebsd-update to go from 9.0-RELEASE-p2 to 9.0-RELEASE-p3 this morning I rebuilt the kernels. However after recompiling, installing, and rebooting with the custom kernels subsequent update checks using freebsd-update cron or freebsd-update fetch indicate that /boot/kernel/kernel (and only /boot/kernel/kernel) needs to be updated despite the custom kernel indicating 9.0-RELEASE-p3 in the output of uname -a. Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Building a Headless FreeBSD Virtual System
When you define the virtual serial port in VirtualBox for the guest VM one of the options available for connection of the port to the host system is a named pipe (I believe it's called Host Pipe in the configuration). You can then specify whatever named pipe on the host system you wish to attach the VM's serial port to then use a utility such as `socat` to present the I/O from the named pipe as a PTY device. From there it's simply a matter of using a utility such as `cu` or `screen` to connect to the PTY. Ryan On 08/29/2012 10:16 AM, Martin McCormick wrote: I am using Oracle's VirtualBox package for the Mac. It is free and I am not sure that Dollars would get past the issue I have, here. VirtualBox uses Microsoft's remote desktop as the one and only output channel to allow remote access to the virtual system one is creating and this is really bad design for computer users who are blind and use screen readers. Pictures of text just don't work. If you had some very complex system with OCR, it might sort of work, but such systems don't exist as a drop-in for a good old ASCII terminal so that's not an option. So far, I downloaded the bootonly ISO image of FreeBSD9.0, mounted it and added the following loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole vesa_load=YES Next, I used VirtualBoxmanage to define the disk and create the machine with a virtual IDE controller that is pointed to the ISO image for FreeBSD9.0 with the serial console. Has anybody been able to use VirtualBox and a fake serial console to get around the remote desktop non solution? I will probably have to add a virtual serial port in the machine definition one puts in the original machine build, but I am not sure this doesn't just go to that remote desktop channel where it gets scrubbed of any usefulness except for eyeballs on screens. This whole thing looks very promising but there's got to be a way around that shoe which doesn't fit in the form of that GUI remote desk top. In my case, the machine build goes without error but I can't tell yet if it is even booting. Mac's, by the way, have a relatively good screen reader built in but VirtualBox doesn't work with it, something that is a problem with a number of third-party programs especially when they were originally developed for Windows. This, of course, does not pertain to the main topic of this list, but I say it here so that you know I am aware you are supposed to be able to use the GUI on the Mac to manage your new virtual system. Essentially, the local GUI and the remote desktop don't work for me for the same reasons. My hope is to get FreeBSD running as a guest system on a powerful Mac and retire an old Dell server with noisy fans and several BTU of heat output which is in the realm of 15 years old and will probably retire itself at some random date in the future. Thank you for any good suggestions. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Virtual FreeBSD9.0 ISO Image Won't Mount Root FS
What option argument did you specify for the -V (volume ID) option when you created the ISO with the `mkisofs` command? I believe that the root filesystem lies under /dev/iso9660/volumeID for which the ISO loader's default configuration specifies as /dev/iso9660/FREEBSD_INSTALL. Thus you'll need to change the vfs.root.mountfrom loader variable to be cd9660:/dev/iso9660/volumeID Ryan On 09/05/2012 09:26 AM, Martin McCormick wrote: The ISO image is the FreeBSD9.0 bootonly CDROM for amd64 systems. I added loader.conf to /boot in order to activate a serial console and this along with socat appears to be working as it should. This is great because remote desktop is not an option. The VM boot starts normally with the spinning bars and normal startup messages until: cd0: cd present [85585 x 2048 byte records] Timecounter TSC frequency 3368628976 Hz quality 800 Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ... Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19. Loader variables: vfs.root.mountfrom=cd9660:/dev/iso9660/FREEBSD_INSTALL vfs.root.mountfrom.options=ro Manual root filesystem specification: fstype:device [options] Mountdevice using filesystemfstype and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) empty line Abort manual input mountroot I enter a Question Mark. mountroot ? List of GEOM managed disk devices: iso9660/CDROM cd0 ada0 mountroot The host system is a fairly new 64-bit Macintosh which is using VirtualBox. Here is the script to define the new machine. VBoxManage createvm --name vsys --ostype FreeBSD_64 --register VBoxManage modifyvm vsys --memory 1000 --vram 128 --acpi on \ --boot2 dvd --boot1 disk --nic1 nat #setup ttyu0 so the VM can communicate. VBoxManage modifyvm vsys --uart1 0x3F8 4 VBoxManage -q modifyvm vsys --uartmode1 server '/tmp/vmx' VBoxManage createhd --filename FreeBSD.VMDK --size 1 VBoxManage storagectl x --name SATA Controller --add sata --controller \ IntelAHCI --hostiocache on VBoxManage storageattach x --storagectl SATA Controller \ --port 0 --device 0 --type hdd --medium FreeBSD.VMDK VBoxManage storagectl vsys --name IDE Controller \ --add ide --controller PIIX4 VBoxManage storageattach vsys --storagectl IDE Controller \ --port 0 --device 0 --type dvddrive --medium /users/sysbuild/headless.iso ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Procmail Decoding Mime Messages
Forgot to cc the list. On 04/24/2013 04:47 PM, Ryan Frederick wrote: I believe mimencode is in ports as converters/mmencode. It is also included as part of mail/metamail. Ryan On 04/24/2013 04:07 PM, Martin McCormick wrote: Is there a filter that one can run in procmail in which base64 encoded data go in and text comes out so one can allow procmailrc to do its work? I use bogofilter to filter spam and it does a very good job after one builds a core of spammishness, but legitimate messages are often-times filled with base64 sections that look like garbage to the regular expressions that one puts in .procmailrc for sorting mail. When searching for information, I found something called mimencode which both encodes and decodes these attachments, but there is no FreeBSD port called mimencode so it occurred to me that some other application might exist which is in the ports that does basically the same thing. Is there anything which will take a raw email message and spit out linear strings which can be processed like normal text? Thank you. Martin McCormick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freesbd-update Continuously Wants to Update linker.hints
I have a number of boxes running 9.1-RELEASE (amd64) that I updated to p3 yesterday via freebsd-update. However freebsd-update still indicates that linker.hints needs to be updated. Running `freebsd-update install` appears to install a new linker.hints file but still doesn't appear to satisfy freebsd-update. Incidentally I have another amd64 system that I did a clean install on last week, and it isn't exhibiting the same issue. Has/is anyone run(ning) into this issue? Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: update from apache22 to apache24
The Apache site has documentation on upgrading from 2.2 to 2.4 -- http://httpd.apache.org/docs/2.4/upgrading.html The main change for me was the new allow/deny syntax. I've updated almost all of my Apache installs from 2.2 to 2.4 with no issues. The only installs I haven't updated yet are those using mod_evasive, since it's currently broken with 2.4 Ryan On 05/03/2013 09:47 AM, Jerry wrote: I was just wondering if anyone had updated from apache22 to apache24. Specifically, are there any problems to be overcome? Does the existing httpd.conf file work with the apache24 branch. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Curl -7.24.0_4 heap corruption
Update your ports vulnerability database before attempting to compile curl. `portaudit -Fda` should do the trick. Ryan On 07/02/2013 08:49 AM, Reggie Euser wrote: We're running FreeBSD 8.3-RELEASE-p3 and portaudit says: Affected package: curl-7.24.0_2 Type of problem: cURL library -- heap corruption in curl_easy_unescape. Reference: http://portaudit.FreeBSD.org/01cf67b3-dc3b-11e2-a6cd-c48508086173.html 1 problem(s) in your installed packages found. You are advised to update or deinstall the affected package(s) immediately. Have updated ports tree, checked UPDATING (nothing on curl since 2010). For last several days, portmaster curl has attempted to install curl-7.24.0_3 - same heap corruption issue. Today, portmaster curl attempted to install curl-7.24.0_4. I thought, great, the port has been updated! Except that the heap corruption issue persists and the update fails. Anyone have any insights into this issue? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What's wrong here? Can't reinstall graphics/lcms2
There was an entry in vuxml for lcms2 2.5 earlier this week that initially included 2.5 accidentally. It's been corrected now, so an update of your ports vulnerability database should allow you to install/update lcms2. Ryan On 08/20/2013 01:15 PM, Kurt Buff wrote: On Tue, Aug 20, 2013 at 10:23 AM, Walter Hurry walterhu...@gmail.com wrote: $ sudo portupgrade -f graphics/lcms2 snip = Please update your ports tree and try again. *** [check-vulnerable] Error code 1 I have of course updated the ports tree but it made no difference. Try updating ports again. I was successful in updating lcms2 this morning on a couple of boxes, after failures yesterday. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
sysinstall in a jail
I am running into a problem installing packages via sysinstall within a jail using the CD media. I did a minimal install, but added the /usr/src directory. I followed the directions to setup a jail and copied /stand/sysinstall into the jail subdirectory. As per the directions, I then started up the jail and ran sysinstall. But when I attempt to install off of the cdrom media, I get the following error: Error mounting /dev/acdoc on /dist: Operation not permitted (1). Now it makes sense that a jail might not be allowed to mount a system device. My confusion is that these were the instructions and I have not seen any posts saying this is a problem. Is there a way to give the jail permission to access the CD device? Should I mount the CD from the host (outside the jail) but to a subdirectory the jail has access to? Such as /usr/jail/myjail/dist? Versus /dist? Thank you for any suggestions. Frederick N. Brier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysinstall in a jail
I do not know whether this is the proper way of doing it, but I mounted the CD using mount -v -t cd9660 /dev/acd0c /usr/jail/myjail/dist Then I went back into the jail'ed environment, started up sysinstall, selected Configure/Media, choosing File System, specifying /dist, then selecting Packages, and it worked. Fred. Frederick N. Brier wrote: I am running into a problem installing packages via sysinstall within a jail using the CD media. I did a minimal install, but added the /usr/src directory. I followed the directions to setup a jail and copied /stand/sysinstall into the jail subdirectory. As per the directions, I then started up the jail and ran sysinstall. But when I attempt to install off of the cdrom media, I get the following error: Error mounting /dev/acdoc on /dist: Operation not permitted (1). Now it makes sense that a jail might not be allowed to mount a system device. My confusion is that these were the instructions and I have not seen any posts saying this is a problem. Is there a way to give the jail permission to access the CD device? Should I mount the CD from the host (outside the jail) but to a subdirectory the jail has access to? Such as /usr/jail/myjail/dist? Versus /dist? Thank you for any suggestions. Frederick N. Brier ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Multiple IP addresses in a Jail
Perhaps there is another way to do this, but I am trying to layout as fault tolerant a network architecture as possible. Most rack mounted boxes come with at least 2 Ethernet ports for what one would assume is to have each go to a separate switch (or to act as a firewall). If either switch goes Tango Uniform, the network is still up. But if my processes are running in Jails and I create an IP alias for each network interface for the jail, I need to specify 2 IP addresses for the Jail, not one. I had heard there was a patch to do this and that it had been added to FreeBSD 5.3. Is this not the case? Is there a patch? Is there another way to do this? Thank you. Frederick N. Brier Multideck Corporation ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How do I diagnose and fix a boot problem?
I had an old FreeBSD 4.8 server and wanted to upgrade it to 5.4. So I backed it up to both DVD and to another 5.4 system. The only change in the hardware was adding a Zonet ZEN3300E gigabit PCI adapter (Realtek RTL8169S-32). It is an old dual 600 P3 with 1GB RAM and a 3Ware 7000-2 controller with 2 160GB drives. I wiped the system and started from scratch with a standard (everything) install. I added the updated packages and got Samba, Apache2, the TWiki installed with all the shared files and twiki files restored. The system was rebooted at least 5-6 times to make sure everything started up properly, and it did great. I was just tweaking the sshd settings so that I could run cygwin XFree86 over ssh, and did a ps to get the pid of sshd, and ps came back with an error message. I had never seen this before and so figured perhaps a reboot was in order. So I did and ended up with this:: -- FreeBSD/i386 bootstrap loader, Revision 0.8 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok -- So I booted using floppies and a CD (the SCSI CD is not bootable - old Adaptec controller) and loaded the Live CD (disk 1). Going into Fixit mode, I mounted the first slice. Everything was fine no damage. The kernel was there with the same date and size as the version on the Live CD. I read through the Handbook section 12.3. None of the files had a recent timestamp. I thought perhaps the MBR a file had been corrupted. I tried the command disklabel -B twed0s1 which executed with no errors. When I tried the command fdisk -B -b /boot/boot0 twed0 It failed saying it could not find /dev/twed0 or if the correct directory was /dev, then twedo could not be found. Yet the device file was in /dev, the values looked reasonable, and df and other file system utilities were returning valid values. I tried rebooting again and looked variable values. Currdev and Loaddev are both disk1s1a which I am not sure is correct, but I get an error message if I try to change it to twed0s1a. Not sure what to try next. I don't know what the problem is or what caused the it. Any help or hints as to how to diagnose the problem or fix this would be greatly appreciated. Thank you. Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Reinstalling the standard boot manager
How do I reinstall just the standard MBR/Boot Manager without effecting anything else or accidentally doing a reinstall? Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Repairing kernel not found
Giorgos Keramidas was kind enough to point me at the boot0cfg command and I had already tried the disklabel command, but my 5.4 system still won't boot. The boot0cfg and disklabel commands executed fine, but it is still saying it can't find or load the kernel file despite it being in the correct directory on the correct slice. Please point me to a howto or docs on how to repair an installation without wiping out all the files and packages I have already installed/loaded/configured on this system. Thank you. Frederick N. Brier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Repairing kernel not found
More info. If I ls either before or after setting the bootpath or module_path environment variables, the response is: open '/' failed: no such file or directory. The load kernel command returns: can't file 'kernel'. Do I need to load a module so that the 3Ware drive twe is loaded? The loaddev and currdev variables are both set to disk1s1a: Thank you again. Fred. Giorgos Keramidas wrote: On 2005-09-06 11:13, Frederick N. Brier [EMAIL PROTECTED] wrote: Giorgos Keramidas was kind enough to point me at the boot0cfg command and I had already tried the disklabel command, but my 5.4 system still won't boot. The boot0cfg and disklabel commands executed fine, but it is still saying it can't find or load the kernel file despite it being in the correct directory on the correct slice. You can interrupt the boot loader and at the OK prompt run ls to see what the loader has mounted as the root partition. Then, assuming that you locate your kernel in ``/boot/kernel/kernel'', loading a specific kernel can be done with: OK set bootfile=/boot/kernel/kernel OK set module_path=/boot/kernel OK load kernel OK boot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Repairing kernel not found
What is odd is that the machine booted FreeBSD perfectly at least 5-6 times before I ran into the weird ps error and then it would not boot. I still need to figure out what caused the problem in the first place. For the moment, is there a way to reinstall just the core 5.4 kernel distribution files, but not anything else? Is it legitimate to do a recursive copy of all the boot files on the CD, ie: /dist/boot to the twed1s1a slice's /boot directory. Then I do the boot0cfg and disklabel command and then fixes any boot manager config files. Would that work? Fred. Giorgos Keramidas wrote: On 2005-09-06 19:34, Frederick N. Brier [EMAIL PROTECTED] wrote: More info. If I ls either before or after setting the bootpath or module_path environment variables, the response is: open '/' failed: no such file or directory. The load kernel command returns: can't file 'kernel'. Do I need to load a module so that the 3Ware drive twe is loaded? The loaddev and currdev variables are both set to disk1s1a: Thank you again. Hmmm, isn't it a job of the system BIOS to present a disk from the twe controller? Not sure why this would fail; I haven't used twe so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
