from which version that
started).
Does anyone observe something similar?
This sounds like:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204426
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204764
This problem exists since 10.2.
10.1 is fine.
-Erik
as some sort of
"overflow buffer" from time to time.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
bsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LEAK
(Short version: That is expected behaviour from rpc.statd)
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
avisjail)
restart newamavisjail
I don't think I permanently lost disk space from the pool because of
this. I guess you have checked that there are no snapshots referring to
the huge files? (zfs list and zfs list -t snapshot)
--
Erik
___
freebsd-stable@
e ought to show up
as cd0 rather than acd0.
Anyway, I think burncd will only work with the old ata(4) driver. The
new ahci(4) and ada(4) drivers use the cam(4) system and looks pretty
much like SCSI drives to the rest of the system.
Try the sysutils/cdrecord port for burning. (Should work with all SCSI
a
that are not yet
> terminated. I would like to know in what way can I fix it using the system
> tools only (not ezjail, Qjail etc).
Increasing rcshutdown_timeout in /etc/rc.conf may help. The default
value is set to 30 seconds in /etc/defaults/rc.conf.
--
Erik
re following, then announce@ is
probably sufficient since all security advisories are sent there and
there are essentially no other changes made to a security branch.
If, on the other hand, they are interested in what will be included/not
included in future major releases, then current@ is
entually those old releases stop
receiving security fixes at which point it might become downright
dangerous to continue using the old release.
I think that is exactly the situation now which started this discussion
- the last release supporting ISDN was 6.4, which is to be EOL soon.
--
Erik
bout 37 seconds.
I suspect that other hardware watchdogs have similar limits, which
leads to the conclusion that one should not assume watchdog timeouts
longer than maybe 30 seconds to be supported.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebs
hat particular model
<http://www.wdc.com/wdproducts/library/SpecSheet/ENG/2879-701176.pdf>
the transfer rate is actually specified as 98MB/s. (Presumably along
the outer tracks of the disk -- on the inner tracks you probably can't
get more than around 50 MB/s)
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
No, it does not need to do that. It might be a good idea (but I am far
from convinced of it), but there most certainly is no *need* to move in
that direction.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http
S2882 system board). I am seeing kernel
panics very similar to those described in this thread on this
hardware. pciconf -lcv output below. If you'd like access to this
hardware I can arrange it; please contact me off list.
Erik
b...@pci0:2:9:0:class=0x02 card=0x164414e4 chip=0x164
On Wed, Jan 20, 2010 at 03:42:08PM -0800, Pyun YongHyeon wrote:
> On Wed, Jan 20, 2010 at 03:12:51PM -0800, Erik Klavon wrote:
> > On Thu, Jan 14, 2010 at 03:26:18PM -0800, Erik Klavon wrote:
> > > On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> > > &
On Thu, Jan 14, 2010 at 03:26:18PM -0800, Erik Klavon wrote:
> On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> > On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> > > One of my amd64 machines running 8.0p1 acting as a NAT system for many
> > &
")
c = 0
f = open(fname, "w")
while True:
if c == 100:
f.close()
f = open(fname, "w")
c = 0
c += 1
time.sleep(5)
f.write("a")
f.flush()
os.fsync(f.fileno())
--
On Wed, Jan 13, 2010 at 06:06:40PM -0800, Pyun YongHyeon wrote:
> On Wed, Jan 13, 2010 at 05:47:19PM -0800, Erik Klavon wrote:
> > One of my amd64 machines running 8.0p1 acting as a NAT system for many
> > network clients dropped into kdb today. tr indicates a problem in
> >
on in the above trace that this is the type of panic the
commit attempts to address? I don't have a core dump for this
panic. This machine has been unstable on 8, so I may be able to get a
core dump in the future. If there is other information you'd like me
to gather, please let me know.
y other SATA controllers which also do not
support AHCI.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ms but I
> can't find any evidence of that in SVN so I am not sure what I am
> thinking..
Look for amdtemp or k8temp (which it was named before K10/K11 support was
added.)
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd
_
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
--
Erik Trulsson
ertr1...@student.uu.se
___
will be for your setup and your
disk usage is something only you can answer.
My guess is that it will be quite noticable, but that is only a guess.
(Keep in mind that UFS+softupdates does quite a bit of write-caching on its
own, so just switching to ZFS is unlikely to improve write performan
Technologies Inc'
> device = 'VT6105M/LOM Rhine III PCI Fast Ethernet Controller'
> class = network
> subclass = ethernet
> cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0
That looks very much like a VIA chip which shou
dumped from brain, untested and may
be incomplete. It Worked For Me(tm) 3 months ago on 6.3. And your box
will probably get a new host key btw.
--
Erik
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
On Wed, Jun 03, 2009 at 09:13:21AM -0500, Brooks Davis wrote:
> On Tue, Jun 02, 2009 at 06:06:48PM -0500, Erik Osterholm wrote:
> > On Tue, Jun 02, 2009 at 12:20:34PM -0700, Doug Barton wrote:
> > > Up till Sunday in 8-current, and for a long time in general
> > > net
e the loading of the module
happens at a different time?
At best, users doing things the 'network_interfaces' way may be in for
a surprise when the update (remotely), and this may be worthy of a
note in UPDATING.
If this has changed in 7.2 or -current, then I apologize for the
noise!
at will you do if your RAID5
> > fails?
> >
> > Roland
> > --
> > R.F.Smith
> > http://www.xs4all.nl/~rsmith/<http://www.xs4all.nl/%7Ersmith/>
> > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
all
> # shutdown -r now
>
> Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to
> upgrade to FreeBSD 7.2-RC1, but will be prompted to rebuild all third-party
> applications (e.g., anything installed from the ports tree) after the second
> invocation
ging over firewire - see dcons(4), and over
old-fashioned serial ports. If you don't have either of those you are
probably out of luck as far as remote debugging is concerned.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org
On Thu, Mar 19, 2009 at 02:04:14AM -0500, Robert Noland wrote:
> On Thu, 2009-03-19 at 07:14 +0100, Erik Trulsson wrote:
> > On Wed, Mar 18, 2009 at 09:22:37PM -0500, Robert Noland wrote:
> > > On Wed, 2009-03-18 at 18:18 -0500, Greg Rivers wrote:
> >
> > [snip]
>
This path can be overridden by setting
the environment variable PCICONF_VENDOR_DATABASE.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
trol, but
> for sata disk.
>
The sysutils/ataidle port ought to do the trick.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send a
Were those later versions (maybe just version strings) included in
> 7.1-RELEASE by mistake? Were they tagged by mistake and this latest
> change is just fixing that error?
The tagging itself causes the version number of the file to be updated.
This makes the fi
here is almost
certainly room for improvement.
(The latest generation of harddisk, on the other hand, are fast enough that
a standard 32-bit/33MHz PCI-bus can actually be a bottle-neck.)
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.
docs contains the documentation.
implying that the "livefs" CD is not supposed to be bootable.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
Make backups of all data
2) Delete the old RAID array.
3) Create a new array from scratch
4) Restore data from backups)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD's support for it is horribly, horribly broken. You
> *will* lose your data. Read my Wiki entries in full.
>
> I'm only going to say this once more: please reconsider. You very
> likely are not going to be able to recover that failed array. The last
> p
blem. If you look closer at his dmesg you will see that
it detects both the PATA-controller part of ICH7 (as atapci0) and the
SATA-controller part (as atapci1.) The detected disk is attached to atapci0
(as ata0-master.) Besides the reported disk model (WD800BB) is a
PATA-model. (http://www.wd
ot a problem (not any
more than any other file system anyway.)
Using background fsck together with the above setup is not recommended
however. Background fsck will only handle a subset of the errors that a
standard foreground fsck can handle. In particular i
ll builds other than 'buildkernel', CTF generation is turned off. You
> don't
> need or want it yet.
>
> --
> John Birrell
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ial adapters
> nodevice uvisor # Visor and Palm devices
> nodevice uvscom # USB serial support for DDI pocket's PHS
> # USB Ethernet, requires mii
> nodevice aue # ADMtek USB ethernet
> nodevice axe # ASIX Electronics USB Ethernet
> nodevice cdce# Generic USB over Ethernet
> nodevice cue # CATC USB ethernet
> nodevice kue # Kawasaki LSI USB ethernet
> nodevice rue # RealTek RTL8150 USB Ethernet
>
> # Sound support (Requires System Management Bus for ICH)
> devicesmbus
> deviceiicbus
> deviceiicbb
> deviceintpm
> deviceichsmb
> devicesmb
> #device sound
> #device snd_ich
>
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
arl Denninger
> > [EMAIL PROTECTED]
>
> Ok, another followup!
>
> Is there a mangement interface program for the "mfi" driver somewhere? I
> rooted around in "ports" but didn't find one, nor on the base system.
>
re, so the make system chooses
-march=athlon-mp since that is the closest architecture that can be
specified. (Look in /usr/share/mk/bsd.cpu.mk too see how it chooses -march
flags based on your setting of CPUTYPE.)
I am fairly certain however that gcc 4.x does know about the K8 CPUs these
days,
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
>
> real 8m58.524s
> user 7m18.995s
> sys 1m22.150s
>
> Solaris Nevada
To maximise the available bandwidth one would want to spread out the chips
over these links, which this motherboard does fairly well, using three
of the four available links.
(And hanging the most important things from CPU0, so you can actually use
the board even if you have only one CPU installed
here 6.2 does not. Is there a way to
disable that feature using sysctl to see if thats the issue?
sysctl net.inet.tcp.rfc1323=0
This may disable more than you want, but maybe it's worth a try.
http://www.ietf.org/rfc/rfc1323.txt
--
Erik
___
fr
c0: failed to probe at irq 7 on isa0
>
> Any suggestions would be appreciated.
>
Take a look in /boot/device.hints
Do you have any lines in there referring to ppc0 ?
If so try commenting them out.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Wed, Mar 12, 2008 at 06:29:46PM +0700, Eugene Grosbein wrote:
> On Wed, Mar 12, 2008 at 12:06:48PM +0100, Erik Trulsson wrote:
>
> > I have had good experiences with the Promise Ultra100 TX2.
> > The Promise Ultra133 TX2 should be even better, but I have no personal
>
mise Ultra133 TX2 should be even better, but I have no personal
experience with it. (Apart from the slightly higher speed, the Ultra133
should be able to handle large disks out of the box, while the Ultra100
needed a firmware update to handle disks larger than 128GiB.)
--
> It looks to me like gcc is trying to allocate a single 130MiB object, but
> you don't say anything about how much memory is already in use. It may
> well be that there are no remaining places in the memory map to place such
> a large object.
Ivan Voras wrote:
Erik Stian Tefre wrote:
Results from bonnie++ with default settings on my box (7.0-RELEASE,
amd64, 480 MB system memory, BBU, write cache enabled, 7 drive raid-5,
storsave = balance, NCQ on):
Version 1.93d --Sequential Output-- --Sequential Input-
--Random
+ +++ 27581 45 8454 20 + +++
+ +++
Latency 1147ms 371us3529us 197ms 15397us
703us
--
Erik
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
en using cvsup, and did
not check out RELENG_7, but instead got a copy of the whole
CVS repository - which cannot be compiled from directly.
Remove all the contents of your current /usr/src/, fix your supfile,
and try again.
--
Erik Trulsson
[EMAIL PROTECTED]
the options for a given port, and when in
> doubt; /what/ the particular option provides -
> eg; WITH_, or WITHOUT_.
No such method exists. Many of the options available in ports are
not documented at all. Those that are documented often have only
a brief one-line description.
--
Stepping = 4
>
>
> Features=0xbfebfbff ,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>
> Features2=0xe4bd,>
>
> AMD Features=0x2010
>
> AMD Features2=0x1
>
> Cores per package: 2
>
> Logical CPUs per core: 2
>
&g
rts.
The 'options' line in the output is those that are enabled while the
'capabilities' line are those which are supported.
Checksum offloading is indicated by RXCSUM and TXCSUM (for receive and
transmit respectively.)
--
Erik Trulsson
[EMAIL PROTECTED]
__
nnect the device as a usb keyboard.
--
Erik
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ildworld as well.)
Beware that there are a few, fairly rare, situations where it is actually
needed to clean the tree first before building. If you run into problems
it is a good idea to skip the '-DNO_CLEAN' flag.
--
Erik Trulsson
[EMAIL PROTECTED]
___
ct, and that
> users can't have any specific expectations - this is not a threat, as I
> like FreeBSD and want to remain in the community, but I would need a new
> server to work properly!
>
>
> Looking at CVSweb, it seems that ambrisko@ and scottl@ are the two people
just two separate lines getting mixed together.
One of them is "SMP: AP CPU #1 Launched!", i.e.
the second CPU/core was just started and it wrote a message
to the console announcing that at the same time as the first
CPU wrote "da1: Fixed Direct A
ly other option for us is to abandon FreeBSD and go with
Linux on the server, and we have already replaced too many FreeBSD boxes
with Linux for my liking, I don't want to see yet another one go...
Regards,
Lars Erik Gullerud
___
freebsd-stable@fre
keeping
8
e. Granularity's of the port management system
5
12. Please rate your personal technical skill level?
Medium.
Erik
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubs
lothos# zpool status tank
pool: tank
state: ONLINE
scrub: scrub in progress, 3.97% done, 0h40m to go
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz1ONLINE 0 0
are probably better off putting the files on a webpage somewhere
and just telling us the URL.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
> But ot must be:
> { ATA_VIA8237A, 0x00, 7, 0x00,ATA_SA150, "8237A" },
>
> after this improvement and recompilation the kernel anything work fine!
> Misha.
Yes. This bug was fixed several months ago in both -CURRENT and 6-STABLE.
--
Erik Trulsson
[EMAIL PROT
e schg flag on /lib/libc.so.6
- use /rescue/cp to copy libc.so.6 from /usr/obj to /lib/libc.so.6
- continue installworld, you should be fine now
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lis
I have tried parsing the following. Is there a cleaner way
> to do this?
>
> sysctl -A | grep phy | grep desc
'ifconfig -m' might be what you are looking for.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailin
ints?
It looks like different timecounters are used depending on your kernel
options. In the first case you probably used TSC or i8254 as timecounter
while in the second (where you get timer interrupts on cpu0 instead of on
irq0) you use ACPI as timecounter.
The output of 'sysctl kern.timeco
complain if anything breaks though - you are only supposed to
touch those flags if you know what you are doing.
Don't expect any major (or even noticable) improvements from these settings
though.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-s
7;
> >
> > Eugene Grosbein
>
> I don't think it was in HEAD to be MFCed?
Correct. That code has not yet been added to -CURRENT, so technically it
was not an MFC (Merge From -Current), but rather an MFV (Merge From Vendor).
--
Erik Trulsson
[EMAIL PROTECTED]
___
anyone actually using PAE with FreeBSD 6.2? I have found practically
> > no information using
> > google.
>
> But why use i386 with so much ram? Wouldn't it make more sense running
> amd64 instead?
The CPUs in his machine do not support amd64, so he is stuck with i386.
.enable to 1, and find and fix the
> hang-on-close bug in the pts code (if it hasn't been fixed already)
This last option is only available if you are running 7-CURRENT though.
The pts code is not in 6-STABLE (or older.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
x-stable" under "COMMON ITEMS".)
It is documented quite clearly there how you are supposed to do it.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lso think that it would be a bad idea to create *any* new release until
after the X.org upgrade has settled down - it has not done that quite yet
as far as I can tell.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
ht
ctual paths from the build
machine (/usr2/obj/... in your case) and needs to have those at the right
places.
This is not a new behaviour for 6.2. It has been this way for many years.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd
access memory below the 4GB boundary that is shadowed
by various I/O-devices, the RAM will have to be remapped to somewehere else.
So if you could remap the memory then PAE or 64-bit mode would give you the
ability to access it. If you can't remap it you can't get hold of it.
If that does not work (and I don't think
it will) you probably need snd_hda(4).
Unfortunately snd_hda is only available in -CURRENT at the moment and
not in -STABLE.
--
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://l
t is not really new but probably exciting.
> Aren't there any hw devs reading and motivated?
>
> Imagine a graphics chip with a BSD style license... ;)
>
> Just dreaming?
You are not the first to have this idea.
See http://en.wikipedia.org/wiki/Open_Graphics_Project fo
rdised on them.
The 9550SX should be a bit faster than the 9500S and the 9650SE faster
still, but that is for other reasons. (Faster processor for handling the
parity calculations for RAID-5, faster memory on the card, being able to do
more operations in parallell, etc.)
--
Erik Trulsson
[EMAIL
een known to have problems with PAE.
PAE mode is an ugly hack which is best avoided unless you really have to go
beyond the 4 GB limit on older x86 CPU's.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
f 6.2-RELEASE I will also welcome positive answeres about this.
>
> -
> Intel PRO/1000 PT Desktop Adapter, 1x 1000Base-T, PCIe x1, low profile
> (EXPI9300PTL)
--
Erik Trulsson
[EMAIL PROTECTED]
__
On Thu, Nov 30, 2006 at 01:42:35PM +0100, Oliver Fromme wrote:
> Erik Trulsson wrote:
> > Oliver Fromme wrote:
> > > Christopher Sean Hilton wrote:
> > > > Please understand that this is an honest question but isn't that true
> > > > only of
t were broken in this regard.)
>
> Best regards
>Oliver
>
> PS: Quantum is today owned by maxtor, isn't it? I've lost
> track of HD manufacturers when Seagate bought Conner ...
Quantum and Maxtor merged and became Maxtor. Maxtor was recently
bought by Sea
>
> - while (nmount(iov, iovlen, fsb->f_flags) < 0) {
> + while (nmount(iov, iovlen, fsb->f_flags | MNT_UPDATE) < 0) {
> if (cp)
> *cp-- = savedc;
> else
--
Erik Trul
t;
> > That pci-id is used by several different VIA chips for the PATA
> > controller.
> > The FreeBSD ata(4) driver searches among the other PCI-ids in the box to
> > find out which chips it actually is.
> >
> > It may be that the first one is some recent chip that
nt to 'nodevice' for options ?
Yes, there is such a thing. It is (not too surprisingly) spelled 'nooption'
and is actually documented in the config(5) manpage.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ntium 4 processors do support EM64T which is Intel's
name for the AMD64 architecture. Older Pentium 4 processors do not have
this support.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/m
ou can just add -DNO_CLEAN to the arguments to make to.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
-4 device
da2: 200.000MB/s transfers, Tagged Queueing Enabled
da2: 1907504MB (3906568192 512 byte sectors: 255H 63S/T 46564C)
Best regards,
Erik Østlyngen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unt
the card.
A copy of the kernel log:
http://spider.netlife.no/~erik2/kernellog.txt
--
Erik Stian Tefre
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ow,
but that is only my personal guess and I do not have any special inside
information on this matter.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, s
y who is looking
for a project to do. If the problem cannot be solved at all, it
will be closed, rather than suspended."
Of course, you can always take a look at an open PR.
http://www.freebsd.org/support/bugreports.html
Cheers, Erik
dont have the time to mess with bug tracking
> and what not, but i need a working OS, not a bata !
>
> Thank you everyone for your help !
5.5-PRERELEASE and 5.4-STABLE are the same thing.
Only the name is different.
--
Erik Trulsson
[EMAIL PROTECTED]
___
whart directories etc... do i have to transfer.
see the handbook, this section seems for you:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html
Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/20040
o RELENG_6 (cvsuped today)
seems to make no difference. Compiling the kernel with or without SMP
also makes no difference.
Anyone have any ideas or workarounds other than limiting the memory to
2GB?
--
Erik Stian Tefre
___
freebsd-stable@freebsd.org mailing
omer to BSD, but
> I would really like someone to tell me where to find it so that I can
> stop having to use this bloody Windows laptop to post here ;-)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
lorax1 as its working
> directory.
umount -f will probably work.
>From the umount manual:
-f The filesystem is forcibly unmounted. Active special devices
continue to work, but all other files return errors if further
accesses are attempted.
OS)?
> FAQ/doc/RTFM pointers are welcome. :)
Run dumpfs(8) on the filesystem and look at the first line of the output.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stab
CVSup targets should be used to pull down the source
> that would be compiled, etc
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
his is the Right Way to do
it". So...what's the proper way to make a large file system?
You can avoid the problem by splitting the array up in partitions smaller than
2TB each. (I know this does not answer your question, but it simplifies
things,
On Sat, Jul 23, 2005 at 11:00:55PM -0500, Karl Denninger wrote:
> On Sun, Jul 24, 2005 at 05:43:34AM +0200, Erik Trulsson wrote:
> > On Sat, Jul 23, 2005 at 09:01:36PM -0500, Karl Denninger wrote:
> > > Done.
> > >
> > > Note that the Bustek and Adaptec
1 - 100 of 176 matches
Mail list logo
