Re: mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Victor Sudakov wrote: > > I have several Supermicro-based servers with the mpt RAID adapter: > > # mptutil show adapter > mpt0 Adapter: >Board Name: UNUSED >Board Assembly: > Chip Name: C1068E > Chip Revision: UNUSED > RAID Levels: none > # > > The problem is, I cannot configure any RAIDs (please see output > below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD > still sees them as separate physical discs. What am I doing wrong? > > I cannot use gmirror with these servers because a) if no MPT RAID is > configured in BIOS setup, it cannot boot from HDD and b) if an MPT > RAID *is* configured in BIOS setup, it occupies the last sector and > prevents GEOM from working with these drives. > > Any help please? (or redirect me to a more appropriate maillist). After many unsuccessful trials and googling, we had to reconfigure the adapter from RAID mode to IT mode. It required flashing the adapter's BIOS from a Supermicro-supplied image and changing a jumper setting on the motherboard. Now as the adapter is in IT mode, it is a plain HBA the BIOS can boot from, and I have set up a gmirror on the SAS disks. After flashing the adapter BIOS, don't forget to enter its setup (Ctrl-C) and enable hotplugging of disks (called "Removable Media Support" in the menu, off by default). People come across similar problems and solutions on other OSes, like http://ubuntuforums.org/archive/index.php/t-973912.html -- Victor Sudakov Tomsk, Russia Russian Barefoot FAQ at http://www.barefooters.ru/barefoot.txt ___ 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"
Booting problem
Dear Sir, Please be kind enough to provide solution to the following problem. I have an old, assembled desk top loaded with win7 ultimate. It has got 80 GB hard disk and 1 GB RAM. Earlier there was XP. That time CD drive was not working at all. Subsequently I upgraded to win7. After few days suddenly I discovered that CD drive was working. I could burn files also through this drive. Though booting was not possible from CD. After few days suddenly, system stopped loading win7. I wanted to re install win7, but was not possible without the option of booting from CD. Whenever I tried to boot, one welcome screen and another screen came after one beep each and then it halts with a blank screen. I prepared a bootable USB drive with XP with an intention to install XP and thereafter upgrade to win7 (instructions for XP alone was available in the internet). After preparing the USB, I checked it in another system to see if it was working. In the BIOS there is no option to boot from USB. So I disabled all three boot options (Floppy, CD, HDD) and enabled “other” boot option and tried to boot from USB. Out of my nearly ten attempts, only twice, USB drive was displayed in the boot menu as a boot option, though it did not boot from it. Presently system does not boot either from HDD or from CD or from USB.(Floppy drive is not active since the relative cable is missing). My question is:- 1.Why should the boot menu display the USB drive only twice? Only in case of a loose connection such things can happen. I believe there is no question of any loose connection here. So either it should display all the time or it should not display at all. There is no specific option in the BIOS for booting from USB. If that means system does not support USB booting, then it should not have come in the boot menu at all. Fact that it appeared in the boot menu, means system supports booting from USB. 2. Why does not the system boot? I have a feeling that perhaps there is a component which is responsible for detecting drives or booting in general was failing slowly because of which CD drive was not working (when XP was there) and there after it was not booting from CD and again there after it stopped booting altogether from all the drives. Can there be a problem with mother board? 3. Someone told me that, in case of RAM failure, system will not start the boot process at all. Here since boot process goes few steps producing two screens and two beeps, perhaps it is trying to boot but why unable to detect the drives. 4. There are two separate cables for hard disk and CD drive. CD drive is primary and hard disk secondary. When I exchange the cables, it is reflected in the BIOS that is CD drive becomes secondary and vice versa. That means BIOS is recognizing the drives. 5. I tried with different boot order in the BIOS as well as by making the BIOS setting as default. 6. I tried the installation CD, so there is no question of whether the CD is bootable or not. Similarly if MBR is corrupt, it should give problem only for HDD booting and not for others like CD and USB. Then where is the problem? 7. Why doesn’t any error message displayed during boot process? ___ 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"
mpt problem on a Supermicro motherboard (FreeBSD 9.2 amd64)
Colleagues, I have several Supermicro-based servers with the mpt RAID adapter: # mptutil show adapter mpt0 Adapter: Board Name: UNUSED Board Assembly: Chip Name: C1068E Chip Revision: UNUSED RAID Levels: none # The problem is, I cannot configure any RAIDs (please see output below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD still sees them as separate physical discs. What am I doing wrong? I cannot use gmirror with these servers because a) if no MPT RAID is configured in BIOS setup, it cannot boot from HDD and b) if an MPT RAID *is* configured in BIOS setup, it occupies the last sector and prevents GEOM from working with these drives. Any help please? (or redirect me to a more appropriate maillist). # mptutil clear Are you sure you wish to clear the configuration on mpt0? [y/N] y mpt0: Configuration cleared # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # mptutil show drives mpt0 Physical Drives: da0 ( 558G) ONLINE SCSI-6 bus 0 id 0 da1 ( 558G) ONLINE SCSI-6 bus 0 id 1 da2 ( 558G) ONLINE SCSI-6 bus 0 id 2 da3 ( 558G) ONLINE SCSI-6 bus 0 id 3 # # mptutil create raid1 -v da2,da3 mptutil: Reading config page header failed: Invalid configuration page Added drive da2 with PhysDiskNum 0 mptutil: Reading config page header failed: Invalid configuration page # # mptutil show volumes mpt0 Volumes: Id SizeLevel Stripe State Write-Cache Name # -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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: Problem completing a 9.1 release to 9.2 release upgrade
On 06/10/2013 04:51, Eric Feldhusen wrote:
> I figured I'd walk through those steps from start to finish and just
> correct my main problem and any other little glitches I might have.
>
> I'm on step 6 and when I run mergemaster -p, I get the following error.
>
> *** Creating the temporary root environment in /var/tmp/temproot
> *** /var/tmp/temproot ready for use
> *** Creating and populating directory structure in /var/tmp/temproot
>
> /usr/bin/install: Undefined symbol "gid_from_group"
>
> *** FATAL ERROR: Cannot copy files to the temproot environment
>
> I found this thread on the Freebsd forums
> http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
> I do the same diagnostic steps of
>
> truss install -d -g wheel ~/testdirectory
>
> I find an error of
>
> lstat("/usr/local/etc/libmap.d",0x7fffb990) ERR#2 'No such file or
> directory'
>
> Any suggestions? Thank you for the help thus far.
The 'undefined symbol' error means you have a binary which is somehow
not dynamically linking against the shared libraries it was compiled to
use. As install(1) has pretty simple dynamic library usage -- just
libmd and libc:
# ldd /usr/bin/install
/usr/bin/install:
libmd.so.5 => /lib/libmd.so.5 (0x800822000)
libc.so.7 => /lib/libc.so.7 (0x800a33000)
... and libmd.so just contains code for computing various checksums,
nothing to do with groups and GIDs. This suggests that your libc.so is
somehow incompatible with your /usr/bin/install. Which really shouldn't
be the case given that you'ld previously used freebsd-update to upgrade
your userland to 9.2-RELEASE.
Things to double check:
* you haven't been faffing about with /etc/libmap.conf -- that file
or any file it includes should basically be empty except in quite
unusual circumstances. Remember folks: libmap is not your
solution of choice. It's what you turn to when there are no other
viable alternatives.
* Your freebsd-update really has been updating the source tree you
attempted to upgrade from. Check /etc/freebsd-update.conf. By
default it contains:
# Components of the base system which should be kept updated.
Components src world kernel
If you don't have src in there your buildworld procedure will at
best be trying to take you back down to 9.1-RELEASE-p???, and at
worst trying to create some unholy mixture of 9.2 kernel with
earlier bits of the system.
I think you should be able to recover to a system managed via
freebsd-update by something like:
# vi /etc/freebsd-update.conf
{ Make sure you're getting 'src world kernel' components as shown
above }
# freebsd-update fetch
# freebsd-update install
but I haven't tested that so ICBW. In any case, this should get you
back to the state where you have a 9.2-RELEASE world but your modified
9.1-RELEASE kernel. If you still need a custom kernel then you can
build and install it like so:
# cd /usr/src
# make KERNCONF=MYKERNEL buildkernel
# make KERNCONF=MYKERNEL installkernel
and reboot. Otherwise, I'm not sure exactly how you'ld revert from a
custom kernel to the standard generic kernel you'ld normally get via
freebsd-update. What I'd try is moving aside my customized kernel and
re-running freebsd-update:
# cd /boot
# mv kernel kernel-MYKERNEL
# freebsd-update install
If that creates a new /boot/kernel and populates with a new kernel and
many loadable modules then you're golden. If not, move your saved
kernel back into place (mv kernel-MYKERNEL kernel) and ask here again.
The 'no such file or directory' error for /usr/local/etc/libmap.d thing
is a false problem: /usr/local/etc/libmap.d is an optional directory --
all you are seeing is install(1) trying to open it and discovering that
it doesn't exist.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk
signature.asc
Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote: > On 05/10/2013 21:41, Polytropon wrote: > > On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: > >> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just > >> be able to do a > >> > >> cd /usr/src > >> make buildworld > >> make installworld > >> reboot > >> > >> and I'll be running up on the 9.2 kernel and then I'll be all set? > > > > No. You should follow the procedure mentioned in the > > comment header of /usr/src/Makefile. From my (old) > > b-STABLE system: > > > > # 1. `cd /usr/src' (or to the directory containing your source > > tree). > > # 2. `make buildworld' > > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is > > GENERIC). > > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is > > GENERIC). > > # [steps 3. & 4. can be combined by using the "kernel" target] > > # 5. `reboot'(in single user mode: boot -s from the loader > > prompt). > > # 6. `mergemaster -p' > > # 7. `make installworld' > > # 8. `make delete-old' > > # 9. `mergemaster'(you may wish to use -i, along with -U or > > -F). > > # 10. `reboot' > > # 11. `make delete-old-libs' (in case no 3rd party program uses them > > anymore) > > > > Pick what you need to do. When kernel and world sources are > > in sync, a new kernel can always be installed in multi-user > > mode. To install world, you should drop to single-user mode > > to avoid interferences with a full-featured system running > > in the "background". This procedure (or parts of it) will > > also work when you have been using freebsd-update to modify > > your kernel, world, and sources. > > > > Errrmm... The OP is maintaining his system using freebsd-update -- just > building and installing a replacement kernel from the source tree > installed via freebsd-update is in fact perfectly OK and a supported way > to manage a FreeBSD system. That is true. But if I understand the question (as quoted above) correctly, installing world from source has been involved, that's why my suggestion of following the instructions (or a subset of them, as it applies). > While you are quoting the official instructions from /usr/src/UPDATING > here (so they are completely correct in that sense) these are the > instructions to do something rather different to what the OP intended. I've copied the the instructions from the comment header of /usr/src/Makefile (at least on my outdated system at home they're there). Of course if the _only_ problem of the initial question is to install a custom kernel, with an otherwise updated system using freebsd-update (with world, kernel and sources in sync), just installing a custom kernel from within multi-user mode is fully supported by the system. This implies that only a small subset of the quoted instructions would apply here (steps 1 and 3 - 5), after freebsd-update has been finished successfully. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 21:41, Polytropon wrote: > On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: >> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just >> be able to do a >> >> cd /usr/src >> make buildworld >> make installworld >> reboot >> >> and I'll be running up on the 9.2 kernel and then I'll be all set? > > No. You should follow the procedure mentioned in the > comment header of /usr/src/Makefile. From my (old) > b-STABLE system: > > # 1. `cd /usr/src' (or to the directory containing your source tree). > # 2. `make buildworld' > # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). > # [steps 3. & 4. can be combined by using the "kernel" target] > # 5. `reboot'(in single user mode: boot -s from the loader prompt). > # 6. `mergemaster -p' > # 7. `make installworld' > # 8. `make delete-old' > # 9. `mergemaster'(you may wish to use -i, along with -U or -F). > # 10. `reboot' > # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) > > Pick what you need to do. When kernel and world sources are > in sync, a new kernel can always be installed in multi-user > mode. To install world, you should drop to single-user mode > to avoid interferences with a full-featured system running > in the "background". This procedure (or parts of it) will > also work when you have been using freebsd-update to modify > your kernel, world, and sources. > Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
I figured I'd walk through those steps from start to finish and just
correct my main problem and any other little glitches I might have.
I'm on step 6 and when I run mergemaster -p, I get the following error.
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
/usr/bin/install: Undefined symbol "gid_from_group"
*** FATAL ERROR: Cannot copy files to the temproot environment
I found this thread on the Freebsd forums
http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
I do the same diagnostic steps of
truss install -d -g wheel ~/testdirectory
I find an error of
lstat("/usr/local/etc/libmap.d",0x7fffb990) ERR#2 'No such file or
directory'
Any suggestions? Thank you for the help thus far.
Eric
On Sat, Oct 5, 2013 at 4:41 PM, Polytropon wrote:
> On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
> > I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should
> just
> > be able to do a
> >
> > cd /usr/src
> > make buildworld
> > make installworld
> > reboot
> >
> > and I'll be running up on the 9.2 kernel and then I'll be all set?
>
> No. You should follow the procedure mentioned in the
> comment header of /usr/src/Makefile. From my (old)
> b-STABLE system:
>
> # 1. `cd /usr/src' (or to the directory containing your source
> tree).
> # 2. `make buildworld'
> # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is
> GENERIC).
> # [steps 3. & 4. can be combined by using the "kernel" target]
> # 5. `reboot'(in single user mode: boot -s from the loader
> prompt).
> # 6. `mergemaster -p'
> # 7. `make installworld'
> # 8. `make delete-old'
> # 9. `mergemaster'(you may wish to use -i, along with -U or
> -F).
> # 10. `reboot'
> # 11. `make delete-old-libs' (in case no 3rd party program uses them
> anymore)
>
> Pick what you need to do. When kernel and world sources are
> in sync, a new kernel can always be installed in multi-user
> mode. To install world, you should drop to single-user mode
> to avoid interferences with a full-featured system running
> in the "background". This procedure (or parts of it) will
> also work when you have been using freebsd-update to modify
> your kernel, world, and sources.
>
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
>
___
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: Problem completing a 9.1 release to 9.2 release upgrade
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: > I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just > be able to do a > > cd /usr/src > make buildworld > make installworld > reboot > > and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. & 4. can be combined by using the "kernel" target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the "background". This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Problem completing a 9.1 release to 9.2 release upgrade
Ah, yes, when this particular box was a 9.0-release, I had compiled a custom kernel to enable ipsec. When I check the strings, it's a 9.1 release kernel. I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? Thanks for the help. Eric On Sat, Oct 5, 2013 at 3:34 PM, Matthew Seaman wrote: > On 05/10/2013 20:11, Eric Feldhusen wrote: > > I have a server that was/is running 9.1 release that I tried to upgrade > to > > 9.2 release. I missed the step of updating to the latest 9.1 patches by > > doing > > > > freebsd-update fetch > > freebsd-update install > > > > I went right to > > > > freebsd-update upgrade -r 9.2-RELEASE > > freebsd-update install > > > > rebooot > > > > freebsd-update install > > > > reboot again > > > > But my system still comes up as 9.1 release. > > > > Any suggestions on the steps to fix my goof? > > Did you replace the generic kernel from 9.1-RELEASE with something you > compiled yourself? If so, you may well have caused freebsd-update to > ignore any modifications to the kernel. > > You can fix that by re-compiling a kernel using the 9.2-RELEASE sources > and basically the same kernel configuration as for 9.1 (you will need to > check for 9.2 related differences to the configuration, but these are > likely to be pretty minor or not needed at all.) > > If you aren't using a customized kernel, then has the kernel in the > standard location on your system actually been updated? You can tell if > it's a 9.2 kernel by running strings(1) against the kernel binary, like so: > ># strings /boot/kernel/kernel | grep RELEASE > > If that's clearly a 9.2 kernel, then are you actually booting up from a > different kernel somewhere else on your system? First of all, are > there any other copies of FreeBSD kernels around anywhere -- on > memsticks, or on split mirrors perhaps? You may need to fiddle with the > bios settings or interrupt the boot sequence and type things directly at > the loader if so. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > > ___ 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: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 20:11, Eric Feldhusen wrote: > I have a server that was/is running 9.1 release that I tried to upgrade to > 9.2 release. I missed the step of updating to the latest 9.1 patches by > doing > > freebsd-update fetch > freebsd-update install > > I went right to > > freebsd-update upgrade -r 9.2-RELEASE > freebsd-update install > > rebooot > > freebsd-update install > > reboot again > > But my system still comes up as 9.1 release. > > Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Problem completing a 9.1 release to 9.2 release upgrade
I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Eric Feldhusen ___ 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 routing problem
> From: hrkesh sahu > Date: Thu, 3 Oct 2013 19:09:02 +0530 > To: "Julian H. Stacey" > Cc: Polytropon , > FreeBSD questions Hi, No idea why it was To: me. > Content-Type: text/html; charset=windows-1252 > Content-Transfer-Encoding: quoted-printable I dislike MS & windows & quoted-printable, > Content-Type: application/msword; name="1.5.VendorD.Topology.doc" > Content-Disposition: attachment; filename="1.5.VendorD.Topology.doc" MS excrement not accepted. http://www.berklix.com/~jhs/std/no_ms_format.txt Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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"
Problem with IPSec setup
Hello. Does anyone have a clue why kernel always directs ESP packets via default route (or default gateway in FIB 0), even if there are other FIBs with per-interface routes? I'm stuck with the gateway, which is connected to 2 ISPs and the necessity to configure IPSec tunnels on both external channels. Using setfib(8) I've managed to successfully establish an IKE session via both channels (using a separate instance of racoon per each channel), but the tunnel is just not working. Using IPFW's setfib option does not make any difference. Is this a bug or I'm missing some point? ___ 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 routing problem
Hi All, I am facing a routing issue for the Interoperability 1.5 topology. Please find the attachment of the exact topology map. As per test setup – Ø Configured REF-Router2 NOT to transmit Router Advertisement on Network1. But REF-Router2 is able to transmit Router Advertisement on Network2 with 2001:db8::3::/64 . Ø Configured a static route on TAR-RouterD ( ubuntu) Indicating REF-Router2’s Link local address as the next hop for the Network2 . Ø But Ref-Router Not able to routes between Network1 and Network2. Due to this ICMPv6 request from TAR-router to the global address of REF-Host2 is not working. There is no reply for this ICMPv6 request. Ø Same when I try to transmit ICMPv6 Echo request from REF-HOST2 to global address of TAR-HOST1( Prefix of TAR-RouterD), no ICMPv6 reply. Ø Within Network1 , nodes are able to communicate. But when I try to communicate Netwrok2 from Network1, it is not working. Could you please suggest tell me if I am missing something to route the traffic on REF-Router ? I suspect , as there is no Route Advertisement on Interface1 of the Ref-Router, it is not able to route the traffic between the interfaces. Please help me to find this solution. Regards ___ 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: Port of icedtea-web-1.4_1, on 64 bit system might have a problem in the install process.
On 10/02/2013 6:35 am, Volodymyr Kostyrko wrote: 01.10.2013 21:12, dweimer wrote: On 10/01/2013 11:09 am, dweimer wrote: I was struggling to get itweb-javaws to execute, due to it not being able to find libjava.so, after running it through truss, I was able to determine that its looking for the library under /usr/local/lib/amd64, the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able to work around the problem by creating a symbolic link to point /usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64 sub-directory didn't exist in /usr/local/lib. This does make me wonder though, if I am just missing something from my environment, that's causing this. Or is the port install not doing something that it should be doing? System is a new build of 9.2-RELEASE, compiled from source, source and ports all built with clang where possible. Just an update, this only worked the first time I executed it, now all I get is: java.lang.UnsatisfiedLinkError: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: Undefined symbol "jpeg_resync_to_restart" Try `-headless`. You wont see the shiny logo though... Thank you, this fixed that part, silly me, I was searching the help for things like -nosplash, and disable splash screen. Didn't realize that this was the same thing: -headless Disables download window, other UIs. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: Port of icedtea-web-1.4_1, on 64 bit system might have a problem in the install process.
01.10.2013 21:12, dweimer wrote: On 10/01/2013 11:09 am, dweimer wrote: I was struggling to get itweb-javaws to execute, due to it not being able to find libjava.so, after running it through truss, I was able to determine that its looking for the library under /usr/local/lib/amd64, the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able to work around the problem by creating a symbolic link to point /usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64 sub-directory didn't exist in /usr/local/lib. This does make me wonder though, if I am just missing something from my environment, that's causing this. Or is the port install not doing something that it should be doing? System is a new build of 9.2-RELEASE, compiled from source, source and ports all built with clang where possible. Just an update, this only worked the first time I executed it, now all I get is: java.lang.UnsatisfiedLinkError: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: Undefined symbol "jpeg_resync_to_restart" Try `-headless`. You wont see the shiny logo though... -- Sphinx of black quartz, judge my vow. ___ 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: Port of icedtea-web-1.4_1, on 64 bit system might have a problem in the install process.
01.10.2013 19:09, dweimer wrote:
I was struggling to get itweb-javaws to execute, due to it not being
able to find libjava.so, after running it through truss, I was able to
determine that its looking for the library under /usr/local/lib/amd64,
the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able to
work around the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64
sub-directory didn't exist in /usr/local/lib.
This does make me wonder though, if I am just missing something from my
environment, that's causing this. Or is the port install not doing
something that it should be doing?
Never faced this, itweb-javaws works for me without library shuffling
but with one tiny fix to startup script: `exec "${COMMAND[@]}"`.
--
Sphinx of black quartz, judge my vow.
___
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: Port of icedtea-web-1.4_1, on 64 bit system might have a problem in the install process.
On 10/01/2013 11:09 am, dweimer wrote: I was struggling to get itweb-javaws to execute, due to it not being able to find libjava.so, after running it through truss, I was able to determine that its looking for the library under /usr/local/lib/amd64, the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able to work around the problem by creating a symbolic link to point /usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64 sub-directory didn't exist in /usr/local/lib. This does make me wonder though, if I am just missing something from my environment, that's causing this. Or is the port install not doing something that it should be doing? System is a new build of 9.2-RELEASE, compiled from source, source and ports all built with clang where possible. Just an update, this only worked the first time I executed it, now all I get is: java.lang.UnsatisfiedLinkError: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: /usr/local/openjdk7/jre/lib/amd64/libsplashscreen.so: Undefined symbol "jpeg_resync_to_restart" I somewhat worked around it by installing the linux_sun_jre 7.40, and pointing icedtea webstart at it, searching online shows this to be most likely be a bug in the port of openjdk. http://www.freebsd.org/cgi/query-pr.cgi?pr=119654 -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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"
Port of icedtea-web-1.4_1, on 64 bit system might have a problem in the install process.
I was struggling to get itweb-javaws to execute, due to it not being able to find libjava.so, after running it through truss, I was able to determine that its looking for the library under /usr/local/lib/amd64, the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able to work around the problem by creating a symbolic link to point /usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64 sub-directory didn't exist in /usr/local/lib. This does make me wonder though, if I am just missing something from my environment, that's causing this. Or is the port install not doing something that it should be doing? System is a new build of 9.2-RELEASE, compiled from source, source and ports all built with clang where possible. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: problem with stoping process
On 15.12.2011 20:00, Коньков Евгений wrote: > I am trying to stop process > /usr/local/etc/rc.d/radiusd top > Stopping radiusd. > Waiting for PIDS: 27618 > > top > 27618 freeradius2 20 -20 333M 295M STOP0 4:42 0.00% radiusd > > ps aux > freeradius 27618 0.0 7.4 341144 302528 ?? T /usr/local/sbin/radiusd > > nothing is happen > > Why process do not stop? > Does it stops when you kill it by hand with kill -15 27618? David. ___ 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 ports problem
On Thu, Aug 29, 2013 at 11:39 PM, Harpreet Singh Chawla < preet10101...@gmail.com> wrote: > yup...did it...and downloaded manually... > But its giving a checksum matching error. > > *Harpreet Singh Chawla* > > > On 29 August 2013 22:48, Amitabh Kant wrote: > >> >> On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla < >> preet10101...@gmail.com> wrote: >> >>> I have been trying to install virtualbox support for my FreeBSD 9.1. A >>> package named v4l_compat-1.0.20120501.tar.gz is causing problems in the >>> installation. The package was downloaded automatically and it exists in >>> /usr/ports/distfiles, yet it keeps giving an error stating that the file >>> doesn't exist. >>> >>> Please help. >>> *Harpreet Singh Chawla* >>> ___ >>> >> >> No idea about virtualbox port, but have you tried deleting the offending >> file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? >> >> Amitabh >> > > After deleting, you don't need to download it manually. The port should download it if needed. Try updating your ports tree to see if the problem has been rectified. Amitabh ___ 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 ports problem
On Thu, Aug 29, 2013 at 7:32 PM, Harpreet Singh Chawla < preet10101...@gmail.com> wrote: > I have been trying to install virtualbox support for my FreeBSD 9.1. A > package named v4l_compat-1.0.20120501.tar.gz is causing problems in the > installation. The package was downloaded automatically and it exists in > /usr/ports/distfiles, yet it keeps giving an error stating that the file > doesn't exist. > > Please help. > *Harpreet Singh Chawla* > ___ > No idea about virtualbox port, but have you tried deleting the offending file (rm -f /usr/ports/distfiles/v4l_compat-1.0.20120501.tar.gz)? Amitabh ___ 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 ports problem
I have been trying to install virtualbox support for my FreeBSD 9.1. A package named v4l_compat-1.0.20120501.tar.gz is causing problems in the installation. The package was downloaded automatically and it exists in /usr/ports/distfiles, yet it keeps giving an error stating that the file doesn't exist. Please help. *Harpreet Singh Chawla* ___ 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: pkgng problem
must be code unrot On 19 August 2013 16:13, Michael W. Lucas wrote: > For the archives: > > I left the problem alone for a few days, with no changes on my side. > > Came back Monday. Tried again. Everything worked on the affected > machines. > > ==ml > > -- > Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor > http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ > Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e > coupon code "ILUVMICHAEL" gets you 30% off & helps me. > ___ > 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: pkgng problem
For the archives: I left the problem alone for a few days, with no changes on my side. Came back Monday. Tried again. Everything worked on the affected machines. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ 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: pkgng problem
On Fri, Aug 16, 2013 at 11:23:41AM -0700, Adrian Chadd wrote: >Have you done a "pkg update" first, just in case you needed to pull in a >pkgng update? Yep, tried that. ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ 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: pkgng problem
Have you done a "pkg update" first, just in case you needed to pull in a pkgng update? -adrian ___ 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: pkgng problem
Matt, Another data point on this: Machines converted to pkgng a couple weeks ago can install new packages just fine despite showing the same error. And it looks like they download the new repo information: # pkg install sysrc Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 1.4MB/s 1.9MB/s 00:04 pkg: Invalid manifest format: mapping values are not allowed in this contex Incremental update completed, 0 packages processed: 8292 packages updated, 1115 removed and 129 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy The following 1 packages will be installed: Installing sysrc: 5.2 The installation will require 39 kB more space 15 kB to be downloaded Proceed with installing packages [y/N]: y sysrc-5.2.txz 100% 16KB 15.8KB/s 15.8KB/s 00:00 Checking integrity... done [1/1] Installing sysrc-5.2... done Machines upgraded to pkgng this week, using the same script as I used a couple weeks ago, cannot install packages. # pkg install sysrc Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 2.7MB/s 1.5MB/s 00:02 pkg: Invalid manifest format: mapping values are not allowed in this context Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 22568 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy pkg: No packages matching 'sysrc' has been found in the repositories Not sure if this supports the "bad repo" theory, but it's interesting. Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ 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: pkgng problem
On 16/08/2013 16:02, Michael W. Lucas wrote: > > Thanks, Matt. > > # pkg -vv | sed -ne '/Repositories/,$p' > Repositories: > packagesite: > url: http://pkg-test.freebsd.org/pkg-test-freebsd:9:x86:32/latest > key: > enabled: yes > mirror_type: SRV > > Also: > > # pkg -v > 1.1.4 > Well, looks like both of those are up-to-date versions. I wonder if the pkg-test build system threw a wobbly at all on it's i386 builder? Bapt is on holiday or I'd ask him. Cheers, Matthew ___ 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: pkgng problem
Thanks, Matt. # pkg -vv | sed -ne '/Repositories/,$p' Repositories: packagesite: url: http://pkg-test.freebsd.org/pkg-test-freebsd:9:x86:32/latest key: enabled: yes mirror_type: SRV Also: # pkg -v 1.1.4 ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ 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: pkgng problem
On 16/08/2013 13:43, Michael W. Lucas wrote: > Hi, > > I'm sure someone has had this before, but I can't find any reference > to it. > > # pkg upgrade > Updating repository catalogue > digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 > packagesite.txz 100% 5530KB 1.8MB/s 3.2MB/s 00:03 > pkg: Invalid manifest format: mapping values are not allowed in this context > Incremental update completed, 0 packages processed: > 0 packages updated, 0 removed and 22568 added. > pkg: No digest falling back on legacy catalog format > packagesite repository catalogue is up-to-date, no need to fetch fresh copy > Nothing to do > > This is from a machine freshly converted to pkgng. > > Any suggestions? What repositories are you using? Please show us the result of: pkg -vv | sed -ne '/Repositories/,$p' I'd hazard a guess that the repository either had a bit of a flail when creating the catalogue, or it's running some ancient version of pkg. "mapping values are not allowed in this context" is an error message from libyaml, so you've got a +MANIFEST file (or the partial copy of it that gets incorporated into the repository catalogue) which it thinks contains a mapping ( a sequence of key : value pairs ) when the YAML parser was expecting an array or whatever. Cheers, Matthew ___ 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"
pkgng problem
Hi, I'm sure someone has had this before, but I can't find any reference to it. # pkg upgrade Updating repository catalogue digests.txz 100% 997KB 997.1KB/s 997.1KB/s 00:00 packagesite.txz 100% 5530KB 1.8MB/s 3.2MB/s 00:03 pkg: Invalid manifest format: mapping values are not allowed in this context Incremental update completed, 0 packages processed: 0 packages updated, 0 removed and 22568 added. pkg: No digest falling back on legacy catalog format packagesite repository catalogue is up-to-date, no need to fetch fresh copy Nothing to do This is from a machine freshly converted to pkgng. Any suggestions? Thanks, ==ml -- Michael W. Lucas - mwlu...@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. ___ 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: 9.2-RC1: Problem with Kernel
On Tue, 13 Aug 2013 05:14:52 +0200, Polytropon wrote: > On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: >> Sorry again. Anyway, I have it nailed down now. For anyone who is >> interested, the missing entry was: >> >> options ATA_CAM > > Correct. Line 84 and 264 have it commented out. This is the "new" method > of talking to disk devices, similarly as the acd interface for optical > media has been trans- formed into "SCSI over ATA" (ex device atapicam). > So the disk drive has not been recognized by the kernel, therefore: No > soup for you (i. e., no boot device). :-) Thanks, Polytropon! I have changed the controller (this is a VM, remember) to which the (same) virtual hard drive is attached, from ISA to SATA and "options ATA_CAM" is no longer needed. So I have learned a few things. Thanks again. ___ 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: 9.2-RC1: Problem with Kernel
On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: > Sorry again. Anyway, I have it nailed down now. For anyone who is > interested, the missing entry was: > > options ATA_CAM Correct. Line 84 and 264 have it commented out. This is the "new" method of talking to disk devices, similarly as the acd interface for optical media has been trans- formed into "SCSI over ATA" (ex device atapicam). So the disk drive has not been recognized by the kernel, therefore: No soup for you (i. e., no boot device). :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: 9.2-RC1: Problem with Kernel
On Sun, 11 Aug 2013 22:47:36 +1000, Ian Smith wrote:
> In freebsd-questions Digest, Vol 479, Issue 8, Message: 10 On Sun, 11
> Aug 2013 09:43:57 + (UTC) Walter Hurry
> wrote:
> > On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
> >
> > > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> > >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching
> > >> the source from releng/9.2 and rebuilding kernel and world).
> > >>
> > >> The kernel compiles and runs fine using the supplied GENERIC, but
> > >> when I try to use my custom kenel config file, on reboot I get
> > >> this:
> > >>
> > >> Mounting from ufs:/dev/ada0p2 failed with error 19
> > >>
> > >> What module(s) have I missed?
> > >
> > > Diff against the GENERIC kernel. Maybe "device xhci"?
> > > What bootable media is listed when you type "?" at the mountroot
> > > prompt?
> > > If GENERIC boots and your kernel doesn't, there should be a
> > > significant difference regarding the config file's content. :-)
> >
> > Thanks for the reply. When I type "?" at the mountroot prompt I get:
> >
> > List of GEOM managed disk devices:
> >
> > with nothing shown.
> >
> > After restoring the GENERIC kernel, the output from 'gpart list' is:
> >
> > Geom name: ada0
> [..]
> > Consumers:
> > 1. Name: ada0
> >Mediasize: 21474836480 (20G)
> >Sectorsize: 512 Mode: r2w2e3
> >
> > (This is a small VirtualBox VM.)
> >
> > Kernel config is at http://paste2.org/h17Ih0PD
>
> Please Walter, it's not fair to make us do the work of figuring out what
> you've changed from GENERIC in that, when all you need to provide is:
>
> # diff -uw /path/to/GENERIC /path/to/YOURKERNEL
>
> More ideal for custom kernel configs - for just these occasions - is:
>
> include GENERIC ident YOURKERNEL # custom {no,}device and {no,}options
> statements
>
Sorry again. Anyway, I have it nailed down now. For anyone who is
interested, the missing entry was:
options ATA_CAM
___
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: 9.2-RC1: Problem with Kernel
On Sun, 11 Aug 2013 22:47:36 +1000, Ian Smith wrote:
> In freebsd-questions Digest, Vol 479, Issue 8, Message: 10 On Sun, 11
> Aug 2013 09:43:57 + (UTC) Walter Hurry
> wrote:
> > On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
> >
> > > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> > >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching
> > >> the source from releng/9.2 and rebuilding kernel and world).
> > >>
> > >> The kernel compiles and runs fine using the supplied GENERIC, but
> > >> when I try to use my custom kenel config file, on reboot I get
> > >> this:
> > >>
> > >> Mounting from ufs:/dev/ada0p2 failed with error 19
> > >>
> > >> What module(s) have I missed?
> > >
> > > Diff against the GENERIC kernel. Maybe "device xhci"?
> > > What bootable media is listed when you type "?" at the mountroot
> > > prompt?
> > > If GENERIC boots and your kernel doesn't, there should be a
> > > significant difference regarding the config file's content. :-)
> >
> > Thanks for the reply. When I type "?" at the mountroot prompt I get:
> >
> > List of GEOM managed disk devices:
> >
> > with nothing shown.
> >
> > After restoring the GENERIC kernel, the output from 'gpart list' is:
> >
> > Geom name: ada0
> [..]
> > Consumers:
> > 1. Name: ada0
> >Mediasize: 21474836480 (20G)
> >Sectorsize: 512 Mode: r2w2e3
> >
> > (This is a small VirtualBox VM.)
> >
> > Kernel config is at http://paste2.org/h17Ih0PD
>
> Please Walter, it's not fair to make us do the work of figuring out what
> you've changed from GENERIC in that, when all you need to provide is:
>
> # diff -uw /path/to/GENERIC /path/to/YOURKERNEL
>
> More ideal for custom kernel configs - for just these occasions - is:
>
> include GENERIC ident YOURKERNEL # custom {no,}device and {no,}options
> statements
>
Sorry. A diff wouldn't have helped much, as every line had changed due to
my reformatting. Never mind, I'll work it out for myself by a process of
elimination - and I'll post the answer here just in case anyone else is
interested.
___
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: 9.2-RC1: Problem with Kernel
In freebsd-questions Digest, Vol 479, Issue 8, Message: 10
On Sun, 11 Aug 2013 09:43:57 + (UTC) Walter Hurry
wrote:
> On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote:
>
> > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote:
> >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the
> >> source from releng/9.2 and rebuilding kernel and world).
> >>
> >> The kernel compiles and runs fine using the supplied GENERIC, but when
> >> I try to use my custom kenel config file, on reboot I get this:
> >>
> >> Mounting from ufs:/dev/ada0p2 failed with error 19
> >>
> >> What module(s) have I missed?
> >
> > Diff against the GENERIC kernel. Maybe "device xhci"?
> > What bootable media is listed when you type "?" at the mountroot prompt?
> > If GENERIC boots and your kernel doesn't, there should be a significant
> > difference regarding the config file's content. :-)
>
> Thanks for the reply. When I type "?" at the mountroot prompt I get:
>
> List of GEOM managed disk devices:
>
> with nothing shown.
>
> After restoring the GENERIC kernel, the output from 'gpart list' is:
>
> Geom name: ada0
[..]
> Consumers:
> 1. Name: ada0
>Mediasize: 21474836480 (20G)
>Sectorsize: 512
>Mode: r2w2e3
>
> (This is a small VirtualBox VM.)
>
> Kernel config is at http://paste2.org/h17Ih0PD
Please Walter, it's not fair to make us do the work of figuring out what
you've changed from GENERIC in that, when all you need to provide is:
# diff -uw /path/to/GENERIC /path/to/YOURKERNEL
More ideal for custom kernel configs - for just these occasions - is:
include GENERIC
ident YOURKERNEL
# custom {no,}device and {no,}options statements
cheers, Ian
___
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: 9.2-RC1: Problem with Kernel
On Sat, 10 Aug 2013 21:29:10 +0200, Polytropon wrote: > On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote: >> This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the >> source from releng/9.2 and rebuilding kernel and world). >> >> The kernel compiles and runs fine using the supplied GENERIC, but when >> I try to use my custom kenel config file, on reboot I get this: >> >> Mounting from ufs:/dev/ada0p2 failed with error 19 >> >> What module(s) have I missed? > > Diff against the GENERIC kernel. Maybe "device xhci"? > What bootable media is listed when you type "?" at the mountroot prompt? > If GENERIC boots and your kernel doesn't, there should be a significant > difference regarding the config file's content. :-) Thanks for the reply. When I type "?" at the mountroot prompt I get: List of GEOM managed disk devices: with nothing shown. After restoring the GENERIC kernel, the output from 'gpart list' is: Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 41943006 first: 34 entries: 128 scheme: GPT Providers: 1. Name: ada0p1 Mediasize: 65536 (64k) Sectorsize: 512 Stripesize: 0 Stripeoffset: 17408 Mode: r0w0e0 rawuuid: c5ae2f8e-f5e1-11e2-92dd-08002755f0f7 rawtype: 83bd6b9d-7f41-11dc-be0b-001560b84f0f label: (null) length: 65536 offset: 17408 type: freebsd-boot index: 1 end: 161 start: 34 2. Name: ada0p2 Mediasize: 20401029120 (19G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 82944 Mode: r1w1e1 rawuuid: c5ba5d2c-f5e1-11e2-92dd-08002755f0f7 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 20401029120 offset: 82944 type: freebsd-ufs index: 2 end: 39845921 start: 162 3. Name: ada0p3 Mediasize: 1073707008 (1G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 3221242880 Mode: r1w1e0 rawuuid: c5ccb46a-f5e1-11e2-92dd-08002755f0f7 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 1073707008 offset: 20401112064 type: freebsd-swap index: 3 end: 41943005 start: 39845922 Consumers: 1. Name: ada0 Mediasize: 21474836480 (20G) Sectorsize: 512 Mode: r2w2e3 (This is a small VirtualBox VM.) Kernel config is at http://paste2.org/h17Ih0PD ___ 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: 9.2-RC1: Problem with Kernel
On Sat, 10 Aug 2013, Walter Hurry wrote: This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the source from releng/9.2 and rebuilding kernel and world). The kernel compiles and runs fine using the supplied GENERIC, but when I try to use my custom kenel config file, on reboot I get this: Mounting from ufs:/dev/ada0p2 failed with error 19 What module(s) have I missed? options GEOM_PART_GPT But without information on what you removed, it's only a guess. ___ 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: 9.2-RC1: Problem with Kernel
On Sat, 10 Aug 2013 19:04:29 + (UTC), Walter Hurry wrote: > This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the > source from releng/9.2 and rebuilding kernel and world). > > The kernel compiles and runs fine using the supplied GENERIC, but when I > try to use my custom kenel config file, on reboot I get this: > > Mounting from ufs:/dev/ada0p2 failed with error 19 > > What module(s) have I missed? Diff against the GENERIC kernel. Maybe "device xhci"? What bootable media is listed when you type "?" at the mountroot prompt? If GENERIC boots and your kernel doesn't, there should be a significant difference regarding the config file's content. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
9.2-RC1: Problem with Kernel
This is 9.2-RC1 on amd64 (upgraded from 9.2-BETA1 by refetching the source from releng/9.2 and rebuilding kernel and world). The kernel compiles and runs fine using the supplied GENERIC, but when I try to use my custom kenel config file, on reboot I get this: Mounting from ufs:/dev/ada0p2 failed with error 19 What module(s) have I missed? 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"
firefox build problem
just did a ports update, haven't done one for a few months. portmaster -w www/firefox craps out with: In file included from /usr/ports/www/firefox/work/mozilla-release/gfx/2d/Blur.cp p:7: In file included from ../../dist/include/mozilla/gfx/Blur.h:12: ../../dist/include/mozilla/CheckedInt.h:179:31: error: non-type template argument of type 'const bool' is not an integral constant expression static const bool value = IntegerType(-1) <= IntegerType(0); ^ ../../dist/include/mozilla/CheckedInt.h:343:28: note: while checking a default template argument used here return IsInRangeImpl::run(x); Have I got something screwed up? I don't know squat about c++ templates and can't see what's wrong. hints? ___ 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: Newbye question VIM problem
On 2013-07-23 18:07, Teske, Devin wrote: (opening a can of squiggly worms here) Well, then you can go fishing This is a A sidenotnote ___ 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: Newbye question VIM problem
On Jul 23, 2013, at 8:56 AM, Pietro Paolini wrote: > > On Jul 23, 2013, at 5:16 PM, Fernando Apesteguía > wrote: > >> https://urldefense.proofpoint.com/v1/url?u=ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-release/Latest/&k=%2FbkpAUdJWZuiTILCq%2FFnQg%3D%3D%0A&r=Mrjs6vR4%2Faj2Ns9%2FssHJjg%3D%3D%0A&m=EqNk3zW%2BFthkGaRpyM7lCZDFPyMcUaqjJFP252xoemg%3D%0A&s=bdff9db189b5402b3645c555057e75498aa8736639cf977d5009f66eb6335304 > > Yep, thanks a lot ! > As a side discussion... (opening a can of squiggly worms here) It's often bothered me that the tools don't know about the archive (which goes back a long ways and has a very consistent and structured layout). So in authoring the latest tool (bsdconfig(8)), I made sure that the archive is checked (grep archive media/ftp.subr from SVN r247280). Don't know if that was the right move, but here @ Vicor, we've been [ab]using the archive for .. over a decade? (looks at julian to chime in if he used the archive before I got here). But I for one would like to see the archive to maintain its steady growth and be available. Of course, the change to look in the archive seemed (to me at least) to be a pretty innocuous one (if the archive goes away, they're back to where they started... no working URLs). Just wondering why for so long the archive has never been checked by tools when (imho) that only serves to break old releases sooner with respect to remote-fetch of a binary release file (e.g., pkg or dist, etc.). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: Newbye question VIM problem
On Jul 23, 2013, at 5:16 PM, Fernando Apesteguía wrote: > ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-release/Latest/ Yep, thanks a lot ! ___ 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: Newbye question VIM problem
On Tue, Jul 23, 2013 at 5:09 PM, Pietro Paolini wrote: > > On Jul 23, 2013, at 4:36 PM, "Teske, Devin" > wrote: > > > env PACKAGESITE= > ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/pkg_add > -r vim-lite > > Thanks for the quick answer but I got the error: > env PACKAGESITE= > ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/pkg_add > -r vim-lite > Error: Unable to get > ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/vim-lite.tbz: > File unavailable (e.g., file not found, no access) > pkg_add: unable to fetch ' > ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/vim-lite.tbz' > by URL > One extra 's' in packages-9.0-releaseS. Try this one: ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-release/Latest/ > > ___ > 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: Newbye question VIM problem
On Jul 23, 2013, at 4:36 PM, "Teske, Devin" wrote: > env > PACKAGESITE=ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/ > pkg_add -r vim-lite Thanks for the quick answer but I got the error: env PACKAGESITE=ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/ pkg_add -r vim-lite Error: Unable to get ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/vim-lite.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/vim-lite.tbz' by URL ___ 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: Newbye question VIM problem
On Jul 23, 2013, at 7:24 AM, Pietro Paolini wrote: > Hello all, > > I have to install in a probably not latest version BSD machine but when I try > to > > pkg_add -r vim-lite > Error: Unable to get > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/Latest/vim-lite.tbz: > File unavailable (e.g., file not found, no access) > pkg_add: unable to fetch > 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/Latest/vim-lite.tbz' > by URL > > I get that error, it should be cause by the fact that my system is not so > new, am I wrong ? Any solution on that ? > Try: env PACKAGESITE=ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-9.0-releases/Latest/ pkg_add -r vim-lite NOTE: That is a single command to be written on a single-line. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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"
Newbye question VIM problem
Hello all, I have to install in a probably not latest version BSD machine but when I try to pkg_add -r vim-lite Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/Latest/vim-lite.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9.0-release/Latest/vim-lite.tbz' by URL I get that error, it should be cause by the fact that my system is not so new, am I wrong ? Any solution on that ? Thanks a lot. Pietro. ___ 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: HP ILO FreeBSD 8.3 Installation problem
Hi, USB memstick img file is solution for me. I try FreeBSD-8.3-RELEASE-amd64-memstick.img. I downloaded this img file and copy to USB, not burn it to USB. Then attach to İLO such as USB virtual image then sysinstall start, BUT I selected installation from usb install NOT CD/DVD installation. thanks for your answers. 05.07.2013, 02:00, "Damien Fleuriot" : > On 5 Jul 2013, at 00:01, "bw.mail.lists" wrote: > >> On 7/4/2013 4:59 PM, Emre Çamalan wrote: >>> Hi, >>> I'm trying to install FreeBSD with an HP ILO 4 advanced, web interface. I >>> tried to install FreeBSD 8.2, FreeBSD 8.3 and FreeBSD 8.4. I tried to use >>> acd0 and cd0 as media. I got the same result. >>> >>> ERROR: I'm trying to add freebsd8.3iso from ILO such as virtual drive not >>> from cd or dvd. >> We had a similar experience with Dell's DRAC and FreeBSD 9.1, after initial >> boot and kernel load it wasn't able to mount / from (virtual) cd. We ended >> up using an mfsBSD iso ( http://mfsbsd.vx.sk/ ), which doesn't mount from >> cd, but uses an .img loaded as memory disk. Didn't try the official bootonly >> iso or the USB image. > > Same here, boot from MFS, gpart manually, install manually, works like a > charm. > > I actually do it for all our installs now, the procedure is quite scriptable. ___ 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: HP ILO FreeBSD 8.3 Installation problem
On 5 Jul 2013, at 00:01, "bw.mail.lists" wrote: > On 7/4/2013 4:59 PM, Emre Çamalan wrote: >> Hi, >> I'm trying to install FreeBSD with an HP ILO 4 advanced, web interface. I >> tried to install FreeBSD 8.2, FreeBSD 8.3 and FreeBSD 8.4. I tried to use >> acd0 and cd0 as media. I got the same result. >> >> >> ERROR: I'm trying to add freebsd8.3iso from ILO such as virtual drive not >> from cd or dvd. > > We had a similar experience with Dell's DRAC and FreeBSD 9.1, after initial > boot and kernel load it wasn't able to mount / from (virtual) cd. We ended up > using an mfsBSD iso ( http://mfsbsd.vx.sk/ ), which doesn't mount from cd, > but uses an .img loaded as memory disk. Didn't try the official bootonly iso > or the USB image. > Same here, boot from MFS, gpart manually, install manually, works like a charm. I actually do it for all our installs now, the procedure is quite scriptable. ___ 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: HP ILO FreeBSD 8.3 Installation problem
On 7/4/2013 4:59 PM, Emre Çamalan wrote: Hi, I'm trying to install FreeBSD with an HP ILO 4 advanced, web interface. I tried to install FreeBSD 8.2, FreeBSD 8.3 and FreeBSD 8.4. I tried to use acd0 and cd0 as media. I got the same result. ERROR: I'm trying to add freebsd8.3iso from ILO such as virtual drive not from cd or dvd. We had a similar experience with Dell's DRAC and FreeBSD 9.1, after initial boot and kernel load it wasn't able to mount / from (virtual) cd. We ended up using an mfsBSD iso ( http://mfsbsd.vx.sk/ ), which doesn't mount from cd, but uses an .img loaded as memory disk. Didn't try the official bootonly iso or the USB image. In Screeshot: Error: mounting /dev/acd0 on /dist: Input/output error (5) There is no screenshot, list strips attachments. other ERROR: Unable to initialize selected media. Would you like to adjust your media configuration and try again? ___ 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"
HP ILO FreeBSD 8.3 Installation problem
Hi, I'm trying to install FreeBSD with an HP ILO 4 advanced, web interface. I tried to install FreeBSD 8.2, FreeBSD 8.3 and FreeBSD 8.4. I tried to use acd0 and cd0 as media. I got the same result. ERROR: I'm trying to add freebsd8.3iso from ILO such as virtual drive not from cd or dvd. In Screeshot: Error: mounting /dev/acd0 on /dist: Input/output error (5) other ERROR: Unable to initialize selected media. Would you like to adjust your media configuration and try again? ___ 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: ALT key problem with Virtual Box?
> On 29 Jun 2013 16:24:57 -, Scott Ballantyne wrote: > > Hi, > > > > I'm running Windows 7 under VirtualBox 4.2.6_OSE, and it seems the ALT > > key doesn't work. I need to use Photoshop, and there are a few > > operations that require a combination of holding down the ALT key and > > using a left-mouse-button click. > > > > I've googled and found reports on Linux from 2011 of this problem, but > > none of the solutions I've tried have fixed the problem. I'm using > > Gnome as my window manager, if that has any bearing on the issue. > > Maybe this is the reason. Several window managers are using > Alt + left mouse key for a windowing operation (usually moving > the window without requiring dragging it by the title bar). > Check if you can "unconfigure" this setting in Gnome's window > management preferences. Thank you. I changed the setting to use the windows key instead of ALT for window dragging, but sadly it didn't help my other difficulty. Thanks so much, though! Best, Scott ___ 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: ALT key problem with Virtual Box?
On 29 Jun 2013 16:24:57 -, Scott Ballantyne wrote: > Hi, > > I'm running Windows 7 under VirtualBox 4.2.6_OSE, and it seems the ALT > key doesn't work. I need to use Photoshop, and there are a few > operations that require a combination of holding down the ALT key and > using a left-mouse-button click. > > I've googled and found reports on Linux from 2011 of this problem, but > none of the solutions I've tried have fixed the problem. I'm using > Gnome as my window manager, if that has any bearing on the issue. Maybe this is the reason. Several window managers are using Alt + left mouse key for a windowing operation (usually moving the window without requiring dragging it by the title bar). Check if you can "unconfigure" this setting in Gnome's window management preferences. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
ALT key problem with Virtual Box?
Hi, I'm running Windows 7 under VirtualBox 4.2.6_OSE, and it seems the ALT key doesn't work. I need to use Photoshop, and there are a few operations that require a combination of holding down the ALT key and using a left-mouse-button click. I've googled and found reports on Linux from 2011 of this problem, but none of the solutions I've tried have fixed the problem. I'm using Gnome as my window manager, if that has any bearing on the issue. Anybody here found a solution, or have an idea? Thanks very much for any help. Scott -- s...@ssr.com ___ 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: Failed to allocate receive buffer problem
On Wednesday, June 12, 2013 3:06:26 am Alex Liptsin wrote: > Hi. > > I have a problem that when running a ping (or any other traffic) over IPoIB port, > Traffic fails after some time. > At destination server DMESG I see that errors: > > Jun 11 14:42:11 h-qa-033 kernel: ib1: failed to allocate receive buffer 253 > Jun 11 14:42:12 h-qa-033 kernel: ib1: failed to allocate receive buffer 254 > Jun 11 14:42:13 h-qa-033 kernel: ib1: failed to allocate receive buffer 255 > Jun 11 14:42:14 h-qa-033 kernel: ib1: failed to allocate receive buffer 0 > Jun 11 14:42:15 h-qa-033 kernel: ib1: failed to allocate receive buffer 1 > Jun 11 14:42:16 h-qa-033 kernel: ib1: failed to allocate receive buffer 2 > Jun 11 14:42:17 h-qa-033 kernel: ib1: failed to allocate receive buffer 3 > Jun 11 14:42:18 h-qa-033 kernel: ib1: failed to allocate receive buffer 4 > Jun 11 14:42:19 h-qa-033 kernel: ib1: failed to allocate receive buffer 5 > Jun 11 14:42:20 h-qa-033 kernel: ib1: failed to allocate receive buffer 6 > Jun 11 14:42:21 h-qa-033 kernel: ib1: failed to allocate receive buffer 7 > > I work with FreeBSD 9.1. > > Is it a bug or some configuration issues? Do you see memory allocation errors in netstat -m? Specifically this line: 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) If so, it may be that the IPoIB layer has an mbuf leak. The rest of netstat - m might be useful here as you can see if any of the zones are full. -- John Baldwin ___ 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: Problem in installing textproc/asciidoc
Hi,
Thank you.
>> On new 9.1 systems, textproc/asciidoc is being installed as dependency
>> to many other ports.
>>
>> But the make install fails with the error:
>>
>> installing Vim files in //usr/local/share/vim/vimfiles
> ^
> Two slashes here?
That's a copy from the make install, don't ask me why there are two slashes.
>> cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
> ^^^
>
> Is this correct? In my opinion, the correct path name
> should be /usr/local/etc/, _not_ in caps!
Ditto, but there lies the problem, the sample configuration files get
installed in /usr/local/etc/asciidoc, but then the Makefile tries to
copy the .conf.sample file into .conf and at this stage, it searches
for the files in /usr/local/ETC.
I'll write to the maintener of the post.
Best regards,
Olivier
>
>
>
>> It is consistent on all the machines.
>
> Maybe an error in the port's configuration?
>
>
>
>> I can install the 20 or so files xxx.conf.sample by hand, it's
>> tedious, but it works.
>
> That step should be completed by the "post-install" target
> in /usr/ports/textproc/asciidoc/Makefile. Is there some
> variable, like ${ETCDIR}, set wrongly?
>
>
>
>> But then, any other port that depend on asciidoc will fail to install,
>> saying that asciidoc have not been installed properly.
>
> You could forcedly register the installation of the port that
> you have "manually completed".
>
>
>
>> I could not find any answer an Google, so I ask the question here:
>> what do I do wrong? Or is there something to tweak to make asciidoc
>> install and work normally?
>
> Check if you have anything "suspicious" set in /etc/make.conf
> or in your environment that might override the logic of the
> Makefile. Check the Makefile as well (I've checked 8.6.6's
> on my 8.2 home system).
>
> Just to be sure, make clean and re-checkout the port, then
> try again.
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
> ___
> 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: Problem in installing textproc/asciidoc
On Fri, 21 Jun 2013 15:36:35 +0700 (ICT), Olivier Nicole wrote:
> Hi,
>
> On new 9.1 systems, textproc/asciidoc is being installed as dependency
> to many other ports.
>
> But the make install fails with the error:
>
> installing Vim files in //usr/local/share/vim/vimfiles
^
Two slashes here?
> cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
^^^
Is this correct? In my opinion, the correct path name
should be /usr/local/etc/, _not_ in caps!
> It is consistent on all the machines.
Maybe an error in the port's configuration?
> I can install the 20 or so files xxx.conf.sample by hand, it's
> tedious, but it works.
That step should be completed by the "post-install" target
in /usr/ports/textproc/asciidoc/Makefile. Is there some
variable, like ${ETCDIR}, set wrongly?
> But then, any other port that depend on asciidoc will fail to install,
> saying that asciidoc have not been installed properly.
You could forcedly register the installation of the port that
you have "manually completed".
> I could not find any answer an Google, so I ask the question here:
> what do I do wrong? Or is there something to tweak to make asciidoc
> install and work normally?
Check if you have anything "suspicious" set in /etc/make.conf
or in your environment that might override the logic of the
Makefile. Check the Makefile as well (I've checked 8.6.6's
on my 8.2 home system).
Just to be sure, make clean and re-checkout the port, then
try again.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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"
Problem in installing textproc/asciidoc
Hi, On new 9.1 systems, textproc/asciidoc is being installed as dependency to many other ports. But the make install fails with the error: installing Vim files in //usr/local/share/vim/vimfiles cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory *** [post-install] Error code 1 It is consistent on all the machines. I can install the 20 or so files xxx.conf.sample by hand, it's tedious, but it works. But then, any other port that depend on asciidoc will fail to install, saying that asciidoc have not been installed properly. The version of asciidoc in the ports is asciidoc-8.6.8 I could not find any answer an Google, so I ask the question here: what do I do wrong? Or is there something to tweak to make asciidoc install and work normally? Thanks in advance, Olivier ___ 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"
Failed to allocate receive buffer problem
Hi. I have a problem that when running a ping (or any other traffic) over IPoIB port, Traffic fails after some time. At destination server DMESG I see that errors: Jun 11 14:42:11 h-qa-033 kernel: ib1: failed to allocate receive buffer 253 Jun 11 14:42:12 h-qa-033 kernel: ib1: failed to allocate receive buffer 254 Jun 11 14:42:13 h-qa-033 kernel: ib1: failed to allocate receive buffer 255 Jun 11 14:42:14 h-qa-033 kernel: ib1: failed to allocate receive buffer 0 Jun 11 14:42:15 h-qa-033 kernel: ib1: failed to allocate receive buffer 1 Jun 11 14:42:16 h-qa-033 kernel: ib1: failed to allocate receive buffer 2 Jun 11 14:42:17 h-qa-033 kernel: ib1: failed to allocate receive buffer 3 Jun 11 14:42:18 h-qa-033 kernel: ib1: failed to allocate receive buffer 4 Jun 11 14:42:19 h-qa-033 kernel: ib1: failed to allocate receive buffer 5 Jun 11 14:42:20 h-qa-033 kernel: ib1: failed to allocate receive buffer 6 Jun 11 14:42:21 h-qa-033 kernel: ib1: failed to allocate receive buffer 7 I work with FreeBSD 9.1. Is it a bug or some configuration issues? Thanks. Regards, Alex Liptsin Software Quality Assurance Engineer | Mellanox Technologies Ltd. Office: +972 (74) 7236141 Mobile: +972(54) 7833986 Fax: +972(74) 7236161 Email: al...@mellanox.com<mailto:al...@mellanox.com> Mellanox, Tel-Hai Industrial Park. Building 7, M.P. Upper Galilee 12100 Israel ___ 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"
pkg-devel problem with incremental update
Installed pkg-devel 1.1.0.b3 and get the following message about incremental update whenever update is called. sudo pkg update Updating repository catalogue pkg: incremental update is not possible as repo format is inappropriate, trying full upgrade packagesite repository catalogue is up-to-date, no need to fetch fresh copy What should I do to make incremental updates possible? -- Michael Gass mg...@csbsju.edu ___ 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: route problem
Hi, Hope you have rebooted after enabling the gateway, but you can check this with " sysctl net.inet.ip.forwarding " :) So far from the server side it looks OK for me, but what are you pinging actually? How is done the configuration of the target device? This sounds like a pure routing problem, as you do not use NAT, then the devices in the 192.168.1.0/24 should know where to find your server. The basic ideas are: 1. Make 192.168.1.250 default gateway for the devices in 192.168.1.0/24 or 2. route add -net 192.168.2 gw 192.168.1.250 (syntax depends on the OS) Also check if the device you ping accepts pings - many devices denies this by default, also Windows 7/2008 and later has firewall enabled which do not permits pings. Best regards, Ivailo Tanusheff -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Pol Hallen Sent: Monday, May 20, 2013 10:59 PM To: FreeBSD Questions Subject: route problem Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U 0 6145re0 192.168.1.250 link#1 UHS 00lo0 192.168.2.0/24 link#7 U 0 2282xl0 192.168.2.250 link#7 UHS 00lo0 and gateway_enable="YES" from server1 I can ping whole lan: 192.168.1.0/24, 192.168.2.0/24 from server2 re0 - 192.168.2.52 DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.250 UGS 0 8450 fxp0 127.0.0.1 link#8 UH 00lo0 192.168.2.52 link#6 UHS 00lo0 I can ping 192.168.2.0/24 and ONLY 192.168.1.250. I need ping 192.168.1.0/24 lan but I can only see 192.168.1.250 any idea? thanks! Pol ___ 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: route problem
On 2013-05-20 5:01 pm, Pol Hallen wrote: If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843 metric 0 mtu 1500 options=8209b ether 70:71:bc:94:c3:6d inet 192.168.1.250 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::7271:bcff:fe94:c36d%re0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active xl0: flags=8843 metric 0 mtu 1500 options=80008 ether 00:60:08:6d:59:50 inet 192.168.2.250 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::260:8ff:fe6d:5950%xl0 prefixlen 64 scopeid 0x7 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21 server2 fxp0: flags=8843 metric 0 mtu 1500 options=2009 ether 00:0f:fe:b3:db:8c inet6 fe80::20f:feff:feb3:db8c%fxp0 prefixlen 64 scopeid 0x6 inet 192.168.2.52 netmask 0xff00 broadcast 192.168.2.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=8810 metric 0 mtu 1500 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21 On 'server1', what is the output of 'sysctl net.inet.ip.forwarding'? Perhaps you did not reboot after you set 'gateway_enable="YES"'? This is from my box with forwarding enabled: root@daemon ~ # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 root@daemon ~ # -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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: route problem
> If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843 metric 0 mtu 1500 options=8209b ether 70:71:bc:94:c3:6d inet 192.168.1.250 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::7271:bcff:fe94:c36d%re0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active xl0: flags=8843 metric 0 mtu 1500 options=80008 ether 00:60:08:6d:59:50 inet 192.168.2.250 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::260:8ff:fe6d:5950%xl0 prefixlen 64 scopeid 0x7 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21 server2 fxp0: flags=8843 metric 0 mtu 1500 options=2009 ether 00:0f:fe:b3:db:8c inet6 fe80::20f:feff:feb3:db8c%fxp0 prefixlen 64 scopeid 0x6 inet 192.168.2.52 netmask 0xff00 broadcast 192.168.2.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active plip0: flags=8810 metric 0 mtu 1500 nd6 options=29 lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff00 nd6 options=21 ___ 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: route problem
On 2013-05-20 4:19 pm, Pol Hallen wrote: Try: route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol Interesting. I had a similar issue I got around with a similar route addition, though I was going from a LAN PC through my server that was running openvpn out to a remotely connected client. What was the error that the route command failed with? I could have the syntax wrong (may need a "-net" in there), but I'm sure I used almost the exact same thing to solve my issue -- in my case, I ran 'route add 10.0.1.0/24 10.0.0.98', where '10.0.1.0/24' is the openvpn client network and '10.0.0.98' is the LAN interface of the openvpn server. If you don't mind could you post the output of ifconfig from both boxes? -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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: route problem
> Try: > route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol ___ 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: route problem
On 2013-05-20 3:58 pm, Pol Hallen wrote: Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U 0 6145re0 192.168.1.250 link#1 UHS 00lo0 192.168.2.0/24 link#7 U 0 2282xl0 192.168.2.250 link#7 UHS 00lo0 and gateway_enable="YES" from server1 I can ping whole lan: 192.168.1.0/24, 192.168.2.0/24 from server2 re0 - 192.168.2.52 DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.250 UGS 0 8450 fxp0 127.0.0.1 link#8 UH 00lo0 192.168.2.52 link#6 UHS 00lo0 I can ping 192.168.2.0/24 and ONLY 192.168.1.250. I need ping 192.168.1.0/24 lan but I can only see 192.168.1.250 any idea? thanks! Pol I'm pretty sure you need a route on "server2" to 192.168.1.0/24. Try: route add 192.168.1.0/24 192.168.2.250 -- Andre Goree -=-=-=-=-=- Email - an...@drenet.net Website - http://blog.drenet.net PGP key - http://www.drenet.net/0x83ADAAAB.asc -=-=-=-=-=- ___ 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"
route problem
Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U 0 6145re0 192.168.1.250 link#1 UHS 00lo0 192.168.2.0/24 link#7 U 0 2282xl0 192.168.2.250 link#7 UHS 00lo0 and gateway_enable="YES" from server1 I can ping whole lan: 192.168.1.0/24, 192.168.2.0/24 from server2 re0 - 192.168.2.52 DestinationGatewayFlagsRefs Use Netif Expire default192.168.2.250 UGS 0 8450 fxp0 127.0.0.1 link#8 UH 00lo0 192.168.2.52 link#6 UHS 00lo0 I can ping 192.168.2.0/24 and ONLY 192.168.1.250. I need ping 192.168.1.0/24 lan but I can only see 192.168.1.250 any idea? thanks! Pol ___ 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"
Subversion load problem- "svnadmin: Dump stream contains a malformed header (with no ':')"
Hi all,
I have problem loading a partial dump of one repository into a new
repository. When I try to load a partial dump of the old repository, which
paths also corrected, I've got the "Checksum mismatch" error for a file.
When I try to replace the "Text-content-md5" field of the file on the dump
with the correct one using sed command, another error regarding malformed
header is occurred("svnadmin: Dump stream contains a malformed header (with
no ':')")!
I don't know how to fix this problem and I really need this migration to be
done. I've searched a lot but couldn't find any solution.
Any suggestions or ideas?
___
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: 9.1 Postfix problem
Paul Kraus writes: > That was exactly the problem. I knew it was in the > installation configuration *somewhere*, but I just could not find > it. Thanks. > > Should I report this as a bug in the postfix port ? No need. Looks like sahil@ has already fixed it. Be well. ___ 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: 9.1 Postfix problem
On Apr 17, 2013, at 10:04 AM, Lowell Gilbert wrote: > Paul Kraus writes: > >> When building postfix under 91. I am running into an odd >> problem. I use the INST_BASE option, which seems to cause the problem >> (it worked fine with 9.0). The 'make' goes fine, but the 'make >> install' fails when trying to install the startup script to >> /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is >> disabled. I looked through the Makefile but could not suss out how >> that difference in configuration was actually causing the problem. >> >> Has anyone else run into this problem and what was the fix (or did you >> just install into /usr/local) ? > > I use /usr/local, but this seems to be a typo in the last checkin, > which changed the internal names of the port options to our brave new > naming scheme. > > If you look in the Makefile clause for installing to base, renaming the > option itself went correctly, but both halves of the '.if' now invoke > USE_RC_SUBR. That's correct for PREFIX, but for installing into base > should be USE_RCORDER instead. Lowell, That was exactly the problem. I knew it was in the installation configuration *somewhere*, but I just could not find it. Thanks. Should I report this as a bug in the postfix port ? -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ 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: Problem creating user account
Outback Dingo wrote: > On Tue, Apr 23, 2013 at 10:10 AM, Julian H. Stacey wrote: > > > "Herbert J. Skuhra" wrote: > > > Den 23.04.2013 13:17, skrev AMS_MDF_operations: > > > > LS, > > > > What is going ewrong? > > > > > > > > Problem : Creating user account > > > > > > > > -bash-2.05b$ uname -a > > > > FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD > > > > 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 > > > > r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 > > > > -bash-2.05b$ > > > > > > This version of FreeBSD is 9 years old and long EOL'ed. > > > Have you ever considered upgrading this machine? > > > > Wow ! Actually I too still run some 4 (for reasons > > I won't distract this thread with) as well as other hosts on > > 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay > > on 4, he/she should at least consider upgrading to 4.11-RELEASE for > > various bug fixes while staying on same feature set. > > > > > looking at the hostname, it simply appears to be a syslog server, so why > upgrade it, if it aint broke dont fix it > 4.X was rock solid stable and fast Yes, 4 was light on resources too, no bloated gcc make worlds thrashing on *insn*.c back then. But I still long ago upgraded all my 4.x to 4.11, just as I similarly raised sundry 6.* hosts to last minor number of 6.4. Raising to last minor numbers is generaly easy, reduces local version diversity, gets free bug fixes without the cost of problems from new features/ changes in new major numbers. Increases the chances someone out there is running the same major.minor combo, even if EOL'd. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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: Problem creating user account
On Tue, Apr 23, 2013 at 10:10 AM, Julian H. Stacey wrote: > "Herbert J. Skuhra" wrote: > > Den 23.04.2013 13:17, skrev AMS_MDF_operations: > > > LS, > > > What is going ewrong? > > > > > > Problem : Creating user account > > > > > > -bash-2.05b$ uname -a > > > FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD > > > 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 > > > r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 > > > -bash-2.05b$ > > > > This version of FreeBSD is 9 years old and long EOL'ed. > > Have you ever considered upgrading this machine? > > Wow ! Actually I too still run some 4 (for reasons > I won't distract this thread with) as well as other hosts on > 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay > on 4, he/she should at least consider upgrading to 4.11-RELEASE for > various bug fixes while staying on same feature set. > > looking at the hostname, it simply appears to be a syslog server, so why upgrade it, if it aint broke dont fix it 4.X was rock solid stable and fast > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich > http://berklix.com > Reply below not above, like a play script. Indent old text with "> ". > Send plain text. No quoted-printable, HTML, base64, > multipart/alternative. > ___ > 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: Problem creating user account
"Herbert J. Skuhra" wrote: > Den 23.04.2013 13:17, skrev AMS_MDF_operations: > > LS, > > What is going ewrong? > > > > Problem : Creating user account > > > > -bash-2.05b$ uname -a > > FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD > > 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 > > r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 > > -bash-2.05b$ > > This version of FreeBSD is 9 years old and long EOL'ed. > Have you ever considered upgrading this machine? Wow ! Actually I too still run some 4 (for reasons I won't distract this thread with) as well as other hosts on 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay on 4, he/she should at least consider upgrading to 4.11-RELEASE for various bug fixes while staying on same feature set. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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: Problem creating user account
Den 23.04.2013 13:17, skrev AMS_MDF_operations: LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ This version of FreeBSD is 9 years old and long EOL'ed. Have you ever considered upgrading this machine? -bash-2.05b$ sudo adduser Use option ``-silent'' if you don't want to see all warnings and questions. Check /etc/shells Check /etc/master.passwd Check /etc/group Usernames must match regular expression: [Usernames must match regular expression]: Enter your default shell: bash csh date no sh tcsh [bash]: Your default shell is: bash -> /usr/local/bin/bash Enter your default HOME partition: [/home]: Copy dotfiles from: /usr/share/skel no [/usr/share/skel]: Send message from file: /etc/adduser.message no [no]: Do not send message Use passwords (y/n) [y]: Ok, let's go. Don't worry about mistakes. I will give you the chance later to correct any input. Enter username [Usernames must match regular expression]: l-ong Username doesn't match the regexp /Usernames must match regular expression/ For this message I deleted an existing user, and try to create this same user. Also this failed, see below I guess someone has modified /etc/adduser.conf or the adduser script after this user has been created. Have you checked? -- Herbert ___ 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"
Problem creating user account
LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ -bash-2.05b$ sudo adduser Use option ``-silent'' if you don't want to see all warnings and questions. Check /etc/shells Check /etc/master.passwd Check /etc/group Usernames must match regular expression: [Usernames must match regular expression]: Enter your default shell: bash csh date no sh tcsh [bash]: Your default shell is: bash -> /usr/local/bin/bash Enter your default HOME partition: [/home]: Copy dotfiles from: /usr/share/skel no [/usr/share/skel]: Send message from file: /etc/adduser.message no [no]: Do not send message Use passwords (y/n) [y]: Ok, let's go. Don't worry about mistakes. I will give you the chance later to correct any input. Enter username [Usernames must match regular expression]: l-ong Username doesn't match the regexp /Usernames must match regular expression/ For this message I deleted an existing user, and try to create this same user. Also this failed, see below p-vrij:*:1010:1010:Peter Vrij:/home/p-vrij:/usr/local/bin/bash -bash-2.05b$ sudo rmuser p-vrij Password: Matching password entry: Is this the entry you wish to remove? y Remove user's home directory (/home/p-vrij)? y Updating password file, updating databases, done. Updating group file: utbackup (removing group p-vrij -- personal group is empty) done. Removing user's home directory (/home/p-vrij): done. Removing files belonging to p-vrij from /tmp: done. Removing files belonging to p-vrij from /var/tmp: done. Removing files belonging to p-vrij from /var/tmp/vi.recover: done. Enter username [Usernames must match regular expression]: p-vrij Username doesn't match the regexp /Usernames must match regular expression/ Regards, Ronald van Nigtevecht Engineer Network ll Afd. Transmission MDF Tele2 Zakelijk Postbus 22697 1100 DD Amsterdam Z-O The Netherlands T +31 (0) 20 750 2590 MDF T +31 (0) 20 750 2631 mailto:ronald.vannigteve...@tele2.com http://www.tele2zakelijk.nl Tele2 Zakelijk is a trade name of Versatel Nederland B.V. This message and any attachment are company proprietary and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person and destroy all copies of the original message and attachment. IMPORTANT NOTICE This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system. Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. ___ 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: 9.1 Postfix problem
Paul Kraus writes: > When building postfix under 91. I am running into an odd > problem. I use the INST_BASE option, which seems to cause the problem > (it worked fine with 9.0). The 'make' goes fine, but the 'make > install' fails when trying to install the startup script to > /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is > disabled. I looked through the Makefile but could not suss out how > that difference in configuration was actually causing the problem. > > Has anyone else run into this problem and what was the fix (or did you > just install into /usr/local) ? I use /usr/local, but this seems to be a typo in the last checkin, which changed the internal names of the port options to our brave new naming scheme. If you look in the Makefile clause for installing to base, renaming the option itself went correctly, but both halves of the '.if' now invoke USE_RC_SUBR. That's correct for PREFIX, but for installing into base should be USE_RCORDER instead. ___ 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: 9.1 Postfix problem
On Tue, 16 Apr 2013 17:16:20 -0400, Paul Kraus wrote: > When building postfix under 91. I am running into an odd problem. I use > the INST_BASE option, which seems to cause the problem (it worked fine > with 9.0). The 'make' goes fine, but the 'make install' fails when > trying to install the startup script to /usr/etc/rc.d instead of > /etc/rc.d. It works fine if INST-BASE is disabled. I looked through the > Makefile but could not suss out how that difference in configuration was > actually causing the problem. > > Has anyone else run into this problem and what was the fix (or did you > just install into /usr/local) ? No problems at all for me with Postfix on 9.1-RELEASE, which I just install with the defaults. My postfix is in /usr/local/sbin. Why would you want to do things differently? ___ 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"
9.1 Postfix problem
When building postfix under 91. I am running into an odd problem. I use the INST_BASE option, which seems to cause the problem (it worked fine with 9.0). The 'make' goes fine, but the 'make install' fails when trying to install the startup script to /usr/etc/rc.d instead of /etc/rc.d. It works fine if INST-BASE is disabled. I looked through the Makefile but could not suss out how that difference in configuration was actually causing the problem. Has anyone else run into this problem and what was the fix (or did you just install into /usr/local) ? -- Paul Kraus Deputy Technical Director, LoneStarCon 3 Sound Coordinator, Schenectady Light Opera Company ___ 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: Problem making software distros
"Don O'Neil" writes: > I've got an older FreeBSD 6.1 install that will no longer allow me to build > any software distributions. Any time I try to do a 'configure', the > configure seems to run fine, then I get a "config.status: error: cannot find > input file:". This has happened on several packages from several different > sources. > > > > Any ideas as to what could be causing this? Is one of my binaries make > corrupted possibly? Unlikely to be a corrupted binary. Much more likely to be that configure scripts are trying to use a file as input for their testing, and not finding it. Tracking down *what* file they want shouldn't be too much effort. If it turns out to be, you can always update to something recent enough to be supported, but that's probably unnecessary for this problem. ___ 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"
Problem making software distros
I've got an older FreeBSD 6.1 install that will no longer allow me to build any software distributions. Any time I try to do a 'configure', the configure seems to run fine, then I get a "config.status: error: cannot find input file:". This has happened on several packages from several different sources. Any ideas as to what could be causing this? Is one of my binaries make corrupted possibly? 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"
Re: OT: posix sh problem
On Thu, 04 Apr 2013 11:16:11 -0500, Teske, Devin wrote: Here's what I suggest (the following works for me -- lists all my pools and shows healthy): Fantastic! I'd have never considered wrapping the entire thing into STRING="$STRING$()". I can't tell you how much I appreciate your assistance with making this functional. Thank you!! ___ 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: OT: posix sh problem
On Apr 4, 2013, at 8:11 AM, Mark Felder wrote:
> Sorry, my email client did something weird with collapsing and I didn't see
> you mention that it appeared to be working for you.
>
> On Thu, 04 Apr 2013 08:54:30 -0500, Teske, Devin
> wrote:
>
>> The only things I saw that needed changing to go from ksh to /bin/sh were:
>> if [ … == … ]; then
>> Needs to be
>> if [ … = … ]; then
>> And optionally, a style nit would be to convert back-tick pairs into
>> nestable $(…) syntax. For example, change:
>> cap=`…`
>> to instead:
>> cap=$(…)
>> Oh and of course, the HTML should go away since you're making a command-line
>> tool and not a BB/Hobbit/Xymon module.
>
> I actually will be using this with Xymon at work. I did fix the == and style
> nit when I went over this script I'm still having a problem.
No worries…
> When I started debugging this last night $STRING led me to believe the pipe
> into read wasn't working right. At the bottom of the script I added echo in
> front of the "$BB $BBDISP" line.
Ok, going back to the original script, I see the error.
Yes… you're right, you can't modify a string from the rvalue of a pipe; simply
put.
[snip]
> Do you see what I mean now? :(
Yes, I do.
Here's what I suggest (the following works for me -- lists all my pools and
shows healthy):
--- bar.orig2013-04-04 09:05:27.0 -0700
+++ bar 2013-04-04 09:14:37.0 -0700
@@ -1,4 +1,5 @@
-#!/bin/ksh
+#!/bin/sh
+BB=echo MACHINE=$(hostname)
# Revision History:
# 1. Mike Rowell , original
# 2. Uwe Kirbach
@@ -22,19 +23,20 @@ STRING="<
# mypool 33.8G 84.5K 33.7G 0% ONLINE -
# bash-3.00#
-/usr/sbin/zpool list -H | while read name size used avail cap health altroot
+STRING="$STRING$(
+/sbin/zpool list -H | while read name size used avail cap health altroot
do
LINE_COLOR="green"
- if [ "${health}" == "ONLINE" ]; then
+ if [ "${health}" = "ONLINE" ]; then
HEALTH_COLOR="green"
- elif [ "${health}" == "DEGRADED" ]; then
+ elif [ "${health}" = "DEGRADED" ]; then
HEALTH_COLOR="yellow"
- elif [ "${health}" == "FAULTED" ]; then
+ elif [ "${health}" = "FAULTED" ]; then
HEALTH_COLOR="red"
fi
- cap=`echo ${cap} | cut -d% -f1`
+ cap=$(echo ${cap} | cut -d% -f1)
if [ ${cap} -lt $DISKYELL ]; then
CAP_COLOR="green"
elif [ ${cap} -gt $DISKYELL ]; then
@@ -43,7 +45,7 @@ do
CAP_COLOR="red"
fi
- if [ "$HEALTH_COLOR" == "red" -o "$HEALTH_COLOR" == "yellow" -o "$CAP_COLOR"
== "red" -o "$CAP_COLOR" == "yellow" ]; then
+ if [ "$HEALTH_COLOR" = "red" -o "$HEALTH_COLOR" = "yellow" -o "$CAP_COLOR" =
"red" -o "$CAP_COLOR" = "yellow" ]; then
DISPCOLOR=$COLOR
LINE_COLOR=$COLOR
fi
@@ -58,13 +60,14 @@ do
yellow) FIRST_LINE_CAP="nearly full" ;;
esac
- STRING="$STRING
&${LINE_COLOR}${name}${health}${cap}"
+ echo
"&${LINE_COLOR}${name}${health}${cap}"
done
+)"
# What: accumulate the bb message strings.
STRING="$STRING "
-STRING="$STRING`/usr/sbin/zpool status -xv`"
+STRING="$STRING$(/sbin/zpool status -xv)"
FIRST_LINE="zfs - health: $FIRST_LINE_HEALTH - capacity: $FIRST_LINE_CAP"
# What: Sent out the final bb message to hobbit server.
-$BB $BBDISP "status $MACHINE.$TEST $DISPCOLOR `date` $FIRST_LINE $STRING"
+$BB $BBDISP "status $MACHINE.$TEST $DISPCOLOR $(date) $FIRST_LINE $STRING"
--
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
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: OT: posix sh problem
Sorry, my email client did something weird with collapsing and I didn't see you mention that it appeared to be working for you. On Thu, 04 Apr 2013 08:54:30 -0500, Teske, Devin wrote: The only things I saw that needed changing to go from ksh to /bin/sh were: if [ … == … ]; then Needs to be if [ … = … ]; then And optionally, a style nit would be to convert back-tick pairs into nestable $(…) syntax. For example, change: cap=`…` to instead: cap=$(…) Oh and of course, the HTML should go away since you're making a command-line tool and not a BB/Hobbit/Xymon module. I actually will be using this with Xymon at work. I did fix the == and style nit when I went over this script I'm still having a problem. When I started debugging this last night $STRING led me to believe the pipe into read wasn't working right. At the bottom of the script I added echo in front of the "$BB $BBDISP" line. My output is this: # sh zfs_xymon.sh status .zfs green Thu Apr 4 09:59:36 CDT 2013 zfs - health: okay - capacity: okay Zpool NameStatusCapacity all pools are healthy Where are the other parts of the table showing each zpool? Those are just the headers. If you sh -x you'll see it flow like this: + read name size used avail cap depup health altroot + STRING='Zpool NameStatusCapacity ' + /sbin/zpool status -xv It's like everything between do ... done never happened? If you put echo in front of line 60 you DO get output: # sh zfs_xymon.sh STRING=Zpool NameStatusCapacity &greentankONLINE48 status .zfs green Thu Apr 4 10:07:30 CDT 2013 zfs - health: okay - capacity: okay Zpool NameStatusCapacity all pools are healthy But as you can see, everything in that do ... done is disappearing. According to Rich's Posix sh tricks site it explains that the things to the right of that pipe are completed in a subprocess. The updates it makes to STRING never make it out so it can be used in the rest of the script. Do you see what I mean now? :( ___ 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: OT: posix sh problem
Oh, and just to cover all bases… If you suspect you have sub-shells in the loop, use "export" to export the vars so that the sub-shells get the vars in the loop. -- Devin On Apr 4, 2013, at 8:04 AM, Teske, Devin wrote: > > On Apr 4, 2013, at 7:42 AM, Mark Felder wrote: > >> On Thu, 04 Apr 2013 08:54:30 -0500, Teske, Devin >> wrote: >> >>> Wait, you can't? Then I've been doing something wrong all these years… >>> #!/bin/sh >>> printf "line1\nline2\n" | while read line >>> do >>> echo "line=[$line]" >>> done >> >> You sort-of can, but it's not portable at all. As detailed here: >> http://www.etalabs.net/sh_tricks.html >> >>>> One common pitfall is trying to read output piped from commands, such as: >>>> foo | IFS= read var >>>> POSIX allows any or all commands in a pipeline to be run in subshells, > > And for most purposes that's fine. Read-on… > > >>>> and which command (if any) runs in the main shell varies greatly >>>> betweenimplementations > > … that is only if you truly need the variables to be read into the main > shell. This is most always not what you want. > > The page you linked about doesn't talk about the special case of "while", in > example: > > foo | IFS= while read var > > On the back-end nothing changes (the same caveat applies -- variables set on > the right side of the pipe may not be available to the main shell; as-per the > quoted text). However, the high-level task changes from: > > I want to read some text from a pipe into some variables > > to instead: > > I want to read some text from a pipe and process it word-by-word (in > your case) and act on the words in a loop > > So in other words… the only reason for wanting the variables in the main > shell is if you want to act on the last set of variables for the last line > after the loop has run (and presumably already processed the last line). This > is what I am saying anyone will rarely ever want. In other words, once the > loop (potentially running in a sub-shell) has completed, you likely don't > care about the variable contents and are willing to throw them away anyhow. > > > >>>> — in particular Bash and ksh differ here. The standardidiom for overcoming >>>> this problem is to use a here document: >>>> >>>> IFS= read var << EOF >>>> $(foo) >>>> EOF >> > > But you're not processing a single line; you're processing the entire input > at-once and performing an action (writing to the screen) that also doesn't > care whether it's in a sub-shell or not. > > SO… > > I say rock-on with the original syntax. It's portable. You don't need those > vars when the loop ends. > >> >> I was having problems with the variables magically becoming empty, >> remembered I had Rich's site bookmarked, checked to see if it mentioned and >> it was. I'll admit there's a high chance that due to lack of sleep user >> error was the culprit. > > I'm interested in why you need the variables after the loop has completed. > Put your code in the loop where the variables are defined and have values. > -- > Devin > > _ > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; > and (iii) notify the sender immediately. In addition, please be aware that > any message addressed to our domain is subject to archiving and review by > persons other than the intended recipient. Thank you. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: OT: posix sh problem
On Apr 4, 2013, at 7:42 AM, Mark Felder wrote: > On Thu, 04 Apr 2013 08:54:30 -0500, Teske, Devin > wrote: > >> Wait, you can't? Then I've been doing something wrong all these years… >> #!/bin/sh >> printf "line1\nline2\n" | while read line >> do >> echo "line=[$line]" >> done > > You sort-of can, but it's not portable at all. As detailed here: > http://www.etalabs.net/sh_tricks.html > >>> One common pitfall is trying to read output piped from commands, such as: >>> foo | IFS= read var >>> POSIX allows any or all commands in a pipeline to be run in subshells, And for most purposes that's fine. Read-on… >>> and which command (if any) runs in the main shell varies greatly >>> betweenimplementations … that is only if you truly need the variables to be read into the main shell. This is most always not what you want. The page you linked about doesn't talk about the special case of "while", in example: foo | IFS= while read var On the back-end nothing changes (the same caveat applies -- variables set on the right side of the pipe may not be available to the main shell; as-per the quoted text). However, the high-level task changes from: I want to read some text from a pipe into some variables to instead: I want to read some text from a pipe and process it word-by-word (in your case) and act on the words in a loop So in other words… the only reason for wanting the variables in the main shell is if you want to act on the last set of variables for the last line after the loop has run (and presumably already processed the last line). This is what I am saying anyone will rarely ever want. In other words, once the loop (potentially running in a sub-shell) has completed, you likely don't care about the variable contents and are willing to throw them away anyhow. >>> — in particular Bash and ksh differ here. The standardidiom for overcoming >>> this problem is to use a here document: >>> >>> IFS= read var << EOF >>> $(foo) >>> EOF > But you're not processing a single line; you're processing the entire input at-once and performing an action (writing to the screen) that also doesn't care whether it's in a sub-shell or not. SO… I say rock-on with the original syntax. It's portable. You don't need those vars when the loop ends. > > I was having problems with the variables magically becoming empty, remembered > I had Rich's site bookmarked, checked to see if it mentioned and it was. I'll > admit there's a high chance that due to lack of sleep user error was the > culprit. I'm interested in why you need the variables after the loop has completed. Put your code in the loop where the variables are defined and have values. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: OT: posix sh problem
On Thu, 04 Apr 2013 08:54:30 -0500, Teske, Devin wrote: Wait, you can't? Then I've been doing something wrong all these years… #!/bin/sh printf "line1\nline2\n" | while read line do echo "line=[$line]" done You sort-of can, but it's not portable at all. As detailed here: http://www.etalabs.net/sh_tricks.html One common pitfall is trying to read output piped from commands, such as: foo | IFS= read var POSIX allows any or all commands in a pipeline to be run in subshells, and which command (if any) runs in the main shell varies greatly between implementations — in particular Bash and ksh differ here. The standard idiom for overcoming this problem is to use a here document: IFS= read var << EOF $(foo) EOF I was having problems with the variables magically becoming empty, remembered I had Rich's site bookmarked, checked to see if it mentioned and it was. I'll admit there's a high chance that due to lack of sleep user error was the culprit. ___ 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: OT: posix sh problem
On Apr 4, 2013, at 5:32 AM, Mark Felder wrote: > Hi all, > > Hopefully someone here is much more clever than I am. I've run out of ideas > on how to cleanly convert this chunk of ksh to posix sh. /me takes the challenge (and shame on some of the current responses; this is trivial in sh and there's actually nothing wrong with the OPs code -- it works) > This is from a BB/Hobbit/Xymon monitoring script for ZFS. I'd really like to > have this working cleanly on FreeBSD without requiring any funky shells or > using any temporary files. > Cool! After I help you fix whatever the issue is, I'd be interested in this a little more. ZFS monitoring would be nice. > The following is supposed to be able to loop through the output of multiple > zpools reading one line at a time and each line item is set as a variable: > > > /sbin/zpool list -H | while read name size used avail cap dedup health altroot > do > # do interesting things here > done > > Unfortunately you can't pipe through read in posix sh. Wait, you can't? Then I've been doing something wrong all these years… #!/bin/sh printf "line1\nline2\n" | while read line do echo "line=[$line]" done === dte...@scribe9.vicor.com ~ $ sh bar line=[line1] line=[line2] === Just a side note, on my "zpool list -H" on my 8.1-R system doesn't provide the "dedup" column, so your mileage may vary (you may have to adjust the script to account for that on systems like mine). Aside from that, I took your script as-is, copy/paste and it worked fine on 8.1-RELEASE-p6: dte...@oos0a.lbxrich.vicor.com ~ $ cat bar #!/bin/sh /sbin/zpool list -H | while read name size used avail cap dedup health altroot do echo $name done dte...@oos0a.lbxrich.vicor.com ~ $ sh bar NEC1-RAID6-ARRAY1 NEC1-RAID6-ARRAY2 NEC1-RAID6-ARRAY3 > You also can't use process substitution: while read var1 var1 < <(/sbin/zpool > list -H) > I'll admit that one's unsupported. > Any ideas are greatly appreciated. I know there's a python-based script > floating on github but I cant guarantee every server will have python on it… > Stick to /bin/sh if you can (like you say, portability and potability in using base utilities). > Source of script is here: > http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOWTO#Hobbit_Client_and_ZFS_monitoring The only things I saw that needed changing to go from ksh to /bin/sh were: if [ … == … ]; then Needs to be if [ … = … ]; then And optionally, a style nit would be to convert back-tick pairs into nestable $(…) syntax. For example, change: cap=`…` to instead: cap=$(…) Oh and of course, the HTML should go away since you're making a command-line tool and not a BB/Hobbit/Xymon module. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: OT: posix sh problem
On 4/4/2013 3:32 μμ, Mark Felder wrote: Hi all, Hopefully someone here is much more clever than I am. I've run out of ideas on how to cleanly convert this chunk of ksh to posix sh. This is from a BB/Hobbit/Xymon monitoring script for ZFS. I'd really like to have this working cleanly on FreeBSD without requiring any funky shells or using any temporary files. The following is supposed to be able to loop through the output of multiple zpools reading one line at a time and each line item is set as a variable: /sbin/zpool list -H | while read name size used avail cap dedup health altroot do # do interesting things here done Unfortunately you can't pipe through read in posix sh. I am not sure about posix compliance but I haven't seen a bourne-like shell not supporting the "prog | while read a b c ..." syntax. FreeBSD's /bin/sh supports this. Did you mean something else, did I misunderstand your question? Nikos ___ 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: OT: posix sh problem
fail on an unwritable filesystem. ...By which I mean you can't create new files because your disk is completely full or you're booting from a ramdisk that's messed up, etc. __ it has a certain smooth-brained appeal ___ 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: OT: posix sh problem
On Thu, 04 Apr 2013 07:47:09 -0500, Quartz wrote: I'd really like to have this working cleanly on FreeBSD without requiring any funky shells Define "funky shell". Does it have to be straight up plain sh? Can it use csh or tcsh syntax? Does bash count as 'funky'? Any shells not in the FreeBSD base system, basically. I don't want this script to stop working because someone somehow broke bash or zsh and nobody noticed because nobody ever uses it. or using any temporary files. Do you mean "manually created temp files"? because some of the different ways of doing process substitution and redirection will automatically create temp files for you in the background and fail on an unwritable filesystem. Yes, I mean manually created temp files. It looks pretty ugly to > /tmp/foo and read from it a line later :) ___ 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: OT: posix sh problem
I'd really like to have this working cleanly on FreeBSD without requiring any funky shells Define "funky shell". Does it have to be straight up plain sh? Can it use csh or tcsh syntax? Does bash count as 'funky'? or using any temporary files. Do you mean "manually created temp files"? because some of the different ways of doing process substitution and redirection will automatically create temp files for you in the background and fail on an unwritable filesystem. __ it has a certain smooth-brained appeal ___ 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"
OT: posix sh problem
Hi all, Hopefully someone here is much more clever than I am. I've run out of ideas on how to cleanly convert this chunk of ksh to posix sh. This is from a BB/Hobbit/Xymon monitoring script for ZFS. I'd really like to have this working cleanly on FreeBSD without requiring any funky shells or using any temporary files. The following is supposed to be able to loop through the output of multiple zpools reading one line at a time and each line item is set as a variable: /sbin/zpool list -H | while read name size used avail cap dedup health altroot do # do interesting things here done Unfortunately you can't pipe through read in posix sh. You also can't use process substitution: while read var1 var1 < <(/sbin/zpool list -H) Any ideas are greatly appreciated. I know there's a python-based script floating on github but I cant guarantee every server will have python on it... Source of script is here: http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Other_Docs/HOWTO#Hobbit_Client_and_ZFS_monitoring ___ 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: gettext problem in FreeBSD 8.3 system hosed
On Tue, Mar 26, 2013 at 06:53:11AM -0500, Antonio Olivares typed: > Dear Sir, > > > > > As bapt@ hints: try rebuilding binutils without NLS. > > > > -- > > -- > > I have binutils installed without NLS. I ran make deinstall reinstall > inside /usr/ports/devel/binutils/ and it deinstalls and it fails to > reinstall because it depends on gettext :( Now I guess I am really in > trouble. Don't do make deinstall reinstall! Run make deinstall, than make config, disable the NLS option and then run make install. Ruben ___ 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: Still a problem with 'pkg check -Ba'
On 26/03/2013 21:36, Matthew Seaman wrote: > On 26/03/2013 19:18, Walter Hurry wrote: >> On Tue, 26 Mar 2013 19:13:04 +, Walter Hurry wrote: >> >>> I hope Matthew Seaman sees this: >>> >>> All the files are of course present and correct in /usr/local/lib/ >>> virtualbox >> >> >> >> Should have mentioned: This is pkg-1.0.9_2 > > I see it. There haven't been any changes to the shlib code in pkg-1.0.x > -- however, things have been improved in pkg-1.1. Still not perfect though: > > worm:...matthew/src/pkgng:# pkg check -B virtualbox-ose > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - > shared library VBoxRT.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - > shared library VBoxXPCOM.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - > shared library VBoxRT.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - > shared library VBoxXPCOM.so not found > pkg: (virtualbox-ose-4.2.6) > /usr/local/lib/virtualbox/VBoxExtPackHelperApp - shared library > VBoxRT.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - > shared library VBoxDDU.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - > shared library VBoxRT.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - > shared library VBoxXPCOM.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared > library VBoxDDU.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared > library VBoxRT.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared > library VBoxXPCOM.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - > shared library VBoxXPCOM.so not found > pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - > shared library VBoxRT.so not found > > Still working on it... Actually, fixed that problem and just pushed the commit to master... worm:...matthew/src/pkgng:# pkg check -vB virtualbox-ose Reanalyzing files for shlibs: virtualbox-ose worm:...matthew/src/pkgng:# pkg info -B virtualbox-ose virtualbox-ose-4.2.6: libxml2.so.5 libvncserver.so.0 libssl.so.8 libpng15.so.15 libiconv.so.3 libcurl.so.6 libcrypto.so.8 VBoxXPCOM.so VBoxVMM.so VBoxRT.so VBoxREM.so VBoxDDU.so VBoxDD2.so Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: Still a problem with 'pkg check -Ba'
On 26/03/2013 19:18, Walter Hurry wrote: > On Tue, 26 Mar 2013 19:13:04 +, Walter Hurry wrote: > >> I hope Matthew Seaman sees this: >> >> All the files are of course present and correct in /usr/local/lib/ >> virtualbox > > > > Should have mentioned: This is pkg-1.0.9_2 I see it. There haven't been any changes to the shlib code in pkg-1.0.x -- however, things have been improved in pkg-1.1. Still not perfect though: worm:...matthew/src/pkgng:# pkg check -B virtualbox-ose pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxExtPackHelperApp - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - shared library VBoxRT.so not found Still working on it... Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: Still a problem with 'pkg check -Ba'
On Tue, 26 Mar 2013 19:13:04 +, Walter Hurry wrote: > I hope Matthew Seaman sees this: > > All the files are of course present and correct in /usr/local/lib/ > virtualbox Should have mentioned: This is pkg-1.0.9_2 ___ 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"
Still a problem with 'pkg check -Ba'
I hope Matthew Seaman sees this: All the files are of course present and correct in /usr/local/lib/ virtualbox # pkg check -Ba pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxAutostart - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxAutostart - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxBalloonCtrl - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxManage - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxManage - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxManage - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxSVC - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxSVC - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxSVC - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxTestOGL - shared library VBoxOGLhostcrutil.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxTestOGL - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxTestOGL - shared library VBoxREM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxTestOGL - shared library VBoxVMM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxTestOGL - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxXPCOMIPCD - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/bin/VBoxXPCOMIPCD - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxAutostart - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxBalloonCtrl - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/ VBoxExtPackHelperApp - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxManage - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxDDU.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxSVC - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxTestOGL - shared library VBoxOGLhostcrutil.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxTestOGL - shared library VBoxRT.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxTestOGL - shared library VBoxREM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxTestOGL - shared library VBoxVMM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxTestOGL - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - shared library VBoxXPCOM.so not found pkg: (virtualbox-ose-4.2.6) /usr/local/lib/virtualbox/VBoxXPCOMIPCD - shared library VBoxRT.so not found # ___ 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: gettext problem in FreeBSD 8.3 system hosed
Dear Sir, > > As bapt@ hints: try rebuilding binutils without NLS. > > -- > -- I have binutils installed without NLS. I ran make deinstall reinstall inside /usr/ports/devel/binutils/ and it deinstalls and it fails to reinstall because it depends on gettext :( Now I guess I am really in trouble. I am not using pkgng just ports. On three machines I am successfull, two 9.1-RELEASE-p1 and one 8.3-RELEASE, but this 9.1-RELEASE box I could not build some ports, I tried deinstall/reinstall options, and now I guess I am in a major problem, unless gettext starts to build soon, I uninstalled glib20, and tried reinstall it fails with gettext. There is a new version out, but it has not made it to ports :( I'll hang in there for a little while longer, but if it comes down to deleting and reinstalling all ports, I may do just that. Best Regards && Thanks for the suggestions and advice provided. 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"
