Re: gnu/31772: [patch] New option in dialog(1)
Synopsis: [patch] New option in dialog(1) State-Changed-From-To: open-closed State-Changed-By: eadler State-Changed-When: Thu Feb 24 08:02:34 EST 2011 State-Changed-Why: Binutils has been updated http://www.freebsd.org/cgi/query-pr.cgi?pr=31772 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/117756: dialog_checklist() does not honour DisplayX/DisplayY
Synopsis: dialog_checklist() does not honour DisplayX/DisplayY State-Changed-From-To: open-feedback State-Changed-By: eadler State-Changed-When: Thu Feb 24 08:09:19 EST 2011 State-Changed-Why: Is this still an issue now that dialog has been updated? http://www.freebsd.org/cgi/query-pr.cgi?pr=117756 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/139239: ld(1) /usr/bin/ld: Please report this bug.
Synopsis: ld(1) /usr/bin/ld: Please report this bug. State-Changed-From-To: open-feedback State-Changed-By: eadler State-Changed-When: Thu Feb 24 08:12:26 EST 2011 State-Changed-Why: Is this still an issue with the recent binutils update? http://www.freebsd.org/cgi/query-pr.cgi?pr=139239 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/26362: cvs server doesn't honour the global --allow-root
Synopsis: cvs server doesn't honour the global --allow-root State-Changed-From-To: analyzed-suspended State-Changed-By: eadler State-Changed-When: Thu Feb 24 08:13:50 EST 2011 State-Changed-Why: Suspended awaiting patches and/or upstream fix http://www.freebsd.org/cgi/query-pr.cgi?pr=26362 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/148609: [libdialog] [patch] printing to a checklist window on the first item from the selected callback prints behind the window.
Synopsis: [libdialog] [patch] printing to a checklist window on the first item from the selected callback prints behind the window. State-Changed-From-To: open-patched State-Changed-By: brucec State-Changed-When: Thu Feb 24 13:28:33 UTC 2011 State-Changed-Why: MFC reminder. Responsible-Changed-From-To: freebsd-bugs-imp Responsible-Changed-By: brucec Responsible-Changed-When: Thu Feb 24 13:28:33 UTC 2011 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=148609 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
kern/155004: kernel panic in bce0 driver
Number: 155004
Category: kern
Synopsis: kernel panic in bce0 driver
Confidential: no
Severity: serious
Priority: low
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Thu Feb 24 14:10:07 UTC 2011
Closed-Date:
Last-Modified:
Originator: Konstantin
Release:7.3
Organization:
Kasperksy Lab
Environment:
FreeBSD 7.3-RELEASE-p2 FreeBSD 7.3-RELEASE-p2 #0: Fri Sep 10 16:59:11 MSD 2010
root@/usr/obj/usr/src/sys/GENERIC amd64
Description:
We have some IBM System x3550 servers with Broadcom NetXtreme II BCM5708 NICs.
Sometimes kernel panic occurs on them under high load (about 900-950Mbs and
70-90 kpps).
# kgdb kernel.debug /var/crash/vmcore.6
Unread portion of the kernel message buffer:
118Feb 22 15:39:51 d-ca1 syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...1 0 done
All buffers synced.
Uptime: 29m2s
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x10
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x802bed2a
stack pointer = 0x10:0xff80001b7b70
frame pointer = 0x10:0x0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 30 (irq257: bce1)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 29m2s
Physical memory: 4082 MB
Dumping 1385 MB: 1370 1354 1338 1322 1306 1290 1274 1258 1242 1226 1210 1194
1178 1162 1146 1130 1114 1098 1082 1066 1050 1034 1018 1002 986 970 954 938 922
906 890 874 858 842 826 810 794 778 762 746 730 714 698 682 666 650 634 618 602
586 570 554 538 522 506 490 474 458 442 426 410 394 378 362 346 330 314 298 282
266 250 234 218 202 186 170 154 138 122 106 90 74 58 42 26 10
(kgdb) where
#0 doadump () at pcpu.h:195
#1 0x0004 in ?? ()
#2 0x805285f9 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418
#3 0x80528a02 in panic (fmt=0x104 Address 0x104 out of bounds) at
/usr/src/sys/kern/kern_shutdown.c:574
#4 0x807ec813 in trap_fatal (frame=0xff000158aae0, eva=Variable
eva is not available.
) at /usr/src/sys/amd64/amd64/trap.c:777
#5 0x807ecbe5 in trap_pfault (frame=0xff80001b7ac0, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:693
#6 0x807ed50c in trap (frame=0xff80001b7ac0) at
/usr/src/sys/amd64/amd64/trap.c:464
#7 0x807d614e in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:218
#8 0x802bed2a in bce_intr (xsc=Variable xsc is not available.
) at /usr/src/sys/dev/bce/if_bce.c:5771
#9 0x80506a92 in ithread_loop (arg=0xff000158ea60) at
/usr/src/sys/kern/kern_intr.c:1181
#10 0x805034e3 in fork_exit (callout=0x80506930 ithread_loop,
arg=0xff000158ea60, frame=0xff80001b7c80)
at /usr/src/sys/kern/kern_fork.c:811
#11 0x807d652e in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:554
#12 0x in ?? ()
#13 0x in ?? ()
#14 0x0001 in ?? ()
#15 0x in ?? ()
#16 0x in ?? ()
#17 0x in ?? ()
#18 0x in ?? ()
#19 0x in ?? ()
#20 0x in ?? ()
#21 0x in ?? ()
---Type return to continue, or q return to quit---
(kgdb) up 8
#8 0x802bed2a in bce_intr (xsc=Variable xsc is not available.
) at /usr/src/sys/dev/bce/if_bce.c:5771
5771sc-rx_mbuf_ptr[sw_rx_cons_idx] = NULL;
(kgdb) p *sc
$2 = {bce_ifp = 0xff0001591800, bce_dev = 0xff0001575100, bce_unit = 1
'\001', bce_res_mem = 0xff0001688c00, bce_ifmedia = {ifm_mask = 0,
ifm_media = 0, ifm_cur = 0x0, ifm_list = {lh_first = 0x0}, ifm_change = 0,
ifm_status = 0}, bce_btag = 1, bce_bhandle = 18446742977654030336,
bce_vhandle = 18446742977654030336, bce_res_irq = 0xff0001688580, bce_mtx
= {lock_object = {lo_name = 0xff00015856d0 bce1,
lo_type = 0x80856f26 network driver, lo_flags = 16973824,
lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}},
mtx_lock = 18446742974220511970, mtx_recurse = 0}, bce_intr =
0x802bea80 bce_intr, bce_intrhand = 0xff0001688b00, bce_irq_rid =
1,
bce_msi_count = 1, bce_chipid = 1460146208, bce_flags = 97, bce_cap_flags =
9, bce_phy_flags = 2, bce_shared_hw_cfg = 325, bce_port_hw_cfg = 0,
max_bus_addr = 1099511627775, bus_speed_mhz = 133, link_width = 0, link_speed
= 0, bce_flash_info = 0x80a64330, bce_flash_size = 270336,
bin/155006: named(8): /etc/rc.d/named might set wrong pid file
Number: 155006
Category: bin
Synopsis: named(8): /etc/rc.d/named might set wrong pid file
Confidential: no
Severity: non-critical
Priority: low
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Thu Feb 24 16:00:19 UTC 2011
Closed-Date:
Last-Modified:
Originator: Helmut Schneider
Release:8.1-RELEASE-p2
Organization:
Environment:
Description:
According to man named 8 the default pid file is /var/run/named/named.pid.
/etc/rc.d/named says:
pidfile=${named_pidfile:-/var/run/named/pid}
There might be a reason for it but if not /etc/rc.d/named should state:
pidfile=${named_pidfile:-/var/run/named/${name}.pid}
How-To-Repeat:
Fix:
--- /etc/rc.d/named.org 2011-02-24 16:43:08.0 +0100
+++ /etc/rc.d/named 2011-02-24 16:43:37.0 +0100
@@ -279,7 +279,7 @@
#
required_dirs=$named_chrootdir # if it is set, it must exist
-pidfile=${named_pidfile:-/var/run/named/pid}
+pidfile=${named_pidfile:-/var/run/named/${name}.pid}
named_confdir=${named_chrootdir}${named_conf%/*}
run_rc_command $1
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
kern/155010: ntfs-3g via iscsi using msk driver cause kernel panic
Number: 155010 Category: kern Synopsis: ntfs-3g via iscsi using msk driver cause kernel panic Confidential: no Severity: serious Priority: low Responsible:freebsd-bugs State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Thu Feb 24 19:20:07 UTC 2011 Closed-Date: Last-Modified: Originator: Bogdanov Roman Release:7.2-RELEASE Organization: JSC TEL Company Environment: HomeBSD 7.2-RELEASE-p8 FreeBSD 7.2-RELEASE-p8 #7: Wed Feb 23 23:52:04 MSK 2011 Description: msk0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500 ntfs-3g -o noatime,nosuid,nomand,users,noauto /dev/da0p1 /mnt = kernel panic (panic: vm_fault: fault on nofault entry...) via another network adapter: rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 all is ok! mounts without any errors. all seems to be okay. Same result with 7.4-PRERELEASE (22 Feb 2011) and fixed(watchdog) msk driver, ported back to 7.2 /dev/da0p1 - virtual iscsi device with ntfs filesystem. pciconf -lv: mskc0@pci0:1:0:0: class=0x02 card=0x81f81043 chip=0x436411ab rev=0x12 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8056 Yukon PCI-E Gigabit Ethernet Controller' class = network subclass = ethernet fusefs-kmod-0.3.9.p1.20080208_7 = up-to-date with port fusefs-libs-2.7.4 = up-to-date with port fusefs-ntfs-2010.10.2 = up-to-date with port How-To-Repeat: attach iscsi device with ntfs filesystem and mount it with ntfs-3g via msk network adapter Fix: change network adapter Release-Note: Audit-Trail: Unformatted: ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Installing FreeBSD on Dell-mini 9
Hello: I'm working on a task of installing FreeBSD 4.8 or 4.9 on a Dell-mini computer. I'm getting an error at my CD boot of: *BTX halted* OR, * ** * int=0005 err= elf=000300206 eip=00c1 .etc.. ss:esp=ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff BTX halted * ** * I've tried version 4.9 miniftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ISO-IMAGES/4.9/, and I got the same error at boot.. P.S: I'm sure the CD is perfect; as I used it to install a FreeBSD of a VM using VMware http://www.VMware.com and it was successful!!! My Source: FreeBSD Old Releasesftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/ISO-IMAGES/ Thanks in advance, Khalid.. -- Khalid Abd El-Halim Rehan Redhat http://www.redhat.com/ RHCT Certified. System Administration, KTAIT. --- Visit : http://english.islamway.com/ http://www.openoffice.org/ For family safe on-line: http://www.opendns.com/ ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: Installing FreeBSD on Dell-mini 9
On Thu, 24 Feb 2011 14:24:04 -0500, Khalid Rehan kre...@ktait.com wrote: Hello: I'm working on a task of installing FreeBSD 4.8 or 4.9 on a Dell-mini computer. Is there any specific reason you *need* to install this release? You can try to use the current version (8.1, or 8.2 when available) which should run fine even on systems with lower specs. Just try to install with the 8.1 first disc. P.S: I'm sure the CD is perfect; as I used it to install a FreeBSD of a VM using VMware http://www.VMware.com and it was successful!!! This should indicate that there seems to be something at least problematic (wrong) with the system you're trying to install on. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/155000: make(1) doesn't handle .POSIX: correctly
On 02/24/11 14:35, Bruce Evans wrote: Except that there is the opportunity to set %POSIX using make -D. This might be enough in practice. The namespace pollution avoidance is too perfect -- there seems to be no way to set %POSIX or .POSIX in the environment. Is this relevant? POSIX says that the Right Way to demand POSIX mode is to put .POSIX on the first non-comment line of the Makefile; our %POSIX variable is a red herring as far as POSIX is concerned. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/155000: make(1) doesn't handle .POSIX: correctly
The following reply was made to PR bin/155000; it has been noted by GNATS. From: Colin Percival cperc...@freebsd.org To: Bruce Evans b...@optusnet.com.au Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/155000: make(1) doesn't handle .POSIX: correctly Date: Thu, 24 Feb 2011 15:41:51 -0800 On 02/24/11 14:35, Bruce Evans wrote: Except that there is the opportunity to set %POSIX using make -D. This might be enough in practice. The namespace pollution avoidance is too perfect -- there seems to be no way to set %POSIX or .POSIX in the environment. Is this relevant? POSIX says that the Right Way to demand POSIX mode is to put .POSIX on the first non-comment line of the Makefile; our %POSIX variable is a red herring as far as POSIX is concerned. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/155000: make(1) doesn't handle .POSIX: correctly
On Thu, 24 Feb 2011, Colin Percival wrote: Description: make(1) doesn't handle .POSIX: correctly. It sucks in sys.mk before it reads the Makefile, and sys.mk has several instances of .if defined(%POSIX) to switch between POSIX and non-POSIX mode; because sys.mk is processed first, there is no opportunity for a .POSIX: directive to take effect. How-To-Repeat: $ echo .POSIX: Makefile $ make -V CC (prints cc; it should print c89.) Except that there is the opportunity to set %POSIX using make -D. This might be enough in practice. The namespace pollution avoidance is too perfect -- there seems to be no way to set %POSIX or .POSIX in the environment. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/155000: make(1) doesn't handle .POSIX: correctly
The following reply was made to PR bin/155000; it has been noted by GNATS. From: Bruce Evans b...@optusnet.com.au To: Colin Percival cperc...@freebsd.org Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/155000: make(1) doesn't handle .POSIX: correctly Date: Fri, 25 Feb 2011 09:35:30 +1100 (EST) On Thu, 24 Feb 2011, Colin Percival wrote: Description: make(1) doesn't handle .POSIX: correctly. It sucks in sys.mk before it reads the Makefile, and sys.mk has several instances of .if defined(%POSIX) to switch between POSIX and non-POSIX mode; because sys.mk is processed first, there is no opportunity for a .POSIX: directive to take effect. How-To-Repeat: $ echo .POSIX: Makefile $ make -V CC (prints cc; it should print c89.) Except that there is the opportunity to set %POSIX using make -D. This might be enough in practice. The namespace pollution avoidance is too perfect -- there seems to be no way to set %POSIX or .POSIX in the environment. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
misc/155017: [patch] remove check for /usr/share/mk/bsd.port.options.mk
Number: 155017
Category: misc
Synopsis: [patch] remove check for /usr/share/mk/bsd.port.options.mk
Confidential: no
Severity: non-critical
Priority: low
Responsible:freebsd-bugs
State: open
Quarter:
Keywords:
Date-Required:
Class: sw-bug
Submitter-Id: current-users
Arrival-Date: Fri Feb 25 02:10:13 UTC 2011
Closed-Date:
Last-Modified:
Originator: Eitan Adler
Release:
Organization:
Environment:
Description:
bsd.port.options.mk exists in 7.1.0 and beyond. There is no reason to include
this check anymore.
How-To-Repeat:
Read bsd.port.mk expecting sanity. Realize this will never happen and just look
for code that is not needed anymore.
Fix:
Index: bsd.port.mk
===
RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.669
diff -u -r1.669 bsd.port.mk
--- bsd.port.mk 16 Feb 2011 10:43:53 - 1.669
+++ bsd.port.mk 24 Feb 2011 21:00:06 -
@@ -2928,24 +2928,6 @@
@${ECHO_CMD} ${MAINTAINER}
.endif
-.if !target(check-makefile)
-check-makefile::
-.if !exists(/usr/share/mk/bsd.port.options.mk)
- @${ECHO_CMD} !!! Detected system without bsd.port.options.mk (probably
old FreeBSD version)
- @${ECHO_CMD} !!! Dropping bsd.port.options.mk into /usr/share/mk
- -@${ECHO_CMD} USEOPTIONSMK= yes /usr/share/mk/bsd.port.options.mk
2/dev/null
- -@${ECHO_CMD} INOPTIONSMK=yes
/usr/share/mk/bsd.port.options.mk 2/dev/null
- -@${ECHO_CMD} .include bsd.port.mk
/usr/share/mk/bsd.port.options.mk 2/dev/null
- -@${ECHO_CMD} .undef INOPTIONSMK /usr/share/mk/bsd.port.options.mk
2/dev/null
-.if exists(/usr/share/mk/bsd.port.options.mk)
- @${ECHO_CMD} !!! Done
-.else
- @${ECHO_CMD} !!! Failed
-.endif
-.endif
- @${DO_NADA}
-.endif
-
.if !defined(CATEGORIES)
check-categories:
@${ECHO_MSG} ${PKGNAME}: Makefile error: CATEGORIES is mandatory.
Release-Note:
Audit-Trail:
Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/139239: ld(1) /usr/bin/ld: Please report this bug.
Synopsis: ld(1) /usr/bin/ld: Please report this bug. State-Changed-From-To: feedback-closed State-Changed-By: eadler State-Changed-When: Thu Feb 24 21:09:26 EST 2011 State-Changed-Why: Feedback said that they no longer use ld in this manner and are unable to test http://www.freebsd.org/cgi/query-pr.cgi?pr=139239 ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: bin/155000: make(1) doesn't handle .POSIX: correctly
On Thu, 24 Feb 2011, Colin Percival wrote: On 02/24/11 14:35, Bruce Evans wrote: Except that there is the opportunity to set %POSIX using make -D. This might be enough in practice. The namespace pollution avoidance is too perfect -- there seems to be no way to set %POSIX or .POSIX in the environment. Is this relevant? POSIX says that the Right Way to demand POSIX mode is to put .POSIX on the first non-comment line of the Makefile; our %POSIX variable is a red herring as far as POSIX is concerned. It allows A Way. Of course you should fix make(1) to support the POSIX way if this is not too hard. If make can see .POSIX before including sys.mk, then it could alternatively include a POSIX-sys.mk instead. This would be cleaner than the ifdefs in sys.mk, and would inhibit breakage of the POSIX case by putting things like CTF in its rules. Bruce ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: Installing FreeBSD on Dell-mini 9
On Thu, 24 Feb 2011 21:50:07 -0500, Khalid Rehan kre...@ktait.com wrote: Yes, an old OpenSSH version is needed... In that case, use a current release, then get the ports tree of 4.9 (or wherever the OpenSSH version occurs that you require) and build it from source. Or maybe even better: Use the port portdowngrade to get an older version of OpenSSH and install it. You can install it as an additional program, or overwrite the system's SSH with it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: Installing FreeBSD on Dell-mini 9
You mean force installing the old version, right? OK, I will go through it. I'm sorry, I'm not familiar with BSD, so I will try it, and I will be confirming you my results. Thanks so much, Khalid.. On Thu, Feb 24, 2011 at 9:54 PM, Polytropon free...@edvax.de wrote: On Thu, 24 Feb 2011 21:50:07 -0500, Khalid Rehan kre...@ktait.com wrote: Yes, an old OpenSSH version is needed... In that case, use a current release, then get the ports tree of 4.9 (or wherever the OpenSSH version occurs that you require) and build it from source. Or maybe even better: Use the port portdowngrade to get an older version of OpenSSH and install it. You can install it as an additional program, or overwrite the system's SSH with it. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... -- Khalid Abd El-Halim Rehan System Administration, KTAIT. --- Visit : http://english.islamway.com/ http://www.openoffice.org/ For family safe on-line: http://www.opendns.com/ ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
Re: gnu/139239: ld(1) /usr/bin/ld: Please report this bug.
The following reply was made to PR gnu/139239; it has been noted by GNATS. From: Bruce Cran br...@cran.org.uk To: bug-follo...@freebsd.org, bee...@gambler.ru Cc: Subject: Re: gnu/139239: ld(1) /usr/bin/ld: Please report this bug. Date: Fri, 25 Feb 2011 07:18:47 + It looks like this has been fixed, too: passing -m32 automatically causes ld to link with libraries in /usr/lib32 on 9-CURRENT. -- Bruce Cran ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to freebsd-bugs-unsubscr...@freebsd.org
