handy when the specfile is the absolute authority for the
contents of the image. It fails early and loudly, instead of causing
late and sometimes obscure run-time errors.
I checked NetBSD-current; the -X flag is available there.
Would someone like to commit it for me?
Eric
commit
> space to handle the entire dump uncompressed" made it too easy for us to
> run out of space on our /var/crash partition
Yes, please. I've run into this occasionally, but it never annoyed me
enough to fix it. Procrastination pays off yet again. ;)
Eric
__
gt;>>
>>> -Kimmo
>> dmesg(8) output of the system:
>>
>> http://pastebin.com/hqjsak2n
> Kimmo,
>
> Thanks for the information. Can you try following patch:
>
> cd /usr/src/usr.sbin/config
> fetch http://people.freebsd.org/~wkoszek/patch
On 12/13/2012 10:08, Ed Maste wrote:
I've been working generating userland debugging symbols, with the goal
that we'll build them for each release. The user could install them
along with the system, or later on when needed for debugging. The
symbols files will also be useful for profiling and t
On 11/01/2012 01:48, Alfred Perlstein wrote:
/* Registration of dumpers */
int
-set_dumper(struct dumperinfo *di)
+set_dumper(struct dumperinfo *di, const char *devname)
{
if (di == NULL) {
bzero(&dumper, sizeof dumper);
+dumpdevname[0] = '\0';
return (0);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In the process of the EFI on intel work, I ran across a strange issue.
The procedure for creating loader.efi goes something like this:
1) compile to ELF object files
2) generate an ELF executable with -Bsymbolic and a custom linker
script that puts
Received this yesterday, about Linux's plans for supporting secure
booting with EFI. I've looked into it as a possibility for FreeBSD, but
I won't be in a position to do anything about it for some time.
But the possibilities are enticing to say the least.
Original Message
Su
On 6/17/12 8:43 PM, Mike Meyer wrote:
Eric McCorkle wrote:
The -m32 flag seems to be the culprit; removing it fixes the problem.
This is why I was having problems, as the offsets in EFI_SYSTEM_TABLE
were wrong.
In any case, this is a pretty serious error, and someone should try to
On 6/17/12 8:26 PM, Adrian Chadd wrote:
Hiya,
don't suppose you could file a PR for this?
Typing one up just now, after figuring out the root cause.
The short version is this: __uint64_t gets defined in
as unsigned long. This breaks when you use -m32, in
which case sizeof(unsigned long)
On 6/17/12 6:45 PM, Eric McCorkle wrote:
On 6/15/12 6:44 PM, Eric McCorkle wrote:
int main() {
printf("%d\n", UINT64);
return 0;
}
Correction: it should be sizeof(UINT64)
___
freebsd-hackers@freebsd.org mailing
On 6/15/12 6:44 PM, Eric McCorkle wrote:
However, the EFI programs I produce using the EDK system work
properly, and don't have the same issues as the ones I produce using
what's in the base system.
Okay, after a whole lot of slogging, I figured out the root of the
problems I'
On 06/16/12 06:03, Andrey V. Elsukov wrote:
> Hi, Eric.
>
> Did you try the GNU EFI toolchain? It contains a good descriptions
> on how to build EFI application and we probably can use some
> suggestions even without importing it.
>
> http://sourceforge.net/projects/gnu-efi/
I've been working on EFI support for intel platforms. I've managed to
build the EFI Development Kit (EDK II) and the IASL compiler for
FreeBSD, which raises the possibility of integrating them either as
ports, or possibly into the base system.
Here is some background:
Right now, there is only on
bsd.org/cgi/query-pr.cgi?pr=76972
If you filed a PR, please submit a follow-up to both PRs so they
reference each other.
Thanks,
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To uns
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/08/12 13:35, Eric McCorkle wrote:
> Hello everyone,
>
> I'm going to be working on EFI boot support on the amd64/i386
> platforms as a GSoC project. The idea is to allow booting from
> EFI (as opposed to legacy BIOS) on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/17/12 10:36, John Baldwin wrote:
>> Do the kernel and modules actually do anything that depends on
>> being in a contiguous space in some way (ie some relocation
>> trick)? Because it seems like it shouldn't really matter
>> otherwise.
>
> The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/16/12 01:32, Andrey V. Elsukov wrote:
> As i see we already have sys/boot/efi/libefi/efipart.c that uses
> EFI BLOCK_IO_PROTOCOL to make "part" devsw. EFI BLOCK_IO_PROTOCOL
> provides access to each disk and partition. AFAIK it supports only
> G
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/15/12 11:44, John Baldwin wrote:
> The i386 kernel assumes it starts out with a flat 32-bit mode with
> the kernel loaded into a contiguous memory region at a fixed
> physical address. If we need a relocatable kernel (as Marcel
> hinted at I thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/10/12 07:45, Marcel Moolenaar wrote:
>
> On May 8, 2012, at 1:35 PM, Eric McCorkle wrote:
>
>> Here are some specific points to be decided:
>>
>> * An EFI boot service could potentially function similarly to
>
s on these matters.
- --
Eric McCorkle
Computer Science Ph.D Student
e...@shadowsun.net
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (FreeBSD)
iQIcBAEBAgAGBQJPqVlgAAoJENSCzbQ+koZ7CpYP/27NtM6Vz1069OLjV/+BRUt0
yxW4t8Tl5QXmMUroNAwhnABMKnFG7HAkYxa0twMLudalQVRxCPhyY3
on, containing a BSDlabel. Inside that, there is a swap
partition, and a single ZFS instance. When installing, you'll need to
use dd to install the first part of zfsboot to the bsdlabel, and the
remaining portion to the free space after the ZFS header (there's a
guide on how
On 04/03/12 13:22, Doug Ambrisko wrote:
> Eric McCorkle writes:
> | I'm assessing possible summer of code projects, and the EFI work caught
> | my attention. I've been running FreeBSD on a macbook for a little under
> | a year now, and booting on EFI is definitely an
it to a partition reserved for that purpose.
Anyway, if I'm going to propose this, I need to list possible mentors.
Skill-wise, I'm well equipped to take it on. I anticipate needing
someone who's a committer, preferably with good knowledge of the kernel
sources.
--
Eric
I'm assessing possible summer of code projects, and the EFI work caught
my attention. I've been running FreeBSD on a macbook for a little under
a year now, and booting on EFI is definitely an interest to me. Does
anyone know if this is still a viable project proposal? I certainly
have the skills
Here is some code which fails with malloc < 1 page
and sometimes succeeds with large mallocs (> 16 pages)
What's wrong?
#include
#include
#include
#include
#include
#include
#include
#include
#include
// Copyright: skeleton took from an older post on the freebsd list
#include
#include
> If your kernel module creates a device in /dev that implements the
> mmap method, then you don't need to worry about mucking around with
> vm_maps and objects and whatnot. Your mmap method just needs to be
> able to convert offsets into the device into physical memory
> addresses,
Yes I'm aware
> By using kernel_map instead of kmem_map, vm_map_lookup() now always
> return a vm_object. That's a big progress.
> As expected, when this object is kmem_object, the user mapping works
> fine (for smaller or larger mallocs.)
>
> Otherwise that object doesn't match kernel_object. It's an anonymous
for mapping into user map (using
vm_map_find()) doesn't directly fail,
it does provide a virtual address in the user map. However I read
zeros at that address, from within the user process.
Any help would be highly appreciated.
Thanks!
Eric
___
freebsd-hac
ing cost *for
each page*:
1/ a page fault
2/ a call to a pager function that will do the "on demand" mapping.
Thank you.
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
T
Given that NVidia is releasing the CUDA platform source on a limited
basis, is anyone actively working to port it to FreeBSD? The reason I
ask is that to get access to the source, you have to submit a request
explaining what you intend to use it for. It might be a good idea to
get ahold of the so
On Mar 6, 2011, at 6:09 AM, Vlad Galu wrote:
>
>
> On Sun, Mar 6, 2011 at 2:06 PM, Vlad Galu wrote:
>
>
> On Sun, Mar 6, 2011 at 6:53 AM, Eric Anderson wrote:
> On Mar 5, 2011, at 10:44 AM, Deomid Ryabkov wrote:
>
> > On 03/05/2011 04:02 AM, Eric Anderson w
EAD. Under 8.1
> MALLOC_OPTIONS=g will disable the thread-specific caching. See the
> malloc(3) man page for the definitive list of available options.
Thanks - I think I tried that at one point with no change, but I'll double
check just in case. Thanks for the hints!
Eric
_
On Mar 5, 2011, at 10:44 AM, Deomid Ryabkov wrote:
> On 03/05/2011 04:02 AM, Eric Anderson wrote:
>> Hi all,
>>
>> I have a moderately threaded userland program (all C) I am working on (using
>> pthreads, freebsd 8.1 64bit). It seems to leak memory (using standard
On Mar 5, 2011, at 6:23 AM, Eygene Ryabinkin wrote:
> Fri, Mar 04, 2011 at 10:02:45PM -0600, Eric Anderson wrote:
>> I have a moderately threaded userland program (all C) I am working
>> on (using pthreads, freebsd 8.1 64bit). It seems to leak memory
>> (using standard mall
rest don't seem
to matter - I can remove them and still see the leak).
Does anyone know of issues regarding malloc/free on multithreaded userland
apps?
Sorry, I can't post the code..
Thanks!
Eric
___
freebsd-hackers@freebsd.org mailing
nd
> "F2" (slice 2) is "FreeBSD-CURRENT"
GRUB might solve your needs.
sysutils/grub
--
Regards,
Eric
signature.asc
Description: OpenPGP digital signature
386
> >> setenv TARGET i386
> >> setenv TARGET_ARCH i386
> >>
> >> then 'make buildworld' in /usr/src
> >
> > Can you verify that 'make buildworld TARGET=i386' works? If so, can you
> > try just setting MAKEOBJDIRPREFIX via sete
On Tue, 2009-11-03 at 20:35 +0800, Eric wrote:
> On Tue, 2009-11-03 at 11:52 +0100, Nick Hibma wrote:
> > Anyone interested in Mesh networking might want to have a look at
> >
> > http://meshcom.com/en/products/meshdriver/
> >
> > We have started to use the
.: I am not affiliated to them other than that I am very impressed
> with the quality of the software.
Does it IEEE 802.20 compliant?
--
Best Regards,
Eric L. Chen
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailma
ed will be done.
danny
Peter Jeremy
We were hitting this quite a bit (also bce), and updated to a recent 7-
branch and it seems to be behaving better for now. Running 12 days so
far (which is better than what we had been seeing).
Eric
"Matthew Macy" <[EMAIL PROTECTED]> writes:
Hi Kip,
> Xen support will be MFC'd when it proves to be sufficiently stable for
> some uses. It probably won't make the freeze for 7.1. Xen 3.2 is the
> initial target.
Dom0/DomU or DomU only please ?
Regards
Éric Masson
--
tétu comme un mule :) E
"Kip Macy" <[EMAIL PROTECTED]> writes:
> DomU only to start off with. The currently planned progression is:
> stabilize in HEAD -> SMP -> x86_64 -> dom0
Great, Thanks a lot for your work :)
Éric Masson
--
Vous faites chier avec vos annonces à la con ! Ou sont les modérateurs
? Ca se dégr
t won't buy you much.
Snapshots also impede on your general file system performance. In
FreeBSD 7, you could use ZFS, which would give you the power and control
you need (plus FreeBSD 7 has many many performance improvements).
Eric
___
fr
ould have something for you to try tonight.
Also - can you tell me the exact 'mount' command you tried to do the
remount/update?
it's only in the diskless boot, where setting
boot-nfsroot-options = "nfsv3"
in /boot/loader.conf
e the exact 'mount' command you tried to do the
remount/update?
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
structure would not be prudent at this time, since almost all
servers are
57 * still Version 2 anyhow.)
58 */
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
0% sure what is happening, but it sounds like the file handle
for the mount point or maybe one of the directories is not getting reset
on remount.
When do you get the BADHANDLE error? Can you capture a
tshark/wireshark/tcpdump of the remount and error?
Eric
__
have ad0 and ad1, you're probably out of luck.
-
Eric F Crist
Secure Computing Networks
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Nov 16, 2007, at 12:47 PM, Julian Elischer wrote:
Alexander Leidinger wrote:
Although the moon is smaller than the earth, it is farther away.
George Bush?
I mow my lawn.
-
Eric F Crist
Secure Computing Networks
___
freebsd-hackers
will merge the changes (unless there are conflicts).
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kostik Belousov wrote:
On Wed, Oct 17, 2007 at 08:00:03PM +1000, Peter Jeremy wrote:
On 2007-Oct-16 06:54:11 -0500, Eric Anderson <[EMAIL PROTECTED]> wrote:
will give you a good understanding of what the issue is. Essentially, your
disk is hammered making copies of all the cylinder
scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
Anyone have any clue about what might be going on?
Can you also send the output of ps -auxl?
Also - do you notice this performance drop when running something like
one of the network performance
g else they wish.
I think, that in the end, for some of these aging issues to get
resolved, there needs to be another bounty put out on it. I think
rsync.net might even have one started for this issue already - you might
think about adding to the bounty, or officially offering hardware
thro
Sharad Chandra wrote:
On Friday 05 October 2007 5:25 pm, Eric Anderson wrote:
Sharad Chandra wrote:
> On Thursday 04 October 2007 6:51 pm, Eric Anderson wrote:
>> Sharad Chandra wrote:
>>> Hello,
>>>
>>> How to distinguish if /dev/da* devices are int
age attached to system, nothing else.
You must be blocking my mails.
camcontrol devlist -v
^^
It will tell you which controllers the devices are on. You can even
show devices on a particular controller, say, an isp device.
Eric
On Friday 05 October 2007 5:19 pm,
Sharad Chandra wrote:
> On Thursday 04 October 2007 6:51 pm, Eric Anderson wrote:
>> Sharad Chandra wrote:
>>> Hello,
>>>
>>> How to distinguish if /dev/da* devices are internal scsi drivers
or LUNs
>>> of external SAN?
>> camcontrol devlist
Sharad Chandra wrote:
Hello,
How to distinguish if /dev/da* devices are internal scsi drivers or LUNs of
external SAN?
camcontrol devlist -v
Might help you..
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman
m wrong, but I could have sworn I read something today
about linuxolator being 2.6.16 kernel with Fedora Core 6?
-
Eric F Crist
Secure Computing Networks
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
raudit /etc/auditpipe | grep --line-buffered -e "xxx"
If you just want to pipe to a file, use something like:
# praudit /etc/auditpipe | grep --line-buffered -e "$" >> file.log
HTH
-
Eric F Crist
Secure Computing Networks
On Aug 21, 2007, at 8:21 AMAug 21, 2007, sam wrote:
Eric Crist wrote:
On Aug 21, 2007, at 7:52 AMAug 21, 2007, sam wrote:
Robert Watson wrote:
On Mon, 20 Aug 2007, sam wrote:
I am installed AUDIT
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/
audit.html
# praudit /etc
of sounding rude, the 5.x series of FreeBSD is
deprecated. I'm running UnrealIRCd on a few different FreeBSD
systems, and I've never had any problems. Try running on 6.2-RELEASE
and I'm sure you won't have any problems.
of sounding rude, the 5.x series of FreeBSD is
deprecated. I'm running UnrealIRCd on a few different FreeBSD
systems, and I've never had any problems. Try running on 6.2-RELEASE
and I'm sure you won't have any problems.
of sounding rude, the 5.x series of FreeBSD is
deprecated. I'm running UnrealIRCd on a few different FreeBSD
systems, and I've never had any problems. Try running on 6.2-RELEASE
and I'm sure you won't have any problems.
-
Eric F Crist
Secure Computing Networks
__
e/modify the ethernet frames as they pass through?
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sven Hazejager wrote:
So, the question really is: how to send a IRP_MN_REMOVE_DEVICE
command?
`camcontrol da? stop` seemed to do the trick before (5.2.1-R, AFAIR),
but now I'm not sure (looks like it doesn't)
sorry, I meant to say that `camcontrol da? stop` does not power down
the device anym
ndering if it is a
FreeBSD oddity that I'm not understanding.
If FreeBSD is off the hook, then I'll go bug the Cacti crowd.
Are you using NFS at all? If so, check your locking.
Otherwise, some more debugging would help - can you become the cacti
user, and then access
slower because you then have to read a lot of small
files off of CD.
Or have I missed something?
Or, when the day comes that my tarfs implementation is in the tree and
root booting enabled, you boot the tar file as the root fs, and use that
same tar file to build the syst
Doug Barton <[EMAIL PROTECTED]> writes:
Hello,
> Not disputing your answer, but I'm curious. Why would it cause
> problems on some systems but not others? I haven't done anything with
> my cflags ...
Can't give any response, but I was hit by the bug Alex talks about
during upgrade. My box ran ou
s ran...
That's supposed to happen - look at the script.
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
your machine
runs with process accounting enabled, you will need to re-enable it
after the script terminates (the script will tell you how). I intend to
make the data you send me part of the process accounting regression testing.
Many thanks,
http://www.googlebit.com/freebsd/acct-data/
etfstype [fsize bsize bps/cpg]
a: 585018626 10485764.2BSD 2048 16384 28552
b: 10485760 swap
c: 5860672020unused0 0 # "raw" part,
don't edit
Could it be because your root partition is not at offset 0?
Eric
older hierarchies and
text files and write a libary in C that provides portupgrade
functionality. The code under src/usr.sbin/pkg_install/lib/ would be a
good base for this. Then you could use a frontend program that makes use
of this library. This frontend could be a CLI program or a GUI base
input: is this idea sane? Are there any utilities that actually
parse the type name?
The benefit of this conversion is that MIME types are easier on the eyes
and will help unfamiliar users understand what's going on.
How about adding a -m switch to sysctl that outputs the MIME com
ing like:
uint64_t l;
l = 1 << 40;
but instead did:
l = (1 << 30) * 1024;
which works fine.
This was on i386.
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nt me in the correct direction
to get this working?
See geom multipath (gmultipath) in -CURRENT. I think it's going to be
MFC'ed at some point..
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
you post a
meeting place/time (or a few) to one of the right lists, I'd like to
know about it..
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e them, or vmware needs to be
smarter and emulate that feature.
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
aware
but I'd still like to understand by I saw what I did i.e. ls
displayed the files yet running vim didnt.
I'm going to investigate this more in an effort to determine why I
got these results and report back. Thanks for everyone's feedback
so far most appreciated.
Ok, at this
On 03/02/07 09:37, Steven Hartland wrote:
Jeremy Chadwick wrote:
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and
On 03/02/07 08:44, Jeremy Chadwick wrote:
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
Mounting an NFS share on top of a skimmed down /usr is very common, and
very desirable. You may mount /usr from a small read-only partition
(vnode file, etc) and then mount a different
On 03/02/07 08:37, Steven Hartland wrote:
Eric Anderson wrote:
On 03/02/07 07:46, Steven Hartland wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and then mount a different
On 03/02/07 07:46, Steven Hartland wrote:
Eric Anderson wrote:
I don't know about the fs corruption, but the double mounts is
something you asked it to do (maybe unknowingly). When you added
that partition, one of the options is to mount it.
Clearly an easy work around in that case the
was so badly corrupted.
Steve
I don't know about the fs corruption, but the double mounts is something
you asked it to do (maybe unknowingly). When you added that partition,
one of the options is to mount it.
Eric
___
freebsd-hackers@freebs
Attached is the patch i use for 6.x kernel.
Can you both send me the dmesg of these machines?
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 02/20/07 11:44, Arone Silimantia wrote:
--- Eric Anderson <[EMAIL PROTECTED]> wrote:
after this attempt, swapinfo still shows zero swap
in use.
What does this mean ?
Is my system now in an unstable state ? Should I
reboot ?
Did you try reducing your maxdsiz to something a few
h
ducing your maxdsiz to something a few hundred mb's less?
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
, or possible kgdb
tricks to try.
Can you reproduce this easily? Can you explain how you get it to fail?
Eric
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
On 02/07/07 07:44, Kostik Belousov wrote:
On Wed, Feb 07, 2007 at 12:17:51PM +0300, Maxim Konovalov wrote:
On Tue, 6 Feb 2007, 22:56-0600, Eric Anderson wrote:
On one of my boxes where I have a decent amount of (less than 50)
users in a few groups, I finally hit the limit. Not 1024 bytes
PRERELEASE from about mid-September. I have also seen
some issues on amd64, which I went through some debugging with
Konstantin Belousov back in November (cc'ed).
Thanks!
Eric
--
----
Eric AndersonSr. System
ion of the null_fs code. Having named pipes work in null_fs
filesystems would be a very handy thing indeed.
I'd appreciate any insights into this.
Just wanted to say that it seems like this should work, and I'm not yet
certain why it doesn't. I've looked
On 01/20/07 12:37, LI Xin wrote:
Eric Anderson wrote:
On 01/20/07 02:48, Mike Silbersack wrote:
On Fri, 19 Jan 2007, Soeren Straarup wrote:
Hi
I'm looking for a project.
Something that would actually be used.
Preferely something with kernel and geom.
I have looked over the project
ormat. Just turning off softupdates and
adding the journal on another device should work.
Eric
--
----
Eric AndersonSr. Systems AdministratorCentaur Technology
An undefined problem has an infinite
ays people there with
ideas.
Eric
--
----
Eric AndersonSr. Systems AdministratorCentaur Technology
An undefined problem has an infinite number of
eas are OK..maybe something simple I overlooked.
I need to reserve another build server early this week, and go over my
options again on whats not been working, and get the list numbers as well.
Thanks in advance.
See Bruce Evans very recent work on this on freebsd-fs@ mailing l
ll bet it stands for something along
the lines of VNode Least Recently Used.
Yep, that's what it means.
vn* is commonly used in the kernel for vnodes, and an 'lru' is commonly
known for a 'least recently used' sort of list.
Eric
--
ave
that much RAM, but enough to store /usr/src, then using
a RAM disk for it is a win.
Reading /usr/src from a physical disk certainly requires
quite some I/O that takes more than zero time.
But, in order to populate the ram disk, you must r
On 09/18/06 10:02, Eric Anderson wrote:
Hi all,
On one of our NFS servers, we've seen repeated filesystem issues with
two of the filesystems (it has 4 exported via NFS). It usually
manifests itself by a hung 'df -lk' (wedged in 'ufs'), and mountd
becomes wedged also
mnt_cred = 0xc59f2080,
mnt_data = 0x0, mnt_time = 0, mnt_iosize_max = 131072, mnt_export =
0xc5d25c00, mnt_mntlabel = 0x0, mnt_fslabel = 0x0, mnt_nvnodelistsize = 1,
mnt_hashseed = 3369618744, mnt_markercnt = 0, mnt_holdcnt = 0,
mnt_holdcntwaiters = 0, mnt_secondary_writes = 0,
mnt_s
ke a look
at smartd.
Eric
--
----
Eric AndersonSr. Systems AdministratorCentaur Technology
Anything that works is better than a
On 08/27/06 00:53, Pawel Jakub Dawidek wrote:
On Sat, Aug 26, 2006 at 08:19:40PM -0500, Eric Anderson wrote:
On 08/26/06 07:44, Pawel Jakub Dawidek wrote:
On Sat, Aug 26, 2006 at 07:23:36AM -0500, Eric Anderson wrote:
Hmm - had another panic. Again, screen shots are here:
http
1 - 100 of 396 matches
Mail list logo
