Anyone know what periodic script runs the sunrpc service ? as ive been
geting a lot of:
Connection attempt to TCP 127.0.0.1:111 from 127.0.0.1:50571 flags:0x02
according to log_in_vaim
was wondering if there is a way to stop that as i dont run it.
-chris
Actually, last time I checked, I think stable did not install with a RO
/usr/src either. Anyone know if this is still the case?
Chris
It looks like it's trying to mess around with something in /usr/src,
which is a read-only NFS mount. Needless to say we do not want to
break
ffhand now.
These problems were observed on a 4.2-STABLE box, not too long ago. I have
compiled the source from scratch (with and without matrox DRM stuff), as
well
as using the stock 4.0.2_5 package, both of which behave the same.
Chris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
all the previous posters with no luck. Any
suggestions would greatly be appreciated!
Chris
On Sat, Mar 3, 2012 at 10:43 AM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:
On 03/03/12 15:19, Florian Smeets wrote:
On 03.03.12 14:24, Chris Rees wrote:
On 3 March 2012 11:48, O. Hartmann ohart
On Mon, Apr 16, 2012 at 2:45 AM, Dimitry Andric d...@freebsd.org wrote:
On 2012-04-16 03:03, Chris wrote:
I recently updated my system from 8.2-STABLE to 9.0-STABLE and I'm
seeing a similar error when trying to build the VirtualBox kernel
module:
*** Building 'vboxdrv' module ***
/usr
I updated current today and now the system refuses to boot and my 3ware
card constantly has it's LED on and it resets. booting the old kernel
boots up fine ?
___
freebsd-current@freebsd.org mailing list
On 2/21/2013 9:54 PM, Steve Kargl wrote:
On Thu, Feb 21, 2013 at 09:50:11PM -0600, Chris wrote:
I updated current today and now the system refuses to boot and my 3ware
card constantly has it's LED on and it resets. booting the old kernel
boots up fine ?
Which timezone? 1-2pm is a little
On 2/21/2013 10:42 PM, matt wrote:
On 02/21/13 19:58, Chris wrote:
On 2/21/2013 9:54 PM, Steve Kargl wrote:
On Thu, Feb 21, 2013 at 09:50:11PM -0600, Chris wrote:
I updated current today and now the system refuses to boot and my 3ware
card constantly has it's LED on and it resets. booting
use whatever 16001 uses the only ports opened are the ones
opened by MSN,AIM,IRC so can someone tell me what trys to connect to those
ports ive looked in the /etc/periodic/security no go ??
-chris
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
that involves OpenGL...
Also, it's odd the the thing fails in such a strange manner (rebooting
the machine without any error messages).
I had this with an ASUS mother board. Could not figure it out intill
the board failed and I replaced the board.
Chris
to be sure that I'm installing on a clean disk. Also, I've
tried building the bootloader (even though the guide said it's
depreciated as of 8.0-STABLE and 9.0-CURRENT) as well as installing
the boot blocks, both to no avail.
Any ideas and/or suggestions would greatly be appreciated!
Thanks,
Chris
Xin,
The only thing I copied over was the zpool.cache file, as per the
wiki. Should I have copied over the entire /boot/zfs folder?
Thanks,
Chris
On Tue, Feb 16, 2010 at 9:07 PM, Xin LI delp...@delphij.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010/02/16 18:03, Chris wrote
Scot,
I did, as part of step 7 in section 1:
7. Create ZFS Pool zroot
Fixit# mkdir /boot/zfs
Fixit# zpool create zroot /dev/gpt/disk0
Fixit# zpool set bootfs=zroot zroot
Thanks,
Chris
On Tue, Feb 16, 2010 at 9:42 PM, Scot Hetzel swhet...@gmail.com wrote:
On Tue, Feb 16, 2010 at 8:42 PM
Also, I believe the portion where you extract the different distfiles
(base, manpages, etc..) does a lot of that for you.
On Tue, Feb 16, 2010 at 9:49 PM, Chris behrnetwo...@gmail.com wrote:
Scot,
I did, as part of step 7 in section 1:
7. Create ZFS Pool zroot
Fixit# mkdir /boot/zfs
Doug,
Haven't tried with different GPT parameters so I guess I could try
that. It's just odd since that same guide worked for me without a
hitch on my desktop machine. I'll try that as well as dd'ing the drive
completely.
Thanks,
Chris
On Tue, Feb 16, 2010 at 10:36 PM, Doug Poland d
farther this time but this is still weird.
Any ideas on this one?
Thanks,
Chris
On Wed, Feb 17, 2010 at 8:28 AM, Chris behrnetwo...@gmail.com wrote:
Doug,
Haven't tried with different GPT parameters so I guess I could try
that. It's just odd since that same guide worked for me without
copying over gptzfsboot and zfsloader
from my 8.0-STABLE machine.
On Wed, Feb 17, 2010 at 1:15 PM, Matt Reimer mattjrei...@gmail.com wrote:
On Wed, Feb 17, 2010 at 7:46 AM, Chris behrnetwo...@gmail.com wrote:
Ok, went back to my 8.0-RELEASE memstick image and after playing with
the GPT settings
Pegasus,
Thanks for the tip. I'll give it a shot. If it is the case, then the
RootOnZFS wiki guides need to be updated to account for that. They all
currently say to use vfs.root.mountfrom=zfs:zroot in loader.conf
Thanks,
Chris
On Wed, Feb 17, 2010 at 1:40 PM, Pegasus Mc Cleaft k
...
On Wed, Feb 17, 2010 at 4:03 PM, Scot Hetzel swhet...@gmail.com wrote:
On Wed, Feb 17, 2010 at 12:40 PM, Pegasus Mc Cleaft k...@mthelicon.com
wrote:
Hello Chris, Scott Current
I use gptzfsboot on my AMD64 (current) machine all the time and also
on
my laptop. I am not sure
bootloader. Anyone have any ideas on that? I checked
for any BIOS updates but it looks like I'm current. It sure would be
nice to not have to select my hard drive each time.
Thanks,
Chris
On Wed, Feb 17, 2010 at 5:16 PM, Chris behrnetwo...@gmail.com wrote:
How's this for bizarre? If I hit F12 to bring
179552888
error 1 lba 59243926
ZFS: i/o error - all block copies unavailable
FreeBSD/i386 boot
Default: zroot:/boot/kernel/kernel
boot:
It may or may not be related, but I notice that while in this state my
hard drive activity light stays on.
Thanks,
Chris
I think you're probably right about this being a BIOS problem.
Does the gptzfsboot 'status' command show the same output when you run it
with and without the F12 workaround? Here's what I see from FreeBSD and from
gptzfsboot:
[root ~]# zpool status
pool: glamdring
state: ONLINE
scrub:
I'm seeing some difference in the bootloader output between using the
F12 workaround or not:
F12 workaround mode:
FreeBSD/i386 boot
Default: zroot:/boot/zfsloader
boot: status
config:
NAME STATE
zroot ONLINE
gpt/disk0 ONLINE
No F12 key
bump...
On Thu, Feb 18, 2010 at 10:38 PM, Chris behrnetwo...@gmail.com wrote:
I'm seeing some difference in the bootloader output between using the
F12 workaround or not:
F12 workaround mode:
FreeBSD/i386 boot
Default: zroot:/boot/zfsloader
boot: status
config:
NAME
, 2010 at 1:03 PM, Matt Reimer mattjrei...@gmail.com wrote:
On Tue, Feb 23, 2010 at 8:20 AM, John Baldwin j...@freebsd.org wrote:
On Thursday 18 February 2010 10:38:38 pm Chris wrote:
I'm seeing some difference in the bootloader output between using the
F12 workaround or not:
F12
On Thu, Feb 25, 2010 at 1:08 PM, John Baldwin j...@freebsd.org wrote:
On Thursday 25 February 2010 12:58:13 pm Chris wrote:
On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin j...@freebsd.org wrote:
On Wednesday 24 February 2010 10:12:25 pm Chris wrote:
So it sounds like somehow my system
I guess we can officially declare this thread dead?
On Fri, Feb 26, 2010 at 1:43 AM, Chris behrnetwo...@gmail.com wrote:
On Thu, Feb 25, 2010 at 1:08 PM, John Baldwin j...@freebsd.org wrote:
On Thursday 25 February 2010 12:58:13 pm Chris wrote:
On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin j
Which mobo/chipset ?
* Lamont Granquist [EMAIL PROTECTED] [020323 02:14]:
I just cvsupped about an hour ago, built world and built a kernel that was
GENERIC with 486/586 turned off and SMP and IOAPIC turned on. It crashed
while trying to mount root. Apologies for mistakes in the
1
Stop in /usr/ports/x11/xorg.
It looks like a boo-boo in the code. This is from a freshly pulled
down ports tree from this morning and with WITHOUT_NOUVEAU=yes in
/etc/make.conf. Is there a patch in the works or do we need to let the
Freedesktop folks know?
Thanks,
Chris
Sorry, I should have posted this in the ports mailing list and will do so.
On Fri, Oct 22, 2010 at 2:13 PM, Chris behrnetwo...@gmail.com wrote:
Hello,
Seeing this on an amd64 box when doing a fresh Xorg build:
=== Building for dri-7.6.1,2
gmake[1]: Entering directory `/usr/ports/graphics
.
Does anyone have any experience with the 9280-16i4e on FreeBSD?
Does it work? Well? If not, anytime soon?
Thank you very much.
Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Just a huge thank you to you, and everyone else for all the information.
Greatly appreciated!
On 2019-09-03 11:29, Jung-uk Kim wrote:
On 19. 9. 1., Chris wrote:
Hello all,
I recently picked up an LSI/AVAGO/Broadcom 9280-16i4e card with
the intent of flashing it to IT mode (pass through). So
On Fri, 8 Nov 2019 07:53:49 -0500 Ed Maste ema...@freebsd.org said
On Thu, 7 Nov 2019 at 03:38, Chris wrote:
>
> I'm wondering what happened between RELENG-12, and 13 that made the change?
What is the latest 12.x you tried that worked in this configuration?
Thanks for the rep
On Fri, 8 Nov 2019 20:43:33 +0200 Toomas Soome tso...@me.com said
> On 8. Nov 2019, at 20:34, Chris wrote:
>
> On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com
> <mailto:gljennj...@gmail.com> said
>
>> On Thu, 07 Nov 2019 09:41:01 -0800
>> Chris wro
On Fri, 8 Nov 2019 10:32:25 +0100 gljennj...@gmail.com said
On Thu, 07 Nov 2019 09:41:01 -0800
Chris wrote:
> On Thu, 7 Nov 2019 17:28:16 +0200 Toomas Soome tso...@me.com said
>
> > > On 7. Nov 2019, at 17:23, Daniel Nebdal wrote:
> > > > >> On Thu,
thxtra
length: 751407124480
offset: 248797741056
type: freebsd-ufs
index: 6
end: 1953525127
start: 485933088
Consumers:
1. Name: ada1
Mediasize: 1000204886016 (932G)
Sectorsize: 512
Stripesize: 4096
Stripeoffset: 0
Mode: r0w0e0
rgds,
toomas
--Chris
DISKS
Description:
On Thu, 7 Nov 2019 09:49:52 +0100 gljennj...@gmail.com said
On Thu, 07 Nov 2019 00:38:29 -0800
Chris wrote:
> On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said
>
> > > On 7. Nov 2019, at 10:05, Chris wrote:
> > > > > On Thu, 7 Nov 2019 08:31
ler could review the information and make fixes.
Right. Sorry. I forgot you had asked for the output of dd(1).
I've done so, and will send you the output directly (off list).
Thank you!
rgds,
toomas
[snip]
--Chris
___
freebsd-current@f
as expected.
While I have no troubles booting (U)EFI. Isn't the so-called
LEGACY boot option still supported?
Thank you for all your time, and consideration.
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
On Thu, 7 Nov 2019 10:15:49 +0200 Toomas Soome tso...@me.com said
> On 7. Nov 2019, at 10:05, Chris wrote:
>
> On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said
>
>> On Wed, 06 Nov 2019 17:23:08 -0800
>> Chris wrote:
>> > I put a box together to t
On Thu, 7 Nov 2019 08:31:14 +0100 gljennj...@gmail.com said
On Wed, 06 Nov 2019 17:23:08 -0800
Chris wrote:
> I put a box together to test 13 about a mos ago.
> It's a second gen core i3. But whether choosing automatic
> disk layout, or choosing manual. When the install finishes, an
bient difference.
I've read that (most?) of the Intel CPUs (everything since "core" versions)
has a copy of MINIXv3 on them @ ring -3. Does/could the AMD System Management
Network provide any *additional* clues?
And *why* won't AMD provide more *definitive* specs? Hoping consumers &qu
.%desc: AMD CPU On-Die Thermal Sensors
dev.amdtemp.%parent:
dev.cpu.3.temperature: 12.5C
dev.cpu.2.temperature: 12.5C
dev.cpu.1.temperature: 12.5C
dev.cpu.0.temperature: 12.5C
Thanks again!
--Chris
___
freebsd-current@freebsd.org mailing list
https
t higher than it
actually is.
My BIOS appears to have the correct temp reading. Would it be of any use
to anyone besides myself, if I were to decompile it, and get the source
for the temp reading/monitoring from it?
--Chris
---Mike
___
freebsd-curr
of (e)mail; that the cert(s) issued by LetsEncrypt
also work well for all my MXs.
Hope this is helpful!
Thanks for any help with this, rick
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
256 bits))
(Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified
OK))
by mx2.freebsd.org (Postfix) with ESMTPS id 1B07B7E9A8;
Wed, 4 Mar 2020 04:37:12 + (UTC)
(envelope-from owner-freebsd-curr...@freebsd.org)
Not sure if it would help with
set do-ip6=no. Meanwhile I've whitelisted the IPv6 address
in postfix.
FWIW I thought I might chime in here to report that I'm also seeing
*periodic* failures.
IOW lookups fail, but aren't *completely* fatal. :)
--Chris
FreeBSD 14.0-FUTURE #0.000 cray256
--
Herbert
_
On Mon, 17 Feb 2020 05:52:33 +1100 Peter Jeremy pe...@rulingia.com said
On 2020-Feb-13 13:27:17 -0800, Chris wrote:
>My BIOS appears to have the correct temp reading. Would it be of any use
>to anyone besides myself, if I were to decompile it, and get the source
>for the tem
On a hunch, try the following:
# cd /usr/ports/x11-servers/xorg-server
# make clean
# make rmconfig
# make config
then try your upgrade again.
NOTE: the last command; make config, is optional. If you're fine with
the default settings, it isn't
On Wed, 12 Feb 2020 15:23:51 -0500 mike tancsa m...@sentex.net said
On 2/12/2020 1:39 PM, Chris wrote:
> Hard as I try I can not get anything close to the actual temperature
> of the CPUs or cores while running on FreeBSD.
> Family: Athlon X4
> Manufacturer: AuthenticAM
On Thu, 13 Feb 2020 07:00:36 +0100 Andrea Venturoli m...@netfence.it said
On 2020-02-12 23:17, Chris wrote:
> # dmidecode -t4 | grep AMD
> Manufacturer: AMD
> Version: AMD Athlon(tm) II X4 630 Processor
> # sysctl -a | grep tempe
> dev.cpu.3.temperature: 33.5C
> dev.cpu.2.
f thing within jails for years, and have never had this problem.
Thanks!
--Chris
___
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"
ail' folder. Nor within the jail itself, and I've been doing
this
sort of thing within jails for years, and have never had this problem.
Never mind.
I just noticed an omission from my jail.conf(5) that is to blame:
allow.chflags;
Sorry for the noise.
--Chris
Thanks!
--Chris
M in VirtualBox.
Can you send me some link to documentation who should I create new ISO
after rebuild?
Here's what I do
After building world && kernel:
# cd /usr/src/
# make installworld DESTDIR=/to/path/with-2Gig-space
# make distribution DESTDIR=/to/path/with-2Gig-space
(you need a slice
On Mon, 6 Apr 2020 09:35:03 +0200 Niclas Zeising zeis...@freebsd.org said
On 2020-04-04 01:44, Chris wrote:
> I'm struggling with a build of 13/current on a box.
> Everything went pretty much as I might expect. But I'm stuck
> on Xorg; big changes. I read updating, and u
:41, Chris wrote:
>
> Sorry for the ling title. But wasn't sure how make my
> question more concise.
> Why did we begin making an initial console "graphics mode"
> by default. My understanding has always been that (Free)BSD
> has been a "Server by default",
before bouncing the box.
While this "works" for long-time users. It's an *extra*, and
seemingly *unnecessary* step. It is also likely to behoove
first-time/new users -- except those already targeting a
Desktop.
Thanks for any insight into this! :)
--Chris
___
, and added kern_vty=sc
to loader.conf(5). However. That seems to have been ignored.
How to get it on a fresh install?
Ahem... I used the wrong syntax.
changing the entry to
kern.vty=sc
solved it! :)
Sorry for the noise! :(
--Chris
Thanks!
--Chris
On Thu, 2 Apr 2020 19:31:53 -0400 Ed Maste ema...@freebsd.org said
On Thu, 2 Apr 2020 at 17:13, Chris wrote:
>
> Ahem... I used the wrong syntax.
> changing the entry to
>
> kern.vty=sc
>
> solved it! :)
I'm glad it's working for you, but note that sc(4) is deprecat
! :)
Thanks for your time, and sorry for the noise!
--Chris
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebs
been ignored.
How to get it on a fresh install?
Thanks!
--Chris
___
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 Thu, 2 Apr 2020 19:31:53 -0400 Ed Maste ema...@freebsd.org said
On Thu, 2 Apr 2020 at 17:13, Chris wrote:
>
> Ahem... I used the wrong syntax.
> changing the entry to
>
> kern.vty=sc
>
> solved it! :)
I'm glad it's working for you, but note that sc(4) is deprecat
On Fri, 3 Apr 2020 20:10:36 +0900 junch...@dec.sakura.ne.jp said
On Fri, 03 Apr 2020 01:25:18 -0700
Chris wrote:
> On Thu, 2 Apr 2020 19:31:53 -0400 Ed Maste ema...@freebsd.org said
>
> > On Thu, 2 Apr 2020 at 17:13, Chris wrote:
> > >
> > > Ahem... I used th
On Fri, 3 Apr 2020 14:01:47 -0400 Ed Maste ema...@freebsd.org said
On Fri, 3 Apr 2020 at 04:25, Chris wrote:
>
> On Thu, 2 Apr 2020 19:31:53 -0400 Ed Maste ema...@freebsd.org said
>
> > On Thu, 2 Apr 2020 at 17:13, Chris wrote:
> > >
> > > Ahem... I used
s informed that the
xf86-input-evdev driver was not installed. I installed it. But
the results were the same.
Thoughts? Solutions?
Thank you for all your time, and consideration.
--Chris
P.S. source for ports is from head yesterday, base (install) is from
2
s /dev/ada0p4 /mnt/
# ls /mnt/EFI/freebsd/
loader.efi
Why the difference? When will FreeBSD (u)EFI work as expected?
Thanks in advance for any insights!
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/f
On Sat, 28 Mar 2020 01:10:37 +0300 Andrey Fesenko f0and...@gmail.com said
On Sat, Mar 28, 2020 at 12:53 AM Chris wrote:
>
> On an experiment of the FreeBSD EFI implementation. I installed
> a copy of releng/12 from install media. Which left me with:
> # gpart show ada0
> =>
On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh i...@bsdimp.com said
On Fri, Mar 27, 2020 at 4:54 PM Chris wrote:
> On Sat, 28 Mar 2020 01:10:37 +0300 Andrey Fesenko f0and...@gmail.com said
>
> > On Sat, Mar 28, 2020 at 12:53 AM Chris wrote:
> > >
> > > On an
On Fri, 27 Mar 2020 18:31:50 -0700 bsd-li...@bsdforge.com said
On Fri, 27 Mar 2020 17:27:27 -0600 Warner Losh i...@bsdimp.com said
> On Fri, Mar 27, 2020 at 4:54 PM Chris wrote:
>
> > On Sat, 28 Mar 2020 01:10:37 +0300 Andrey Fesenko f0and...@gmail.com said
> >
> >
On Sat, 28 Mar 2020 11:07:38 +0200 Toomas Soome tso...@me.com said
> On 28. Mar 2020, at 05:28, Chris wrote:
>
> On Fri, 27 Mar 2020 18:31:50 -0700 bsd-li...@bsdforge.com
> <mailto:bsd-li...@bsdforge.com> said
>
>> On Fri, 27 Mar 2020 17:27:27 -0600 Warne
no longer supported?
Thanks for any, and all insight into solving this.
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-uns
On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka li...@gjunka.com said
On 02/05/2020 14:56, Grzegorz Junka wrote:
>
> On 02/05/2020 14:15, Grzegorz Junka wrote:
>> cpuid = 3
>>
>> time = 1588422616
>>
>> KDB: stack backtrace:
>>
>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
>>
On Sun, 3 May 2020 00:15:48 +0100 Grzegorz Junka li...@gjunka.com said
On 02/05/2020 20:43, Chris wrote:
> On Sat, 2 May 2020 20:19:56 +0100 Grzegorz Junka li...@gjunka.com said
>
>> On 02/05/2020 14:56, Grzegorz Junka wrote:
>> >
>> > On 02/05/2020 14:15, Grzegor
? Or will I need initiate a new
install, and hope for the best checking out a newer revision
of src.
Thanks in advance.
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send
.
I simply added it before installworld. Knowing it would pick up
the change. Well, as it turns out, both copies do *not* exist.
End of story, and sorry for the noise.
--Chris
Any chance for recovery? Or will I need initiate a new
install, and hope for the best checking out a newer revision
of src
On Tue, 17 Mar 2020 16:17:31 +0200 Toomas Soome tso...@me.com said
> On 17. Mar 2020, at 15:51, Matthew Seaman wrote:
>
> On 17/03/2020 12:58, Florian Limberger wrote:
>> On 16.03.20 23:33, Chris wrote:
>>
>>> For the record. I'm *only* using FreeBSD in this si
On Mon, 16 Mar 2020 22:03:02 -0500 Karl Denninger k...@denninger.net said
On 3/16/2020 17:33, Chris wrote:
> On Mon, 16 Mar 2020 17:24:24 -0500 Karl Denninger k...@denninger.net said
>
>> On 3/16/2020 17:23, Chris wrote:
>> > I'm attempting to boot multiple versions of Fr
partition. Or is
there a recommended bootmanager I can use to boot multiple
versions of FreeBSD? Windows?
Thank you!
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
On Mon, 16 Mar 2020 17:24:24 -0500 Karl Denninger k...@denninger.net said
On 3/16/2020 17:23, Chris wrote:
> I'm attempting to boot multiple versions of FreeBSD.
> I started with an install of older 11 with a (u)efi
> boot partition installed. I then grabbed an current 11
&
c/SourceManager.cpp:1228:10:
> fatal error: 'emmintrin.h' file not found
> #include
> ^
> 1 error generated.
> *** Error code 1
I ran ionto this awhile back, and I think the way I was able to solve it with a
make kernel-toolchain
and then building wor
me in your ~/.ignorelist ~/.killfile ;-)
--Chris
___
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 2020-09-03 11:33, Kristof Provost wrote:
On 3 Sep 2020, at 19:56, Chris wrote:
Why was the intention to switch NOT announced as such MUCH sooner?
There was discussion about a possible switch to git on the freebsd-git
mailing
list as early as February 2017:
https://lists.freebsd.org
-}
And all those that do the really heavy work are very, very short on
time and capacity.
I commented on both of these in the original post. But you trimmed that
out. :-(
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
servers. It's easier to distinguish, and while many boards
include more complex sound. The speaker is "cheap" and easy to use.
I should be able to help test.
Thanks for the heads-up!
--Chris
Warner
___
freebsd-current@freebsd.org mailing
://gitlab.com/esr/reposurgeon
FTR I'm unaffiliated with the project. It just looked like it might be of
interest.
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Tue, 28 Jul 2020 21:16:28 -0700 Matthew Macy mm...@freebsd.org said
On Tue, Jul 28, 2020 at 21:06 Chris wrote:
> On Tue, 28 Jul 2020 20:50:33 -0700 Matthew Macy mm...@freebsd.org said
>
> > On Tue, Jul 28, 2020 at 20:43 Chris wrote:
> >
> > > On Tue, 28 Jul
licitly.
> more important than the fact that it is old or we have more choices
> in the ports tree. If we have negative factors on maintaining them,
> removing them would be one of the choices as a result. If the
> existing routed/route6d makes difficulty on people who want to
so used 12.
There was a great deal of technical advice that appeared to improve his
situation. Interestingly; he was also experiencing this on his "builder"
altho he was using synth as opposed to poudriere.
Maybe it'll help your situation?
--Chris
K
ake sense
to document this tunable on the stack(9) and/or tty(4) man page(s)?
Just my 2 cents
A huge +1 here.
I think you captured it well, Michael.
Thanks.
--Chris
[0] Typical use case:
$ dd if=/dev/random of=/dev/da0 bs=1m
load: 0.37 cmd: dd 32247 [running] 0.91r 0.00u 0.88s 8% 2672
/freebsd-openzfs-3d833bea-f10f94aa-2020072900/
Is this in an attempt to replace the opensolaris version used now?
Thanks.
--Chris
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
On Tue, 28 Jul 2020 20:08:33 -0700 Matthew Macy mm...@freebsd.org said
On Tue, Jul 28, 2020 at 8:03 PM Chris wrote:
>
> On Tue, 28 Jul 2020 19:10:21 -0700 Matthew Macy mm...@freebsd.org said
>
> > On Wednesday, July 8th I issued the initial call for testing for the
>
On Tue, 28 Jul 2020 20:50:33 -0700 Matthew Macy mm...@freebsd.org said
On Tue, Jul 28, 2020 at 20:43 Chris wrote:
> On Tue, 28 Jul 2020 20:08:33 -0700 Matthew Macy mm...@freebsd.org said
>
> > On Tue, Jul 28, 2020 at 8:03 PM Chris wrote:
> > >
> > > On Tue, 28 J
d in /var/messages?
Michael
--Chris
___
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"
e debug output something that should be logged?
Aren't the installs/up(grade|date)s individually logged in /var/messages?
Ahem... I mean't:
/var/log/messages
Sorry. :(
>
> Michael
--Chris
___
freebsd-current@freebsd.org mailing list
https://
head, high throughput, IPv6-able,
traffic shaping/queueing
thanks,
--Chris
___
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 2020-12-11 13:07, Jeffrey Bouquet wrote:
On Fri, 11 Dec 2020 10:53:55 -0800, Chris wrote:
On 2020-12-11 10:32, Chris wrote:
> On 2020-12-11 08:10, Steve Kargl wrote:
>> On Fri, Dec 11, 2020 at 06:12:42AM -0800, Jeffrey Bouquet wrote:
>>> Longtime BSD current us
eam becomes aware of them.
On a slight aside;
Any plans to incorporate GitLab into any of this?
--Chris
Warner
* for a limited period.
<
https://github.com/bsdimp/freebsd-git-docs/blob/4833066feda51cc3a907cf7bff1c4344b3edd5c6/big-picture.md#L103
>
In context:
<https://github.com/bsdimp
On 2020-12-23 07:41, Graham Perrin wrote:
On 23/12/2020 15:36, Chris wrote:
… Any plans to incorporate GitLab into any of this?
<https://github.com/bsdimp/freebsd-git-docs/search?q=GitLab> ▶
big-picture.md is
probably the best starting point.
Brilliant! :)
I mainly asked because
On 2020-12-23 08:52, Warner Losh wrote:
On Wed, Dec 23, 2020 at 9:44 AM Chris wrote:
On 2020-12-23 07:41, Graham Perrin wrote:
> On 23/12/2020 15:36, Chris wrote:
>
>> … Any plans to incorporate GitLab into any of this?
>
>
> <https://github.com/bsdimp/freebsd-
ded/deleted
--Chris
___
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"
1 - 100 of 931 matches
Mail list logo
