>> 8.2 amd64
>> ad8 is a 3TB Seagate on nforce4-ultra controller
>>
>> At boot:
>> ad8: 2861588MB > at ata4-master UDMA100 SATA 3Gb/s
>> DEBUG g_part_gpt.c gpt_read_hdr() ad8 succeeded with pp->>sectorsize=512
>>
>> An hour later:
>> # dd if=/dev/ad8 bs=4k count=1 of=/dev/null
>> dd: /dev/ad8: No s
8.2 amd64
ad8 is a 3TB Seagate on nforce4-ultra controller
At boot:
ad8: 2861588MB at ata4-master UDMA100 SATA 3Gb/s
DEBUG g_part_gpt.c gpt_read_hdr() ad8 succeeded with pp->sectorsize=512
An hour later:
# dd if=/dev/ad8 bs=4k count=1 of=/dev/null
dd: /dev/ad8: No such file or directory
BUT: th
>> I have a problem with various parts of web pages stopping
>> before getting completely downloaded. Links has a useful retries
>> setting (setup->network options->retries) which seems to fix
>> this. I need a similar fix for firefox 3.6.2
> Firefox 15
> URL: about:config
> search: retry
> networ
[ no response on mozilla@ list, trying questions@ ]
I have a problem with various parts of web pages stopping
before getting completely downloaded. Links has a useful retries
setting (setup->network options->retries) which seems to fix
this. I need a similar fix for firefox 3.6.2
_
grarpamp writes:
> Plenty of millionaires
> out there now who are in tune with opensource who could startup,
> buy the same ARM/ATOM/etc chips, the same support chips, load
> Android and sell it to the masses.
Would you please post a list of these millionaire FLOSS entrepreneurs?
Thank you.
__
> Have you tried:
> $ xset +dpms
> to use standby etc.?
xset: unknown option +dpms
I assume it needs more than the 5 coaxes to do dpms.
(It did appear to be working with the short cable that came
with the monitor.)
> Font for xterm: x11-fonts/inconsolata-ttf
I installed package inconsolata-ttf
Reducing the color depth to 16 allows the wimpy Rage XL (8 MiB) to do 1920x1080.
So then I moved the old slow X terminal out of the way and moved the shiny new
Dell ST2220T LCD into the prime spot in front of the keyboard drawer...
...and the cable doesn't reach. Two HD-15 to BNC cables back-to-ba
>>> Now to see if I can get this wimpy rage xl to do 1920x1080.
>>
>> Please don't mess with modelines, it should not be needed any more.
>> Just set the resolutions desired in the Screen/Display section. If
>> modelines are really required, get them out of /var/log/Xorg.0.log.
>> But they almost
> That is incorrect. Don't set AllowEmptyInput, just turn off AutoAddDevices.
> http://www.wonkity.com/~wblock/docs/html/aei.html
I reduced the config file to:
Section "ServerLayout"
Identifier "X.org Configured"
# Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "C
> Q1: how do you start X?
"Xorg"
(no config file)
result: display works (1400x1050), but no keyboard or mouse
"Xorg -configure"
(creates /root/xorg.conf.new)
"Xorg -config /root/xorg.conf.new"
result: 1280x1024 which monitor doesn't like
I also tried "Xorg -keyboard Keyboard0 -pointer Mouse0"
FreeBSD 8.2
packages: packages-8.2-release
amd64
ATI Rage XL
Dell ST2220T (1920x1080)
"Xorg -configure" generates an xorg.conf file that somehow
puts it into 1280x1024 mode and the monitor refuses to use it.
I haven't found a way to get the full modeline info for whatever
it is actually putting ou
perryh> running 8.1-RELEASE (and not 8-STABLE)
[ ... ]
perryh> /packages-8.1-release/
AH HA
The .message file contains the solution (I hope):
"packages-*-release directories are built from the ports collection
shipped with the release, and are not updated thereafter.
packages-*-stable and
RW> The problem as I see it is that he is installing packages that
RW> aren't built from the same tree. One of the dependencies of
RW> xf86-video-fbdev-0.4.2 was built when perl 5.10 was the default
RW> and one after the default switched to perl 5.12.
RW> If building isn't an option then it's bet
Dieter> Attempt to install package xf86-video-fbdev-0.4.2.tbz
Dieter> gives conflict between perl-5.10.1_3 and perl-5.12.3
Dieter> even when installing into clean directory tree.
Randal> Packages seem like a great idea when you get started,
Randal> but they're all built with
FreeBSD 8.2
amd64
Attempting to install X11 server.
Attempt to install package xf86-video-fbdev-0.4.2.tbz
gives conflict between perl-5.10.1_3 and perl-5.12.3
even when installing into clean directory tree.
# mkdir /tmp/test_pkg_install
# export PKG_DBDIR=/tmp/test_pkg_install/var/db/pkg
# pkg_
# dmidecode 2.11
SMBIOS 2.2 present.
Handle 0x0005, DMI type 5, 24 bytes
Memory Controller Information
Error Detecting Method: 64-bit ECC
Error Correcting Capabilities:
None
Supported Interleave: One-way Interleave
Current Interleave: One-way Interle
Machine has been running FreeBSD/amd64 with 2 GiB of memory.
I just installed a 2nd 2 GiB of memory for 4 GiB total.
FreeBSD thinks it now has 32 GiB ???
FreeBSD 8.2-RELEASE #22: Tue Jun 7 12:37:21 PDT 2011
CPU: AMD Athlon(tm) 64 Processor 3000+ (1808.34-MHz K8-class CPU)
real memory = 343597383
FreeBSD 8.2 amd64
xpdf version 3.02
whines:
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':osfActivate:
ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation tabl
FreeBSD 8.2 amd64
xpdf version 3.02
whines:
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':osfActivate:
ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation tabl
Can you use windows programs in freebsd?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Where is the documentation for /boot/pmbr and /boot/gptboot ?
Where is the documentation on setting up multibooting with
GPT partitioned disks?
Poked around in the FAQ, handbook and google, but no joy.
All I have found is gpt(8) and gpart(8).
MBR partitioning isn't entirely working with 2TB driv
Updating an amd64 box from 7.1 to 8.0.
Console is RS-232.
Check to see if any disk names have changed:
dmesg | grep ^ad
looks reasonable.
added
siis_load="YES"
to loader.conf and rebooted
dmesg | grep siis
gives output that doesn't look right at all:
siis0: port 0x7c00-
Shaun writes:
> Have you tried ^X or ^Z? Often when my cable modem has lost its link and
> I reboot, FreeBSD will hang waiting to start sendmail because it can't
> determine the local IP. Sometimes it will hang while processing my ipfw
> scripts due to DNS failures.
>
> I usually try ^C, ^X, and
Working on updating a amd64 box from 7.0 to 7.1.
A shell script called from rc.local hung.
(Still don't know why, works fine in 7.0, works
fine in 7.1 executed manually once system is up.)
Tried ^C, ^\, ^P and nearly every other key on the
keyboard. They echo, but nothing will interrupt
the hung p
Western Digital SATA disk in "power-up in standby" mode.
disk is connected to nforce4-ultra
FreeBSD 7.0 amd64
Google found that MirBSD's atactl man page has:
puisspinup Explicitly spins up the device if power-up in standby (puis)
mode is enabled.
I can't find anything like
I'm attempting to dig my way out of the Seagate 7200.11 firmware disaster.
Need a non-7200.11 place to store my data before messing with the drives.
Trying a Samsung.
disk: Samsung HD103UJ 1TB SATA
controller: nforce4-ultra
FreeBSD 7.0 amd64
Brand new disk. Running a few tests before entrusting
Does anyone know of a Unix utility that can do
"a scan of connected devices regardless of BIOS status"
similar to Victoria ? The "BUSY" state is of particular
interest. GUI not required. I tried google, no joy.
http://www.msfn.org/board/index.php?showtopic=129263
___
In message <200901252247.29775.fbsd.questi...@rachie.is-a-geek.net>, Mel writes:
> On Sunday 25 January 2009 04:28:47 Dieter wrote:
> > >>>> AMD64 FreeBSD 7.0 2 GiB main memory
> > >>>>
>
> > So the machine doesn't normally use swap
AMD64 FreeBSD 7.0 2 GiB main memory
My console says:
login: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size:
iming out while doing
> > so.
> isn't swapspace supposed to be on a 'b' partition? Are you using swap
> on a slice 10? how is that possible when the i386/amd64 BIOS can't see
> more than 4 primary partitions?
>
> Kris, would you mind giving input to th
> > AMD64 FreeBSD 7.0 2 GiB main memory
> >
> > My console says:
> >
> > login: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
> > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
> > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
AMD64 FreeBSD 7.0 2 GiB main memory
My console says:
login: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 22, size: 4096
swap_pager: indefinite wait
[ This discussion is probably better suited for -multimedia@
than -questions@ ]
> I can pick up really high quality, large, old-style video monitors
> from a computer surplus place near here for next to nothing.
If these were for workstations rather than pee-cees, they might be
composite sync or
> > > I like Intel as much as I like AMD
> >
> > That is your right. Inthell has a long history of buggy products,
> > attempting to hide/ignore bugs, poor customer support, outright
> > theft, etc. AMD isn't perfect, but the list of bad things is far
> > far shorter. And there are other compan
> > My personal approach to avoiding data loss is (a) avoid buggy things like
> > inthell and linux.
>
> Interesting, being as we have another thread going as of late that seems
> to link transparent data loss with AMD AM2-based systems with certain
> models of Adaptec and possibly LSI Logic contr
> FreeBSD 7.0-Release
> Intel D975XBX2 motherboard (Intel Matrix Storage Technology)
> 3 WD Raptor 74 GB in a RAID 5 array
> 1 WD Raptor 150 GB as a standalone disk
> / and /var mounted on the standalone,, /usr on the RAID 5
> I believe what happened was that one of the disks didn't respond for suc
> # mount -t ext2fs /dev/ad0s8 /mnt/
> # ls /mnt
> ls: /mnt: Bad file descriptor
Weird.
I can mount ext2fs on 7.0 (and previously on 6.0 and 6.2) and
things mostly work. In the past I had ext2fs on both primary
and extended slices (or whatever the preferred terminology is).
This is on AMD64 with
> It is. The pageout daemon initializes max_wired with:
>
> /* XXX does not really belong here */
> if (vm_page_max_wired == 0)
> vm_page_max_wired = cnt.v_free_count / 3;
>
I installed the following:
diff -r1.1 vm_pageout.c
1421c1421,1425
< vm_pag
> SU requires that data it once sends to the drive gets written
> immediately, not cached by the drive. Modern desktop drives
> don't do that
They do if you set them to write-through cache instead of
write-back cache.
Modern SATA drives also provide NCQ. When is FreeBSD going
to support NCQ?
___
> > vm.max_wired looks like a sysctl, but sysctl doesn't know about it.
> > sysctl: unknown oid 'vm.max_wired'
>
> Yes, indeed. I posted before looking at the diffs between RELENG_7 and
> CURRENT. The sysctl is only present in 8.0-CURRENT:
This is 7.0-RELEASE amd64 with 2 GiB of memory.
> Can
> > I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
> > get mlock(2) failed: Resource temporarily unavailable.
>
> That's error EAGAIN:
>
> [EAGAIN] Locking the indicated range would exceed
> either the system or per-process limit
>
I never saw mlock(2) fail in 6.2 but with 7.0 I sometimes
get mlock(2) failed: Resource temporarily unavailable.
I commented out a ton of drivers in the kernel config file,
which I didn't do in 6.2, so the 7.0 kernel should be using less
memory, unless something still in there gained a lot of bloa
[ no replies from -drivers, so added -questions ]
> FreeBSD 7.0 amd64
>
> Deleted device umass and added atausb instead.
>
> The bridge shows up, but the disk does not. (sata hard drive,
> not a CD/DVD drive)
> atausb0:
> on uhub1
>
> The kernel moved the chipset-connected SATA drives from ad
> But this doesn't start Emacs in `no colors should be used at all' mode.
> If you want to do that, you can fire up Emacs with:
>
> emacs --color=no
That got rid of the black-on-black invisible ink, thanks.
___
freebsd-questions@freebsd.org mail
FreeBSD 7.0 with package emacs-22.1_2
Attempt to edit a C file and emacs goes into some colorized mode.
Of course it chooses colors that are unreadable.
How do I turn OFF the colors and get simple black and white?
(ASCII mode, not X11)
The man page mentions command line options for foreground and
> I'm looking into the syslogd capabilities at the moment, it might be
> enough.
> I've tried following the serial console setup you've pointed, but when I
> added the 'console=3D"comconsole"' to loader.conf the OS hanged during
> boot time, had to re-install the system.
I assume the info you need
FreeBSD 6.2 running on AMD64
ad6 is sata disk connected to nforce4-ultra
Moving a filesystem via dump|restore pipeline,
source is ad6 (mounted read-only), dest is a sata-via-usb disk.
ad6 also has root and var, so there could have been other
disk activity, but dump would have been the lion's share
>> I got 2 new 160GB drives last month, and my system has been
>> unstable ever since. I have swapped cables, purchased a
>> brand-new sata150 controller (as opposed to the year old
>> sataII), and the results are always the same.
>
> What make & model controllers? What make & model drives?
> Som
> I got 2 new 160GB drives last month, and my system has been
> unstable ever since. I have swapped cables, purchased a
> brand-new sata150 controller (as opposed to the year old
> sataII), and the results are always the same.
What make & model controllers? What make & model drives?
Some combina
> Hi, I'm thinking of getting a couple USB drives to use in
> backing up my 6.2-RELEASE-p4 system. Any suggestions or
> warnings on brands of USB hard drives?
If you go the external box route, be sure to get one with
reasonable cooling.
I have a JM20337 which works fine with FreeBSD 6.2,
except
How do you set a USB disk's write cache to write-through mode?
As far as I can tell, putting "hw.ata.wc=0" in loader.conf
only affects directly connected PATA/SATA disks, not disks
connected via a USB-to-*ATA bridge.
Perhaps via camcontrol? But "camcontrol modepage da0 -l -v"
returns nothing.
__
> >> > but when I try to mount the cd later, I'm unable to do it and the
> >> > Input/Output error is thrown. Is there anything I'm missing? Is there
> >> > any other way to burn the cd other than using cdrecord.
There is something strange going on with burncd/cdrecord and mount.
http://lists.fre
> FreeBSD 6.2
> AMD64 (single CPU)
> /var is FFS with soft-updates, on SATA.
>
> /var/cron/tabs/root contains:
>
> * * * * * /usr/libexec/atrun
>
> I had three at jobs queued. They all call the same shell
> script with different arguments. First one runs
FreeBSD 6.2
AMD64 (single CPU)
/var is FFS with soft-updates, on SATA.
/var/cron/tabs/root contains:
* * * * * /usr/libexec/atrun
I had three at jobs queued. They all call the same shell
script with different arguments. First one runs fine.
Second one g
> > If I use up a slot, I'd like at least 4 ports and NCQ.
> > If FreeBSD doesn't have NCQ support yet I might just get a
> > USB or FW to SATA adapter or two and wait for NCQ.
>
> NCQ is nice but I don't *really* care. I just want something that works
> at all :) Of course I would want NCQ if it
> after spending time and money on several Promise and Sillicon Image
> based cards that don't work properly,
> WARNING - WRITE_DMA48 UDMA ICRC error (retrying request) LBA=
...
> I have tried several different SATA cables (since in other contexts
> with other controllers these messages were suppo
> > > > > > AMD64 running 6.0
> > > > > > Drive is:
> > > > > > acd0: DVDR at ata0-master UDMA66
> > > > > > Media is CD-RW
> > > > > >
> > > > > > Burned a 6.2 disk using:
> > > > > > burncd data 6.2-RELEASE-amd64-disc1.iso fixate
> > > > > > as suggested in
> > > > > >
> > > > > > http:/
An alternative to undocumented graphics/video cards is in the works.
The Open Graphics Project has a prototype working. If you can
assist the project (engineering talent, financial, etc.) the
production boards will be available sooner.
___
freebsd-questi
> > > > AMD64 running 6.0
> > > > Drive is:
> > > > acd0: DVDR at ata0-master UDMA66
> > > > Media is CD-RW
> > > >
> > > > Burned a 6.2 disk using:
> > > > burncd data 6.2-RELEASE-amd64-disc1.iso fixate
> > > > as suggested in
> > > >
> > > > http://www.freebsd.org/doc/en_US.ISO8859-1/boo
> > AMD64 running 6.0
> > Drive is:
> > acd0: DVDR at ata0-master UDMA66
> > Media is CD-RW
> >
> > Burned a 6.2 disk using:
> > burncd data 6.2-RELEASE-amd64-disc1.iso fixate
> > as suggested in
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
>
> I don
AMD64 running 6.0
Drive is:
acd0: DVDR at ata0-master UDMA66
Media is CD-RW
Burned a 6.2 disk using:
burncd data 6.2-RELEASE-amd64-disc1.iso fixate
as suggested in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html
Seemed to go okay. Disk boots, but I cannot mount
I don't see the Sil 3124 SATA controller listed in the
6.2 ata(4) man page. Are there any plans to support it?
I'm told that it is a significant improvement over previous
Sil chips. It even has documentation!
Overview:
http://www.siliconimage.com/products/product.aspx?id=27
Datasheet:
I've always thought that writing to a file descriptor with O_NONBLOCK
set was supposed to return quickly. Isn't that the whole point of
O_NONBLOCK ?
I have a C program writing to stdout, which is set to O_NONBLOCK,
and the shell redirects stdout to a regular disk file. Dispite
O_NONBLOCK, my pro
> > FreeBSD 6.0
>
> Erk. How about retrying with something modern ;-) We do fix lots of
> bugs over time you know!
In my defense, 6.0 is only one revision down. (until 6.2 comes out real soon
now)
>> 32.3%Sys 31.5%Intr 0.0%User 0.0%Nice 36.2%Idl 710892 inact32 3: sio1
>> 74.8%Sys
> Sorry, yes. Nothing else contended for it though, so it doesn't
> appear to be a source of performance problems - it is probably a
> secondary effect from something else. I guess you're running some old
> version of FreeBSD since those line numbers don't correspond to
> anything reasonable in t
> > > Mutex profiling would show if there is a mutex somehow getting in the
> > > way of your I/O (e.g. if Giant is somehow being forced). I dont think
> > > it would show anything though. You can try to study interrupt issues
> > > (e.g. look for an interrupt storm during I/O) with vmstat -i. O
> Mutex profiling would show if there is a mutex somehow getting in the
> way of your I/O (e.g. if Giant is somehow being forced). I dont think
> it would show anything though. You can try to study interrupt issues
> (e.g. look for an interrupt storm during I/O) with vmstat -i. Other
> than that
> > Is Giant the only mutex/lock that could be a bottleneck across disks?
>
> The only one I can think of that is generic. One would have to do
> more extensive profiling and diagnosis to try and figure out what is
> wrong with your system.
Suggestions of what to look at would be welcome.
> The
I've been experimenting with vfs.hirunningspace
and it has some interesting effects.
Is there a different, more detailed, description of
its effects (and/or similar tuning parameters) than found in
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-disk.html
Is there a way to
> Did this problem start before you made port2file run with rtprio?
Yes. I only added rtprio because it wasn't working.
> Can you please include a copy of your kernel configuration file and dmesg?
I think you asked that before: :-)
> > OK, that's correct. Can you also provide details of
> > > > > > > > hw.ata.wc=3D3D3D3D0
> > > > > > > ^^^
> > > > > > > "Make my hard drive go rally slow please (just in case I cr=
> ash)=3D
> > > " :)
> > > > > >=3D3D20
> > > > > > Slower, yes, but not *that* slow.
> > > > > >=3D3D20
> > > > > > Normal ls : 0.032 second.
> > > > > > hw.ata.wc=3D3D3D0
> > > > > ^^^
> > > > > "Make my hard drive go rally slow please (just in case I crash)=
> " :)
> > > >=3D20
> > > > Slower, yes, but not *that* slow.
> > > >=3D20
> > > > Normal ls : 0.032 second. Two processes using same disk, multiply by=
>
Dieter> > 16 IP bsd.63743 > src.65001: . ack 52 win 65535
Dieter> > 11 IP bsd.63743 > src.65001: . ack 53 win 112 <-- why
does
Dieter> > the window suddenly shrink?
Chuck> I'd guess because both sides have requested that the connection
Chu
I found a couple more things that don't look right.
17 IP bsd.63743 > src.65001: . ack 52 win 65535
000107 IP bsd.63743 > src.65001: . ack 52 win 65535
12 IP bsd.63743 > src.65001: F 52:52(0) ack 52 win 65535
05 IP bsd.63743 > src.65001: F 52:52(0) ack 52 win 65535
000172 IP src.65001
Here's another oddity:
With one process reading from ad4, crunching data, writing to ad2:
4 usersLoad 0.31 0.47 0.67 Nov 23 10:05
Mem:KBREALVIRTUAL VN PAGER SWAP PAGER
Tot Share TotShareFree in out
> > > > hw.ata.wc=3D3D0
> > > ^^^
> > > "Make my hard drive go rally slow please (just in case I crash)" :)
> >=20
> > Slower, yes, but not *that* slow.
> >=20
> > Normal ls : 0.032 second. Two processes using same disk, multiply by two,
> > so 0.064 second. Maybe the
> > hw.ata.wc=3D0
> ^^^
> "Make my hard drive go rally slow please (just in case I crash)" :)
Slower, yes, but not *that* slow.
Normal ls : 0.032 second. Two processes using same disk, multiply by two,
so 0.064 second. Maybe the multiplier is more than 2, call it 10x, so
> > > > > > time ls on a small directory on disk2
> > > > > >=3D3D20
> > > > > > real4m51.911s
> > > > > > user0m0.000s
> > > > > > sys 0m0.002s
> > > > > >=3D3D20
> > > > > > I expect access to a busy disk to take longer, but 5 minutes is
> > > > > > a bit much. And that's the root di
In message <[EMAIL PROTECTED]>, Kris Kennaway writes:
>
> --mP3DRpeJDSE+ciuQ
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Wed, Nov 22, 2006 at 11:02:54AM +, Dieter wrote:
>
In message <[EMAIL PROTECTED]>, Kris Kennaway writes:
> > > I'm surprised that you're seeing that much of a "hang". Even if the di=
> sks
> > > are busy, the system should slow down all disk processes equally, so no
> > > one process "blocks", but they're all a little slower.
> >=20
> > I collect
> I'm surprised that you're seeing that much of a "hang". Even if the disks
> are busy, the system should slow down all disk processes equally, so no
> one process "blocks", but they're all a little slower.
I collected a bit of data:
While copying a large file from disk1 to disk2,
time ls on a
> > The machine has 2 GB. I wonder if the process is getting its fair share?
> > I have been observing other problems where disk activity to one disk
> > will make an unrelated process reading data from a different disk *very*
> > unresponsive.
>
> Sounds like a hardware problem to me. If you've
Dan writes:
Dan> A shrinking window and no packet loss is an indication that the program
Dan> the socket is connected to isn't reading data fast enough. If you're
Dan> locally gzipping the output of a remote backup, for example, you'll see
Dan> this.
Just a tight loop reading the socket and writ
In the tcpdump output below, the src machine is sending data to the
bsd machine. At one point during this test, the bsd machine is slowly
falling behind, as shown in the smaller and smaller window size.
It looks like at one point, the bsd machine takes 5.5 seconds to
ack a packet. :-( Am I inte
In the process of debugging a not-working-so-well TCP
application, I've been asked to provide:
> cat /proc/sys/net/ipv4/tcp_window_scaling
> cat /proc/sys/net/ipv4/tcp_wmem
Which of course results in "No such file or directory".
I suspect these are from Linux. Are there equivalent
parameters in
> It seems that this was caused by the (infamous) problem when
> softupdates and write caching are both enabled. Disabling write
> caching seems to have fixed the problem.
Interesting. The disk write cache being on should only cause
problems if the system goes down hard/unclean, e.g. power failur
> You could open the box and cut the 2 wires leading from the
> power on button and connect then together so the motherboard always
> thinks the power on button is depressed. (do this at your own risk)
Rather than cut and splice wires, just try a jumper on the header pins.
Or hold the button down
FreeBSD 6.0 AMD64
newfs -N -b 65536 -f 8192 -i 262144 -m 0 -o space -s 2295104 -S 2048
/dev/ad10s1
/dev/ad10s1: 4482.6MB (9180416 sectors) block size 65536, fragment size 8192
using 4 cylinder groups of 1120.69MB, 17931 blks, 4608 inodes.
super-block backups (for fsck -b #) at:
25
> When source/usr/home/me/public_html is empty then it runs fine. But when I put
> any links in, tar dies with a segmentation fault.
>
> Has anyone got any ideas why?
> Yup, looks like I'm using bsdtar
Now that you know which tar you're using, :-)
time to drag out the standard debugging process f
> That's exactly what I'm doing right now. For example when I need
> to use my Pinnacle DC10+ (Zoran) card, I simply reboot into Gentoo,
> do the capture, and then reboot into FreeBSD to run the rest of
> mjpegtools. Same for MIDI recording etc... or other stuff that's
> currently unavailable withi
> > > since Linux' support for some hardware is better than FreeBSD's,
> > > it would be nice to have an *optional* way of running a FreeBSD
> > > system (userland, including all third party programs) on top
> > > of the Linux kernel.
> >
> > I'd prefer to have a way to use a Linux device driver w
> since Linux' support for some hardware is better than FreeBSD's,
> it would be nice to have an *optional* way of running a FreeBSD
> system (userland, including all third party programs) on top
> of the Linux kernel.
I'd prefer to have a way to use a Linux device driver with a
BSD kernel.
__
> actually instructs you to remove the keyboard.
I think this is for some systems with buggy firmware?
For other systems with different buggy firmware you
should leave the "video" keyboard connected, at least
if you need to get into the firmware's "setup" mode.
> So is there someone who can give
> I can't seem to figure out how to make a screen capture.
xwd > screen_dump_file
Then move the mouse curser to the window you want to dump
and click the left button.
"man xwd" for more details
If you then need to convert the file to gif/jpeg/PostScript/whatever
the xv program can do that.
> >> > Are there any plans to update gcc to gcc-4?
> >>
> >> Perhaps in 8.0? There are already gcc4[0-2] ports in
> >> /usr/ports/lang if you want to have gcc 4 right now.
> >>
> >> - Parv
> >
> > Thanks, my copy of 6.0 doesn't seem to have gcc42 so I'm
> > trying to beat gcc41 into submission.
> > Are there any plans to update gcc to gcc-4?
>
> Perhaps in 8.0? There are already gcc4[0-2] ports in
> /usr/ports/lang if you want to have gcc 4 right now.
>
> - Parv
Thanks, my copy of 6.0 doesn't seem to have gcc42 so I'm
trying to beat gcc41 into submission.
I'm running FreeBSD 6.0 on
Are there any plans to update gcc to gcc-4?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> boot_osflags0,0
leads to:
> Unrecognized boot flag '0'.
> Unrecognized boot flag ','.
> Unrecognized boot flag '0'.
NetBSD/alpha uses
s single-user mode bootstrap.
a (automatic) multi-user mode bootstrap.
although FreeBSD may well use different flags.
I c
> FreeBSD 6 seems to recognize logical slices in extended ones. The
> appropriate entries /dev/ad0sN appear. At least this works with
> logical slices that contain VFAT or ext2fs.
> Just 'fdisk' doesn't list the logical slices. Is there a tool that
> can list these?
NetBSD's fdisk can.
___
> The only odd thing is if the FreeBSD MBR detects a bootable slice with
> a filesystem type it does not know such as NTFS, it identifies it in
> the menu as '???' rather than with a name.
I'm triple-booting FreeBSD, NetBSD and that penguin thingy. NetBSD's
fdisk(8) allows setting the menu labels
1 - 100 of 104 matches
Mail list logo
