Just a suggestion, but isn't this the type of thing that
should be added to UPDATING?
"This file contains a list, in reverse chronologocal order, of major
breakages in tracking -current."
TOny.
On Sun, 27 Aug 2000, Brooks Davis wrote:
> On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsu
Someone stashed a refewrence to an extern int hintmode in /sys/kern/subr_bus.c
a couple of days ago - where's it actually defined? Mr Grep cant seem to find
in /sys.
Stephen
--
The views expressed above are not those of PGS Tensor.
"We've heard that a million monkeys at a milli
On Sun, 27 Aug 2000, John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> > If this is a problem with sbsize, this should take care of any possibility
> > ever of there being a problem...
>
> I tried your patch, but it panics reliably on
subscribe
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
Share information about yourself, create your own public profile at
http://profiles.msn.com.
To Unsubscribe: send mail to [EMAIL PROTEC
David Malone writes:
> We were thinking it might be a good idea to have a flag associated
> with mbufs which means they are writable, providing the reference
> count is 1. Then we can provide a macro for checking writability.
> This flag could be set on jumbo ethernet buffers, but not sendfile
> b
[dropping -questions, this is a -CURRENT problem]
On Sunday, 27 August 2000 at 22:28:34 -0400, Systems Administrator wrote:
> I've been having a strange problem recently after installing a new
> harddrive.. the harddrive works fine in other OS's, but in FreeBSD,
> (seemingly after the HD install)
In upgrading my system I've bought a shiny new SMP mobo to go with my new
30gb Deskstar... The nice thing about this new board is my HighPoint
HPT366 based IDE controller works now (Buggy Phoenix BIOSes prevented it
from working before). Perhaps in a rush to get started, I've compiled and
been u
I've been having a strange problem recently after installing a new
harddrive.. the harddrive works fine in other OS's, but in FreeBSD,
(seemingly after the HD install), the Monitor (CTX VL19") goes into
powersaving and you cant get it back without doing a cold reboot.. not
even a warm reboot will
Ted writes:
> [...]
>
> As far as yarrow versus the current design, I've certainly looked at
> yarrow, and I've certainly considered adding some of yarrow's design
> into my /dev/random implementation. Given that I strongly recommend
> that the 512 bytes of entropy be saved from /dev/random at
Sean-Paul Rees wrote:
>
> On Sun, Aug 27, 2000 at 05:24:07PM -0700, Marcel Moolenaar wrote:
> > "George W. Dinolt" wrote:
> > >
> > > I was wondering whether the setrlimit changes had something to do with
> > > this. This seems to be the major change to the linux code in the last
> > > few days.
On Sun, Aug 27, 2000 at 09:33:21PM +0900, Motomichi Matsuzaki wrote:
>
> When kernel is built with static device wiring
> (i.e. 'hints' line is enabled in the config file),
> is /boot/device.hints required?
>
> Doing 'make install' without /boot/device.hints is failed,
> saying "You must set up
Ted writes:
> A couple of comments here. It was always the intention that
> /dev/random be 0666, and in my implementation, writing to
> /dev/random mixed the input into the entropy pool *without* changing
> the entropy estimate.
I see. This is not clear.
We recently set it /dev/random to grou
Mike Pritchard wrote:
> I just had a problem trying to install the latest -current
> snapshot from the 8/26 snap. Background:
>
> Windows trashed my hard disk on one of my machines, so I had
> to do clean install. Since I run -current on that machine
> anyways, I decided to try the latest snaps
"George W. Dinolt" wrote:
>
> I was wondering whether the setrlimit changes had something to do with
> this. This seems to be the major change to the linux code in the last
> few days. Apparently you were the one to make those changes, so I am
> writing to you (Marcel)
Can you track down whic
< said:
> However, many routines that take an mbuf parameter assume that the
> mbuf given to them is modifiable and proceed to write all over it.
s/assume/require as a necessary precondition/
It's not a coding error, it's part of the specification. No, it's not
documented -- but it's pretty cl
Marcel:
Up until this weekend, I was able to use the staroffice52 port with
little problem (I had installed it earlier without benefit of the port
and it worked fine.) I did a 5.0-current kernel rebuild on Thursday with
sources current on that day and things were fine. When I rebuilt my
kernel ye
James Johnson wrote:
> Having to specify
> which kernel to build with the KERNEL= parameter seems to indicate that
> people should be running GENERIC kernels all the time as it is the default.
No, it seems to indicate that you should specify KERNEL=YOURKERNEL in
make.conf.
--
Ben Smithurst / [
I compiled and booted on alpha. It sees my ad0 now. Plus it also sees the 3
'da' disks that were found.
The only real problem is that it won't see the partitions made for
'dangerously dedicated' 'da' disks. What's the plan for addressing this?
-matt
To Unsubscribe: send mail to [EMAIL PRO
In article <[EMAIL PROTECTED]>,
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> If this is a problem with sbsize, this should take care of any possibility
> ever of there being a problem...
I tried your patch, but it panics reliably on start-up:
Automatic boot in progress...
/dev/da0s1a:
From: "James Johnson" <[EMAIL PROTECTED]>
> The method of building and installing a kernel to me seems a bit off.. Both
> the buildworld and installworld targets default to GENERIC, yet GENERIC is a
> file checked into the -CURRENT CVS repository.. Any changes to this file
> will get blown away if
Adam writes:
>Yes. But the /dev/random device is traditionally crw-r--r-- which
>means user processes can't write to it. So you'd have to be root to
>do that.
>
>What could be done for yarrow is to change the device permissions to
>crw-rw-rw- and mix into a shared user source and set k_of_n_thre
On Sun, Aug 27, 2000 at 02:25:55PM -0700, Archie Cobbs wrote:
> Each mbuf may be either a normal mbuf or a cluster mbuf (if the
> mbuf flags contains M_EXT). Cluster mbufs point to an entire page
> of memory, and this page of memory may be shared by more than one
> cluster mbuf (see m_copypacket(
On Sun, Aug 27, 2000 at 02:25:55PM -0700, Archie Cobbs wrote:
> What do people think? If this is generally agreeable I'll try to
> work on putting together a patch set for review.
Myself and Ian Dowse have been talking about almost this issue
recently in relation to sbcompress. At the moment sbc
In looking at some of the problems relating to divert, bridging,
etc., it's apparent that lots of code is breaking one of the rules
for handling mbufs: that mbuf data can sometimes be read-only.
Each mbuf may be either a normal mbuf or a cluster mbuf (if the
mbuf flags contains M_EXT). Cluster mb
Just a little usability observation(or I am too lazy to script_my_own_tools
and want to whine!)
The method of building and installing a kernel to me seems a bit off.. Both
the buildworld and installworld targets default to GENERIC, yet GENERIC is a
file checked into the -CURRENT CVS repository..
It seems [EMAIL PROTECTED] wrote:
> > BTW, these IBM 75GXP drives off of the HPT-370 are amazingly fast for
> > IDE.
>
> >From my own measurements I'd say these drives are amazingly fast, period.
>
> They compete rather well with SCSI drives.
>
> A big thanks to sos for the HPT-370/UDMA100 suppo
> > That works with what I already have: cat $privatekey > /dev/random :-)
>
> Yes. But the /dev/random device is traditionally crw-r--r-- which
> means user processes can't write to it. So you'd have to be root to
> do that.
I go one further; at close, I do an explicit reseed, and I make sure
One last note, if this is a case for a functional union fs. I'd like to
see my mistyping and the system combine things into one device directory
so this type of problem will not stop my system frm booting up
completely...
Tony Johnson wrote:
>
> Sorry for the repeat. I was playing with the se
Sorry for the repeat. I was playing with the sendmail 8.11.0 you guys
have provided...
But anyway, if DEVFS is in my fstab or not it gets mounted under /dev ,
as you point out. I guess this is the problem because I have to remove
"options DEVFS" from my kernel in single user for my system to bo
In message <[EMAIL PROTECTED]>, Tony Johnson writes:
>I'm sure you know this already, but I just want to reiterate. I have
>done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did
>a cvsup in the "wee" hours in the morning. I then did make world in
>/usr/src to rebuild the system
I'm sure you know this already, but I just want to reiterate. I have
done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did
a cvsup in the "wee" hours in the morning. I then did make world in
/usr/src to rebuild the system, rebuild kernel, and mergemaster -sv.
The system should
Mike Smith wrote:
>
> > (excuse complete ignorance as far as IDE RAID below)
> >
> > For the buildbox here, I decided to go ahead with Soren's ATA-100 RAID
> > suggestion, and bought an Abit KT7-RAID motherboard, which has an onboard
> > Highpoint HPT-370 ATA-100 RAID. I'm using two 15G IBM 75GX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wonderful! Thanks everybody for the help and such...
I have confirmed that this fixes the issue I was having as
well. I look forward to Mike's new drivers!
Laterz
Visigoth
Damieon Stark
Sr. Unix Systems Administrator
[EMAIL PRO
Mark Murray wrote:
[...]
> Again, I'm not so sure; Yarrow goes to great trouble to protect its
> internal state; by blocking, I have this very nasty suspicion that
> this carefully guarded state is being disclosed. The moment you block,
> you are confiding in the fact that you have no updating ent
> BTW, these IBM 75GXP drives off of the HPT-370 are amazingly fast for
> IDE.
>From my own measurements I'd say these drives are amazingly fast, period.
They compete rather well with SCSI drives.
A big thanks to sos for the HPT-370/UDMA100 support!
Steinar Haug, Nethelp consulting, [EMAIL PROT
Thus spake Seigo Tanimura ([EMAIL PROTECTED]):
> - bus_space_write_1(sc->bst, sc->bsh, regno, data);
> + bus_space_write_1(rman_get_bustag(sc->port_res),
>rman_get_bushandle(sc->port_res), regno, data);
Hmm. I used sc->bst/h to save function calls to rman_get_bus*, as
many drivers use
Mark writes:
> Adam writes:
> > OK, I agree that that's an area where yarrow offers better protection.
> > But it's not like Ted's code is broken or anything. We would break
> > things using /dev/random by switching as is to yarrow, so this is why
> > I don't like it: we're trying to improve thi
I just had a problem trying to install the latest -current
snapshot from the 8/26 snap. Background:
Windows trashed my hard disk on one of my machines, so I had
to do clean install. Since I run -current on that machine
anyways, I decided to try the latest snapshot to restore it.
Booting kern
On 27 Aug, Motomichi Matsuzaki wrote:
> Can anyone success compiling kernel with the following config?
>
> # ATA and ATAPI devices
> device ata
> device atadisk # ATA disk drives
> #device atapicd # ATAPI CDROM drives
> device at
When kernel is built with static device wiring
(i.e. 'hints' line is enabled in the config file),
is /boot/device.hints required?
Doing 'make install' without /boot/device.hints is failed,
saying "You must set up a /boot/device.hints file first."
Is this right?
--
Motomichi Matsuzaki <[EMAIL P
Hi,
Can anyone success compiling kernel with the following config?
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
#device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
#de
At 11:07 PM -0700 2000/8/26, Mike Smith wrote:
> The Linux driver for the V and VI cards is (according to a reliable
> source) pretty awful.
I've had to keep making modifications to them to get them to
compile with newer and newer versions of the kernel, and while I keep
contributing
In message <[EMAIL PROTECTED]>, Chris Costello writes:
>On Sunday, August 27, 2000, Boris Popov wrote:
>> No, not all bits are incorporated. At least you've missed two
>> important things. First:
>>
>> # cd /dev/fd
>> # ls
>> 0 1 2
>> # cd ..
>> # ls
>>
In message <[EMAIL PROTECTED]>, Boris Popov
writes:
>On Fri, 18 Aug 2000, Poul-Henning Kamp wrote:
>
>> Missing:
>> Rename
>> Subdirs.
>> Close some race conditions using guaranteed atomic operations.
>> Mountoption (ro ?) to prevent new devices from appearing in a
> Mark writes:
> > [...]
> > FreeBSD is using an earlier version of T'so's code; I beiieve he
> > improved it later, but it has no (or little) backtracking protection,
> > and can be too easily attacked "from both sides".
>
> OK, I agree that that's an area where yarrow offers better protection.
45 matches
Mail list logo
