vice recovered, but given the damage to other hardware,
electrical damage seems like a reasonable conclusion here as well.
--chuck
; hardware/firmware related to my system?
Does the device support Persistent Log pages (LID=0x0d)? If so, it
might be interesting to dump those.
--chuck
is curious the emulated controller had trouble resetting
(i.e., the error message "controller ready did not become 1 within
30500 ms").
--chuck
Bah, actually adding freebsd-net this time
On Tue, Aug 15, 2023 at 7:44 PM Chuck Tuffli wrote:
>
> [Adding freebsd-net@]
>
> On Tue, Aug 1, 2023 at 10:46 AM Chuck Tuffli wrote:
> >
> > Running a recent-ish version (n264266-8f8da1bcc799) on an Intel NUC
> > (R
[Adding freebsd-net@]
On Tue, Aug 1, 2023 at 10:46 AM Chuck Tuffli wrote:
>
> Running a recent-ish version (n264266-8f8da1bcc799) on an Intel NUC
> (RNUC11PABi5), assigning an IPv4 address to igc0 doesn't work. There
> is no error message, and this has been working in the past.
DOWN
igc0: link state changed to UP
The address is set in rc.conf:
ifconfig_igc0="inet 192.168.5.10 netmask 255.255.255.0"
And manually setting it via
# ifconfig igc0 inet 192.168.5.10/24 up
does not work either. Any suggestions?
--chuck
In the bhyve emulation, this command effectively
memcpy's the data structure to the memory provided by the guest and
completes the command. If this panic is reproducible, I can provide a
patch to enhance the debug output to figure out if this is an
emulation or driver issue.
--chuck
rip = 0, rsp = 0, rbp = 0 —
>
> machine is a bhyve guest.
Did bhyve log any warnings or errors? I'm curious if its NVMe
emulation did something dumb or itself noticed an issue.
--chuck
/OptionalObsoleteFiles.inc in the MK_CLANG == no
section. What other information can I provide to help figure this out?
Thanks!
--chuck
ul.c:498
Other random tidbits:
- disabling compiler optimization (i.e. -O0) for the two files in
question (pci_nvme.c and pci_emul.c) makes the core dump go away
- using the default optimization level but generously sprinkling
debug printf everywhere makes the core dump go away.
I'm not sure where to go from here and could use some help.
--chuck
On Wed, May 25, 2022 at 6:59 AM Alexander Motin wrote:
...
> > nvme0: SET FEATURES (09) sqid:0 cid:15 nsid:0 cdw10:000b cdw11:031f
> > nvme0: INVALID_FIELD (00/02) sqid:0 cid:15 cdw0:0
...
> Those messages mean that driver tried to enable certain types of
> asynchronous events, but probabl
g to set
hw.nvme.verbose_cmd_dump to confirm this is happening.
--chuck
On Tue, Mar 22, 2022 at 4:25 PM Kevin Oberman wrote:
> Not enough information to guess.
>
> What is the content of /etc/rc.conf in regard to configuration of this
> interface?
defaultrouter="192.168.5.1"
ifconfig_igc0="inet 192.168.5.10 netmask 255.255.255.0"
> What shows up in the log file wh
On a recent-ish current (git hash 66b86c8a7604), after resuming from
sleep, the main network interface doesn't get restored. Further,
manually fixing this via service netif or ifconfig seems to fail. Am I
doing something wrong?
root@stargate:~ # uname -a
FreeBSD stargate.tuffli.net 14.0-CURRENT Fr
osticCommonKinds.inc"
^~~
1 error generated.
*** [Core/ModuleList.o] Error code 1
Where did I goof? TIA
--chuck
On Mon, Nov 22, 2021 at 9:34 AM Chris wrote:
>
> On 2021-11-22 08:47, Chuck Tuffli wrote:
> > Running on a recent-ish -current
> > # uname -a
> > FreeBSD stargate.tuffli.net 14.0-CURRENT FreeBSD 14.0-CURRENT
> > main-81b22a9892 GENERIC amd64
> >
> &g
h viid-4c918@
nd6 options=9
tap0: flags=8943 metric 0
mtu 1500
description: vmnet-freebsd-0-public
options=8
ether 58:9c:fc:10:ff:f6
groups: tap vm-port
media: Ethernet autoselect
status: active
nd6 options=29
Opened by PID 38298
--chuck
reebsd.org/D30995
https://reviews.freebsd.org/D31002
--chuck
On Tue, Mar 2, 2021 at 10:13 AM Mark Johnston wrote:
>
> On Tue, Mar 02, 2021 at 09:31:22AM -0800, Chuck Tuffli wrote:
> > I'm porting some code to bhyve and am getting a failure I don't
> > understand. This is git as of af11c2029006 FWIW.
> >
> > The co
t;fopen");
Running this fails with:
fopen: Not permitted in capability mode
Googling suggests this might be capsicum related. If so, what do I
need to change to allow writes to a debug file?
--chuck
___
freebsd-current@freebsd.org mailing list
ht
On Wed, Dec 30, 2020 at 4:38 PM Neel Chauhan wrote:
>
> Hi Chuck,
>
> On 2020-12-30 10:04, Chuck Tuffli wrote:
> > What is the output from
> > # pciconf -rb pci0:0:14:0 0x40:0x48
>
> The output is:
>
> 01 00 00 00 01 2e 68 02 00
Perfect. The Linux drive
us because, looking at the "lspci all"
output from the XPS link you provided, the NVMe device shows up in PCI
domain 0x1000 (i.e. not 0x). Which (and I have no direct
experience with this device or code) only happens if the bus number
start function returns 0x0.
What is the output from
#
2020" "Nov 26 03:51:14 2020" 32768 16 0
> /mnt/usr/include/sys/smr_types.h
> $
>
> So I'm not sure what's going on in your case. smr_types.h was added a
> number of months ago.
Weird, it looks like I borked my system somehow. But thank you, that
helped imm
On Thu, Dec 3, 2020 at 3:18 PM Mark Johnston wrote:
>
> On Thu, Dec 03, 2020 at 01:08:52PM -0800, Chuck Tuffli wrote:
> > Hi
> >
> > I'm trying to fix the build of qemu-utils but am seeing failures on
> > CURRENT (13.0-HEAD-9e082d278b9) like:
> >
> &
src/amd64.amd64/sys/GENERIC-NODEBUG
amd64
# ls -l /usr/include/sys/*smr*
-r--r--r-- 1 root wheel 1988 Nov 30 14:04 /usr/include/sys/_smr.h
-r--r--r-- 1 root wheel 7822 Nov 30 14:04 /usr/include/sys/smr.h
So it appears the file is missing. Any
lav, would it be possible to comment out/delete the above code in
your kernel and retest to see if that helps your case as well?
--chuck
___
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"
ify_static.pico
ittnotify_static.pico: \
/usr/home/ctuffli/dev/freebsd/freebsd.hg/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c
\
The first two lines of the 32-bit depend are:
$ head -2
../obj/usr/home/ctuffli/dev/freebs
On Sun, Dec 9, 2018 at 3:50 PM Chuck Tuffli wrote:
> On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov wrote:
>
>> Chuck Tuffli wrote:
>> > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > > <mailto:yur...@yuripv.net>> wrote:
>> >
>> > Hi,
>&
On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov wrote:
> Chuck Tuffli wrote:
> > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > <mailto:yur...@yuripv.net>> wrote:
> >
> > Hi,
> >
> > Running -HEAD in VMware Workstation 15.0.2 VM. Trying to u
and get it committed. If not, please post
the output from:
nvmecontrol identtify nvme0
--chuck
diff -r 1fbb2025b263 sys/cam/nvme/nvme_da.c
--- a/sys/cam/nvme/nvme_da.c Sun Dec 09 21:53:45 2018 +
+++ b/sys/cam/nvme/nvme_da.c Sun Dec 09 15:18:08 2018 -0800
@@ -798,7 +798,7 @@
disk->d_mediasize
enerate core dumps that a Linux gdb can decode. It has
limited testing, but I'm happy to rebase + share it with you.
--chuck
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
Hi--
On Apr 14, 2017, at 11:32 AM, Ernie Luzar wrote:
> Chuck Swiger wrote:
>> On Apr 14, 2017, at 6:47 AM, Ernie Luzar wrote:
>>> To aid in debugging the script I'm writing, I place "echo" commands
>>> throughout so I can kind of have a trace of
after I get the
> script working.
Since you've gotten an answer to the question you asked, let me only note that
both sh and csh support the -x flag, which causes the shell to echo the
commands as it runs. This is extremely helpful for debugging.
Regards,
--
-Chuck
_
On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote:
> Am 01.10.2014 um 05:44 schrieb Chuck Burns:
> > On Tuesday, September 30, 2014 8:13:01 AM O. Hartmann wrote:
> >> Hello.
> >>
> >> I just made the last update of the ports yesterday (I use
port
t -usually- works great, I've noticed that
occassionally it loops like that.
kill the script, upgrade the port that is looping.
That usually fixes it.
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
On Wednesday, November 27, 2013 11:21:58 AM Andriy Gapon wrote:
> When building ports on head I sometimes see messages like the
following
> during a patch phase:
>
> ===> Applying FreeBSD patches for firefox-25.0_1,1
> No such line 262 in input file, ignoring
> ===> Applying NSS patches
> No su
er compares in
startup code that usually runs ~once per process.
(Worrying about and minimizing file access to the pidfile would be a
different matter, since the compiler can't optimize around that...)
Regards,
--
-Chuck
___
freebsd-current@free
On 12/7/2012 9:10 PM, Warren Block wrote:
On Fri, 7 Dec 2012, Chuck Burns wrote:
dd if=/dev/zer of=/dev/ada0
^^^ There's your "badblocks" program. Any hard drive made in the last
decade have been self-remapping..
That should be /dev/zero. And this will be very slow, goi
"losing" storage space... IE the
number of total sectors on the drive will begin to shrink.
--
Chuck Burns
___
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"
fine,
just that other OS may not probe/use/access it in exactly the same manner.
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freeb
-bootstrapped with no need to compile
anything. -but- If you want to use -stable or -current, then you really
should use ports as well...
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
On 11/20/2012 11:51 AM, Eitan Adler wrote:
On 20 November 2012 12:47, Chuck Burns wrote:
Nonsense. More options are always preferable to fewer options.
Even when those options must be maintained? Documented? Bug fixed?
The ones who want the old pf can maintain it.. those who want the new
On 11/20/2012 10:52 AM, Aldis Berjoza wrote:
20.11.2012, 18:34, "Chuck Burns" :
On 11/20/2012 10:27 AM, O. Hartmann wrote:
On 11/20/12 11:43, Olivier Smedts wrote:
2012/11/20 Paul Webster :
I am aware this is a much discussed subject since the upgrade of PF, I
believe
want the old one can use it.
Or, another option is a knob USE_NEWPF during buildworld will build the
new pf, otherwise it'd build the old, default one.
This way you can still introduce the change, but default to the old one
for those of us who are too crusty to change. :)
--
C
rcoaster goes up and down* No worries. :)
--
Chuck Burns
___
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"
o "freebsd-current-unsubscr...@freebsd.org"
Quite honestly, the head/current branch is going to have build
failures.. It's the test bed.. Stick with the release system unless you
want cutting edge.. just remember.. cutting edge cuts sometimes...
--
Chuck Burns
_
e a smaller i386 box... 100G or so
free, 512M ram.. just drop me a line..
--
Chuck Burns
___
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"
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"
Just remember, if you can't laugh at yourself for dumb misakes, there
will always be som
lans to eventually write a devd SOLID
backend, but they are extremely busy, so any help in that would be most
welcome.. avilla@ can probably elaborate on that.. cross-posting my
reply to the kde@ ML so they can chime in if need be.
--
Chuck Burns
___
still works as it
should... In the meantime, someone should probably write a
devd<->udisks[12] translation daemon.. for things like gnome, kde, xfce,
and virtualbox, which have the udisks linuxisms can actually continue to
work in the future..
I'd do it if I
terest to userland
code
even for such a utility as lsof.
Honestly, if you do not like the way lsof does things, I'm sure patches
are welcome..
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Known issue. KMS prevents console switching, still. KMS is not quite
ready for use, but works fine as long as you stay in Xorg
--
Chuck Burns
___
freebsd-current@f
in recent xorg-server, even for
running without an xorg.conf file. This was not the case for a while,
but with recent xorg-server, hal is NOT NEEDED even for autodetection.
It has been deprecated by the linux folks for a few years now.
--
Chuck Burns
___
be running
FreeBSD on older equipment where polling might still make sense.
Do we throw them under the bus?
--
Chuck Burns
___
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"
fix ports so that one can compile 32bit ports on
FreeBSD amd64. If that's not what you meant, then ok.. but it's still a
good idea for a task. :P
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mail
ghost.
Then give it some love yourself! No one is
stopping you! :)
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curren
ests that fail when libm is compiled using clang.
> I've not investigate those at all. I'd tend to guess that we have a
> wider range of issues there.
>
> This is clearly an area we need more focus on before a switch to clang.
> To a point I would be OK with it delaying the switch to work these
> issues, but as with C99 long double support we can't let the quest for
> perfection delay us indefinitely.
>
> -- Brooks
Also, you probably want to be sure you are running these tests against clang
3.2, not the clang that is in base, since -that- is the version that will be
going live, right?
--
Chuck Burns
___
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"
clang, crash!
http://code.google.com/p/gperftools/issues/detail?id=394
--
Chuck Burns
___
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"
ly trolled.. right?
*shakes head and walks away*
Chuck Burns
___
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"
might be the most elegant solution..
Chuck
___
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 4/2/2012 10:52 AM, Chris Rees wrote:
This is a known issue with ZFS. Is that your case?
Chris
Yes. Interesting that it happens only with ZFS.
and jb, thanks, I could've sworn I'd hit "Reply to list" - thanks for
forwardin
On 3/25/2012 9:35 PM, Super Bisquit wrote:
I'm a retired 69 year old pregnant male looking for part-time work
during my career break.
I'm not a pregnant male, I just look like it
ouch. :(
Chuck
___
freebsd-current@freebsd.o
.1 for .0 versions.
The reason for the padding is to help with sorting, at least until
freebsd 100.0 comes out. :P
Chuck Burns
On 3/20/2012 5:40 AM, Alexander Yerenkow wrote:
IMHO,
32 / 64 = easily parsable and represent integer.
i386/amd64 - wellknown names, but this info about processor bit
..
At least, thats how I read it, I could be wrong, it's happened before.
Chuck
___
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"
g at straws on the fix you want, but the
error message is pretty clear.. and without the _after line I'm betting
it would boot fine.
--
Chuck Burns
The Southern Libertarian (owner/editor)
http://www.thesouthernlibertarian.com/
___
freebsd-current@fr
iMac_Keyboard_A1243.png [1]
On other non-American keyboards, the "Insert" key is labelled "Help",
and generated 0xF5 ("F1" + Meta/set-high-bit?).
Regards,
--
-Chuck
[1]: Which is decent, but not perfect. I'd swap ESC and "`~", and
caps-lock with con
driver only supports the more recent devices such as the
>> 10GbE FCoE CNA and 16G FC HBA (i.e. LPe1600x).
>
> any plans for iSCSI?
There is definitely a desire but no commitments at this point.
---chuck
___
freebsd-current@freebsd.o
ed
Home/INS/Delete/End keys. And even when I am using a full 10x-key keyboard, I
would not use them since I prefer using editmode=emacs and Cntl-A / E.
Regards,
--
-Chuck
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/
d side
effects before adopting them wholesale into the default system-wide dot.cshrc
template...
Regards,
--
-Chuck
___
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"
y, it would just be
too disruptive otherwise.
My $0.02
Instead of using -F to denote filetypes, why not use colors? -G -- it
shouldnt affect scripts at all, yet still provide the same sort of
feedback. (Tho, I personally use csh's built-in "ls-F" instead of "ls",
and actua
a native FC/FCoE driver (initiator and/or
target) that should be ready for wider testing in the next 3-4 months.
Note this driver only supports the more recent devices such as the
10GbE FCoE CNA and 16G FC HBA (i.e. LPe1600x).
---chuck
___
fre
e the tvtohz() issue described here:
http://www.dragonflybsd.org/presentations/nanosleep/
...and the prior discussion you had with Peter Wemm:
http://www.mavetju.org/mail/view_message.php?list=freebsd-stable&id=3022641
Regards,
--
-Chuck
___
of kernel
OR
(b) new mpd 5.6 (previous version had 5.5).
P.S. Adding net@ and mav@ to CC, original posting with all data is in
current@
If it were me, I would also try with the older 44BSD scheduler, just to
see what happens.
--
Chuck Burns
The Southern Libert
terproductive, but folks
can adjust kern.ipc.somaxconn as they see fit and perhaps Dan or others would
gain some value from it.
Regards
--
-Chuck
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
t pointless, but counterproductive,
because the answers will come too late to meet the SLA. If the system faces a
backlog that will take longer than 10 seconds to answer, then it needs to start
dropping requests rather than continue to queue up more requests than it can
handle in a sufficien
so is the
inflection point after which it is better/necessary for the software to
recognize and start doing overload mitigation then it is for the OS to blindly
queue more requests.
Put more simply, there comes a point where saying "no", ie, dropping the
connection with a reset, w
On Jan 4, 2012, at 1:49 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Wed, Jan 4, 2012 at 4:42 PM, Chuck Swiger wrote:
>> On Jan 4, 2012, at 1:03 PM, Dan The Man wrote:
>>>> However, I'm not convinced that it is useful to do this. At some point,
>>>> yo
I expect developers to code well enough to handle malloc() failures.
Setting the listen queue to an arbitrarily high value isn't useful, and
developers would be better advised to pay attention to best practices in the
face of a massive connection backlog.
Regards,
--
-Chuck
___
er than waiting for 60+
seconds just to exchange data.
Regards,
--
-Chuck
___
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"
ever, I'm not convinced that it is useful to do this. At some point, you
are better off timing out and retrying via exponential backoff than you are
queuing hundreds of thousands of connections in the hopes that they will
eventually be serviced by something sometime considerably later.
Regard
.h:90:2: note: array 'name' declared here
__uint8_t name[1]; /* name bytes, no null */
^
1 warning generated.
just as an aside, the XFS module didn't seem to work when I last
attempted to use it, so it may be worth just removing it?
--
Chuck Burns
The Souther
On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
> Here is quick, hackish patch to allow your make update to work, it appears
> that the Makefile.inc1 does not include the full path to svn, while it does
> include the full path to cvs and other tools, this makes me think
ars
that the Makefile.inc1 does not include the full path to svn, while it does
include the full path to cvs and other tools, this makes me think that the
user path is ignored (which is a good thing)
--
Chuck Burns
The Southern Libertarian
http://www.thesouthernlibertarian.com/
Ind
I recently source-up'd to 10-current, and began the slow process of rebuilding
all my installed ports, devel/google-perftools fails with an undeclared
"__isthreaded"
The following should be more than enough information.
Thanks,
Chuck Burns
root@freebeast /usr/src
BL for pass/fail blocking-- aside from
postmaster.rfc-ignorant.org, maybe, and even that one likely needs some
whitelisting if your mail system has a non-trivial # of users-- instead,
consider using RBLs for scoring.
Regards,
--
-Chuck
___
freebsd
nd GhostBSD uses the gnome 2.32 environment.
If you want something else, feel free to create your own. There is nothing in
the BSD license that prevents you from doing that.
Instead of complaining that SOMEONE ELSE should do something that YOU want
done, why not just do it your
st be built from source, and SHOULD always point to the latest source
code.
If you are using pkg_add -r to install software, on anything but
release versions, you should expect breakage.
If you do not wish to build from source, then you should p
Hi--
On Nov 8, 2011, at 4:32 PM, Dan The Man wrote:
> On Tue, 8 Nov 2011, Chuck Swiger wrote:
>> On Nov 8, 2011, at 3:47 PM, Dan The Man wrote:
>>> In the daily cron "Daily run output" email always get the following:
>>>
>>> Verifying gro
o adopt this change back into FreeBSD-- I've seen a few people wanting
to increase MAXLOGNAME since 2003 or so.
Regards,
--
-Chuck
___
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"
dy aware of this, then my apologies.
Chuck
___
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"
g as "-1"
Also, I am running zfs root, if that makes a difference
--
Chuck Burns
"We have the right as individuals to give away as much of our own money as we
please in charity; but as members of Congress we have no right to appropriate
a dollar of the
no longer technically, current, but
since it isn't released yet, I figure it's close enough)
--
Chuck Burns
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
be) fully bug-for-bug "compatible" with GCC. In this
case, at least, clang is reporting legitimate issues which should be fixed,
even if folks continue to build lsof with GCC from now until the end of days.
To echo a word someone else just used, I'm baffled as to why you would hold
s
ot even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Regards,
--
-Chuck
___
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 Sep 1, 2011, at 12:00 PM, Matt Thyer wrote:
> Shouldn't we use MBR partitioning instead of GPT for the memstick image ?
They aren't exclusive. Anything which doesn't understand GPT should
fall back to the 'protective' MBR kept inside the GPT fo
-mno-align-long-strings -mpreferred-stack-boundary=2 \
-mno-mmx -mno-3dnow -mno-sse -mno-sse2
INLINE_LIMIT?= 8000
.endif
Trying to override the default compiler flags to force it to use MMX/SSE is
simply not going to work.
Regards,
--
-Chuck
_
it consuming CPU until it actually gets
more work to do.
See select(2), kqueue(2), and friends.
Regards,
--
-Chuck
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
otCamp to setup a free partition
(intended for Windows, but reformat it for FreeBSD) and setup FreeBSD to boot
natively.
Regards,
--
-Chuck
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
hes to continue to try and help you.
Perhaps you were trying to be ironic by discussing someone else's grammar with
such a construct? :-/
--
-Chuck
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
t; invokes
> the kernel to memory ? Any help will be appreciated.
You're asking about the process here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html
...? Frankly, none of these are especially big, start by reviewing the source
code for 'em.
Regards,
--
-Chuck
1 - 100 of 369 matches
Mail list logo
