FreeBSD_HEAD - Build #2863 - Still Failing:
Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD/2863/ to
view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
Hello,
/usr/sbin/pw useradd -n user -s /bin/csh -g wheel -w yes -V
/usr/obj/_.mount.freebsd/etc/ -d /usr/home/user
make not user with /usr/obj/_.mount.freebsd/etc/ but creates it in the
main system /etc
___
freebsd-current@freebsd.org mailing list
http://
FreeBSD_HEAD - Build #2862 - Still Failing:
Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD/2862/ to
view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
[ Redirect to -geom, bcc'd to -current for transition ]
On Sat, Jun 13, 2015 at 04:10:38PM +0200 I heard the voice of
José García Juanino, and lo! it spake thus:
> Hi FreeBSD current,
>
> I get a reproducible panic following these steps:
>
> 1- Mount a geli encrypted DVD:
[...]
> 4- Open again
The recent change from historic mandoc to the newer stuff
has broken apropos(1). From the apropos(1) manpage
MANPATH The standard search path used by man(1) may be changed by
specifying a path in the MANPATH environment variable.
Invalid paths, or paths without manual d
FreeBSD_HEAD - Build #2861 - Still Failing:
Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD/2861/ to
view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
FreeBSD_HEAD - Build #2860 - Failure:
Check console output at https://jenkins.freebsd.org/job/FreeBSD_HEAD/2860/ to
view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Jun 13, 2015, at 7:10, José García Juanino wrote:
> Hi FreeBSD current,
>
> I get a reproducible panic following these steps:
>
> 1- Mount a geli encrypted DVD:
>
> # geli attach /dev/cd0
> Password:
>
> # mount -o ro /dev/cd0.eli /cdrom
>
> 2- Do some work in the /cdrom filesystem.
>
>
FreeBSD_HEAD-tests - Build #1107 - Failure:
Check console output at
https://jenkins.freebsd.org/job/FreeBSD_HEAD-tests/1107/ to view the results.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
On Fri, Jun 12, 2015 at 1:30 AM, Ranjan1018 . <21474...@gmail.com> wrote:
>
>
> 2015-06-12 1:13 GMT+02:00 Henry Hu :
>
>> On Thu, Jun 11, 2015 at 1:55 PM Kevin Oberman
>> wrote:
>>
>>> The same issue exists in fusefs, but has an uglier result. The fuse
>>> daemon
>>> shuts down before any fusefs
On Sat, Jun 13, 2015 at 05:23:42PM +0200, Oliver Pinter wrote:
> 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 gene
On Sat, Jun 13, 2015 at 02:35:46PM +, 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 stopped wit
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 stopped with
>> error, just ignore them, and co
Hi Kevin,
you signed up as tester of run(4). I have converted run(4)
and uploaded new patch at:
https://reviews.freebsd.org/D2655
Please try, report and update the project page.
https://wiki.freebsd.org/projects/ifnet/net80211
Thanks a lot for your help.
--
Totus tuus, Glebius.
_
[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 stopped with
> error, just ignore them, and continue with memstick images.
>
>
> cp /
On 6/13/15 10:01 PM, O'Connor, Daniel wrote:
On 13 Jun 2015, at 09:17, Julian Elischer wrote:
could it be that more than one CPUs get the NMI at the same time?
i guess, its possible. is there an easy way to check for that?
hard code checks in the code so that all except the first do somethin
Hi FreeBSD current,
I get a reproducible panic following these steps:
1- Mount a geli encrypted DVD:
# geli attach /dev/cd0
Password:
# mount -o ro /dev/cd0.eli /cdrom
2- Do some work in the /cdrom filesystem.
3- Close my laptop lid. The system suspends.
4- Open again the lid a wait. The sys
> On 13 Jun 2015, at 09:17, Julian Elischer wrote:
>
>>> could it be that more than one CPUs get the NMI at the same time?
>> i guess, its possible. is there an easy way to check for that?
> hard code checks in the code so that all except the first do something
> different.
> (even only as a de
On 6/13/15 2:49 AM, Maksim Yevmenkin wrote:
Andriy,
i have a question about obtaining minidump as result of panic() being
called from nmi handler. basically, i have a way to trigger nmi, and,
i would like to panic() system and obtain a minidump.
i have modified isa_nmi() to appropriately inspe
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
20 matches
Mail list logo