efore you reboot - 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/listinf
ss!
> Nothing works.
Nothing that you've tried works because everything you tried 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
(dp->d_name[1] != '\0' &&
You should replace the err() 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://lis
Bakul Shah writes:
> "Dag-Erling Smørgrav" 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.
necessarily equal to Y.
Since, 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
ht
e intended to go hand 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/ma
[redirected from -hackers to -security]
Jakub Lach writes:
> http://marc.info/?l=openbsd-tech&m=129236621626462&w=2
http://maycontaintracesofbolts.blogspot.com/2010/12/openbsd-ipsec-backdoor-allegations.html
DES
--
Dag-Erling Smørgrav -
ring_ into the change-auth-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
t to use it can" 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-ha
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.or
To test, stop nscd, then run it from the command line like so:
$ su -
# cd /tmp
# ulimit -c 0
# /usr/sbin/nscd -nst
(do something in another terminal that causes it to crash)
# echo backtrace | gdb -batch -x /dev/stdin /usr/sbin/nscd nscd.core
and send me the output from both nscd and gdb once it cr
and even 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@
t happens?
> 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 l
ly 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
Michael Bushkov 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.
Robert Simmons 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 Smørgrav
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/listi
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/ma
parate 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@
works
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
00
;; AUTHORITY SECTION:
des.no. 3600IN NS ns.des.no.
des.no. 3600IN NS ns.hyp.net.
;; ADDITIONAL SECTION:
ns.des.no. 3600IN A 194.63.250.121
;; 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
. If you know the people who run it, you 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
broadb
race is that its interactive mode is useful for playing text adventures
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"
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"
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
Konstantin Belousov writes:
> "Dag-Erling Smørgrav" 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
Konstantin Belousov writes:
> "Dag-Erling Smørgrav" 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 perc
grarpamp 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
le/9/share/mk/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
Dimitry Andric writes:
> Dag-Erling Smørgrav 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,
>
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"
verting 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
___
Wojciech Puchar writes:
> Lev Serebryakov writes:
> > It is not exact so. Some Atoms on some motherboards with some
> > firmwares are 64-bit CPU.
> don't know of any now in shops that are not
http://soekris.com/products/net5501.html
http://soekris.com/products/net6501.h
e 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, send
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/cd
"Steven Hartland" 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://lists.fre
Daniel Rudy <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > man 3 devinfo
> A little too late since I already hacked the source for sysctl(8) and
> figured out how it works.
The dev sysctl tree contains only a subset of the information
ntil the mount succeeds.
No, it will fail immediately (as seen above) if it can't resolve the
server name. The only way to fix this is to modify mount_nfs to sleep
and retry in such cases. The *current* sleep-and-retry code is in the
NFS mount code in the kernel, which doesn't come in
Mike Meyer <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Mike Meyer <[EMAIL PROTECTED]> writes:
> > > How about an extra flag in your fstab? The default behavior for
> > > mount_nfs is to keep retrying until the mou
t test it on FreeBSD 6.2 i386 -
> without this check a can map 2400 Mb file.
There's very little to gain from doing so. If you need more address
space than 2 GB, switch to a 64-bit platform.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd
(ataraid) to recognize the on-disk configuration data.
This is *not* a RAID controller, BTW, merely a SATA controller with a
RAID-capable BIOS.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.f
anks in advance.
This is usually handled by refusing to unload the module if it still
as active consumers.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Because you aren't - somebody is forwarding list traffic to you,
> > possibly maliciously.
> How can I stop it?
I don't know, we need to figure out who's forwarding this
"Ali Mashtizadeh" <[EMAIL PROTECTED]> writes:
> Is there a way to detect a cdrom insert/eject (in the kernel or usermode)?
> Or is there a way to check a media change?
No, you have to poll.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
two of the CPUs
during installation, this should be fairly easy to fix: change the
definition of NLAPICS in /usr/src/sys/{amd64,i386}/acpica/madt.c and
rebuild your kernel, then boot with ACPI enabled and report back to
us.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
rogrammable? not that I am suggesting that, I
> can think of headaches of all the places (like interrupt tables)
> where it needs to be changed, not to mention the worry that the
> lower APIC IDs were assigned to IOAPICs.
I don't know, you'd have to ask jhb@ about the details.
D
emporary disk storage.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e it on your systems
> if you like.
Not if you want to use pre-built packages. You made sure of that when
you decided (against my objections) to include .la files in packages.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-
oducing .la files which override the
existing mechanism and *do* hardcode directories is a regression.
I don't buy the argument that "KDE won't build without them", or
whatever it was you used to justify this. There is nothing an .la file
does which can't be done more
Once you realize that the vanilla ice cream is right next to
the check-out register while the others are deeper within the store and
therefore take considerably longer to get, you start looking for vapor
lock.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
d in
the presence of .la files. Please understand that they are the problem,
not the solution.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ivan Voras <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav wrote:
> > Ivan Voras <[EMAIL PROTECTED]> writes:
> > > You can inspect s sqlite database with the provided utility. Unless the
> > > database gets corrupted (which it tries to avoid by respec
Ivan Voras <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav wrote:
> > The world would be a much nicer place if people would stop redefining
> > technical terms to mean whatever suits them.
> I think you're overreacting. You say: if the database is consistent,
&g
sure consistency?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
y
copy of the package in memory or on disk; you extract the metadata in
memory, and the rest of the package directly in its final location.
AFAIK, pkg_create makes sure that +CONTENTS is always the first file in
the archive, precisely to make this possible. The fact that pkg_add
doesn't take ad
Roman Divacky <[EMAIL PROTECTED]> writes:
> ruby2.0 will come with a virtual machine which should speed up things. ruby2.0
> is expected "soon enough" (2008?)
Sure, just like Perl 6...
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
sr break this? Of course, equally valid
> is the question "what will break if I set LOCALBASE=/usr"? Hmm. I
> think I may found out
For one, man pages for ports will end up in the wrong place (/usr/man
instead of /usr/share/man)
Michel Talon <[EMAIL PROTECTED]> writes:
> Seriously, the FreeBSD package system is in great need of a profound
> overhaul, pretending it works well is complete denial of reality.
Perhaps, but I seriously doubt that you are the correct person for the
job.
DES
--
Dag-Erling Smørg
#x27;t need to. Your code should build cleanly on a stock install
of FreeBSD 6.0 or newer.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mike Meyer <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Mike Meyer <[EMAIL PROTECTED]> writes:
> > > How would setting LOCALBASE=/usr break this? Of course, equally valid
> > > is the question "what will break
Tom Judge <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Michel Talon <[EMAIL PROTECTED]> writes:
> > > Seriously, the FreeBSD package system is in great need of a profound
> > > overhaul, pretending it works well is c
ority is to fix your base system,
not muck around with packages. They can wait until the base system is
working again.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
/" it gives no error or warning and
> just drops to a "Manual mount root specification" prompt. If I type
> "ufs:ad0s1a" it boots up and everything is perfect. This is the same
> slice "/" was on the old drive as well.
What's in your
"Thomas Sparrevohn" <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > There is a reason why people have been discussing this for ten years
> > without getting anywhere.
> I suspect that is because that by and large the
Alexander Leidinger <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > The existence of .la files is a bug.
> I fully agree [but this needs to be addressed upstream]
Note that we are apparently not the only ones dissatisfied with thi
7 +1442,7 @@
;;
freebsd*) # from 4.6 on
shlibpath_overrides_runpath=yes
-hardcode_into_libs=yes
+hardcode_into_libs=no
;;
esac
;;
I've chosen not to change the default for versions older than 4.6.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
's still pretty
impressive - especially the fact that sqlite imported the index file
directly without any form of preprocessing.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
${WRKSRC}/configure
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Mohsen Pahlevanzadeh <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > [The] code should build cleanly on a stock install of FreeBSD 6.0 or
> > newer.
> Our FreeBSD is 4.11 because we can't use another version.
In that case, we
gt; fact, dealing with sources seems to be a noticable weakness for them.
apt-get --build source
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To u
David Cramblett <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > What's in your /boot.config and /boot/loader.conf?
> I have no boot.config.
>
> [EMAIL PROTECTED] /]# cat /boot/loader.conf
> # -- sysinstall generated del
"Matthew D. Fuller" <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Beats me... I can't even remember what userconfig_script is
> > supposed to do. Note that support for 5.2.1 ended on July 31, 2004.
> Neither can I,
m within
> kernel space and dump characters into it.
Look at the ktrace code.
Note that it opens the file in userland and passes it down to the
kernel. You may want to consider a similar mechanism.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
tty much rules them out then.
It would, if it were true. It isn't.
apt-get --build source package_name
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
st as well been a custom
query language stripped of SQL's warts), and ACID. The only thing it
lacks is strong typing. Implementing strong typing and a better query
language on top of the SQLite storage and relational engine is left as
an exercise to the reader :)
DES
--
Dag-Erling Smørgra
ions ON PURPOSE to discourage the practice.
Is there a web page somewhere (or an archived mailing list discussion,
or whatever) which discusses the issue and explains the rationale for
intentionally generating incorrect code?
DES
--
Dag-Erling Smørgrav
a file table. Different threads have
different file tables.
If you want to read from or write to files within the kernel, you need
to operate directly on vnodes, not on file descriptors.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-ha
-sleepable lock.
> I tried wrapping the call to kio_write in a mutex, in case there was a
> race condition caused by multiple threads trying to write to the file
> at the one time, but that hasn't made a difference at all.
It complains about sleeping with a non-sleepable lock held
Lawrence Stewart <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Since you are writing kernel code, I assume you have KDB/DDB in your
> > kernel and know how to use it.
> I don't know how to use them really. Thus far I haven&
els are flush to the left
(c-set-offset 'label [0])
;; Fill column
(make-local-variable 'fill-column)
(setq fill-column 74))
(add-hook 'c-mode-common-hook 'des-knf)
As for how to cross-build, read build(7).
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
probably be the default.
> I'm not familiar with forth, otherwise I'd come up with a patch. Maybe
> I'll try learning it (argh, another language to learn...), or hack
> around a bit.
The box-drawing code is in frames.4th and should be fairly easy to
understand and mod
Jeremy Chadwick <[EMAIL PROTECTED]> writes:
> On Tue, Jun 12, 2007 at 04:07:40PM +0200, Dag-Erling Smørgrav wrote:
> > Jeremy Chadwick <[EMAIL PROTECTED]> writes:
> > > One could enable use of this with some loader.conf variable like
> > > loader_frames=&q
.
Any more nonsense you wish to share?
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
rwise), the first thing you'll be told is "it works for me on i386,
> have you tried i386?"
Absolute nonsense. FreeBSD is just as solid on amd64 as on i386, and
the people who do most of the kernel work in FreeBSD tend to have
up-to-date hardware (meaning Athlon64, Opteron, or Core
for debugging and will impact performance nega-
tively.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Brian Chu" <[EMAIL PROTECTED]> writes:
> I have a question about indentation. In the previously supplied
> .emacs hook, tabs are represented by 8 spaces.
No, Emacs automatically converts spaces to tabs according to the current
setting of tab-width, which is normally
"Brian Chu" <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > "Brian Chu" <[EMAIL PROTECTED]> writes:
> > > I have a question about indentation. In the previously supplied
> > > .emacs hook, tabs
the entry for the commit that deleted
it. The Attic serves absolutely no function except an increase in code
complexity, a minimal increase in speed for operations on the trunk, and
a corresponding decrease for operations on branches, since they must
check the Attic for files that are deleted on the
llers do, not sure about Sil or
nVidia MCP.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ess space is 36 bits
(64 GB) which is more than room enough for your 4 GB of RAM *plus* the
PCI configuration and MMIO space.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mail
off on a tangent, I too have several motherboards (965P-based)
which do not define any ACPI thermal zones, which leads me to wonder:
what is the preferred way to access thermal data these days? IPMI? Do
we have IPMI support in base or ports?
DES
--
Dag-Erling
ore than just PPP:
net/zlib.c optional crypto | geom_uzip | ipsec | \
mxge | ppp_deflate | netgraph_deflate
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing
70810.diff
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e temperature of 39°C and not 54°C (the box has a
2.4 GHz C2D but spends most of its time barely ticking over at 200 MHz)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> I've written a quick-and-dirty driver for the built-in digital
> temperature sensor in Intel's Core and Core 2 CPUs (and Xeons built on
> the Core architecture).
Rui Paolo (SoC student) already had a driver which was far b
ads, which it DOES do under XP.
All modern disks (since at least the early 1990s) automatically park
their heads when they lose power. There is no need to do it in
software.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org
egs, rs->sizeof_g_packet, 0);
> +memset (regs, 0, rs->sizeof_g_packet);
> for (i = 0; i < NUM_REGS + NUM_PSEUDO_REGS; i++)
>{
> struct packet_reg *r = &rs->regs[i];
These should go upstream to the gdb maintainers ([EMAIL PROTECTED]).
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Simon 'corecode' Schubert <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > All modern disks (since at least the early 1990s) automatically park
> > their heads when they lose power. There is no need to do it in
> > softwa
a
> > > clean cvsup.
> > Because we are so far away it is hard to keep things sinkronized.
> How is that the case?
Humor detector on the fritz again, Kris? :)
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@
a clean
> > > cvsup.
> > Because we are so far away it is hard to keep things sinkronized.
> We really need to plug those holes.
sinkholes?
*ducks* *runs*
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.o
1 - 100 of 726 matches
Mail list logo
