t;all" in /usr/src/lib/clang
make[4]: stopped making "all" in /usr/src/lib
make[3]: stopped making "_generic_libs" in /usr/src
make[2]: stopped making "libraries" in /usr/src
375.76 real 1368.14 user 121.33 sys
make[1]: stopped making "b
So will doing git reset —hard solve it?
- Nathan
On October 10, 2024, Konstantin Belousov wrote:
On Wed, Oct 09, 2024 at 06:13:44PM +, Nathan Nasby wrote:
> > Hello,
> >
> > When I try to compile world with the latest source, I get error of
> > undeclared ident
Hello,
When I try to compile world with the latest source, I get error of
undeclared identifiers
/usr/src/usr.bin/procstat/procstat_vm.c:118:7: error: use of undeclared
identifier ‘KVME_FLAG_SYSVSHM’
118 | KVME_FLAG_SYSVSHM ? “true : “false”);
/usr/src/usr.bin/procstat/procstat_vm.c:169:25: er
umption is that the microsd images *are* the
installed system rather than a tool you use to install a system.
-Nathan
On 5/4/21 3:22 PM, tech-lists wrote:
Hi,
I've been trying to set up a boot-from-usb3 raspberry pi 4. I thought
i'd be able to do this by booting into latest current snap
?
Any errors in dmesg?
--HPS
I would guess the green might be a manifestation of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252712. I was never
able to fully debug it and it stopped happening at some point when the
webcam was attached through the USB hub in my monitor.
-Nathan
I didn't see in the (excellent!) docs is whether we should
be PGP-signing commits or not. Is that encouraged?
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
On 2020-03-29 20:02, Simon J. Gerraty wrote:
> Nathan Whitehorn wrote:
>> It's basically this that has been the problem: we need a way to manage
>> updates of the EFI loader in this situation, which we don't currently
>> have. The ESP needs to be mounted at a
n older systems, etc. The original (failed --
and I wrote it) concept with boot1.efi was that we could install a shim
that never needs updates, which avoids needing to think about these
things, but that didn't work ideally.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 2019-05-27 19:14, Warner Losh wrote:
> On Mon, May 27, 2019, 7:18 PM Nathan Whitehorn
> wrote:
>
>>
>> On 2019-05-27 15:50, Eric McCorkle wrote:
>>> On 5/27/19 5:53 PM, Edward Napierala wrote:
>>>> On Mon, 27 May 2019 at 16:14, Eric McCorkle
I don't believe is the
> case today.
>
> At least in the EFI case, loader is talking through the system's EFI
> implementation, which takes care of all that for you. BIOS works in a
> similar way. My sense is getting loader to the point where it could be
> a coreboot (w
gt; Cheers!
>>
> Hey that's great! Now that the precedent is set, we start the timer to
> deprecate on FreeBSD in roughly 10 years now :)
>
Or maybe we are ahead of the game since we never supported x32 in the
first place?
-Nathan
_
This probably seems to come from the loader geli support. If I rebuild
loader with WITHOUT_LOADER_GELI=1 set, everything is fine. Could anyone
else who is having trouble try to reproduce that?
-Nathan
On 10/5/18 1:38 PM, Andreas Tobler wrote:
> On 04.10.18 13:34, Alex McKeever wrote:
>>
Submitting this here as I believe this may be best place to ask the question as
I use poudriere to test ports before sending patches
I am on 12 current. If I’m building a port that can use either py27 or py36 on
an non x86based system the py27 works fine on all my jails. If I test with py36
poud
the two, by default drm-kmod (amd64) or drm-kmod-legacy
(i386), pulled in as a dependency by the relevant X11 drivers
- Garbage-collect dev/drm, which supports 3DFX and Rage 128 and such
archaic things
I think this keeps the user experience intact and lets the graphics
developers upda
at some later date.
-Nathan
On 03/28/18 11:22, Sean Fertile wrote:
Hi Mark,
Just so we are clear this is about V1 abi support in lld, not in llvm.
The compiler will still be able to produce valid code for big-endian
ppc64.
Regards
Sean
- Original message -
From: Mark Millard
This is my fault. Apologies. I will fix it immediately.
-Nathan
On 01/19/18 13:16, Milan Obuch wrote:
Hi,
after updating to revision 328171, building 12-CURRENT kernel gives
cc -target armv7-gnueabihf-freebsd12.0
--sysroot=/usr/obj/usr/src/arm.armv7/tmp
-B/usr/obj/usr/src/arm.armv7/tmp/usr
. The userspace version is platform-dependent and not
always available: for example, on PPC, you can't do this from userland
and we provide a sysctl machdep.cacheline_size to userland. It would be
nice to have an MI API.
-Nathan
___
freebsd-current@f
sting. I appologize for the breakage.
Still broken with GCC.
/usr/src/sys/dev/vt/colors/vt_termcolors.c:148: warning: function
declaration isn't a prototype [-Wstrict-prototypes]
*** [vt_termcolors.o] Error code 1
-Nathan
___
freebsd-curren
y are the equivalent of active in the UEFI standard?
They are a FreeBSD-ism. Because UEFI handles parsing the GPT tables
internally, it is not even possible to read them from loader.efi.
-Nathan
___
freebsd-current@freebsd.org mailing list
https
On 08/08/16 10:56, Glen Barber wrote:
On Mon, Aug 08, 2016 at 10:53:26AM -0700, Nathan Whitehorn wrote:
On 08/08/16 10:43, Lars Engels wrote:
On Mon, Aug 08, 2016 at 10:15:07AM -0700, Devin Teske wrote:
On Aug 8, 2016, at 8:02 AM, Lars Engels wrote:
On Mon, Aug 08, 2016 at 02:44:05PM
art of bsdconfig,
actually, and an option to open bsdconfig be an option at the end of the
installer.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Unfortunately, the glabel and (especially) GPT partition ID labelling
has in-kernel race conditions that make it impossible to rely on in the
installer. This has been an open problem since FreeBSD 9; hopefully it
will be solved soon.
-Nathan
On 08/02/16 20:35, Alive 4ever wrote:
Greetings
xcept in the CD case).
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
If it's worth anything:
"Mellanox OFED 2.3 or later has RoCE v2 support,"
(https://en.wikipedia.org/wiki/RDMA_over_Converged_Ethernet#RoCE_v2)
On Fri, Jul 15, 2016 at 8:06 PM, Matthew Macy wrote:
>
>
>
> On Thu, 14 Jul 2016 10:31:40 -0700 David Somayajulu <
> david.somayaj...@qlogic.com> w
on the DVD image. So
let's do that.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
It is not 64-bit only; like the normal loader, it can load both 32-bit
and 64-bit kernels. Those two flags are probably obsolete at this point
and were for compatibility with pre-2.17.5 versions of binutils. Can you
do a test build with the -CFLAGS+= -Wa,-mppc64bridge line removed?
-Nathan
On
I was just testing this a bit.
I can now set max in loader.conf as expected.
I did notice one thing that I thought was a bit strange though.
As a reference, here are my defaults without any ARC tunables/sysctls:
vfs.zfs.arc_meta_limit: 3903459328
vfs.zfs.arc_min: 1951729664
vfs.zfs.arc_max: 1561
ng if ARC is not configured.
> Request to commit the fix is with re@
>
> In the mean time the patch is attached.
>
> Thanks for the report and sorry about the breakage.
>
>
> On 06/07/2016 07:20, Nathan Bosley wrote:
>
>> Maybe I misunderstood after all.
>> I to
t; 1073741824
root@athlonbsd:~ # sysctl vfs.zfs.arc_max="8589934592"
vfs.zfs.arc_max: 15613837312 -> 8589934592
They also work fine sysctl.conf.
Sorry if this is a silly question:
I should still be able to set these max/min values in loader.conf,
right--not just in sysctl.conf?
Thanks.
OK, I follow you now.
Thanks for the explanation.
I will try that later tonight or tomorrow.
On Tue, Jul 5, 2016 at 9:45 PM, Allan Jude wrote:
> On 2016-07-05 21:32, Nathan Bosley wrote:
> > I think in about 4 - 5 hours I can show what values I'm using in
> > loader.conf und
even Hartland wrote:
> > Ahh right, let me check that.
> >
> > On 06/07/2016 00:51, Nathan Bosley wrote:
> >> I actually have this same problem.
> >> I'll send more details when I get home later.
> >>
> >> I think the problem start
I actually have this same problem.
I'll send more details when I get home later.
I think the problem started for me after r302265.
Before that, I can set vfs.zfs.arc_max and vfs.zfs.arc_min in loader.conf.
After r302265, setting either vfs.zfs.arc_max or vfs.zfs.arc_min in
loader.conf results in t
about walls and lords and whatever can
only make people angry (or demotivated) and is never persuasive. This is
really great work; there is a discussion about some nits in how to
distribute the results that corresponds to maybe 1% of the total
o longer
self-contained (due to lack of pkg), what specific problems were
intended to be solved, how package dependencies work, etc. Something
like a few-page white paper would be *really* helpful for those of us
who weren't at the BSDcan where this was discussed.
p, I am happy to generate a patch to make the discussion
concrete.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
at I am objecting to. The upside of that seems pretty dubious
and the downside is that it is much easier to accidentally put the
system into an inconsistent state. Is there a reason you want to have
such very fine discretization?
-Nathan
___
freebsd-cur
e) are way too
complex and will just lead to breakage. Can anyone provide an argument
against (1) or, alternatively, for (2)? (2) seems to add a lot of
complexity for no clear gain and I remain pretty confused about why it
was chosen.
-Nathan
On 04/18/16 20:17, Alfred Perlstein wrote:
Maybe wha
r than this issue. We need better tools than tar
and patch to manage the system; using pkg is a huge step forward.
-Nathan
thanks.
-Alfred
On 4/18/16 1:07 PM, Lev Serebryakov wrote:
On 18.04.2016 22:40, Glen Barber wrote:
This granularity allows easy removal of things that may not be wante
es to replacements with typical size (a few MB)
that are no larger than typical package updates for ports.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freeb
I just fixed this (r291877). Thanks for the report!
-Nathan
On 12/05/15 14:57, Oliver Pinter wrote:
Hi all!
After the "recent" wireless rewrite from Gleb, the enumeration of
wireless interfaces has gone from the bsdinstall.
This line:
https://github.com/HardenedBSD/hardenedBSD/blo
Yes. At http://people.freebsd.org/~nwhitehorn/cmake
-Nathan
On 10/07/15 14:28, Dimitry Andric wrote:
On 07 Oct 2015, at 16:44, Nathan Whitehorn wrote:
On 10/07/15 00:52, NGie Cooper wrote:
...
How do you reproduce this issue? Do you have any core dumps?
sudo bash
pkg install -y kyua
kyua
tart after this
upgrade. Recompiling it fixes the issue.
-Nathan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 03/23/15 09:47, Sergey V. Dyatko wrote:
On Mon, 23 Mar 2015 09:15:57 -0700
Nathan Whitehorn wrote:
On 03/23/15 09:06, Devin Teske wrote:
On Mar 22, 2015, at 10:47 PM, Sergey V. Dyatko
wrote:
Hi Devin,
Recently I'm trying to install FreeBSD CURRENT from bootonly image
( FreeBSD
probably be
removed from the FTP server.
3. You could reroll the ISO (just untar and run makefs again),
commenting out line 180 of /usr/libexec/bsdinstall/scripts/auto.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
the PC-BSD project
http://wiki.pcbsd.org/index.php/Creating_an_Automated_Installation_with_pc-sysinstall/10.0/en
(3) Please see "SCRIPTING" in bsdinstall(8).
Let me know if you have any trouble with it.
-Nathan
I am trying to work with a devops team who is very experienced
with settin
ipt has been replaced, by the way, and doesn't use BSD
labels anymore.
-Nathan
The request is: it would also be nice if 'make-memstick.sh' would allow
to pass from the command line some values for the size of the file
system to be created in the image; I modified it to fit my nee
depends
on BIOS? For proper X support I guess I have to wait for the Haswell
drivers)
You can use xf86-video-scfb for a VESA-like experience on EFI systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/
best to put this in the
core vt code.
-Nathan
diff --git a/sys/dev/fb/fbd.c b/sys/dev/fb/fbd.c
index ff2488d..923292a 100644
--- a/sys/dev/fb/fbd.c
+++ b/sys/dev/fb/fbd.c
@@ -316,6 +316,11 @@ fbd_attach(device_t dev)
return (ENXIO);
err = fbd_register(sc->sc_info
ed to a
willing developer would be hugely valuable for the usability of the
operating system on recent hardware. This is probably more important
even than Haswell graphics since without a driver, Haswell is merely
slow, whereas networking is completely broken.
-Nathan
RENT likely works, since it is based on code Kurt
submitted, but is untested on sparc since his original patch.
I think the more likely issue is that the boot blocks have bitrotted
somehow on SPARC. That's certainly consistent with the "Memo
Could you try adding -mno-avx2 to /sys/boot/amd64/Makefile.inc line 9?
-Nathan
On 09/23/14 07:28, Harald Schmalzbauer wrote:
Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime):
…
The problem I reported about in the first place is triggered by a faulty
loader.efi that
a
any kind of status update on Haswell? The wiki has the last
update 11 months ago and it's becoming a major useability issue for the
operating system.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
non-existant)
video BIOS, which fails. Is there any option like "NoInt10" you can turn
on in X configuration?
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 09/16/14 14:50, O. Hartmann wrote:
Am Tue, 16 Sep 2014 00:09:01 -0700
Nathan Whitehorn schrieb:
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing
On 09/15/14 22:51, O. Hartmann wrote:
Am Mon, 15 Sep 2014 17:39:26 -0700
Nathan Whitehorn schrieb:
On 09/15/14 17:36, Allan Jude wrote:
On 2014-09-15 20:05, O. Hartmann wrote:
Installing FreeBSD-11.0-CURRENT-amd64-20140903-r270990 on a Laptop works for
UEFI
fine. After I updated the
sure how 'in sync' boot1.efi (on the fat partiton) and
loader.efi have to be.
https://wiki.freebsd.org/UEFI
boot1.efi is designed never to need updating. (It also hasn't changed
since April)
-Nathan
___
freebsd-current@freebsd.org ma
d in early boot. This is potentially a problem for wireless
driver firmware modules, for example.
-Nathan
On 09/12/14 14:38, Bryan Drewery wrote:
"No" (as portmgr).
Ports should not be touching the base system like this. Let's NOT go
backwards and add a /bin/bash. In fact the
I'd point out that the perl ports have exactly such an option already
(putting links in /usr/bin, in this case). The CUPS port does too.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curren
thanks,
Can you test the memstick image? That uses the same bootblocks as an
installed system.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "free
On 08/19/14 12:02, Jean-Sébastien Pédron wrote:
On 19.08.2014 19:46, Nathan Whitehorn wrote:
On 08/19/14 09:28, Jean-Sébastien Pédron wrote:
o vt_vga introduces a new callback, vd_bitblt_text_t, which takes
as argument the text buffer, the dirty area, the font and the
On 08/19/14 09:28, Jean-Sébastien Pédron wrote:
On 19.08.2014 10:42, Jean-Sébastien Pédron wrote:
On 16.08.2014 01:51, Nathan Whitehorn wrote:
It also has bad effects on boot time. My desktop takes something like 3
times as long to boot after r269471. If it can't be fixed quickly, it
nee
It also has bad effects on boot time. My desktop takes something like 3
times as long to boot after r269471. If it can't be fixed quickly, it
needs to be reverted.
-Nathan
On 08/15/14 15:27, Adrian Chadd wrote:
keep in mind that the vt_vga code will be used for new VGA bring-up on
har
it's still broken. There's a related PR at
http://bugs.freebsd.org/192452 and, I suspect, 192456. Aleksandr, would
you mind reverting this reversion? It seems to have created a lot of
problems.
-Nathan
___
freebsd-current@freebsd.org ma
On 08/06/14 09:52, Roger Pau Monné wrote:
On 06/08/14 16:35, Nathan Whitehorn wrote:
On 2014-08-06 02:35, Roger Pau Monné wrote:
On 06/08/14 02:37, Nathan Whitehorn wrote:
Kernels with r269580 will panic when loading the radeonkms driver in
pmap_page_set_memattr(). This probably indicates a
On 2014-08-06 02:35, Roger Pau Monné wrote:
On 06/08/14 02:37, Nathan Whitehorn wrote:
Kernels with r269580 will panic when loading the radeonkms driver in
pmap_page_set_memattr(). This probably indicates a bug in radeonkms,
but
the system is unusable in the meantime.
-Nathan
I seem to be
Kernels with r269580 will panic when loading the radeonkms driver in
pmap_page_set_memattr(). This probably indicates a bug in radeonkms, but
the system is unusable in the meantime.
-Nathan
___
freebsd-current@freebsd.org mailing list
http
On 07/26/14 12:40, Baptiste Daroussin wrote:
On Sat, Jul 26, 2014 at 11:39:46AM -0700, Nathan Whitehorn wrote:
On 07/24/14 23:56, John Hay wrote:
On Wed, Jul 23, 2014 at 04:42:51PM +0200, Baptiste Daroussin wrote:
Hi all,
I'm very please to announce the release of pkg 1.3.0
This versi
t the architecture from the kernel, with a
manual override for cross-installs? It seems like that would prevent
cases like this permanently.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curre
I'd point out that, as of last week, the standard -CURRENT ISOs (and
generate-release.sh script) make EFI-bootable media by default. All the
snapshots should have this done already, for instance.
-Nathan
On 07/12/14 03:09, Anders Bolt-Evensen wrote:
I also got a message like that when I b
On 07/11/14 15:50, Matthew D. Fuller wrote:
On Fri, Jul 11, 2014 at 03:38:56PM -0700 I heard the voice of
Nathan Whitehorn, and lo! it spake thus:
I don't honestly remember where that number came from. It's at line
72 of usr.sbin/bsdinstall/partedit/partedit_x86.c. If 128 works
b
?
Strange, resizing the freebsd-boot to 128k solved my issue. why default
slice size making such issue?
Good question. Perhaps Nathan (cc'd) knows?
I don't honestly remember where that number came from. It's at line 72
of usr.sbin/bsdinstall/partedit/partedit_x86.c. If 128 wo
ht would be rather a problem.
GENERIC is such a kernel as of a few days ago. The idea is to provide a
transition mechanism for people who want syscons for whatever reason but
also want to, say, use KMS drivers or boot with EFI without building a
new kernel.
-Nathan
___
sYb etc
I thought the label was a nice way to do it, but it backfired.
Oh, zfsboot uses labels? The UFS partition editor never has, mostly for
this reason. Sorry for spreading misinformation -- I'm not really
familiar with the ZFS code.
-Nathan
ose should not make the others
disappear then. Only opening ada0 for writting would make them disappear.
Indeed. This would also fix some tasting races, allow programmatic
retrieval of the label device from gpart, and expand label device
support from GPT to all partition schemes supported by gpart
while it
does set labels on the disk, it does not use them.
-Nathan
I put the following into /boot/loader.conf to make the system more
sane:
kern.geom.label.disk_ident.enable=0
-Kurt
___
freebsd-current@freebsd.org mailing list
http://lists.freebs
The attached patch enables login shells on ttyu0 if ttyu0 is a kernel
console. It should preserve existing behavior (i.e. have no shell)
otherwise. Testing would be appreciated. If no problem reports are
received, I will commit this on Friday. Thanks!
-Nathan
Index: etc/etc.amd64/ttys
would simplify a lot of code and most of the
code for the non-kbdmux case is heavily bitrotten at this point (see here).
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
st set the default for acpi_throttle and p4tcc in HEAD to disabled
by adding these line to the default /boot/device.hints. If you want them
back, editing your device.hints will restore them. This can be reverted
if many people want throttling enabled by default, but all I have
PowerPC) use it in conjunction with cpufreq.
But seriously, let's just pull tcc from GENERIC. I'll do it next week
unless I hear any objections.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
x
well and TCC is not effective, as mentioned earlier in this thread.
Is there any reason that TCC is on by default, actually? It seems like
an anti-feature.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
Thanks for the report. It should be fixed now. Apologies for the breakage!
-Nathan
On 04/12/14 22:16, Thomas Hoffmann wrote:
Reference:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=9766061+0+current/svn-src-head
An attempt to make buildworld on -CURRENT amd64 at r264394 failed with the
y freezes
completely.
All three systems work fine with the old ofwfb (though the very slow
scrolling makes booting take twice as long as with syscons) and I'm a
bit at a loss to debug this correctly. Any ideas?
-Nathan
___
freebsd-current@freebsd.org
deal with it.
>
> Roger.
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
Attaching s
On 01/06/14 18:36, Michael Dexter wrote:
> On 1/5/14 1:04 PM, Nathan Whitehorn wrote:
>> On 12/01/13 07:34, Jilles Tjoelker wrote:
>>> On Sat, Nov 30, 2013 at 04:36:18PM -0600, Nathan Whitehorn wrote:
>>>> This took much longer than I'd anticipated, but the patc
On 12/01/13 07:34, Jilles Tjoelker wrote:
> On Sat, Nov 30, 2013 at 04:36:18PM -0600, Nathan Whitehorn wrote:
>> This took much longer than I'd anticipated, but the patch to init is
>> attached. I chose not to make the changes to init rather than
>> getttyent() and friend
On 12/17/13 17:28, Aleksandr Rybalko wrote:
On 18.12.2013 01:27, Nathan Whitehorn wrote:
On 12/17/13 15:32, Aleksandr Rybalko wrote:
On Tue, 17 Dec 2013 14:12:05 -0600
Nathan Whitehorn wrote:
On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising
, only based on base system and
sources?
Thanks
matthias
There's svnlite in -CURRENT now.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &qu
On 12/17/13 15:32, Aleksandr Rybalko wrote:
On Tue, 17 Dec 2013 14:12:05 -0600
Nathan Whitehorn wrote:
On 12/17/13 14:07, Steve Kargl wrote:
On Mon, Dec 16, 2013 at 12:20:53PM +0100, Niclas Zeising wrote:
To get VT switching when using KMS drivers (ATI, Intel) please use
newcons: https
snow (or at least it did
the last time I tried it).
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
should
fix it for people just upgrading now.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 12/10/13 17:41, Douglas Gilbert wrote:
On 13-12-10 10:09 PM, Nathan Whitehorn wrote:
Modern SCSI hardware often uses 64-bit logical units (LUNs). The
patch found at
http://people.freebsd.org/~nwhitehorn/lun64.diff widens the type of
lun_id_t to
64 bits, bumps CAM_VERSION, and begins
issues, I will commit this on Friday.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On 11/11/13 14:57, Teske, Devin wrote:
> On Nov 11, 2013, at 12:54 PM, Nathan Whitehorn wrote:
>
>> On 11/11/13 14:30, Nathan Whitehorn wrote:
>>> On 11/11/13 14:18, Teske, Devin wrote:
>>>> -BEGIN PGP SIGNED MESSAGE-
>>>> Hash: SHA512
>>
On 11/11/13 18:22, Julian Elischer wrote:
On 11/11/13, 1:32 PM, Nathan Whitehorn wrote:
On 11/11/13 15:19, Teske, Devin wrote:
Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout...
Should we do the quick patch to change the default
from /boot/boot0 to /boot/mbr:
Index: zfsboot
On 11/11/13 15:51, Teske, Devin wrote:
On Nov 11, 2013, at 1:43 PM, Nathan Whitehorn wrote:
On 11/11/13 15:39, Teske, Devin wrote:
On Nov 11, 2013, at 1:32 PM, Nathan Whitehorn wrote:
On 11/11/13 15:19, Teske, Devin wrote:
Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout
On 11/11/13 15:39, Teske, Devin wrote:
On Nov 11, 2013, at 1:32 PM, Nathan Whitehorn wrote:
On 11/11/13 15:19, Teske, Devin wrote:
Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout...
Should we do the quick patch to change the default
from /boot/boot0 to /boot/mbr:
Index: zfsboot
On 11/11/13 15:35, Allan Jude wrote:
On 2013-11-11 16:32, Nathan Whitehorn wrote:
On 11/11/13 15:19, Teske, Devin wrote:
Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout...
Should we do the quick patch to change the default
from /boot/boot0 to /boot/mbr:
Index: zfsboot
probably best done as a post-install
config step ("Install FreeBSD boot manager" or something), which also
means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freeb
h decides what to do autonomously
based on a number of driver and platform-dependent things including, but
not limited to, kenv (loader variables, for instance).
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
On 11/11/13 14:30, Nathan Whitehorn wrote:
On 11/11/13 14:18, Teske, Devin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Nov 11, 2013, at 11:46 AM, Michael Dexter wrote:
Hello all,
I have been experimenting with various BSD and GNU/Linux boot media
under bhyve and noticed that
1 - 100 of 299 matches
Mail list logo
