. This should eliminate the need for ivoras@'s gnop trick
when creating ZFS pools on Advanced Format drives.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_geom.c
===
--- sys/cddl/contrib
Steven Hartland kill...@multiplay.co.uk writes:
Hi DES, unfortunately you need a quite bit more than this to work
compatibly.
*chirp* *chirp* *chirp*
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http
/products/net6501.html
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
trying to force your worldview on them. Maybe they know something you
haven't learned yet.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
community.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
by diverting such efforts to other
man power or resources required areas.
You're assuming that maintaining i386 as a tier 1 platform really *does*
add significantly to our workload.
You should also check your calendar :)
DES
--
Dag-Erling Smørgrav - d...@des.no
/bsd.own.mk(revision 244989)
+++ stable/9/share/mk/bsd.own.mk(working copy)
@@ -581,6 +581,8 @@
.if ${MK_CLANG} == no
MK_CLANG_IS_CC:= no
+.elif ${MK_GCC} == no
+MK_CLANG_IS_CC:= yes
.endif
MK_LIBCPLUSPLUS?= no
DES
--
Dag-Erling Smørgrav - d...@des.no
Dimitry Andric d...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
The following patches (for head and stable/9) automatically enables
CLANG_IS_CC if GCC is disabled but CLANG is not. Any objections?
This looks fine to me. Otherwise, if ${CC} isn't set to clang,
buildworld
grarpamp grarp...@gmail.com writes:
Any of hundreds of committer and admin accounts could be compromised
with the attacker silently editing the repo.
FUD. Committer accounts don't have direct access to the repo.
DES
--
Dag-Erling Smørgrav - d...@des.no
Konstantin Belousov kostik...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
+ otable = fdp-fd_ofiles;
+ ofileflags = fdp-fd_ofileflags;
These two new calculations could be unused if the function return early.
I assume you mean assignments, not calculations. I trust
Konstantin Belousov kostik...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
I assume you mean assignments, not calculations. I trust the compiler
to move them to where they are needed - a trivial optimization with SSA.
It is a dereference before the assignment, so I perceive
aside for that purpose.
(I assume that the old behavior was harmless, since it has persisted for
decades, but it was certainly confusing.)
The slightly repetitive nature of the new code is intentional.
DES
--
Dag-Erling Smørgrav - d...@des.no
Index: sys/kern/kern_descrip.c
.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
(1), but dig(1) is
not nearly as widely used, and ldns's drill(1) supports the same
command-line syntax for the most common operations.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
is that they are separate from the
authoritative nameserver (named). Yes, they are, but they have a *lot*
of code in common. In fact, *most* of the code in BIND is common code
shared between named, dig etc.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers
with thousands of clients, but I doubt my boss is going to let me run
performance comparisons on the university's network)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
;; Query time: 0 msec
;; SERVER: 194.63.250.121
;; WHEN: Mon Jul 9 23:22:23 2012
;; MSG SIZE rcvd: 128
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
might let them know
that it is inadvisable to process recursive queries from outside their
own network.
FWIW, the reply I got was not truncated. Perhaps there is a transparent
DNS proxy somewhere between you and 178.250.72.130 - quite common with
broadband CPE.
DES
--
Dag-Erling Smørgrav - d
implemented with DNS TXT records :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Robert Simmons rsimmo...@gmail.com writes:
OpenSSH 6.0p1
No. It doesn't build cleanly on FreeBSD (I reported two issues during
the pre-release cycle, one was fixed but the other was not), and even if
it did, it's too big a change to push through on such short notice.
DES
--
Dag-Erling
.
I'm willing to import and maintain unbound (BSD-licensed validating,
recursive, and caching DNS resolver) if you remove BIND.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
?
I'd like to see it stay in base. Moving it (slowly) towards a point
where we can turn it on by default would be cool.
Agreed, in principle.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
to Artem Belevich
earlier in this thread.
While we're at it, I'd be very grateful if someone could email me a
quick and dirty guide to setting up an LDAP server for testing. I have
too much on my plate right now to start reading documentation...
DES
--
Dag-Erling Smørgrav - d...@des.no
Michael Bushkov bush...@freebsd.org writes:
2. Consequences of the aforementioned problem can probably be
corrected by using _setsockopt(..., SO_NOSIGPIPE) in
__open_cached_connection() in nscachedcli.c
That sounds like a workaround rather than a fix...
DES
--
Dag-Erling Smørgrav - d
in one end to finding someone willing
to clean it up and maintain it and enable it by default in the other.
(no, I'm not volunteering to maintain it)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http
of SIGPIPE? I could never reproduce
the bug, but both users who reported problems used ldap, and I don't
have an LDAP server to test against, so I thought it might be specific
to LDAP.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
if it could, it would still
have to query the backend every time, so you might still get a longish
timeout for every lookup, depending on the type of backend and the
reason it failed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org
-token function
pam_chauthtok(...), which always jumps in an interactive pw-changing
loop.
There is no reliable way to do that. You don't even know that there is
such a thing as a password.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers
[redirected from -hackers to -security]
Jakub Lach jakub_l...@mailplus.pl writes:
http://marc.info/?l=openbsd-techm=129236621626462w=2
http://maycontaintracesofbolts.blogspot.com/2010/12/openbsd-ipsec-backdoor-allegations.html
DES
--
Dag-Erling Smørgrav - d...@des.no
in hand. I would have preferred that
contexts were actually tied to subtrees, but I had to play the ball I
was given.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
, as you point out, the coretemp device is a child of the
corresponding cpu device, there is no risk of orphaning the temperature
OID.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
() call with a warn() call instead of removing
it outright.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers
Bakul Shah ba...@bitblocks.com writes:
Dag-Erling Smørgrav d...@des.no writes:
You should replace the err() call with a warn() call instead of
removing it outright.
That would print the err msg twice as opendir (or something) already
seems to report the error. Try it!
Oh, OK.
DES
--
Dag
- it used to be necessary, but ISTR someone hacked
around it to make it easier to run 32-bit chroots on amd64.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
was wrong.
You can't just make something up and expect it to work because you want
it to work. Read the documentation and use the proper tool for the
proper job.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http
9673 95689555.5 107.12143
+ 4 15359 15359 15359 15359 0
9413 what? Puppies?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http
Peter Jeremy peterjer...@acm.org writes:
Dag-Erling Smørgrav d...@des.no wrote:
9413 what? Puppies?
Ooops, sorry - KB/sec as reported in the dump summary.
Thank you :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org
-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Alexander Best arun...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
No. Where did you get that idea? To repeat what I've said before -
several times - in this thread, a modern disk drive can handle hundreds
of thousands of controlled unloads but only a few hundred emergency
months. Remember, there was a huge flap a couple of years
when Ubuntu shipped with a default timeout of 90 seconds, which is more
than ten times more than what you suggest.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing
shutdown, because you should
know better, and following your advice could damage people's hardware.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
to mechanical damage to
the arms.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
that - the central
feature is their dynamically adjusted rotational speed, which allows
them to conserve power without spinning all the way down.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
the new API if it is available and the old one if it isn't.
Let's try with the patch attached...
Mailman strips binary attachments. The correct MIME type is
text/x-patch.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing
is what happens when the drive loses power while still
spinning).
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd
Alexander Best arun...@freebsd.org writes:
so how about forgetting about expand_number() and simply introducing a
maximum buffer size of 1 megabyte?
so how about just leaving the code alone? :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd
Alexander Best arun...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Alexander Best arun...@freebsd.org writes:
so how about forgetting about expand_number() and simply
introducing a maximum buffer size of 1 megabyte?
so how about just leaving the code alone? :)
i
has a full camcontrol.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Andresen, Jason R. jandr...@mitre.org writes:
Dag-Erling Smørgrav d...@des.no writes:
I see no reason why sector size should be a selection criterium. Just
buy the disk that gives you the best performance and / or capacity for
your money. WD Green disks are cheap, but other vendors offer
not sure, but i think fetch(1) is BSD specific so no POSIX regulations
need
to be taken into consideration. but you probably know more about this matter.
fetch(1) is 100% home-grown.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers
Xin LI delp...@gmail.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Xin LI delp...@gmail.com writes:
My 2 cents: I think we don't really need to care about the size
for rescue binary after the splitfs VFS layer have been introduced
to libstand? Build of release split MFSROOT
Alexander Best arun...@freebsd.org writes:
so how about something like this? the fetch(1) manual would have to be changed
a bit to state that if '-B val' 1G it silently gets set to 1G.
1 GB is ridiculously large. 1 MB should be plenty.
DES
--
Dag-Erling Smørgrav - d...@des.no
shouldn't they? it's their decision
actually.
Good point... although if they set it too high, either malloc(3) will
fail - if they're lucky - or fetch(1) will crash when the system runs
out of physical RAM and swap, and they'll have to start over.
DES
--
Dag-Erling Smørgrav - d...@des.no
distribution) the argument to -S can not be
expressed in [kMGTEP]B.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd
is that big when it's crunched with the
rest of /stand.
textdata bss dec hex filename
268751 26464 54112 349327 5548f camcontrol-crunch
355122 27064 58904 441090 6bb02 camcontrol-full
DES
--
Dag-Erling Smørgrav - d...@des.no
should be a selection criterium. Just
buy the disk that gives you the best performance and / or capacity for
your money. WD Green disks are cheap, but other vendors offer models
with the same capacity and twice the speed for only 5% or 10% more.
DES
--
Dag-Erling Smørgrav - d...@des.no
, that for two subsequent phybs invocations there is big
difference in timings for the same parameters.
Yes. WD Green disks suck.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Thiago Damas tda...@gmail.com writes:
ATA 4K sector issues
http://lists.freebsd.org/pipermail/freebsd-hackers/2010-March/031154.html
Yes, we know. That's what this entire thread (and a zillion others
before it) is about.
DES
--
Dag-Erling Smørgrav - d...@des.no
still have
to include the original license, disclaimer and copyright statement.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
Ilya Bakulin webmas...@kibab.com writes:
Dag-Erling Smørgrav d...@des.no writes:
Why did you shift the gnop? Did you short jumper 7-8?
No, 7-8 remained as-is. ad7p1 was created using:
#gpart add -t freebsd-ufs -s 10G -b 63 ad7
So it begins at sector #63, but physical 4096-block begins
it, that table either did not exist or was empty.
That was three years ago, though, so my recollection is a bit fuzzy.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
Garrett Cooper gcoo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
It might be a good idea to introduce TUNABLE_POINTER and TUNABLE_SIZE.
I would actually argue against doing that because it would only create
divergence between sysctl and tunable KPIs...
Not if we also
jhell jh...@dataix.net writes:
On stable/8 this is needed to build. Seems the need for linking against
libutil came in revision r211233.
Yes, I forgot to commit the Makefile. Thank you for reminding me.
DES
--
Dag-Erling Smørgrav - d...@des.no
121 of Atapi-7
volume 1 (google for ata-atapi-7.pdf).
Yes. We already support this. The problem is that WD's Advanced Format
disks (or at least some of them) lie.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
reports to the BIOS.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
the label - AF disks have AF-specific jumper
settings.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers
Ivan Voras ivo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Not sure what you mean. The original issue was that someone had used
TUNABLE_INT() for something that was actually a memory address. I
changed it to TUNABLE_ULONG(). Of course, if your tunable is a boolean
hw.pci.host_mem_start
hw.physmemstart
The following are not addresses, but can be 32 bits on 64-bit machines
and even on some 32-bit machines using PAE / PTE:
hw.physmem
vm.kmem_size
vm.kmem_size_max
vm.kmem_size_min
It might be a good idea to introduce TUNABLE_POINTER and TUNABLE_SIZE.
DES
--
Dag-Erling
for ages).
As you would know if you had followed the discussion about WD EARS
disks, gnop does what you want and is currently the recommended
solution.
I am looking into a permanent solution and would appreciate if people
held off on this for a couple of weeks.
DES
--
Dag-Erling Smørgrav - d
Ivan Voras ivo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Marius Nünnerich mar...@nuenneri.ch writes:
I did not think of a new GEOM class that looks like glabel but one
that has no metadata stored on disk . It is then activated and
controlled by loader.conf
if with appropriate key entered
to the port we will get non-0xff value.
Sounds gross, but if there's no other way, I guess it'll have to do. I
imagine you check the PCI id etc. first?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org
it was signed.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
the change in response to a
bug report), but there must have been one, either on IRC or in Karlsruhe.
In any case, I never removed TUNABLE_INT(), so...
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http
Garrett Cooper gcoo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Perhaps. I don't remember all the details; I can't find a discussion in
the list archives (other than me announcing the change in response to a
bug report), but there must have been one, either on IRC
Not related to your problem, but related to $SUBJECT: make sure to use
-Psomething in LFLAGS so your lex-generated symbols don't conflict
with those present in applications that use your library, or in other
libraries those applications may use.
DES
--
Dag-Erling Smørgrav - d...@des.no
Xin LI delp...@delphij.net writes:
Dag-Erling Smørgrav d...@des.no writes:
Perhaps the motherboard has additional watchdog hardware? If you
disable the watchdog in BIOS, does ichwd still work?
If I kill -9 watchdogd the system do reset itself so I think ichwd(4)
really works even if BIOS
catch it or pass it through.
Unfortunately, although it is possible for the ichwd driver to detect
programatically (by checking an MSR) if the watchdog timer is disabled
in hardware, it is not possible to determine whether it is disabled in
firmware.
DES
--
Dag-Erling Smørgrav - d...@des.no
hardware? If you
disable the watchdog in BIOS, does ichwd still work?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail
, the top-level make file just
continues on to the next label as if no error occurs.
Make looks at tee's exit status, not the script's.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
work, because tail won't start until the build is done. You
should just pass the file name as an argument to your script and handle
it there.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org
to switch to .o on other platforms?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Ed Schouten e...@80386.nl writes:
In my opinion, we should just rename mailwrapper to whateverwrapper
and list the lpr programs in there as well.
Take a look at /etc/alternatives in any Debian-based Linux distro...
DES
--
Dag-Erling Smørgrav - d...@des.no
the script immediately with a
non-zero exit status if any command after the set line fails.
However, I don't see the point of using shell scripts in the first
place...
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
Bakul Shah ba...@bitblocks.com writes:
Except read doesn't do it quite right:
$ ps | (read a; echo $a ; grep zsh)
PID TT STAT TIME COMMAND
yeah, I forgot that it drops leading whitespace...
DES
--
Dag-Erling Smørgrav - d...@des.no
that it will
not consume more input than necessary.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
; nhead 3; echo hi; nhead 3)
6
7
8
hi
9
10
11
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr
ten (variable == variable)
comparisons and b) good compilers will warn about bare assignments used
as conditions.
The only practical effect of Yoda style is to make code harder to read.
Your .sig is strangely appropriate...
DES
--
Dag-Erling Smørgrav - d...@des.no
Dominic Fandrey kamik...@bsdforen.de writes:
Dag-Erling Smørgrav d...@des.no writes:
Your .sig is strangely appropriate...
Not my invention, this is a pretty common one, used by many people
on the net. I actually have no idea where it comes from.
My point is that it is strangely appropriate
Sergey Babkin bab...@verizon.net writes:
I wonder if a version control system, like SVN, could be used to keep
track of all the changes in /etc. (Or maybe it already is and I'm
simply out of date).
arch is commonly used for things like this.
DES
--
Dag-Erling Smørgrav - d...@des.no
agree, please commit.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Dag-Erling Smørgrav d...@des.no writes:
File is right. The kernel contains relocation entries so kernel modules
can be linked against it.
relocation entries is possibly not the right term, someone with better
knowledge of ELF will have to correct me.
DES
--
Dag-Erling Smørgrav - d...@des.no
Tsuyoshi Ozawa ozawa+...@t-oza.net writes:
Julian Elischer jul...@elischer.org writes:
Who are you? and what have you done with DES?
Sorry [...]
Never mind, Julian was making a joke at my expense.
DES
--
Dag-Erling Smørgrav - d...@des.no
and no shared
libraries are involved. However, it is possible to dynamically load
modules using kldload. See the appropriate man page.
File is right. The kernel contains relocation entries so kernel modules
can be linked against it.
monolithic means something else entirely.
DES
--
Dag-Erling
Julian Elischer jul...@elischer.org writes:
Who are you? and what have you done with DES?
I gave him a week off...
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
, and there was actually a GSoC project last year, but nothing came
out of it. I really hope we can commit this soon!
BTW, at one point, in your blog, you write periodic tick mode instead
of dynamic tick mode, which had me confused for a moment.
DES
--
Dag-Erling Smørgrav - d...@des.no
Mark nesterovych m.nesterov...@gmail.com writes:
Decided to write BSD licensed grep and provide it to FreeBSD project if
success.
There is one already: textproc/bsdgrep.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org
then turn into a wakeup(update_rtc).
Sounds good to me, but if only that thread has access to the RTC, why
bother with a mutex?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Ivan Voras ivo...@freebsd.org writes:
Dag-Erling Smørgrav d...@des.no writes:
Bourne shell is a perfectly fine programming language if you know
how to use it.
I'll agree that it's fine but only in the abstract - e.g. that it is
Turing complete :)
Emphasis on if you know how to use
1 - 100 of 741 matches
Mail list logo
