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.
Rober
>From Warren Block :
> 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 KMS and WITH_
Compiling your 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
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 n
> 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 Do
> > 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, save
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
> tr
> 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 Li
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 w
> 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?
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 ma
>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" a
> 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 install
> > 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 i
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 KERNCONF=YOUR_KERNEL_H
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
conf
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. P
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. P
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 probl
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 p
> On Fri, Oct 11, 2013 at 10:10:26PM +0000, 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 deprecate
>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 stab
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 sti
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: on re0
rgephy0: PHY 1 on miibus0
rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX
> 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 Linu
> 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
> > On 23 October 2013 13:10, claudiu vasadi 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 don't use wifi
> 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
> ether
> 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 i
> 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
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 qu
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; filename="re.81
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 s
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
>
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 d
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
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 thin
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 bu
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 amd
> 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
> 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 recog
> 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 ne
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 wor
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 mul
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 sy
from Julio Merino:
> On Mon, Feb 24, 2014 at 6:47 AM, Thomas Mueller
> wrote:
> > 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
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 de
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
> > 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 fixe
> > 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
> a
> Hi all, the gnash port is broken from two months ago , because have problem
> with the boost ports (link problem)
> Have other ports to emulate flash as browser plugins?
> Rizzo
I have gnash 0.8.10_7 installed on FreeBSD 9.2-STABLE, and it quit working with
the last update.
Before then, i
> I'm using the -current -- FreeBSD valfenda 11.0-CURRENT FreeBSD
> 11.0-CURRENT #16 r263202: Sat Mar 15 00:23:05 BRT 2014
> root@:/usr/obj/usr/src/sys/VALFENDA amd64
>and the gnash don't work to me. I'm not using the flash plugin (from
> linux emulator) because I think different about this
I had two crashes, or more accurately, freezes, when web-browsing.
First was with Firefox on an easy National Weather Service page, I was
scrolling down with down-arrow key, and system suddenly froze, no response to
keyboard or mouse, display stayed (until I hit Reset).
uname -a shows
FreeBSD
I sent this message, without this top part, over an hour ago, and notice wlan0
is still up. I intended but forgot to CC to freebsd-current. But I am in
newcons, having not started X so far this boot session. Maybe something rotten
with Xorg, or interaction between rsu and X, or rsu and Firefo
from Idwer Vollering :
I have a patch for that:
Index: head/sys/dev/usb/wlan/if_rsu.c
===
--- head/sys/dev/usb/wlan/if_rsu.c (revision 266970)
+++ head/sys/dev/usb/wlan/if_rsu.c (working copy)
@@ -69,11 +69,13 @@
#include
> Yes, please apply by hand. I'll see if I can do some testing myself. I happen
> to have one of these adapters too and the link is very unstable :-)
>
--HPS
Sometimes Hiro H50191 USB-stick wireless adapter
from Idwer Vollering :
> I'm on 10-STABLE r267049, with a local change to
> sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3.
> > At least my adapter is working a bit more stable now :-)
> Mine seems to get stuck in "rsu_calib_task: running calibration task" often.
> HTH,
>
from Adrian Chadd:
> please bug freebsd-usb@ about flakey usb devices.
> I have a couple that i need to chase up hans about. they used to be less
> flakey.
Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters.
I get console messages about keyboard and mouse l
from Adrian Chadd:
> Buy a mini-pcie atheros wifi card.
How do I know this would work with FreeBSD and/or NetBSD?
I could switch the hard drives between the two computers, or put one hard drive
in a Sabrent enclosure: IDE and SATA inside, USB 2.0 and eSATA outside
interface.
I could also buy
> Possibly increase the timing variables under:
> sysctl hw.usb.timings
> If they are not there, possibly the USB_DEBUG option has been removed from the
> kernel config. Can you check that?
--HPS
What are the units for sysctl.hw.usb.timings? Seconds? Milliseconds?
I ran sysctl hw.usb.timing
My Internet connection on this computer is very iffy at best, not running as I
type this.
Motherboard is MSI Z77 MPOWER.
Ethernet is Realtek (re): good with NetBSD, Linux and Haiku, (Free,Open and
DragonFly)BSD bug out.
Only Internet connection for FreeBSD is Hiro H50191 USB-stick wireless a
I have a DVD, a data DVD rather than movie or music, from Seagate Business
Storage 2-bay NAS, that is mountable with mount_cd9660 but not readable in
FreeBSD and NetBSD, using current amd64 versions of FreeBSD and NetBSD.
ls /cdrom showed nothing; ls -al /cdrom showed
total 6
dr-xr-xr-x 2 roo
> You need to install sysutils/udfclient. Your cd is in UDF format, that isn't
> covered by standard mount_udf.
--
> Regards,
> Ruslan
I just tried and failed, got error messages but still got fusefs-libs which
could prove useful:
cc -O2 -pipe -fno-strict-aliasing -I/usr/local/include -D_FILE
> You need to install sysutils/udfclient. Your cd is in UDF format, that isn't
> covered by standard mount_udf.
--
> Regards,
> Ruslan
Let me also say, one of the MASTER_SITES listed in the Makefile is no good
(NXDOMAIN):
http://www.13thmonkey.org/udfclient/releases
I just tried and failed, got
I want to build a kernel with debugging for a specific device, rather than for
everything.
Device of interest is re (Ethernet driver), also rsu (USB wlan adapter).
I looked in Makefiles, also NOTES files, found some DEBUG options but
nothing really general that could be applied to any desir
Screen(xf86Screens[i]->ScreenInit, argc, argv);
indicating failure to add the screen.
Building xorg-server with gcc
make USE_GCC=any
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
__
> 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
cl
> In reference to this FreeBSD forums post:
> http://forums.freebsd.org/showpost.php?p=231135&postcount=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 a
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 rel
From: Kostik Belousov
> 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 commit for
> the libr
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 ha
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 though
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. I
Sorry about fubar e-mail address, it was a typo, missing > at the end of the
line:
From: "Thomas Mueller" WKRDIR needs to be an absolute path and will break when it moves up the
> tree to install dependencies. The most likely fix is to adjust the
> default value ${WRKDIRPRE
from Allan Jude:
> > Anyone has any recommendations or experience about how to use native 4K
> > disks with FreeBSD?
> > --HPS
> It is not possible in legacy/BIOS mode, because the BIOS calls do not
> let you specify a sector size.
> However, you SHOULD be able to boot from the 4k devi
from Ngie Cooper:
> > On Oct 28, 2017, at 18:09, Gordon Tetlow wrote:
> > I have an Intel NUC that uses an Intel 8260 wireless driver. This works
> > flawlessly if I load the module if_iwm via the loader or the rc.conf
> > kld_list directive.
> > Do we know if the iwm driver not being in GENERI
> Wow, this blew up quite a lot bigger than I anticipated. I'll try to
> summarize the discussion a bit below and then suggest a way forward.
> The primary reasons we want to do this is because there are conflicts between
> the new drm drivers in ports, and the drm drivers in base, since they con
from Andrey Fesenko:
> bsdinstall script, work in 2019
PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / }
#!/bin/sh -x
# Make diskname independante
gpart modify -l freebsd-boot -i 1 ada0
gpart modify -l efi -i 2 ada0
gpart modify -l root -i 3 ada0
# Make EFI happy
from Ed Maste:
> > Any guidance on amount of diskspace and how long it takes to clone the repo
> > ?
> I see just over 3GB in my clone, including about 2.5GB in the .git directory.
> If you have only one checkout git will require a bit more disk space
> than svn. However, if you have two or mor
from Kevin Oberman:
> > So I am abandoning FreeBSD 12.x .
> > Hopefully I could update 13-current from within 13-current where I have no
> > internet access but could use git from NetBSD, where I also have svn.
> > Tom
> Not really much different from subversion. .svn in /usr/sys is a
> I am seeing a problem since I moved to current on my laptop this week. It's
> odd as it is linked to the keyboard. As long as the keyboard is active,
> everything is fine, but if the keyboard is not used, after a few minutes,
> it locks up and gets very hot. The system may be busy or idle. The sy
from tech-lists:
> As subject - is svn still canonical for -current or is it git now?
> If it's not git now, when roughly is the intended switch?
I recently updated FreeBSD doc, ports, src (current), and src12 (12-stable)
using svn (not svnup or svnlite).
But I read some time before that, FreeB
> Subversion is the source of truth for FreeBSD today.
> In the near future, likely early next month, we'll move our operations over
> to git. Git will be the source of truth after the flag day. All developer
> operations will be in git: committing to current, and MFCing will all be
> d
from Warner Losh and my last message:
> > Thanks for the information, but if you feel the need to send me a
> > not-quite-CC, please don't send me the multipart/alternative version when
> > you send the plain-text version to the list.
> > I hate multipart/alternative!
> I must apologize.
from tech-lists:
> As subject - what will there be in base to interact with the new git repo?
> I mean, right now, for svn there is svnlite. What for git?
> Shouldn't it be in base before the move to git?
Good question, and I hope the developers and others in charge are reading your
post.
You
> > I hope we don't have to start signing all commits. saltstack/salt has
> > that policy, and it's extremely annoying.
> Have to? Not currently. As with all process changes, there will be
> community discussion around the different points.
> Warner
I hope not!
Signatures, at least in email me
> Yes. I was answering the first question asked about FreeBSD and git...
> The clincher for me was that git is better supported by third party tools
> and has gotten quite good at 'recovery from oops' which mercurial is still
> lacking in both areas. I too have used both, and I had to re clone my
> stable/11 as well as the releng branches for as long as the project has
> them under support. I wrote the code to replay commits into subversion for
> the convenience of our users on those branches. The 12.x releases will be
> built out of Subversion to preserve $FreeBSD$ expansion and other obsc
> Disclaimer: I just started to learn git, never used it before.
> If I do understand it correctly, the switch from svn to git comes with a loss
> of continuously increasing revision numbers. Correct? If so I wonder how
> future security advisories and errata notices will be composed. Will there
> > Does that mean CURRENT is now 14.0? I must have missed the
> > announcement.
> That is correct, 13-stable has been branched from 13-current which has now
> been bumped to 14-current.
> Because it's a major version change going from 13 to 14, pkg is a bit
> agitated regarding the ABI.
> > > D
> It is in the mini primer I wrote, along with how to bisect and other useful
> things. This will migrate into the handbook once the doc tree converts to
> asciidoc (happening this weekend).
> https://github.com/bsdimp/freebsd-git-docs/blob/main/mini-primer.md
> Warner
I looked at your mini-p
Good morning!
> I regularly sync my FreeBSD source tree with the central repository using svn
> update. I use a one-lis script to synchonize, which sends the output of svn
> to a file, and also copies to the console. This list contained - according to
> the 'svn help update' - one line
from Kurt Jaeger:
> Hi!
> > > On May 25, 2021, at 8:53 PM, jake h wrote:
> > > I have recently received several pieces of spam mail, apparently sent via
> > > this mailing list. These pieces of mail are the usual spam formula; Your
> > > phone has a virus, Ads, Fake blackmail, so on and s
I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be
successful with "dhclient re0".
UPDATING file says to boot single-user after buildkernel and installkernel, but
then mount -u / or mount -u
I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be
successful with "dhclient re0".
UPDATING file says to boot single-user after buildkernel and installkernel, but
then mount -u / or mount -u
> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is
> missing sw
> IOW the line MUST read as:
> /dev/gpt/Sea1-18noneswapsw 0 0
> or
> /dev/gpt/Sea1-18noneswapsw,trimonce 0 0
> as appropriate for the media referenced.
101 - 198 of 198 matches
Mail list logo
