right file...
>
> .bash_profile for bash and .tcshrc for tcsh.
For bash the solution I've been using for like 15 years is that
my .bash_profile (used only for a login) contains simply:
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
And everything goes into .bashrc which runs on non-lo
Why are you ignoring PAE? It's been working for me for years.
-- Ian
___
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"
On Sun, 2013-09-22 at 19:45 -0400, Glen Barber wrote:
> On Sun, Sep 22, 2013 at 05:37:51PM -0600, Ian Lepore wrote:
> > On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
> > > On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
> > > > What's the r
On Sun, 2013-09-22 at 19:27 -0400, Glen Barber wrote:
> On Sun, Sep 22, 2013 at 05:18:25PM -0600, Ian Lepore wrote:
> > What's the right way to launch the bourne shell from a makefile? I had
> > assumed the ${SHELL} variable would be set to "the right" copy
> &g
with
the script name (as opposed to launching the script and letting the #!
do its thing, which doesn't work if the source dir is mounted noexec).
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
OF on stdin or the
remote shuts down that half of the connection.
How all this applies to netcat's ability to do connectionless (UDP)
stuff probably makes the whole thing that much more interesting.
BTW, earlier in the thread you asserted more or less that telnet is for
interactive and nc for
serial and parallel ports
and so on). They're instantiated based on hints that are definitive, so
I switched to returning BUS_PROBE_NOWILDCARD and sanity returned.
Then I remembered this email, so I applied your patch and re-tested and
everything still worked perfectly. Not exactly an exhausti
br that it needs to reimplement. Are there any better examples?
The one like that I use the most is "service netif restart fpx0" but I'm
not sure the complex network stuff will be the cleanest example of
anything except how to do complex network stuff. :)
-- Ian
addr 0x100" to the /boot/loader.rc file to fix that. You can also enter
it by hand at the loader prompt first to see if that helps... just hit a
character (other than return) while it's loading the kernel, enter that
command, then enter 'boot'.
-- Ian
On Wed, 2013-03-06 at 09:17 -0500, John Baldwin wrote:
> On Thursday, February 28, 2013 2:59:16 pm Ian Lepore wrote:
> > On Tue, 2013-02-26 at 15:29 -0500, John Baldwin wrote:
> > > On Friday, February 22, 2013 2:06:00 pm Ian Lepore wrote:
> > > > I ran into some trou
On Tue, 2013-02-26 at 15:29 -0500, John Baldwin wrote:
> On Friday, February 22, 2013 2:06:00 pm Ian Lepore wrote:
> > I ran into some trouble with rtprio_thread() today. I have a worker
> > thread that I want to run at idle priority most of the time, but if it
> > falls to
ss a key before
> loader(8) is loaded and enter kernel image.
>
> at least it was like that.
Oh, good point, maybe it'll just work fine (although it's been years
since I last loaded an x86 kernel directly from boot2, way back before
the days of acpi and smap data and all of that mo
ios.
Without a loader you may need to modify the kernel to get that
information in some other way early in startup.
-- Ian
___
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"
I'm curious why the concept of scheduling niceness applies only to an
entire process, and it's not possible to have nice threads within a
process. Is there any fundamental reason why it couldn't be supported
with some extra bookkeeping to track niceness per
t say why that matters).
Is this a reasonable way to fix this problem, or is there a better way?
-- Ian
___
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"
On Tue, 2013-02-12 at 22:34 +0200, Konstantin Belousov wrote:
> On Tue, Feb 12, 2013 at 09:03:39AM -0700, Ian Lepore wrote:
> > On Sun, 2013-02-10 at 12:37 +0200, Konstantin Belousov wrote:
> > > On Sat, Feb 09, 2013 at 02:47:06PM +0100, Jilles Tjoelker wrote:
> > > >
On Sun, 2013-02-10 at 12:37 +0200, Konstantin Belousov wrote:
> On Sat, Feb 09, 2013 at 02:47:06PM +0100, Jilles Tjoelker wrote:
> > On Wed, Feb 06, 2013 at 05:58:30PM +0200, Konstantin Belousov wrote:
> > > On Tue, Feb 05, 2013 at 09:41:38PM -0700, Ian Lepore wrote:
> >
On Sun, 2013-02-10 at 12:41 +0200, Konstantin Belousov wrote:
> On Fri, Feb 08, 2013 at 04:13:40PM -0700, Ian Lepore wrote:
> > On Wed, 2013-02-06 at 17:58 +0200, Konstantin Belousov wrote:
> > > On Tue, Feb 05, 2013 at 09:41:38PM -0700, Ian Lepore wrote:
> > > > I&#
egative value.
Does this look right to those of you who understand this part of the
system better than I do?
-- Ian
[1] No way using F_READAHEAD; I know about POSIX_FADV_RANDOM.
Index: sys/kern/kern_descrip.c
===
--- sys/kern/k
On Wed, 2013-02-06 at 17:58 +0200, Konstantin Belousov wrote:
> On Tue, Feb 05, 2013 at 09:41:38PM -0700, Ian Lepore wrote:
> > I'd like feedback on the attached patch, which adds support to our
> > time_pps_fetch() implementation for the blocking behaviors described in
>
tus that hasn't
been updated in four years?
-- Ian
___
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"
ty to block (forever or with timeout) until a new event occurs.
-- Ian
Index: sys/kern/kern_tc.c
===
--- sys/kern/kern_tc.c (revision 246337)
+++ sys/kern/kern_tc.c (working copy)
@@ -1446,6 +1446,50 @@
* RFC 2783 PPS-API implement
On Mon, 2013-01-28 at 18:02 +0200, Konstantin Belousov wrote:
> On Mon, Jan 28, 2013 at 08:11:47AM -0700, Ian Lepore wrote:
> > I've got a question that isn't exactly freebsd-specific, but
> > implemenation-specific behavior may be involved.
> >
> > I
one client/server stuff I've never
had quite this type of interaction (or lack thereof) between client and
server before.
-- Ian
___
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"
on a slightly longer
timeout than the NMI watchdog gives you the best of everything: you get
information if it's possible to produce it, and you get a real hardware
reset shortly thereafter if producing the info fails.
-- Ian
___
freebsd-hackers@f
ll-out performance with separate risk
mitigation strategies. I wouldn't set up a client datacenter that way,
but it's wholly appropriate for what I do with this machine.
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.
iled ("click of death")
within a six hour timespan of each other. Luckily I noticed the
clicking right away and was able to get all the data copied to another
array within a few hours, before they all died.
-- Ian
> 2 fails at the same moment is rather unlikely. Of course - every
tically store a crashdump to swap, then reboot the machine. If
that's not working, perhaps it locks up trying to store the dump?
If the hardware has a watchdog timer, enabling that might be the best
way to ensure a reboot on any kind of crash or hang.
-- Ian
> On Thu, Jan 17, 20
ust reboot itself after a 15 second pause.
-- Ian
>
> On Wed, Jan 16, 2013 at 10:13 PM, John Baldwin wrote:
>
> > On Wednesday, January 16, 2013 2:25:33 pm Sami Halabi wrote:
> > > Hi everyone,
> > > I have a production box, in which I want to install new kerne
of=/dev/null count=100 iflag=direct
100+0 records in
100+0 records out
51200 bytes (51 kB) copied, 0.0628582 s, 815 kB/s
Hmm, just before hitting send I saw your other response that SAS drives
behave badly, SATA are fine. That does seem to point away from dd
behavior. It might still be i
On Tue, 2013-01-15 at 16:10 -0800, Devin Teske wrote:
>
> > -Original Message-
> > From: Devin Teske [mailto:devin.te...@fisglobal.com] On Behalf Of
> > dte...@freebsd.org
> > Sent: Tuesday, January 15, 2013 3:10 PM
> > To: 'Ian Lepore
what these do, they're just
changes that affect files related to booting.
r233211
r233377
r233469
r234563
-- Ian
___
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"
I've got to ask why pthread_self()
isn't the right answer? The requirement wasn't "I need to know what the
OS calls me" it was "I need a unique ID per thread within a process."
-- Ian
___
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"
content that changes based on KERNCONF=, and sys/boot is
built during buildworld, not buildkernel.)
-- Ian
___
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"
ow exactly does this happen?
Assuming the 3.06 and 3.54 are firmware revision numbers, one might
speculate that ongoing testing showed higher sector failure rates than
intially expected, and thus newer firmware sets aside a few more sectors
as spares.
-- Ian
On Thu, 2012-11-15 at 17:47 +, Attilio Rao wrote:
> On 11/15/12, Ian Lepore wrote:
> > On Wed, 2012-11-14 at 22:15 -0800, Adrian Chadd wrote:
> >> Hi all,
> >>
> >> When debugging and writing wireless drivers/stack code, I like to
> >> sprinkle l
are higher on the list.)
When a new problem crops up that isn't harmless, it totally sucks that I
can't just turn on witness without first hacking the code to make the
known problems non-panicky.
-- Ian
___
freebsd-hackers@freebsd.org mai
e kept up to date
with any script renaming/numbering)?
-- Ian
___
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"
to manually string the series of
hardware/dma buffers together without copying the data. Is that sort of
usage still a good idea? (And would it actually be a performance win?
If I hand it off to the net stack and an m_pullup() or similar is going
to happen along the way a
On Sat, 2012-11-03 at 12:50 -0600, Ian Lepore wrote:
> On Sat, 2012-11-03 at 20:41 +0200, Konstantin Belousov wrote:
> > On Sat, Nov 03, 2012 at 12:38:39PM -0600, Ian Lepore wrote:
> > > In an attempt to un-hijack the thread about memory usage increase
> > > between 6.4
does that represent how many
pages are resident due to all the references from all the processes that
have the library open?
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
On Sun, 2012-11-04 at 09:36 -0700, Warner Losh wrote:
> On Nov 3, 2012, at 12:50 PM, Ian Lepore wrote:
>
> > On Sat, 2012-11-03 at 20:41 +0200, Konstantin Belousov wrote:
> >> On Sat, Nov 03, 2012 at 12:38:39PM -0600, Ian Lepore wrote:
> >>> In an attempt to
On Sun, 2012-11-04 at 09:36 -0700, Warner Losh wrote:
> On Nov 3, 2012, at 12:50 PM, Ian Lepore wrote:
>
> > On Sat, 2012-11-03 at 20:41 +0200, Konstantin Belousov wrote:
> >> On Sat, Nov 03, 2012 at 12:38:39PM -0600, Ian Lepore wrote:
> >>> In an attempt to
t;
I had completely missed the fact that jemalloc had its own manpage,
thank you.
Given that new information I think the pieces are in place to put
watchdogd on a memory diet. I'll work up a patch in the next couple
days
-- Ian
> The 'perfect' solution would obviously
On Sat, 2012-11-03 at 12:59 -0700, Xin Li wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 11/3/12 11:38 AM, Ian Lepore wrote:
> > In an attempt to un-hijack the thread about memory usage increase
> > between 6.4 and 9.x, I'm starting a new thread
On Sat, 2012-11-03 at 20:41 +0200, Konstantin Belousov wrote:
> On Sat, Nov 03, 2012 at 12:38:39PM -0600, Ian Lepore wrote:
> > In an attempt to un-hijack the thread about memory usage increase
> > between 6.4 and 9.x, I'm starting a new thread here related to my recen
chdogd to avoid wiring all of libm. The floating point is used just
to turn the timeout-in-seconds into a power-of-two-nanoseconds value.
There's probably a reasonably efficient way to do that without calling
log(), considering that it only happens once at prog
llowup with a separate
discusssion thread about that.
While jemalloc can explain the growth in VSZ between 6.4 and 9.x, it
doesn't look like mlockall() has anything to do with the original
question of why the RSZ got so much bigger. In other words, part of the
original que
etty
> > small.
> >
> Note that libc_r's thread stack is 64K, while libthr has 1M bytes
> per-thread.
That would help explain the large increase in virtual size, but not the
increase in resident size, right? In other words, there's nothing
inherent in libt
64MB of ram). That's a crazy
amount of growth for a relatively simple daemon.
-- Ian
___
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"
need to be defined on a 9.0 system, or is that
something that gets turned on automatically in an official release
build? (I'm always working with non-release stuff so I'm not sure how
that gets handled).
-- Ian
___
freebsd-hackers@freebsd.org maili
>
> Thanks,
> Erik
Look further up in sys/cddl/compat/opensolaris/sys/types.h, they're also
defined (as macros rather than enum) in the KERNEL case. They're also
defined (as enum) in sys/gnu/fs/xfs/xfs_types.h. (Once again, SlickEdit
pays for itself
On Fri, 2012-10-26 at 11:09 -0700, David O'Brien wrote:
> On Fri, Oct 26, 2012 at 09:41:36AM -0600, Ian Lepore wrote:
> > We have to be able to build the same source for multiple versions of
> > freebsd, so even finding all the old :U and :L and any other
> > incompa
'd just
trade "works in freebsd 10" for "broken in every other environment".
If there were some way to turn on a compatibility mode, we'd have a way
to slowly transition to the newer stuff over the course of a couple OS
versions. Eventually we'd reach the point where we no
ded is to
dig deeply into code (often including analyzing call chains) to evaluate
the consequences of any changes.
On the last 3 tasks in your list, I agree completely, just the sort of
thing you'd assign to an intern or new junior engineer to get them
started on a large ex
hen the division by
zero case could never happen. However, at least one of the config
statements handled by parse_lease_time() allows a value of zero.
Since nothing seems to ensure that backoff_cutoff is non-zero, it seems
like a potential source of div-by-zero errors too, in that same
function.
-- Ia
On Sun, 2012-09-02 at 19:50 -0600, Ian Lepore wrote:
> On Mon, 2012-09-03 at 00:35 +0100, Attilio Rao wrote:
> > Hi,
> > I was trying to use syslog(3) in a port application that uses
> > threading , having all of them at the LOG_CRIT level. What I see is
> > that wh
d the PR long ago, if the patches have drifted out of date I'll be
happy to re-work them.
-- Ian
___
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"
I haven't tried the nandfs layer yet, or writing to the flash.
-- Ian
___
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"
I really know nothing about this stuff, except that your request
triggered a memory that the atmel if_ate driver gathers some stats that
I've not seen in most other drivers.)
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/m
anything for hinted children. Adding a
"hint.somedev.0.at=somebus" and then forcing the bus to enumerate hinted
children amounts to forcing the bus to adopt a child it may not be able
to provide resources for, which sounds like a panic or crash waiting to
happen (or at best, no crash
ct the entry maps. I don't understand.
Oh hmmm, wait a sec... could it be that read-ahead or relocation fixup
or various other things caused lots of pages to be faulted in for the
vnode object (so they're resident) but not all of those pages are mapped
into the process because the path of
On Thu, 2012-07-12 at 17:08 +0200, Davide Italiano wrote:
> On Thu, Jul 12, 2012 at 4:26 PM, John Baldwin wrote:
> > On Thursday, July 12, 2012 9:57:16 am Ian Lepore wrote:
> >> On Thu, 2012-07-12 at 08:34 -0400, John Baldwin wrote:
> >> > On Wednesday, July 11, 20
On Thu, 2012-07-12 at 08:34 -0400, John Baldwin wrote:
> On Wednesday, July 11, 2012 5:00:47 pm Ian Lepore wrote:
> > On Wed, 2012-07-11 at 14:52 -0500, Paul Albrecht wrote:
> > > Hi,
> > >
> > > Sorry about this repost but I'm confused about the response
ep. Note that this rounding error in
calculating the length of a tick does not result in a systematic skew in
system timekeeping, because when each tick interrupt happens, the system
reads a clock counter register that may or may not be related to the
clock producing tick interrup
On Fri, 2012-07-06 at 16:45 -0400, Arnaud Lacombe wrote:
> Hi,
>
> On Fri, Jul 6, 2012 at 3:09 PM, Ian Lepore
> wrote:
> > On Fri, 2012-07-06 at 14:46 -0400, Arnaud Lacombe wrote:
> >> Hi,
> >>
> >> On Fri, Jul 6, 2012 at 11:33 AM, Arnaud Lacombe wr
make the connection
between unrelated devices. I think that implies that there would have
to be something near the root of the hiearchy willing to be the
owner/manager of dynamic resources.
-- Ian
___
freebsd-hackers@freebsd.org mailing list
htt
ing curious ... why would you *not* want a feature that
> tells you what to install if you type a command that doesn't exist on
> the system?
>
> Doug
>
The only response I can think of is... If you can even ask that
question, then there's no answer I could give that
On Wed, 2012-06-20 at 13:39 +0530, Varuna wrote:
> Ian Lepore wrote:
> >
> > Using the 'prepend' or 'supercede' keywords in /etc/dhclient.conf is
> > pretty much the standard way of handling a mix of static and dhcp
> > interfaces where the s
ail in
> error, please do delete it along with copies of it existing in any
> other format, and notify the sender immediately. The sender of this
> email believes it is virus free, and does not accept any liability
> for any errors or omissions arising thereof.
>
Using th
ever crash are not often booted
An embedded system may be booted or powered cycled dozens of times a
day, and boot time can be VERY important. Don't assume that the way you
use FreeBSD is the only way.
-- Ian
___
freebsd-hackers@freebsd.org mail
On Tue, 2012-06-12 at 23:45 +0300, Konstantin Belousov wrote:
> On Tue, Jun 12, 2012 at 08:51:34AM -0600, Ian Lepore wrote:
> > On Sat, 2012-06-09 at 22:45 +0200, Wojciech Puchar wrote:
> > > >
> > > > First, all memory allocated by UMA and consequently malloc(9)
fix the instruction-cache-disabled bug
that kills performance on VIVT cache architectures (arm and mips) and it
would reduce the amount of wired memory (that apparently doesn't need to
be wired, unless I've missed the implications of a previous reply in
this thread).
-- Ian
___
to add this option to
their kernel config.
I am VERY curious about the nature of this correlation between vfs
buffer space and wired memory. For the VM gurus: Is the behavior I'm
seeing expected? Why would memory become wired and seemingly never get
released back to one of the page queues
On Tue, 2012-05-22 at 09:59 -0700, Jason Usher wrote:
> Hi Ian,
>
> Thank you very much for taking a look at this, and for understanding what I'm
> talking about here.
>
> Comments inline, below...
>
>
> --- On Tue, 5/22/12, Ian Lepore wrote:
>
> >
e from freebsd 6.4, it appears that while an
rsa hostkey was supported, it would not be added to the server config by
default; it would only be used if you specifically configured it with a
HostKey statement in sshd_config. So maybe you can safely assume that
nobody was ever
On Fri, 2012-05-18 at 16:13 +0200, Svatopluk Kraus wrote:
> On Thu, May 17, 2012 at 10:07 PM, Ian Lepore
> wrote:
> > On Thu, 2012-05-17 at 15:20 +0200, Svatopluk Kraus wrote:
> >> Hi,
> >>
> >> I'm working on DMA bus implementation for ARM11mpcore pla
of
bounced.
It also might be nice to have a knob to enable logging when bouncing or
remapping is used to avoid partial cacheline operations, to make it easy
to find drivers that could be tweaked for better performance. If you're
bouncing 2 or 3 operations per second with a 4-byte buffer
/0 C2/100
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 233us
dev.cpu.0.temperature is provided by the coretemp(4) driver, maybe you
need to kldload it?
-- Ian
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebs
seems from this very minimal test that the implementation of echo
is correct, but the parsing of the command line in csh requires that the
\t in the arg be protected with quotes. (I don't normally spend any
longer in csh than it takes for a .cshrc to launch bash, and even that&
is not
a multi-GHz multi-core Xeon, it's a 180mhz embedded SoC with buggy
builtin devices that will drop or corrupt data if an interrupt happens
during the "do stuff here" part of the code.)
-- Ian
___
freebsd-hackers@freebsd.org mailing
On Wed, 2012-04-18 at 17:36 +0300, Andriy Gapon wrote:
> on 18/04/2012 17:22 Ian Lepore said the following:
> > YES! A size field (preferably as the first field in the struct) along
> > with a flag to indicate that it's a new-style boot info struct that
> > starts wit
On Wed, 2012-04-18 at 17:36 +0300, Andriy Gapon wrote:
> on 18/04/2012 17:22 Ian Lepore said the following:
> > YES! A size field (preferably as the first field in the struct) along
> > with a flag to indicate that it's a new-style boot info struct that
> > starts wit
t of loading the kernel) to be immune to
future changes.
This probably isn't a big deal in the x86 world, but it can be important
for embedded systems where a proprietary bootloader has to pass info to
a proprietary board_init() type routine in the kernel using
non-proprietary
s that aren't in the stock code and manage their resources.
It sure would be nice if some of those diffs could get rolled back in;
it would certainly make it easier for me to integrate things like
Marius' style cleanups back into our repo.
Anyway, if ongoing changes are going to be happe
On Wed, 2012-04-11 at 17:47 +0300, Konstantin Belousov wrote:
> On Wed, Apr 11, 2012 at 08:26:13AM -0600, Ian Lepore wrote:
> > On Wed, 2012-04-11 at 16:11 +0200, Mel Flynn wrote:
> > > Hi,
> > >
> > > I'm currently stuck on a bug in Zarafa-spooler that
locked
status of the signals as set up in main(). Try adding this line to
signal_handler() before it goes into its while() loop:
pthread_sigmask(SIG_UNBLOCK, &signal_mask, NULL);
-- Ian
___
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"
corresponding
state in external resources.
-- Ian
___
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"
ternative, in case there are use cases for the existing
> behavior, would be to provide either another "key" or a command-line
> flag that says "give me all the modes".
>
> Am I the only one who would find such a change useful?
>
> Thanks for any reality che
your statement that the driver should support only
primitive functions to draw lines and dots, that leaves the non-trivial
problem of font rendering to the app. Given your original goal, font
rendering is pretty much the bulk of what you want to do, is the app
layer the right place for it?
-- Ian
___
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"
ss space you need to map to get at your data. Two
things come to mind... have your kernel module export the address in a
sysctl (that feels kind of hack-ish but it should be quick and easy to
do), or use libkvm's kvm_nlist() function to locate the symbol within
your module (I think that shou
o back to Parallels 4
> >
> > FAILURE!!
> >
> > Go back to RELENG_8 LiveCD with Parallels 4
> >
> > SUCCESS!!
> >
> > What's going on here? I think ada(4) is my problem. Can someone please
> > provide
> > feedback? Willin
scenario where changing a drive from
gpt to mbr scheme results in all the gpt partitions reappearing after a
reboot. I concluded (but didn't take time to be absolutely certain)
that during boot the geom layer was seeing the backup gpt partition info
at the end of the disk and concluding that
f a manpage) function named
shutdown_nice() in sys/kern/kern_shutdown.c that will send a signal to
the init process if it's running or call boot(9) if not. Or maybe a
direct call to boot(9) is what you're looking for, if bypassing the
running of rc shutdown scripts and all is your goal. (Th
On Wed, 2012-01-18 at 01:17 +0200, Andriy Gapon wrote:
> on 17/01/2012 23:46 Ian Lepore said the following:
> > Now, before we're even really completely up and running on 8.2 at work,
> > 9.0 hits the street, and developers have moved on to working in the 10.0
> > world.
ite" (if you think FreeBSD lacks manpower to do release engineering,
imagine how hard it is for a small or medium sized business).
-- Ian
___
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"
n.
>
> Anyone else tinkering with one of these? Any
> hints? ;-)
>
> Tim
The freebsd-arm list would be the place for info. There's still work to
do to get FreeBSD running on a Cortex-A8, last I heard.
-- Ian
___
freebsd-hack
es a problem that
only happens when you read the same location repeatedly, and the nvram
driver never does that. But it would still be interesting to examine
the nvram.bin file and see if it "looks reasonable".
-- Ian
___
freebsd-hackers@fre
but
looking at the driver code, it does recalculate the checksum when it
writes to nvram.
-- Ian
___
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"
On Thu, 2012-01-05 at 10:33 -0500, John Baldwin wrote:
> On Wednesday, January 04, 2012 5:22:29 pm Ian Lepore wrote:
> > [...]
> > Because atrtc.c has a long and rich history of modifcations, some of
> > them fairly recent, I thought it would be a good idea to toss out my
1 - 100 of 234 matches
Mail list logo
