On Saturday, June 8, 2019, Konstantin Belousov wrote:
> On Sat, Jun 08, 2019 at 02:57:27AM +, Rick Macklem wrote:
> > Hi,
> >
> > I've started working of a copy_file_range() syscall for FreeBSD. I think
> I have the
> > kernel patched and ready for some testing.
> > However, I'm confused abou
On Sunday, March 17, 2019, Johannes Lundberg wrote:
> On Sun, Mar 17, 2019 at 21:35 Emmanuel Vadot
> wrote:
>
> > On Sun, 17 Mar 2019 16:32:43 +
> > Johannes Lundberg wrote:
> >
> > >
> > > On 3/17/19 3:34 PM, Greg V wrote:
> > > >
> > > >
> > > > On Sun, Mar 17, 2019 at 3:07 PM, Johannes L
On 1/12/19, Oliver Pinter wrote:
> On 1/12/19, Dimitry Andric wrote:
>> On 12 Jan 2019, at 19:40, Oliver Pinter
>> wrote:
>>> According the following comment in ${SRCTOP}/sys/conf/kern.mk:
>>>
>>> #
>>> # Add -gdwarf-2 when compiling -g. The
On 1/12/19, Dimitry Andric wrote:
> On 12 Jan 2019, at 19:40, Oliver Pinter
> wrote:
>> According the following comment in ${SRCTOP}/sys/conf/kern.mk:
>>
>> #
>> # Add -gdwarf-2 when compiling -g. The default starting in clang v3.4
>> # and gcc 4.8 is to ge
D project switched to elftoolchain and mostly to LLVM
tools. LLDB is compiled by default on 13-CURRENT (~ HEAD) and the kgdb
has moved under the libexec directory, to hide them from the common
usage.
Thanks,
Oliver
___
freebsd-current@freebsd.org mailing
Hi!
Before you do anything take a look in /var/db/backup directory - or just
try to find the backups with find /var -name "group*" command.
On Sunday, January 6, 2019, White Wizard wrote:
> Hi,
> i break my config file, peraps /etc/group when un mergemaster.
> No concentrate to that i do and as
On 11/4/18, Rebecca Cran wrote:
> On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote:
>
>> it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi
>> is
>> hard one of course. But then again, it is problem only when we can not
>> setup EFI bootmanager variables ? the bootx
On 10/16/18, Oliver Pinter wrote:
> On 10/6/18, David Wolfskill wrote:
>> On Wed, Oct 03, 2018 at 03:28:45PM +0200, Jakob Alvermark wrote:
>>> ...
>>> This is probably not a proper fix, but it helps to understand the
>>> problem.
>>>
>>> C
On 10/6/18, David Wolfskill wrote:
> On Wed, Oct 03, 2018 at 03:28:45PM +0200, Jakob Alvermark wrote:
>> ...
>> This is probably not a proper fix, but it helps to understand the
>> problem.
>>
>> Could you post the output of 'sysctl dev.hdaa' with and without the
>> patch so we can see what's diff
On Sunday, August 26, 2018, blubee blubeeme wrote:
> On Sun, Aug 26, 2018 at 4:32 PM Hans Petter Selasky
> wrote:
>
> > On 8/26/18 3:20 AM, blubee blubeeme wrote:
> > > Have you or anyone working on this drm-legacy-kmod stuff done any
> > testings
> > > of how this will affect current users?
> >
Hi!
Seems like this patch fixed the boot issue on Dell e5440 with UEFI.
Once you get to MFC, please X-MFC-with the following patch:
commit dfe1112fa878c5d8fa0605d1de10c96ecc993569
Author: rlibby
Date: Fri Jul 21 17:11:36 2017 +
__pcpu: gcc -Wredundant-decls
Pollution from counte
On 8/14/18, Matthias Gamsjager wrote:
> Hi list,
>
> just compiled current and after reboot into the new kernel the machine
> reboots itself at the marked line below. No further info as the reset is
> sudden. Reboot with the old kernel from 12 aug works. Removed all kernel
> modules but with no re
On 8/3/18, Johannes Lundberg wrote:
> On Fri, Aug 3, 2018 at 9:34 PM Oliver Pinter
>
> wrote:
>
>> Hi!
>>
>> On 8/3/18, Johannes Lundberg wrote:
>> > Hi
>> >
>> > After install new kernel+world built from today's checkout I keep
Hi!
On 8/3/18, Johannes Lundberg wrote:
> Hi
>
> After install new kernel+world built from today's checkout I keep getting
> the same crash over and over. Never had this problem before. The previous
> kernel was from 3 weeks ago.
>
> Looks familiar to anyone?
Have you an Intel Broadwell or newer
On Sunday, July 8, 2018, Ian Lepore wrote:
> On Sun, 2018-07-08 at 21:08 +0200, Oliver Pinter wrote:
> > Hi!
> >
> > Have you or Warner any update on this code?
> >
> > On Thursday, April 12, 2018, Eric McCorkle
> > wrote:
> >
>
> Are you aware
sh wrote:
> > > Still reviewing the code. I'm worried it's too i386 specific and it
> > > conflicts with some work I'm doing. I'll have a list of actionable
> > > critiques this week.
> > >
> > > Warner
> > &
On Thursday, June 14, 2018, Mike Tancsa wrote:
> On 6/14/2018 11:03 AM, Konstantin Belousov wrote:
> > I am not sure about only microcode update. Depending on the BIOS
> > vendor and current BIOS, you may need all three: BIOS update, microcode
> > update using cpucontrol/devcpu-data, and running
On Friday, June 1, 2018, Pete Wright wrote:
>
>
> On 05/31/2018 15:34, Oliver Pinter wrote:
>
>> On Thursday, May 31, 2018, Johannes Lundberg wrote:
>>
>> On Thu, May 31, 2018 at 4:34 PM Joe Maloney
>>> wrote:
>>>
>>> I personally
On Thursday, May 31, 2018, Johannes Lundberg wrote:
> On Thu, May 31, 2018 at 4:34 PM Joe Maloney
> wrote:
>
> > I personally wish that more drivers, and firmware were separated from
> > base.
> >
> >
> I'm not a committer
>
>
If you are not a committer, how and why want to remove drm2 from t
On 5/21/18, Oliver Pinter wrote:
> On 5/21/18, Steve Kargl wrote:
>> On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote:
>>>
>>> On 05/21/2018 10:07, Steve Kargl wrote:
>>> > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote:
&g
On 5/21/18, Steve Kargl wrote:
> On Mon, May 21, 2018 at 10:29:54AM -0700, Pete Wright wrote:
>>
>> On 05/21/2018 10:07, Steve Kargl wrote:
>> > On Mon, May 21, 2018 at 02:40:50AM +0300, Rozhuk Ivan wrote:
>> >> On Sun, 20 May 2018 21:10:28 +0200
>> >
On Sunday, May 20, 2018, Niclas Zeising wrote:
> On 05/20/18 18:40, Steve Kargl wrote:
>
>> On Fri, May 18, 2018 at 02:03:32PM -0600, Warner Losh wrote:
>>
>>> On Fri, May 18, 2018 at 1:30 PM, Steve Kargl <
>>> s...@troutmask.apl.washington.edu> wrote:
>>>
>>> On Fri, May 18, 2018 at 09:14:24PM +
On Friday, May 18, 2018, Konstantin Belousov wrote:
> On Fri, May 18, 2018 at 09:33:40PM +0100, Johannes Lundberg wrote:
> > On Fri, May 18, 2018 at 9:22 PM, Ben Widawsky wrote:
> >
> > > On 18-05-18 14:15:03, Warner Losh wrote:
> > > > On Fri, May 18, 2018 at 2:12 PM, Johannes Lundberg <
> joha
Hi!
Is there any update regarding the rebase or the inclusion to base system?
On 3/28/18, Eric McCorkle wrote:
> I'll do another rebase from head just to be sure
>
> On March 28, 2018 3:23:23 PM EDT, Warner Losh wrote:
>>It's on my list for nexr, finally. I have an alternate patch for
>>loader.e
On Monday, December 25, 2017, Dimitry Andric wrote:
> On 25 Dec 2017, at 21:16, O. Hartmann wrote:
> >
> > I have installed most recent CURRENT as of r327219 with LLD_IS_LD=YES set
> > via /etc/src.conf.
> >
> > I try to find some options and tried "man ld", "man lld" and "ld.lld".
> In the the
On Tuesday, December 19, 2017, Warner Losh wrote:
> On Dec 18, 2017 6:06 PM, "Rodney W. Grimes" <
> freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
>
> > On Mon, Dec 18, 2017 at 3:12 PM, Mark Millard
> wrote:
> >
> > > Warner Losh imp at bsdimp.com wrote on
> > > Mon Dec 18 20:29:45 UTC 2017 :
> > >
Hi Adrian!
How big effort is to update he in-tree wpa_supplicant/hostapd to the
latest supported version?
Is there any known regression / feature loss when do the upgrade?
On 10/16/17, Adrian Chadd wrote:
> Right, there are backported patches against 2.6, but we're running 2.5
> in contrib/ .
>
On Monday, June 26, 2017, Shawn Webb wrote:
> This is on the latest HardenedBSD 12-CURRENT on one of my servers:
>
> [141] panic: sleepq_add: td 0xf80008d20560 to sleep on wchan
> 0xf803b7d4e810 with sleeping prohibited
> [141] cpuid = 5
> [141] time = 1498436043
> [141] KDB: stack backtr
On 11/25/16, John Baldwin wrote:
> I plan to enable EARLY_AP_STARTUP on x86 in a week on HEAD. Some folks
> have been testing it for the last week or so which has exposed some
> additional things to fix. I think I've resolved most of those in one
> way or another, but it will make things smoothe
rc.d/netif restart && /etc/rc.d/routing restart
Perhaps we could introduce a wrapper to be used with:
# service network restart
oliver@local ~ % cat /etc/rc.d/network
#!/bin/sh
# PROVIDE: network
# REQUIRE: netif routing
# KEYWORD:
.0 worked but has no output opon boot in
11.0.
Thanks
Oliver
___
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"
but no luck either.
I would love to have 11.0-RELEASE on this device but have no clue how to
narrow down my issue (and debugging FreeBSD anyway). Any help is highly
appreciated.
Thanks in advance
Oliver
[1]: https://files.oliverboettcher.de/s/8vtg5shAPpY9J6M
signature.asc
Description: OpenPGP
On 3/1/16, Carsten Kunze wrote:
> Conrad Meyer wrote:
>
>> "[1] iwn0: mem 0xf7b0-0xf7b01fff
>> irq 18 at device 0.0 on pci3" is fine; "module iwn already present!"
>> is fine.
>>
>> What makes you say it isn't recognized or doesn't work?
>
> ifconfig iwn0 says "interface iwn0 does not e
necessary files.
Did anyone stumble across the same problem?
Thanks
-Oliver
___
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 2/6/16, Konstantin Belousov wrote:
> On Fri, Feb 05, 2016 at 07:34:02PM +0100, Oliver Pinter wrote:
>> Not yet tested, but possible fix:
>>
>> diff --git a/sys/kern/init_main.c b/sys/kern/init_main.c
>> index cb952da..25bae84 100644
>> --- a/sys/kern/init_mai
On 2/5/16, Oliver Pinter wrote:
> Hi all!
>
> I used this gdb macro, to traverse the proc list, and print out the
> relevant p_flag's flags:
>
> set $curr_proc=0
> def next_proc
> if $curr_proc == 0
> set $curr_proc = allproc.lh_first
>
Hi all!
I used this gdb macro, to traverse the proc list, and print out the
relevant p_flag's flags:
set $curr_proc=0
def next_proc
if $curr_proc == 0
set $curr_proc = allproc.lh_first
else
set $curr_proc = $curr_proc.p_list.le_next
end
On 1/26/16, Eric van Gyzen wrote:
> FreeBSD Folks:
>
> I am currently scoping the effort to add hot-plug PCIe support to
> FreeBSD. Is anyone else currently working on this or aware of any
> design, code, or other effort available outside the tree?
>
> FYI, here are perhaps the most interesting r
Hello,
FreeBSD-11.0-CURRENT-arm-armv6-RPI2-20160121-r294499 did not boot on a Rasberry
Pi 2 B with the Gert VGA 666 adaptor connected to the Raspberry's GPIO port.
This adaptor basically is a passive resistor network, using most of the GPIO's
pins.
My guess is that FreeBSD tries to activate th
On 12/24/15, Konstantin Belousov wrote:
> On Thu, Dec 24, 2015 at 08:29:20AM -0700, Ian Lepore wrote:
>> We had exactly this symptom -- long delay with spincursor before
>> loading the kernel -- on arm systems when we first enabled forth in
>> loader. The problem turned out to be the fact that lo
On 12/28/15, Matthias Apitz wrote:
> El día Monday, December 28, 2015 a las 02:12:29PM +0100, Matthias Apitz
> escribió:
>
>>
>> Hello,
>>
>> I downloaded the ISO for the above version and when I boot it in a
>> VMWare it panics reproduceable after trying to mount the root; see the
>> message capt
On Monday, December 28, 2015, Matthias Apitz wrote:
>
> Hello,
>
> I downloaded the ISO for the above version and when I boot it in a
> VMWare it panics reproduceable after trying to mount the root; see the
> message captured in the last screens:
>
> http://www.unixarea.de/panic-01.jpg
> http://w
On Monday, December 28, 2015, Sam Kumar wrote:
> Hello,
> I am working with the code for the TCP Stack. I noticed that support for
> Challenge Acks have been added since the latest release (10.2.0), and I
> think I may have found a bug in how they relate to TCP timestamps. All line
> numbers belo
On 12/24/15, Vijay Rajah wrote:
>
>
> On 12/24/15 12:22 PM, Ian Smith wrote:
>> ~2 minutes delay there. sendmail (mta and msp both) at least
>> are unhappy about your hostname, and sleep on it. I don't know whether
>> that's significant or related to the longer delay you report. I just
>> ski
IOPL = 0
> > current process = 71325 (sh)
> > trap number = 12
> > panic: page fault
> > cpuid = 1
> > KDB: stack backtrace:
> > [...]
> > Uptime: 13d20h43m20s
> > [...]
>
> Hey Fabien,
>
> I'm glad you've seen t
Yes, it's a HardenedBSD commit. Currently only a workaround, because I have
now lesser time for the real fix in this month.
Are you running on ZFS?
On Wednesday, December 16, 2015, Fabian Keil
wrote:
> Oliver Pinter > wrote:
>
> > Is this with latest 11-CURRENT or 1
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/blob/hardened/current/master/usr.sbin/bsdinstall/scripts/netconfig#L52
return no entry, because the wlan interface not
On 11/16/15, Shawn Webb wrote:
> Hey All,
>
> I'm experiencing a buildkernel failure only when doing a multi-job build
> (-jN). Doing a single-job build works fine. Below is the error I'm
> getting.
>
> Begin Log
> In file included from
> /usr/src/sys/modules/tests/framework/../../../tes
On Sun, Nov 8, 2015 at 12:06 PM, Ulrich Spörlein wrote:
> 2015-11-08 11:32 GMT+01:00 Ulrich Spörlein :
>> 2015-11-08 2:51 GMT+01:00 Alfred Perlstein :
>>> Uli,
>>>
>>> One of the biggest concerns I've heard from folks using FreeBSD's git mirror
>>> is that the hashes can change.
>>>
>>> I hav
On Tue, Oct 20, 2015 at 10:07 AM, Thomas Mueller
wrote:
> I was trying to test the new i915 graphics driver but got stuck in building
> and installing the userland:
>
> /usr/share/man/man2/mknodat.2 -> /usr/share/man/man2/mknod.2
> /usr/share/man/man2/munlock.2 -> /usr/share/man/man2/mlock.2
> /u
CC+= swills
On 9/17/15, Oliver Pinter wrote:
> Hi All!
>
> We got this panic on modified FreeBSD (we not touched the ZFS part).
>
> panic: solaris assert: error || lr->lr_length <= zp->z_blksz, file:
> /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.
On 9/16/15, Gary Jennejohn wrote:
> On Tue, 15 Sep 2015 19:32:35 +0900
> Brendan Sechter wrote:
>
>> When compiling a FreeBSD 11.0-CURRENT kernel, what is required to change
>> the keymap used in single user mode? __I originally asked this question on
>> the FreeBSD forums, but was bounced to the
On 9/17/15, Michael Gmelin wrote:
>
>
>> On 17 Sep 2015, at 20:23, Russell L. Carter wrote:
>>
>>
>>
>>> On 09/17/15 10:40, Matthias Apitz wrote:
>>> El dÃa Thursday, September 17, 2015 a las 11:02:07AM -0400, Kris Moore
>>> escribió:
>>>
On 09/17/2015 09:48, Matthias Apitz wrote:
> El
Hi All!
We got this panic on modified FreeBSD (we not touched the ZFS part).
panic: solaris assert: error || lr->lr_length <= zp->z_blksz, file:
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c,
line: 1355
cpuid = 6
KDB: stack backtrace:
#0 0x80639527 at kdb_backtrace+0
On 8/31/15, Jean-Sébastien Pédron wrote:
> On 30.08.2015 21:05, Andriy Gapon wrote:
>> On 30/08/2015 21:37, Oliver Pinter wrote:
>>> You have a running Xorg with radeonkms driver, and this issue
>>> occurrence under high load (for example parallel buildworld)?
>
On 8/30/15, Andriy Gapon wrote:
>
> I've got the following kernel panic seemingly at random.
> I have been using the kernel for about a week without any issues and I
> wasn't
> doing anything special when the panic occurred.
> Does this panic ring any bells? Could the problem be already fixed by
On 8/20/15, Warner Losh wrote:
>
>> On Aug 20, 2015, at 9:38 AM, Oliver Pinter
>> wrote:
>>
>> On 8/20/15, Dimitry Andric wrote:
>>> On 20 Aug 2015, at 00:56, Oliver Pinter
>>> wrote:
>>>> I got this error, when I try t
On 8/20/15, Dimitry Andric wrote:
> On 20 Aug 2015, at 00:56, Oliver Pinter
> wrote:
>> I got this error, when I try to build recent 11-CURRENT with gcc on amd64
>> box:
>>
>> --- delay.o ---
>> cc -O2 -pipe -fPIC -mno-red-zone
>> -I/usr/data/sour
T system, which builded with clang.
Thanks,
Oliver
___
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"
Hi!
On 7/27/15, Matthias Apitz wrote:
>
> Hello,
>
> Yesterday I grabbed r285885 from SVN and launched a
>
> # make -j2 buildworld
>
> which is still running after 19 hours on a server of 2 CPU of the type
> Intel(R) Core(TM)2 Extreme CPU X9100 @ 3.06GHz and 4 GByte memory.
>
> Last time in Janu
On 7/9/15, NGie Cooper wrote:
> On Thu, Jul 9, 2015 at 1:41 AM, Konstantin Belousov
> wrote:
>> On Thu, Jul 09, 2015 at 08:27:17AM +1000, Peter Jeremy wrote:
>>> I'm not sure if we want to explicitly document the conditions under
>>> which
>>> gettimeofday() (or clock_gettime()) are implemented i
On 7/8/15, Konstantin Belousov wrote:
> On Wed, Jul 08, 2015 at 11:53:39AM +0200, Oliver Pinter wrote:
>> On 7/8/15, O'Connor, Daniel wrote:
>> >
>> >> On 8 Jul 2015, at 08:11, Garrett Wollman
>> >>
>> >> wrote:
>> >> Perha
On 7/8/15, O'Connor, Daniel wrote:
>
>> On 8 Jul 2015, at 08:11, Garrett Wollman
>> wrote:
>> Perhaps the test was (erroneously) written to assume that
>> gettimeofday() was a system call, and could therefore detect invalid
>> pointers and return [EFAULT]. This has not been the case for some
>>
On Wed, Jul 8, 2015 at 12:09 AM, Garrett Cooper wrote:
>
>> On Jul 7, 2015, at 15:00, Oliver Pinter
>> wrote:
>>
>> Hi all!
>>
>> We discovered that one of the kyua test failing from gettimeofday tests.
>> The error is reproducible on recent snaps
Hi all!
We discovered that one of the kyua test failing from gettimeofday tests.
The error is reproducible on recent snapshot from 11-CURRENT:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/amd64/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-20150630-r284969-disc1.iso
root@freebsd:~ # cat test-gt
On Mon, Jul 6, 2015 at 10:26 PM, Simon J. Gerraty wrote:
> Oliver Pinter wrote:
>> We got this build failure, when two release make release running in parallel:
>
> Can you elaborate what you mean by "two release make release" ?
Two concurrent make release would be the
the temproot environment
*** Error code 1
Stop.
make[1]: stopped in /jenkins/workspace/HardenedBSD-master-amd64/release
*** Error code 1
I could work it around with build order dependency or with chrooted builds...
Thanks,
Oliver
___
freebsd-cur
Hi all!
I got this build warning with ~recent 11-CURRENT:
--- xen-locore.o ---
/usr/data/source/git/opBSD/opBSD.git/sys/amd64/amd64/xen-locore.S:45:1:
warning: DWARF2 only supports one section per compilation unit
.section __xen_guest
^
/usr/data/source/git/opBSD/opBSD.git/sys/amd64/amd64/xen-loc
On 6/13/15, Glen Barber wrote:
> [re@ CC'd]
>
> On Sat, Jun 13, 2015 at 02:34:37PM +0200, Oliver Pinter wrote:
>> Hi all!
>>
>> We got build error with custom BRANCH= in newvers.sh. The release
>> process unable to generate the ISO files but they not stoppe
Hi all!
We got build error with custom BRANCH= in newvers.sh. The release
process unable to generate the ISO files but they not stopped with
error, just ignore them, and continue with memstick images.
cp /jenkins/workspace/HardenedBSD-stable-master-amd64/release/rc.local
bootonly/etc
sh
/jenkin
On Mon, Jun 1, 2015 at 9:55 PM, Oliver Pinter
wrote:
> On Mon, Jun 1, 2015 at 9:47 PM, Oliver Pinter
> wrote:
>> On Mon, Jun 1, 2015 at 5:37 PM, Gleb Smirnoff wrote:
>>> Hi!
>>>
>>> I've converted the ath(4), probably the most complex ieee80211 dri
On Mon, Jun 1, 2015 at 9:47 PM, Oliver Pinter
wrote:
> On Mon, Jun 1, 2015 at 5:37 PM, Gleb Smirnoff wrote:
>> Hi!
>>
>> I've converted the ath(4), probably the most complex ieee80211 driver.
>>
>> The updated diff is uploaded to https://reviews.freebs
On Mon, Jun 1, 2015 at 5:37 PM, Gleb Smirnoff wrote:
> Hi!
>
> I've converted the ath(4), probably the most complex ieee80211 driver.
>
> The updated diff is uploaded to https://reviews.freebsd.org/D2655.
>
> Pretty sure it will panic or fail on first try :) Nevertheless,
> asking for your help.
Hi Hans!
On 5/10/15, Hans Petter Selasky wrote:
> On 05/10/15 18:53, Wolfgang Zenker wrote:
>> Hi,
>>
>> * Hans Petter Selasky [150510 14:47]:
>>> On 05/09/15 23:05, Wolfgang Zenker wrote:
* Allan Jude [150508 16:29]:
> [..]
> My experience is a little different.
>>
> When susp
On 4/26/15, Oliver Pinter wrote:
> On 4/23/15, Oliver Pinter wrote:
>> Rui, FYI:
>> http://w1.fi/security/2015-1/wpa_supplicant-p2p-ssid-overflow.txt
>>
>> On Sun, Apr 19, 2015 at 9:41 PM, Rui Paulo wrote:
>>> Hi,
>>>
>>> Please test the
On 4/23/15, Oliver Pinter wrote:
> Rui, FYI: http://w1.fi/security/2015-1/wpa_supplicant-p2p-ssid-overflow.txt
>
> On Sun, Apr 19, 2015 at 9:41 PM, Rui Paulo wrote:
>> Hi,
>>
>> Please test the new wpa_supplicant/hostapd. Here's the patch against
>>
Rui, FYI: http://w1.fi/security/2015-1/wpa_supplicant-p2p-ssid-overflow.txt
On Sun, Apr 19, 2015 at 9:41 PM, Rui Paulo wrote:
> Hi,
>
> Please test the new wpa_supplicant/hostapd. Here's the patch against FreeBSD
> HEAD:
>
> https://people.freebsd.org/~rpaulo/wpa-2.4.diff
>
> Thanks,
> -
Hi all!
I just found the line in the subject in our jenkinsbuild log in both
amd64 and i386 case (we don't modified these files):
http://nyi-01.build.hardenedbsd.org:8180/jenkins/job/HardenedBSD-master-i386/56/console
http://nyi-01.build.hardenedbsd.org:8180/jenkins/job/HardenedBSD-master-amd64/
On 4/11/15, David Wolfskill wrote:
> Running:
> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1565
> r281363M/281366:1100068: Fri Apr 10 05:41:13 PDT 2015
> r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY i386
>
> World builds OK; kernel is OK up to:
>
> ...
s
As dirty hack, try to save two state of MBR, one when FreeBSD selected
(MBR.FBSD) , and one when Win95 selected (MBR.W95).
When the windows booted up properly, then write the MBR.FBSD to the
disc, on the same schema do the reverse on freebsd with dd.
http://www.fccps.cz/download/adv/frr/wipembr.ht
Is there any special settings / requirements for xorg.conf to enable
the palm detection and similar features?
On Wed, Apr 8, 2015 at 3:13 PM, Shawn Webb wrote:
> On Wed, 2015-04-08 at 00:19 -0700, Rui Paulo wrote:
>> Hi,
>>
>> The attached patch adds support for newer touchpad features and implem
On Mon, Mar 23, 2015 at 12:32 AM, Marek Novotny
wrote:
> Hi group,
>
> New to this group, and new to FreeBSD via PC-BSD. Really like it so far.
> Sorry if this has been asked to death already. Levono has their new T450
> with the 5th gen intel Broadwell i5 processor. I bought it with the hopes of
On Sat, Feb 28, 2015 at 11:19 PM, Garrett Cooper wrote:
> On Feb 28, 2015, at 14:15, Garrett Cooper wrote:
>
>> On Feb 28, 2015, at 13:56, Ryan Stone wrote:
>>
>>> On Sat, Feb 28, 2015 at 4:51 PM, Garrett Cooper
>>> wrote:
I’m not sure about key_map — are you building with syscons or vt?
On Sat, Feb 28, 2015 at 10:25 PM, Ryan Stone wrote:
> I updated my source tree this morning and now I'm seeing this compile
> error in "make tinderbox";
>
> /repos/users/rstone/freebsd/sys/dev/atkbdc/atkbd.c:382:26: error: use of
> undecla
> red identifier 'key_map'; did you mean 'keymap'?
>
On Wed, Feb 25, 2015 at 9:34 PM, John Baldwin wrote:
> On Monday, February 02, 2015 12:21:19 PM Roger Pau Monné wrote:
>> Hello,
>>
>> r272959 broke compatibility with mfsBSD that stores the default network
>> config file in /etc/rc.conf.d/network. In order to fix that load the
>> network config f
On Tue, Feb 17, 2015 at 11:19 PM, Fabian Keil
wrote:
> John-Mark Gurney wrote:
>
>> If you are running a current kernel r273872 or later, please upgrade
>> your kernel to r278907 or later immediately and regenerate keys.
>
> I tried ...
>
> start_init: trying /sbin/init
> <118>[20] Setting hostuu
On Tue, Jan 27, 2015 at 6:21 AM, Yue Chen wrote:
> My purpose is to modify kernel function instructions directly through
> memory at runtime.
>
> First I use "objdump -S kernel" to see the function names and their
> addresses. And then I use pointers to peek into the content at certain
> function
Hi!
I got this error, when I try to make distribution*:
cd /target/usr/src/etc/sendmail; make distribution
install -o root -g wheel -m 644
/target/usr/src/etc/sendmail/freebsd.mc freebsd.cf /target/etc/mail
install: freebsd.cf: No such file or directory
*** Error code 71
Stop.
make[3]: stopped i
On 1/7/15, Oliver Pinter wrote:
> Hi!
>
> I got this error, when I try to make distribution*:
>
> cd /target/usr/src/etc/sendmail; make distribution
> install -o root -g wheel -m 644
> /target/usr/src/etc/sendmail/freebsd.mc freebsd.cf /target/etc/mail
> install: fre
/HardenedBSD_Master/sys/HARDENEDBSD
*** [buildkernel] Error code 2
Seems like, the error affected the i386 case.
On Thu, Jan 1, 2015 at 6:53 PM, Dimitry Andric wrote:
> On 01 Jan 2015, at 18:35, Oliver Pinter wrote:
>> We at HardenedBSD got this error, with out jenkins instance:
>>
>
4160d..f74291e user/marcel/libvdsk -> freebsd/user/marcel/libvdsk
aeef35a..7a5b8d5 user/pho/stress2 -> freebsd/user/pho/stress2
op@robot hardenedBSD.git.opntr> git diff freebsd/master origin/master
op@robot hardenedBSD.git.opntr>
And I started a new instance of build/
No, we don't touch them. Only added -DHARDEBEDBSD into make
environment. I will schedule a new round of build to recheck them,
On Thu, Jan 1, 2015 at 6:53 PM, Dimitry Andric wrote:
> On 01 Jan 2015, at 18:35, Oliver Pinter wrote:
>> We at HardenedBSD got this error, with out je
ndrew Turner, Justin Hibbits and
>> Antoine Brodin for their invaluable help with this import.
>>
>> -Dimitry
>>
>
> This is great news, thank you very much.
>
> I gave it a try, but my system's drop out at the error shown below. I use
> non-standard
>
On 11/15/14, Dominik Zajac wrote:
> Hi,
>
> I am trying to change the default keymap for my keyboard therefore I
> added the following options to my kernel configuration which leads to
> the error bellow.
>
> Added options:
>
> options KBD_INSTALL_CDEV
>
> options UKBD_DFLT_KEYMAP
>
>
On 10/8/14, Yonghyeon PYUN wrote:
> On Thu, Oct 02, 2014 at 02:07:30PM +0900, Yonghyeon PYUN wrote:
>> On Wed, Oct 01, 2014 at 10:36:37AM +0900, Yonghyeon PYUN wrote:
>> > On Tue, Sep 30, 2014 at 10:57:41AM +0900, Yonghyeon PYUN wrote:
>> > > Hi,
>> > > I've added support for QAC AR816x/AR817x eth
pick
On 9/20/14, William Orr wrote:
> Hey,
>
> I've submitted this patch before, and it's gotten comments and fixes,
> but still hasn't been merged. Any thoughts? Does it need more work?
>
> Thanks,
> William Orr
>
> Index: args.c
>
On 7/15/14, Bruno Lauzé wrote:
> I was looking at dragonfly and why they have libdevattr and we don'tI really
> think having udev compatible api would open the door to a lot of software,
> imho.I feel it wouldn't be so complicated to port dragonfly kern_udev,
> libprop and libdevattr from dragonfl
On 6/15/14, Warner Losh wrote:
>
> On Jun 14, 2014, at 3:57 PM, Oliver Pinter wrote:
>
>> On 6/13/14, John Baldwin wrote:
>>> On Friday, June 13, 2014 6:21:28 am Oliver Pinter wrote:
>>>> Hi All!
>>>>
>>>> When I try to build i3
On 6/13/14, John Baldwin wrote:
> On Friday, June 13, 2014 6:21:28 am Oliver Pinter wrote:
>> Hi All!
>>
>> When I try to build i386 kernel on amd64 host running compile error
>> due wrong cpufunc.h picked up by build system.
>>
>> I used the attached scrip
Hi All!
When I try to build i386 kernel on amd64 host running compile error
due wrong cpufunc.h picked up by build system.
I used the attached script to build the kernel, and I attached a build log.
Any suggestion how can I fix this?
Thanks,
Oliver
cc-log-opBSD.git-20140613030335.txt.xz
1 - 100 of 380 matches
Mail list logo
