Does this mean the bug is fixed in 11-current?
Yes, the bug is fixed in 11-CURRENT, as of Subversion revision r262809.
MFC? Is that to 10-STABLE? Your message is less than clear.
In FreeBSD, fixes are first applied to head (a.k.a -CURRENT), then
after a
Thanks for the fast work! The patched solve the problem for me and I
was able to install and run firefox on 11.0-CURRENT i386.
I have imported the upstream fix for this bug in r262809, and I will MFC
it after one week. Happy Firefoxing. :-)
-Dimitry
Does this mean the bug is fixed in
What is the current status of clang, regarding known bugs, on FreeBSD-current?
There were reports of www/firefox failing to build because of bug in llvm.
Can I currently build ports normally on FreeBSD-current amd64 and i386, or do I
need to wait?
Or update system and build ports on my FreeBSD
from Mark Felder:
Yes, however the Sendmail in base on FreeBSD 8 and 9 is compiled against
OpenSSL 1.0 which means it's missing support for TLS 1.2, SNI, and
other modern best practice features.
That suggests putting sendmail to ports rather than base system, so that
updates would not
from Julio Merino:
On Mon, Feb 24, 2014 at 6:47 AM, Thomas Mueller
mueller6...@bellsouth.netwrote:
To Julio Merino: How long did NetBSD include both sendmail and postfix in
base? What NetBSD releases? What was the first release that included both
sendmail and postfix, and the first
from Don Lewis:
I've got a Fedora server here that has systemd and I've come to dislike
it. It seems to be one of those Do not open. No user serviceable
parts inside. sorts of things.
I was never able to get it to start NUT properly.
More often than not, it fails to come up
I never got far enough with DragonFlyBSD or OpenBSD on live USB to see osmpd or
opensmtpd (OpenBSD or dma (DragonFly).
I couldn't read hard drive from either OpenBSD or DragonFly, could read OpenBSD
but not DragonFly live USB stick from FreeBSD and NetBSD, meaning poor
interoperability on my
To Miguel Clara, you might try a USB wireless adapter. I use Hiro H50191,
driver rsu.
But you would need to do good research to find what the chip is, and which
FreeBSD driver, if any, would it work with, before you buy.
NDISulator looks worth trying. FreeBSD users will want to know if it
I work with Jack on FreeBSD network drivers, and we have a patch that we
think might fix this problem. It re-implements the header pull-up code that
was in the driver pre-2.4.0, but with IPv6 support. Alexandre, could you
apply this patch to the igb version in HEAD and try it out on your
but the problem is we need to patch the re driver somehow because
I have many motherboards where this exact nic does not work correctly.
Sam Fourman Jr.
Misery loves company!
My new MSI Z77 MPOWER motherboard with onboard Realtek 8111E NIC is affected by
this re(4) bug.
Ethernet is
I had (still have) svn on a USB-stick installation of FreeBSD 9.2-STABLE.
So I tried to use that to checkout the src tree for FreeBSD-HEAD; re(4)
recognized my on-motherboard (MSI Z77 MPOWER) Ethernet but couldn't connect.
So, after NetBSD 6.1_STABLE hung consistently on boot, NetBSD-current
On Thu, Dec 19, 2013 at 09:56:31AM +0800, Kevin Lo wrote:
Your usb wlan dongles use RTL8188EU chip which is currently not
supported by any of drivers.
I see; I guess I should not have believed when I was told that most likely
all it would take is id-patch urtwn(4). ;-)
Does anyone know
from Glen Barber (excerpt):
Changes between -BETA3 and -BETA4 include:
- Add preliminary support for RTL8106E, RTL8168G, RTL8168GU,
RTL8411B, and RTL8168EP.
- Enable fingerprint checking in pkg(8) for FreeBSD-provided binary
packages.
- Remove the WITH_LIBICONV_COMPAT
from Adrian Chadd:
hi all,
I'd like a developer or two to organise the MFC of anything that's in
net80211 on -HEAD back to -10 before 10.0-REL.
There's a few critical fixes that need to go in but I just don't have
the time to do it myself. :(
Thanks!
There are a couple things I
from O. Hartmann:
Recently,
I stumbled into this board, which looks promising:
http://www.viaspringboard.com/products.html
Does anybody know whether the offered hardware (chipse, CPU, WiFi
chipset) is supported by FreeBSD?
I went to that URL and noticed that the WiFi chip was Atheros
As some may have noticed, the 10.0-RELEASE cycle has slipped a bit
behind schedule.
Here is where we stand at the moment:
- The iconv issues mentioned in a previous status update email[1] are
being looked at extensively. There are a number of iconv(3) fixes
that have been
from Glen Barber and my previous message:
Software crashes because of incorrect/missing character encodings are
one symptom in particular.
Release engineering estimated dates ought to be updated on the website.
Once -BETA4 is out, the remaining dates will be updated accordingly.
I do not
For a future test of any updates to re driver, it might be best if I comment
out device re in kernel config and test the update by building the module.
I never built just a single module before, not sure if I would do it the
correct way.
Simply make in /usr/src/sys/modules/re
and then make
from Daniel Nebdal:
Ethernet without DHCP is fairly doable.
Assuming that the network is 192.168.0.x , that .100 is free, and your
router has .1 :
ifconfig re0 192.168.0.100/24
route add default 192.168.0.1
As for DNS, I'd suggest checking on another machine what servers you get
from
I tried the patch on 9.2-STABLE, rebuilt the kernel and modules, installed to
the correct place on USB stick,
/media/zip0/boot/kernelre
USB stick was mounted on /media/zip0 when I did this.
Then I umounted, took the USB stick to new computer with MSI Z77 MPOWER
motherboard.
I booted that USB
from Mark Felder:
Question that arises is how does the system know where to send the email,
and through what SMTP server, especially if panicmail_autosubmit=YES.
Every computer on the planet has the capability of being able to send
email directly without an SMTP server. The only question
from Yonghyeon PYUN:
Thomas, would you try attached patch on your system?
[-- Attachment #2: re.8168evl.diff --]
[-- Type: text/x-diff, Encoding: 7bit, Size: 3.6K --]
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment;
Hi all,
After considerable review on freebsd-hackers (thanks dt71 and jilles!) I have
now added sysutils/panicmail to the FreeBSD ports tree. If you install this
and add
panicmail_enable=YES
to your /etc/rc.conf, a panic report will be generated and sent to root@ for
you
On 24.10.2013 05:46, Thomas Mueller wrote:
I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails
to
connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and
Atheros AR9271 onboard wifi: device athn is included in NetBSD (current
only)
and OpenBSD
On 23 October 2013 13:10, claudiu vasadi claudiu.vas...@gmail.com wrote:
Hi,
Still getting the Cannot reset interface wlan0 - exit status 1 in
wifimgr but no crash yet. Will keep trying :D
I have no idea about that. It's likely there's some net80211/iwn bug(s) but
I
The later driver model isn't supported by ndisulator. We'd have to
implement all the newer NDIS stuff for wifi and ethernet.
In the later NDIS layer the Microsoft Wireless Services implement a bunch
of stuff that used to be up to the driver. Ie, the driver just exposed an
ethernet
The NDISulator is a crutch from a time when there wasn't _any_ real
alternative.
There are plenty of alternatives now. What's lacking is desire and
person-power. But the datasheets are there, or the vendor code has been
released, or there's linux/otherbsd drivers.
Leaving it in there is
I'd like to remove the NDISulator. I've had many requests to update it to
the latest NDIS version and support more of the 64 bit wifi drivers. But,
to be perfectly honest, I have no desire to keep hacking at this. The world
has changed quite a bit - we can port/reimplement drivers from Linux
for MSI Z77 MPOWER motherboard on FreeBSD 10.0-BETA1, from /var/run/dmesg.boot:
re0: Using 1 MSI-X message
re0: Chip rev. 0x2c80
re0: MAC rev. 0x
miibus0: MII bus on re0
rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX,
from Juergen Lock:
If you mean it loads the kernel but then crashes instead of booting it
then your grub2 version is missing this fix:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002
I used Super Grub2 Disk image on the System Rescue CD written to USB stick.
From Guido Falsi:
On 10/12/13 15:29, John wrote:
Hello currents,
I have a 9.2-R vm and I'd like to bring it up to 10 (i.e what will
eventually be 10-RELEASE). So, do I svn 10-STABLE or HEAD?
I think 10-STABLE but I just want to check.
You are correct.
branch stable/10 on
I thought I sent this message yesterday, but couldn't find it in the downloaded
list messages, so maybe I forgot.
Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one
supposed to use in its place?
I see nslookup is in FreeBSD 9.2, but why not in -current?
There has been
On Fri, Oct 11, 2013 at 10:10:26PM +, Thomas Mueller wrote:
...
Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one
supposed to use in its place?
Use host.
nslookup was part of BIND, and has been deprecated for years (IIRC).
Peace,
david
--
David H
Quoting without so as not to interfere with the patch:
How does this look:
Index: UPDATING
===
--- UPDATING(revision 256024)
+++ UPDATING(working copy)
@@ -1899,7 +1899,7 @@
make buildkernel
from Devin Teske:
That wasn't the rationale. sysinstall was broken and more people wanted a
replacement than wanted to see it fixed.
bsdinstall is simply coming of age still (sysinstall had a 15 year run).
Some things I disliked about sysinstall were choosing a type of install from a
from Devin Teske:
I'm late to the party again ;D (didn't realize the rcs thread had turned BE)
Both problems can be solved.
The loading of the kernel *after* choosing your boot device is trivial.
We've been doing it at $work for *years* (almost a decade?)
I can put that in, whenever.
from Devin Teske:
I'm late to the party again ;D (didn't realize the rcs thread had turned BE)
Both problems can be solved.
The loading of the kernel *after* choosing your boot device is trivial.
We've been doing it at $work for *years* (almost a decade?)
I can put that in, whenever.
Sorry for previous typo in From: line, missing right angle bracket at end.
Then, in a finger error, I resent that message just before finding the error
and making the needed correction.
from Devin Teske:
I'm late to the party again ;D (didn't realize the rcs thread had turned BE)
Both
From $SRCDIR/UPDATING
To cross-install current onto a separate partition
--
# In this approach we use a separate partition to hold
# current's root, 'usr', and 'var' directories. A partition
# holding /, /usr and
To cross install FreeBSD on a system without the required users/groups
you must either install them on the base system so that install and
mtree can use them or use the -DDB_FROM_SRC option when running the
installworld/installkernel/distribution targets.
-- Brooks
That worked for
But where is DB_FROM_SRC documented? I never saw it anywhere. UPDATING
file needs to be updated for installing FreeBSD on a partition where there
is no OS installed.
It's documented in Makefile.inc1 where the less commonly used options
are documented. It should be documented in the
I just happened to be browsing man urtwn in NetBSD-current (6.99.23), and
Edimax EW-7811Un is listed as supported by this driver.
This strongly suggests it should work for FreeBSD-current (barring bugs).
Tom
___
freebsd-current@freebsd.org
FreeBSD-10.0-ALPHA1-i386-disc1.iso
Verified checksum.
I can not boot from CD-RW at all - it does not seem to be recognized.
Anybody else has similar experience ?
jb
Is your CD-RW not recognized even before it tries to boot?
Is your disc1.iso burned to CD or DVD? Is the drive CD or DVD?
If
In reference to this FreeBSD forums post:
http://forums.freebsd.org/showpost.php?p=231135postcount=4
Would it be a good time to remove those from GENERIC since the
hardware they are for is becoming so seriously outdated?
There's always an option to load those drivers as
As for me I expect something like this:
. 9.x gcc default and clang in base;
. 10.x clang default and gcc in base;
. 11.x gcc withdraw.
There is also the concern whether clang in base will reliably build gcc
required for some ports, and then there are those CPU architectures for which
clang
or with clang and -O0
mage CFLAGS=-O0
gives me an X server that appears to work (displays root weave, xterm,
and twm).
--
Thomas Mueller
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
Thomas Mueller writes:
I built the newer Xorg and it falls flat: goes to a nongraphic
screen that is blank except for a rectangular cursor in the upper
left corner, and now I want to get back to the earlier Xorg.
System is Intel Sandy Bridge with i7 CPU.
Robert Huff responds
From Warren Block wbl...@wonkity.com:
After adding those, graphics/libdrm must be rebuilt, and
x11-drivers/xf86-video-intel must have the KMS option enabled and be
rebuilt. If you just added WITH_NEW_XORG, there will be other xorg
components that need to be updated.
O no, I'm getting rid of
From Andrey Fesenko f0and...@gmail.com:
NDIS failed to raise working version. Win driver terrible ~5 firmware and
other.
urtwn such as usb devices and no porting FreeBSD only dirty hack
http://lists.freebsd.org/pipermail/freebsd-wireless/2012-November/002539.html
just wanted to get wi-fi
Excerpt from Andrey Fesenko f0and...@gmail.com:
And other problems.
1) wi-fi
standart rtl8192cu - not work
change AR5B95 - work n-mode (thanks Adrian Chadd :) need hack BIOS
dev.acpi_ibm.0.wlan: 1 - read only
hardware switch work, not send mesage
What did you try to make rtl8192cu work?
On Tue, 1 Jan 2013 10:55:58 -0800
Tim Kientzle kient...@freebsd.org wrote:
On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote:
Greeting-
The driver is working much better than the driver currently in
head. I have maintained an ssh connection to the BeagleBone for
more than 24
from Brett brett.ma...@gmx.com:
Just an observation: a few years ago when I got sick of Linux's headlong
rush development model, I subscribed to various BSD mailing lists to see what
+else was out there. I considered FreeBSD at the time - there was a
neverending avalanche of [head
Hello there.
I have problem here, and don't know if it's bug or feature :)
If I prerare boot media (hdd, sd card,usb, etc) with FreeBSD, and NOT
create there fstab, I see such behavior:
1. I need enter manually where from mount root (e.g. ufs:ada0s1a or
ufs:ada0s1a rw)
2. If I enter
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: base64, Size: 49K --]
Help
- Reply message -
From: freebsd-current-requ...@freebsd.org
To: freebsd-current@freebsd.org
Subject: freebsd-current Digest, Vol 465, Issue 5
Date: Thu, Sep 13, 2012 8:00 am
(and much more)
This
On 07/17/2012 22:54, Gustau Pérez i Querol wrote:
In fact filesystems not particulary specific and not tied our kernel
would go to userspace; thinks like smbfs, nwfs, ntfs, ext2 o ext4 for
example should be in userspace
Doug Barton responded:
A big -1 here.
The more native FS support we
You can not only run Linux on XFS (which I do) but it is still likely
the most reliable and consistently performant of the filesystems
available in Linux because of its origin and its maturity. XFS did
not originate in Linux (it originated in SGI's Irix) so it should not
surprise that Linux
On 06/29/12 16:32, Attilio Rao wrote:
As already published several times, according to the following plan:
http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS
in 2 months the code dealing with non-MPSAFE filesystem will be
removed and filesystems not yet MPSAFE will be disconnected from the
tree.
pwd_mkdb -p /etc/master.passwd
Cheers,
Matthew
Dr Matthew J Seaman MA, D.Phil.
That did it! Now I can login as nonroot and startx.
I found pwd_mkdb in my searching, but would not have known to use '-p'. I
might have done
pwd_mkdb /etc/master.passwd
from
pwd_mkdb -p /etc/master.passwd
Cheers,
Matthew
Dr Matthew J Seaman MA, D.Phil.
That did it! Now I can login as nonroot and startx.
(snip)
Sorry, I didn't mean to send this old message again! I changed this message to
send to freebsd-stable list, saved
Umm, it's about as factual as The Onion, except not as funny. FreeBSD
never had to jettison two thirds of its code base and start from
scratch. Apple is not involved in FreeBSD development. No Mac OS X or
Darwin version includes FreeBSD. FreeBSD and Mac OS X will never
merge. FreeBSD was
code with -ffast-math -fno-finite-math-only should
restore the call to finite().
--
Thomas Mueller
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current
--- On Sat, 12/10/11, Marius Strobl mar...@alchemy.franken.de wrote:
I'm not sure what CAM IOCTL number change others
are
referring to but
you certainly need to rebuild libcam consumers
after
r225950, which
was merged to stable/9 in r226067 on October 6
2011.
Marius
--- On Fri, 12/9/11, Marius Strobl mar...@alchemy.franken.de wrote:
+, Thomas Mueller wrote:
Recompile the port; the CAM ioctl numbers have
changed.
Cheers
Michiel
When did these CAM ioctl numbers change? Was it
before or after I built and installed cdrtools?
Running ls
Recompile the port; the CAM ioctl numbers have changed.
Cheers
Michiel
When did these CAM ioctl numbers change? Was it before or after I built and
installed cdrtools?
Running ls -rtl /var/db/pkg/cdrtools-3.00_1 produces
total 48
-rw-r--r-- 1 root wheel 17550 Sep 26 09:20 +MTREE_DIRS
from my last message:
I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now I
see RC3 is available.
I tried options ATA_CAM in kernel config, removing device atapicam, but
still
readcd -scanbus or
cdrecord -scanbus
refuses to work, running as root.
camcontrol devlist
I can't get cdrtools (cdrecord or readcd) to work on FreeBSD 9.0-RC2, and now I
see RC3 is available.
I tried options ATA_CAM in kernel config, removing device atapicam, but
still
readcd -scanbus or
cdrecord -scanbus
refuses to work, running as root.
camcontrol devlist shows my DVD drive,
From Mehmet Erol Sanliturk m.e.sanlit...@gmail.com:
Supplying only a console-mode FreeBSD as a release is making FreeBSD
unusable for
peoples who they are not computing experts .
To allow less experienced people to use FreeBSD easily , it is necessary to
include a
selected
^ What version of FreeBSD do you run? Do you not have a ugen manpage? Can you
run man ugen?
^ I have the manpages for ugen, and man usb, also man 4 usb, but no diff as
such.
^ I guess ugen manpage failed to reflect becoming part of usb.
^ Tom
There is:
share/man/man4/ugen.4
in
On Wednesday 30 November 2011 11:24:39 Thomas Mueller wrote:
According to ugen man page, ugen can be compiled into the kernel with
device ugen
in config file.
I tried that in the kernel config when upgrading from FreeBSD 9.0-RC1 to
RC2, but the kernel build stopped quickly
According to ugen man page, ugen can be compiled into the kernel with
device ugen
in config file.
I tried that in the kernel config when upgrading from FreeBSD 9.0-RC1 to RC2,
but the kernel build stopped quickly with the message that ugen was not valid.
After removing that line from kernel
On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote:
b. f. bf1...@googlemail.com writes:
What is the role of options atapicam and device ATA_CAM in kernel
config file?
Are they redundant? Kernel will build with both these options, but
will it make things
In the old days home was typically a separate partition that was
mounted on /home. If you didn't have a partition the installer would
create /usr/home and symlink /home to it. The root was also typically
an independent partition, so it made sense not to clutter it up with
home directories.
On 18/11/2011 10:53, Thomas Mueller wrote:
*default release=cvs tag=RELENG_9
Am I screwed, am I OK, or do I simply have to rerun csup with RELENG_9_0
instead of RELENG_9 ?
Not screwed, but you'll be running 9.0-PRERELEASE rather than 9.0-RC2.
If you want to switch to the 9.0
If you would like to use csup/cvsup mechanisms to access the source
tree the branch tag to use is now RELENG_9_0, if you use . (head)
you will get 10-CURRENT. If you would like to access the source tree
via SVN it is svn://svn.freebsd.org/base/releng/9.0/. We still have
the nit that the
from Tom Evans tevans...@googlemail.com:
I have had this happen before, the PEBKAC. When running mergemaster,
it will prompt you to install new passwd, master.passwd and group
files - if you have added local users you must not say yes to this,
you must either merge the changes in or keep your
from Tom Evans tevans...@googlemail.com:
I have had this happen before, the PEBKAC. When running mergemaster,
it will prompt you to install new passwd, master.passwd and group
files - if you have added local users you must not say yes to this,
you must either merge the changes in or keep your
pwd_mkdb -p /etc/master.passwd
Cheers,
Matthew
Dr Matthew J Seaman MA, D.Phil.
That did it! Now I can login as nonroot and startx.
I found pwd_mkdb in my searching, but would not have known to use '-p'. I
might have done
pwd_mkdb /etc/master.passwd
from
I just finished the upgrade from source from 9.0-BETA2 to RC1, and I find two
problems.
First, I lost my users; nonroot user names are not recognized, if for instance
I type
passwd arlene
I already tried to login as arlene with old password, no good.
I copied the /etc directory to a backup
MHO different OS releases (Unix or not) are usually at the state of
FreeBSD current regarding stability. FreeBSD late BETA and early RC
are usually very stable. Therefore the approximate one month period
between the first beta and the release is adequate time.
I see your point, especially
One issue that has not come up on the emailing list is that dd, designed to
work with memsticks of various capacities, can not make the backup gpt at the
end of the memstick.
Partition is just big enough to hold the data, and I ran out of inodes at times
due to the installer writing to /tmp on
cvsup is a port, so you would need to install that to have cvsup. csup
and cvsup are totally different code bases in different languages.
(csup is C and cvsup is Modula-3.) You probably want to install cvsup
as a package as installing the port also requires building all of the
Modula-3
Hi all,
I've committed this to -head.
I'd appreciate it if csup users would give this a thorough testing and
report back to the list with results.
I won't submit this as a merge candidate this to stable/9 without a
whole lot of testing. :)
Thanks,
Adrian
I am now in 9.0-BETA2
I looked at ftp://ftp.freebsd.org/pub/FreeBSD/releases/
and found a BETA3 but only for some platforms not including i386 and amd64, but
that was yesterday.
I looked later during the day and found the BETA3 for i386 and amd64.
Now the question is how to update without trashing the BETA2
From Brett Glass br...@lariat.net:
Unfortunately, due to past history, /usr is mixed-use. It normally
contains both configuration information -- e.g. /usr/local/etc --
and more volatile data such as users' home directories. This
prevents /usr/local/etc, which also contains mission-critical
I see a thread, FreeBSD 9-Beta3 on X300 problems. and now am curious about
what is the current beta?
I looked at ftp://ftp.freebsd.org/pub/FreeBSD/releases/
and found a BETA3 but only for some platforms not including i386 and amd64.
Maybe the burncd problem, not working on SATA, is a temporary
More concerns and questions onthe new bsdinstall:
There is no upgrade function. How will a user be able to upgrade to BETA3 (or
RC1?) without wiping out BETA2 installation?
For instance, user might have built many software applications from ports and
not want to rebuild everything.
Other
From Matthew D. Fuller fulle...@over-yonder.net:
I've been meaning to mention this, but we really should document
somewhere that it has a _MAXIMUM_ size.
I setup a system a few weeks back with GPT, and figured I'd just make
the first 'real' partition start at the 1 meg mark. And make
Thomas Mueller mueller6727@bellsouth.net
There was a typo on my part that I failed to correct, missing at the end of
From: Thomas Mueller mueller6...@bellsouth.net
Responding to Warren Block wbl...@wonkity.com and others on the boot
partition:
So the 64 KB boot partition, nonbootable on my
Some more ideas on the new bsdinstaller cross my mind.
Since the way the bsdinstaller would make partitions is unpredictable, at least
to the uninitiated, and in all likelihood at variance with how much space the
user wants to allocate, it might be better to offer a roadmap to help guide the
I have successfully installed FreeBSD-9.0-BETA2 to an amd64 bit
machine, I have used the ports to install xfce and xorg. When I type
startx, I get a screen with a bunch of colors no mouse, no keyboard,
just colors. The machine has nvidia onboard graphics. I am trying to
get kernel sources
I just installed FreeBSD 9.0-BETA2 last night, now I try to build ports
starting with Perl 5.14.1 (successful), then Python 2.7 fails on something
dubious, but when I try to build Lynx, ports framework can't find a directory
right under its nose. Problem is with dependency libiconv-1.13.1_1.
Sorry about fubar e-mail address, it was a typo, missing at the end of the
line:
From: Thomas Mueller mueller6...@bellsouth.net
I'm surprised the e-mail went through that way.
WKRDIR needs to be an absolute path and will break when it moves up the
tree to install dependencies. The most
Actually, I think this kind of question is for the freebsd-current list, so I
respond on that list.
Problem with the old sysinstall is that sysinstall expects installation sets to
be broken into 1392 KB chunks as opposed to a full .tgz, .tbz or .txz, or so I
believe: I could be wrong.
I
Since I have plenty of disk space on the new computer, I was planning to keep
the BETA1 partition and install BETA2 to a separate partition.
FreeBSD 9.0 BETA1 is the first hard drive OS on the new computer, not counting
the nonworking NetBSD installation; I am not upgrading from 8.x.
Since I
From: Kostik Belousov kostik...@gmail.com
The bump was done for BETA2, see r225227, done on 2011-08-28.
The bump has much less scope since we did the ABI analysis and
only bumped the libraries which interfaces changed in incompatible
way and which were not yet bumped. See the referenced
When FreeBSD 9.0_BETA1 was announced, the announcement included a notice that
shared library version would be updated some time prior to BETA2, which would
necessitate rebuilding all ports.
Has this happened yet? I don't want to rebuild all ports at the wrong time. I
notice BETA2 has been
-flags ATA_R_DMA) {
--
Thomas Mueller [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
101 - 197 of 197 matches
Mail list logo
