Alexander Motin wrote:
> On 25.11.2012 01:43, Adrian Chadd wrote:
> > I'm surprised it's not tunable via a kenv variable at boottime..
>
> It is tunable. AFAIR that is it:
> kern.msgbufsize="65536" # Set size of kernel message buffer
Yep. That tunable is available in 8.2 (not 8.1), and I
Kevin Oberman wrote:
> Throttling ... is intended for thermal control, not power
> management. The power savings will be negligible ...
How can it possibly provide any thermal benefit, if it does not
reduce power consumption? Is there some significant heat source,
other than power consumed, tha
Ian Lepore wrote:
> On Sat, 2012-03-03 at 09:09 -0800, per...@pluto.rain.com wrote:
> > H wrote:
> > > ... Forever installing FreeBSD Desktop, either KDE or Gnome,
> > > was a nightmare process, or better, to make it appear on screen
> > > was a nightmare.
> >
> > I have never understood the po
H wrote:
> ... Forever installing FreeBSD Desktop, either KDE or Gnome,
> was a nightmare process, or better, to make it appear on screen
> was a nightmare.
I have never understood the point of KDE or Gnome, other than
(perhaps) as eye candy for the uninitiated. If I wanted a
Windows desktop, I
Alexander Leidinger wrote:
> On Sun, 12 Feb 2012 03:05:02 -0800 per...@pluto.rain.com wrote:
> > Alexander Leidinger wrote:
> > > On Sat, 11 Feb 2012 13:40:41 +0100 Thierry Thomas
> > > wrote:
> > > > is there another place to put options to atkbd and sc, like
> > > > these ones:
> > > >
> > > >
Alexander Leidinger wrote:
> On Sat, 11 Feb 2012 13:40:41 +0100 Thierry Thomas
> wrote:
> > is there another place to put options to atkbd and sc, like
> > these ones:
> >
> > options ATKBD_DFLT_KEYMAP # specify the built-in keymap
> > makeoptions ATKBD_DFLT_KEYMAP=fr.iso.acc
> > ...
>
"Bjoern A. Zeeb" wrote:
> various parts of the network stack being loadable, which is not
> as easy as it sounds, especially making them unloadable again
> currently ...
Seems to me unloadability does not matter to the case under
discussion, which is modularizing the kernel to reduce the
number
Ken Smith wrote:
> The release notes were not ready at the point we started up the
> release builds so the online versions are the only ones that have
> any useful information in them.
Perhaps the final version could be made MFCd to the errata/security
branch, and/or added to the FTP sites along
Freddie Cash wrote:
> On Mon, Jan 9, 2012 at 9:50 AM, John Nielsen
> wrote:
> > From what you've said I strongly suspect that you have some
> > kind of hardware issue. Dodgy RAM is my first guess ...
>
> That's what we're leaning toward as well. We're planning on
> doing a BIOS upgrade (betadri
Joshua Boyd wrote:
> This "new" work computer is 64 bit but doesn't have the right
> chipset features to support 64bit guests.
>
> Lame.
Perhaps that sort of machine should be referred to as 63-bit,
since it is a bit short of full 64-bit capability :)
[ducks & runs]
Jeremy Chadwick wrote:
> It is already easy to switch schedulers. You change the
> option in your kernel config, rebuild kernel (world isn't
> necessary as long as you haven't csup'd between your last
> rebuild and now), make installkernel, shutdown -r now,
> done.
and you have thereby shot fre
Adrian Chadd wrote:
> Out of pure interest, I'd love to see whether xl on an earlier
> kernel (say 4.x, if the hardware can even run it) or even 6.x
> would work.
I'll put that on the list for the next time I need to reboot it.
I'm sure I have a 6.1 CD somewhere, and probably a 4.x CD also.
(The
> > ... SOME hubs of that era had series problems if the cable was
> > too short.
> >
> > You mentioned using a short cable. Have you tried a longer one?
> > I seem to recall that 3 meters was the minimum, but it was so
> > long ago that my memory is a bit fuzzy.
>
> The first cable I used was abou
> > You can either replace the NIC with something else,
> > or replace the hub. IMHO, I would replace both.
>
> I can replace the hub easily enough -- I have a 100-only
> Netgear that _is_ a true hub (has been used successfully
> for sniffing) ...
That fixed it. For the archives, this particular
Kevin Oberman wrote:
> Wow. it's 1985 again. O remember those 10/100 hubs. They were a
> royal pain!
>
> If I remember right, they kept costs down by building in half of
> a switch. Traffic from a 10 port to a 100 port was buffered,
Speed conversion had to have been buffered in both directions.
Jeremy Chadwick wrote:
> 1) I think you misunderstand what product it is you own. You have
> a hub, not a switch. This is confirmed by the fact that auto-neg
> chooses to negotiate half-duplex. Instead, you went later and
> messed about trying to force full-duplex, which isn't going to
> work
Damien Fleuriot wrote:
> On 10/21/11 5:00 PM, per...@pluto.rain.com wrote:
> > I have an 8.1-RELEASE system with an xl on the mainboard:
> > xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc80-0xdcff mem
> > 0xf8fffc00-0xf8fffc7f irq 16 at device 4.0 on pci2
> > miibus0: on xl0
> > xlphy0:
I have an 8.1-RELEASE system with an xl on the mainboard:
xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc80-0xdcff mem
0xf8fffc00-0xf8fffc7f irq 16 at device 4.0 on pci2
miibus0: on xl0
xlphy0: <3c905C 10/100 internal PHY> PHY 24 on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100
nickolas...@gmail.com wrote:
> > - try to fiddle with relevant settings in BIOS
...
> You've fogot about BIOS SATA/IDE setting. Try to play with it.
That's arguably one of the "relevant settings in BIOS" :)
___
freebsd-stable@freebsd.org mailing list
ht
Jeremy Chadwick wrote:
> On Tue, Aug 30, 2011 at 11:04:43PM -0700, Kevin Oberman wrote:
> > ... the standrad does not specify EXACTLY what triggers a
> > transition from standby to ready (PM2 to PM0). Only that it is
> > something that requires media access. A write does not
> > necessarily requir
> When the specified or calculated rate exceeds 64KB/sec, the
> required sleep interval between 64KB chunks is less than one
> second. Since diskcheckd calculates the interval in whole seconds
> -- because it calls sleep() rather than usleep() or nanosleep()
> -- an interval of less than one secon
Jeremy Chadwick wrote:
> On Sun, Aug 21, 2011 at 02:00:33AM -0700, per...@pluto.rain.com
> wrote:
> > Jeremy Chadwick wrote:
> > > ... using dd to find the bad LBAs is the only choice he has.
> > or sysutils/diskcheckd ...
> That software has a major problem where it runs constantly, rather
> tha
Jeremy Chadwick wrote:
> ... using dd to find the bad LBAs is the only choice he has.
or sysutils/diskcheckd. It uses a 64KB blocksize, falling back to
512 -- to identify the bad LBA(s) -- after getting a failure when
reading a large block, and IME it runs something like 10x faster
than dd with
Chuck Swiger wrote:
> On Aug 9, 2011, at 7:26 AM, Daniel Kalchev wrote:
> > I am trying to set up 64GB partitions for swap for a system that
> > has 64GB of RAM (with the idea to dump kernel core etc). But, on
> > 8-stable as of today I get:
> >
> > WARNING: reducing size to maximum of 67108864
Jeremy Chadwick wrote:
> On Wed, Jul 20, 2011 at 02:39:28AM -0700, per...@pluto.rain.com wrote:
> > IIRC, Plextor (and maybe some others) had a switch to select 512 or
> > 2048 as the default transfer size, precisely so that they could be
> > used as boot devices with systems that supported only
Chuck Swiger wrote:
> On Jul 19, 2011, at 2:10 PM, Peter Jeremy wrote:
> > On 2011-Jul-19 10:54:38 -0700, Chuck Swiger wrote:
> >> Unix operating systems like SunOS 3 and NEXTSTEP would happily
> >> run with a DEV_BSIZE of 1024 or larger-- they'd boot fine off
> >> of optical media using 2048-byt
Tom Evans wrote:
> On Thu, Jun 30, 2011 at 6:31 PM, Christian Baer
> wrote:
> > A serial console is easy enough to set up on a Sun for example, but in
> > this case, I am running a simple AthlonXP, which has nothing for that
> > sort of help. I would need a special card for that and those cose qu
George Kontostanos wrote:
> On Mon, Jun 27, 2011 at 2:00 PM, Alexander Sabourenkov
> wrote:
> > Seems like my patch fell off the bus when the ata subsystem
> > was rewamped. The problem is a silicon bug in TX4 ASICs.
> > See this thread:
> > http://lists.freebsd.org/pipermail/freebsd-current/200
Bengt Ahlgren wrote:
> nickolas...@gmail.com writes:
> > I've tried to make two journaled partitions on new GPT disk.
...
> > How can I mount this partitions using GPT labels?
...
> I think the idea with labels is great, but whether it works or
> not seems pretty random to me as a user.
Based on
na...@mips.inka.de (Christian Weisgerber) wrote:
> PS/2 is dead.
Not.
The old _ISA-based_ PS/2 is dead. PS/2 interfaces, provided by other
means (such as microcontrollers), are making a comeback, presumably
because USB requires such a large and complex protocol stack to do
much of anything. I
"ill...@gmail.com" wrote:
> On 5 March 2011 20:00, Yue Wu wrote:
> > On Sat, Mar 05, 2011 at 04:48:17PM +0100, Greg Byshenk wrote:
> >> On Sat, Mar 05, 2011 at 11:04:36PM +0800, Yue Wu wrote:
> >> > 1. How to reserve packages that fetched via `pkg_add -r`?
> >> > ...
> >> For (1), do you mean 'pr
Pete French wrote:
> > Why may it hurt ? How may it hurt ? Which sector is written to
> > by this 'gpart' command ?
> >
> > As far as I understand, GPT writes some stuff at the beginning
> > and the end of the harddisk.
>
> Yup, this is true.
>
> > How/why will the newfs overwrite those parts ?
>
Ollivier Robert wrote:
> Or switch to unbound.
^^^
Cute name, but perhaps a tiny bit misleading as to the product's
origin -- the first thing I thought of on seeing a name like
that was the FSF. Not this time: although its development was
commercially sponsored it is BSD-lic
Noticed while digging through devfs_read_f() and devfs_write_f() in
the course of investigating some unexpected (by me) geom behavior:
...
int ioflag, error, resid;
...
resid = uio->uio_resid;
...
if (uio->uio_resid != resid || ...
IOW resid (an int) is being assigned from
Alban Hertroys wrote:
> Ever since installing 7.4-PRERELEASE I'm seeing MCA machine check
> errors on my home-server ...
>
> MCA: Bank 0, Status 0xb6220135
> MCA: Global Cap 0x0104, Status 0x0004
> MCA: Vendor "AuthenticAMD". ID 0x662, APIC ID 1
> MCA: CPU 0 UNCOR
Sergey Kandaurov wrote:
> Committed in r217688.
Thanks!
Will this be eligible for MFC? (Not for 8.2 or 7.4 I suppose --
presumably they are only accepting bug-fixes at this point -- but
I'd expect it to be compatible with 8-CURRENT.)
___
freebsd-stab
Jerahmy Pocott wrote:
> I have a USB Drive that was working fine under 7.3, but since
> updating to 8.1 no longer has the correct /dev entries. Under
> 7.3 it was da0s1, in 8.1 there is now only da0 and da0a, which
> shouldn't exist...
>
> Any ideas on how to correct this problem?
No, but you're
Anyone had a chance to look at this?
http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060793.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebs
Rick Macklem wrote:
> Sun did add a separate file locking protocol called the NLM
> or rpc.lockd if you prefer, but that protocol design was
> fundamentally flawed imho and, as such, using it is in the
> "your mileage may vary" category.
I suppose it was not all that bad, considering that what i
John Baldwin wrote:
> ... even NFS UDP mounts maintain their own set of "socket" state
> to manage retries and retransmits for UDP RPCs.
Not according to what I remember of the SunOS NFS documentation,
which indicated that the driving force behind using UDP instead of
TCP was to have the server
Rick Macklem wrote:
> ... one of the fundamental principals for NFSv2, 3 was a stateless
> server ...
Only as long as UDP transport was used. Any NFS implementation that
used TCP for transport had thereby abandoned the stateless server
principle, since a TCP connection itself requires that stat
Andriy Gapon wrote:
> on 06/12/2010 07:20 per...@pluto.rain.com said the following:
> > Would there be some fundamental problem in changing MSGBUF_SIZE
> > from a compiled-in constant to a tunable that could be set at the
> > loader prompt?
> > I didn't see any obvious downside from examining the
Andriy Gapon wrote:
> on 16/12/2010 11:34 per...@pluto.rain.com said the following:
> > Andriy Gapon wrote:
> >> BTW, are you sure that you correctly placed initialization of
> >> msgbufsize ?
> >
> > I am not at all sure of that ...
> >
> > Apart from the name, msgbufsize is set up in exactly
Andriy Gapon wrote:
> on 15/12/2010 12:37 per...@pluto.rain.com said the following:
> > Fatal double fault:
> > eip = 0xc07feb98
> > esp = 0xc101e000
> > ebp = 0xc101e004
> > cpuid = 0; apic id = 00
> > panic: double fault
> > cpuid = 0
> >
> > How do I go about tracking this down?
>
> Do you hav
Andriy Gapon wrote:
> on 06/12/2010 07:20 per...@pluto.rain.com said the following:
> > Would there be some fundamental problem in changing MSGBUF_SIZE
> > from a compiled-in constant to a tunable that could be set at the
> > loader prompt?
> > I didn't see any obvious downside from examining the
Pete French wrote:
> Is there a way inside the install environment to see
> what the kernel has detected and created in /dev ?
Go into Fixit# and examine /dev and/or the dmesg.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
Andriy Gapon wrote:
> on 06/12/2010 07:20 per...@pluto.rain.com said the following:
> > Would there be some fundamental problem in changing MSGBUF_SIZE
> > from a compiled-in constant to a tunable that could be set at the
> > loader prompt? (I'm _not_ suggesting that it be adjustable while
> > th
"Andrey V. Elsukov" wrote:
> >> NOTE: Some old utilities like bsdlabel may not work if the
> >> kernel doesn't include GEOM_BSD and other old slicer classes.
> >> In other words, bsdlabel et al don't work with GEOM_PART.
> >
> > Does this mean that, in 8.1-RELEASE, bsdlabel/disklabel will
> > not
Would there be some fundamental problem in changing MSGBUF_SIZE
from a compiled-in constant to a tunable that could be set at the
loader prompt? (I'm _not_ suggesting that it be adjustable while
the system is running.)
The upside would be that, if someone needed a larger buffer
temporarily to acc
David DEMELIER wrote:
> Here : http://ivoras.sharanet.org/freebsd/freebsd8.html
>
> GEOM_PART becomes the default slicer
>
> Status: Committed to -CURRENT
> Will appear in 8.0: sure
> Author: Marcel Moolenaar & others
> Web: commit message
>
> GEOM_PART (gpart) is a new GEOM partition class (slic
Irakli wrote:
> mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE
> -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq
> -I/usr/src/sys/i386/compile/NS /usr/src/sys/modules/ae/../../dev/ae/if_ae.c
> ===> aesni (depend)
> @ -> /usr/src/sys
> machine -> /usr/src/sys/i386/include
> make: don
Tom Evans wrote:
> Interesting; I'm trying to give up using firefox (which for me
> leaks memory like a sieve ...
Interesting that it is _still_ doing this. I have that problem with
1.5.0.6, but figured it would have been fixed in current versions.
__
Artem Belevich wrote:
> All you need is intentionally make one data bit bad. Put some
> tape on one of the data pads on the DIMM and run memtest ...
and then spend the next couple of hours cleaning the gunk off of
the DIMM and out of the slot :(
___
f
Harald Weis wrote:
> On Fri, Oct 08, 2010 at 01:33:30PM -0500, Adam Vande More wrote:
> > On Fri, Oct 8, 2010 at 1:00 PM, Harald Weis wrote:
> > > (while waiting for gnash)
> >
> > That's the funniest thing I've heard all week.
>
> Tell me. What is so funny about gnash ?
I took the reference as
Steven Friedrich wrote:
> On Friday 08 October 2010 12:22:40 pm Dimitry Andric wrote:
> > On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
> > > Another thing about VoIP calls: have they solved the
> > > "emergency call needs a location" problem? Here (again: in
> > > Norway) they are still working o
?zkan KIRIK wrote:
> When I watch log messages I see "kernel: arpresolve: can't allocate
> llinfo for 10.0.16.251" messages ...
"can't allocate llinfo" has been in the network code for a _very_
long time.
One cause is, or at least used to be, the machine having no netmask
defined for its own IP
John Baldwin wrote:
> On Friday, September 10, 2010 2:55:15 am per...@pluto.rain.com wrote:
> > ...
> > It is arguably a bug to open O_RDWR when only examining things.
>
> You have to have RDWR permission to issue the ioctl to read config
> registers which pciconf does when examining capabilities.
Gareth de Vaux wrote:
> On Thu 2010-09-09 (16:54), Kurt Jaeger wrote:
> > -c asks for pci device capabilities, which are read in
> >
> > /usr/src/usr.sbin/pciconf/pciconf.c:177 with O_RDWR
>
> Ah. I'll have to schedule a reboot then ..
or hack on pciconf.c to not request more permission than it
John Baldwin wrote:
> We can't e-mail announce@ every time something is going to
> be removed. That would be way too much spam for that list.
That may depend on how often something substantial is removed :)
> I do think stable@ is a good place to e-mail ...
Good, perhaps even "necessary", but
Michal wrote:
> What is really odd is I see your replies but not my original post,
> how very strange??
One of your subscription options is whether you get your own posts
back.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
Dmitry Morozovsky wrote:
> ... sector numbers (in CHS address method)
> [start] at 1 (which always suprized me ;)
This goes back at least as far as soft-sectored 8" diskettes
in the CP/M era.
IIRC, physical sector 0 of each track contained the C number,
possibly the H, and a list of the remainin
Holm Tiffe wrote:
> Why I can't read 1440K blocks from the floppy anymore?
Perhaps something changed in the DMA driver, such that it is
no longer able to handle a request exceeding 65K (which was
the hardwired limit of the "original" PC DMA controller).
I've long used bs=120b for floppies, and n
Jeremy Chadwick wrote:
> The tag= line for ports should always be . (period, indicating
> HEAD) ...
"always" is a bit too strong here IMO. The tag= line for ports
could reasonably be a release label, if the intent is to retrieve
the ports tree as of that release; granted this would be an uncomm
"Kevin Oberman" wrote:
> ... TCC and throttling ...
> they were intended for thermal management, not power management.
Shouldn't the two be equivalent? Heat generated is directly related
to power consumed.
___
freebsd-stable@freebsd.org mailing list
h
Pete French wrote:
> ... using /usr/bin/mail as your primary mail reader ...
> -pete. [resolutely sticking to the command line even in 2010! :-)]
You're not the only one :)
Not to discourage any improvements in the base, but have you
looked at ports/mail/heirloom-mailx (formerly known as Nail)
Ruben de Groot wrote:
> defer all questions about moving out of the base system ...
Last I knew, X was not _in_ the base system :)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
Peter Jeremy wrote:
> ... Once ntpd decides to continuously step, something is broken.
Is there some reason why, as long as it is not yet synced, ntpd
should not do this sort of calculation and rate correction itself
rather than insist on having a human perform the calculation and
enter the adju
Ivan Voras wrote:
> On 02/18/10 16:26, Harald Weis wrote:
> > Has anybody encountered the following problem ?
> >
> > Mac OS X does recognize FreeBSD partitions on USB disks, but
> > doesn't want to mount them because ``Incorrect super block''.
> > This is extremely annoying for my ``client'' beca
Jeremy Chadwick wrote:
> The DOS utilities submit custom ATA CMDs or data to all WD disks
> to toggle or adjust these features. If someone could figure out
> what the command(s) were, the feature(s) could be implemented into
> atacontrol(8). Of course, that would require reverse-engineering
> of
"O. Hartmann" wrote:
> At this very moment I utilise a M-Audio 5.1 PCI-audio board with
> which I'm really satisfied. My next box doesn't have PCI slots
> at all ... I look for the Soundblaster X-Fi range of PCIe cards,
It's possible to get an adapter that plugs into a PCIe slot and
provides a P
Randy Bush wrote:
> imiho, zfs can not be called production ready if it crashes if you
> do not stand on your left leg, put your right hand in the air, and
> burn some eye of newt.
ROFL!
As with any open-source project, I suppose it will be ready
when it is ready. At least it hasn't been made t
Karl Denninger wrote:
> ... the uart driver is BROKEN.
>
> It simply locks up on the port after some period of time,
> returning nothing. I have found no way to reset the port
> other than a reboot either ...
Welcome to the distant past. I'll be interested to see what
the root cause turns out t
Luke Dean wrote:
> my simple USB mouse stopped being detected at boot time.
> The /dev/ums0 device simply does not appear unless I unplug
> the mouse and plug it back in again. Then it is detected.
...
> Is there something I can do to force the system to rescan for
> my mouse to save me from craw
Zaphod Beeblebrox wrote:
> ... reboots of an NFS server are meant to be transparent to the
> clients (save the downtime involved).
Not just downtime; how would you like to have to restart your whole
X11, OpenWindows, or SunTools session -- losing all current user-
oriented state and perhaps consi
"Daniel O'Connor" wrote:
> I wonder how hard it would be to add 3 way merging (like
> sysutils/etcmerge) to mergemaster..
One complication: to do a 3-way merge you have to have the common
ancestor. To ensure the initial availability of such would require
some infrastructure which AFAIK does not
> > And it seems, that my USB2Serial cable can not generate BREAK.
> > When I press "~#" in cu it output "~" and doesn't go to debugger
> > (yse, I have BREAK_TO_DEBUGGER option)...
>
> Have you changed the ssh escape char? It defaults to "~" so if you
> haven't, ssh eats the "~" before cu sees i
> to apply quirks without rebuilding a kernel you can use the recent
> 'kldpatch' port ...
"recent" as in "added within the last couple of weeks"?
I don't see it in an INDEX from Jan. 4. Sounds useful.
___
freebsd-stable@freebsd.org mailing list
http://
77 matches
Mail list logo
