David O'Brien wrote...
> > And it's not like anyone had to upgrade their fstab -- all of the sd
> > devices still work, since the major number is the same. So there's not
> > a lot of room for complaint here.
>
> Only if sysinstall goes back to creating the /dev/sd* devices and
> matching fstab
On Wed, 17 Mar 1999, Matthew Dillon wrote:
> : mount /cdrom
> : find /cdrom -type f -exec cat \{\} >/dev/null \; -ls
> :
> :and pop it goes. Same stack trace. We could do a try-this-game this weekend
> (up to
> :then I'm covered in work) if that would be helpfull.
> :
> :Let me know what
> And it's not like anyone had to upgrade their fstab -- all of the sd
> devices still work, since the major number is the same. So there's not
> a lot of room for complaint here.
Only if sysinstall goes back to creating the /dev/sd* devices and
matching fstab w/``sd''.
--
-- David(obr...
On Wednesday, 17 March 1999 at 14:21:07 +0200, Vallo Kallaste wrote:
> I have reinstalled fresh 3.1-RELEASE to the machine in question,
> before swapped out two memory DIMM's to the single new 32MB one, just
> to be sure it's not some kind of memory error.
This is definitely not a memory error. I
:: mount /cdrom
:: find /cdrom -type f -exec cat \{\} >/dev/null \; -ls
::
::and pop it goes. Same stack trace. We could do a try-this-game this weekend
(up to
::then I'm covered in work) if that would be helpfull.
::
::Let me know what information you need.
::
::Nick
:
:Doesn't hap
On Wed, 17 Mar 1999, S?ren Schmidt wrote:
> It seems Robert Nordier wrote:
> > OK, I'll add it to the bootblocks.
> >
> > Incidentally, while I'm in there and thinking about it, I'd quite
> > like to fix the boot code to boot from LS-120 drives at the same
> > time. So if anyone has one of these
:On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote:
:> A.. And if you make those AMD mounts normal nfs mounts it doesn't
:> fry? If so, then we have a bug in AMD somewhere.
:
:I tried the cp several times again on a regular NFS mount, to make
:sure, and no, it doesn't se
Ollivier Robert wrote...
> According to David E . O'Brien:
> > If not, can we PLEASE rename SCSI disks back to ``sd''?
>
> I'm tempted to agree. Many people I know who are upgrading to 3.* are
> somewhat pissed off by the renaming, even if it is in the release
> notes. They don't see any good reas
:The fault seems to be reproducable.
:
: mount /cdrom
: find /cdrom -type f -exec cat \{\} >/dev/null \; -ls
:
:and pop it goes. Same stack trace. We could do a try-this-game this weekend
(up to
:then I'm covered in work) if that would be helpfull.
:
:Let me know what information you n
On Wed, 17 Mar 1999, James Wyatt wrote:
> Now a small amount of anything multiplied by a large number can amount to
> something. If you have a small root, I can see where you could overwhelm
> it. It will also take longer and longer to ann the links and lookups in
> /tmp will take forever.
On an
According to David E . O'Brien:
> If not, can we PLEASE rename SCSI disks back to ``sd''?
I'm tempted to agree. Many people I know who are upgrading to 3.* are
somewhat pissed off by the renaming, even if it is in the release
notes. They don't see any good reason for it...
--
Ollivier ROBERT -=-
According to Mikhail A. Sokolov:
> nope
>
> /dev/da1e17235735 7414244 844263347%/mnt/arc
> /dev/da2e 8617355 1724705 689265020%/mnt/spool1
> /dev/da3e 8617355 1723638 689371720%/mnt/spool2
disklabel output is what you want to send
On Wed, 17 Mar 1999, Jon Hamilton wrote:
:Under HP-UX 9.x, the behavior you describe was the default, and it
:was changable by altering a kernel config parameter and relinking the
:kernel. The same tunable is available under 10.x, but I'm less certain
:what the default behavior is there. Whether
On Wednesday, 17 March 1999 at 14:21:07 +0200, Vallo Kallaste wrote:
> Newfs -n1 -d0 -v /dev/vinum/rsvol two lines newfs output and
> crash:
>
> Script started on Wed Mar 17 13:24:45 1999
> sh-2.02# gdb -k kernel.gdb vmcore.0
> GDB is free software and you are welcome to distribute copies of
At 6:00 am -0700 17/3/99, freebsd-errata-upd...@roguetrader.com wrote:
>**
>** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE **
>**
>[etc]
Er, why is this se
I am running:
FreeBSD argus 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Sun Mar 14 18:20:15 CST 1999
jbry...@argus:/usr/src/sys/compile/ARGUS i386
I popped in a 60m tape and did an mt erase. After a couple of
minutes, I had a spontaneous reboot. I also noticed that things had
really slowed down
> No, that was not the justification for the name change. The
> justification (Justinfication?) was that in SCSI terminology, these
> things -- not all of which are disks -- are called ``direct access''
> devices. Similarly, `sa' is ``sequential access''.
Then why do we still have ``cd''? Isn
Daniel C. Sobral wrote:
> "Søren Schmidt" wrote:
> > > I know you most certainly could not possibly have forgotten that,
> > > but it's the kind of thing that just *must* be mentioned...
> > > /etc/fstab?
> >
> > Nope thats not it, been there too :)
>
> Ok, I have a clue... bootdev can be diff
It seems David O'Brien wrote:
> > >People are asking for:
> > >
> > >wd0, ...
> > >da0, ...
> > >
> > >Ie, join ad and da namespaces.
> >
> > If you want to join anything, go directly to "disk%d" instead.
>
> But that is not the "deal" that was presented to us when we had to endure
> the gratuito
< said:
> But that is not the "deal" that was presented to us when we had to endure
> the gratuitous sd->da name change. The whole justification was a single
> device name for disks (and what ever else is direct access).
No, that was not the justification for the name change. The
justification
On Wed, 17 Mar 1999, Ladavac Marino wrote:
> chown root:wheel big_file
AFAIK, only root can 'give ownership away' on most modern Unix'.
Later,
-Mike
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the bod
In message <19990317113918.b39...@relay.nuxi.com>, "David O'Brien" writes:
>> >People are asking for:
>> >
>> >wd0, ...
>> >da0, ...
>> >
>> >Ie, join ad and da namespaces.
>>
>> If you want to join anything, go directly to "disk%d" instead.
>
>But that is not the "deal" that was presented to us w
> >People are asking for:
> >
> >wd0, ...
> >da0, ...
> >
> >Ie, join ad and da namespaces.
>
> If you want to join anything, go directly to "disk%d" instead.
But that is not the "deal" that was presented to us when we had to endure
the gratuitous sd->da name change. The whole justification was
"Søren Schmidt" wrote:
>
> It seems Daniel C. Sobral wrote:
> > "Søren Schmidt" wrote:
> > >
> > > Well, that breaks somewhere else, as the mount code is clever enough
> > > to look at the name of the driver in this case "ad" which doesn't
> > > match the specified #0 ie "wd".
> > > I kindof tri
> We all know that there are oodles of security problems associated with
> file giveaways. As I recall, all the texts I have ever read on the subject
> say that unless there is a very good reason to allow giveaways, they
> should be disabled.
You can play games with quotas anyway, because you are
It seems Daniel C. Sobral wrote:
> "Søren Schmidt" wrote:
> >
> > Well, that breaks somewhere else, as the mount code is clever enough
> > to look at the name of the driver in this case "ad" which doesn't
> > match the specified #0 ie "wd".
> > I kindof tried this by having my driver put itself i
In message <36eff0f0.9c57e...@newsguy.com>, "Daniel C. Sobral" writes:
>Poul-Henning Kamp wrote:
>>
>> I think you are missing the point. We will not chuck the old
>> wd* driver until people have crashed all MFM, RLL, ESDI and !ATA
>> IDE drives.
>>
>> So we WANT to be able to tell the differenc
sth...@nethelp.no wrote:
>
Amen.
> >
> > Does this mean ata disks won't come under CAM/da ?
> > If not, can we PLEASE rename SCSI disks back to ``sd''?
>
> Agreed. I see no justification for the sd -> da change if
> the ATA disks won't (eventually) be included.
To Unsubscribe: send mail to
Andrzej Bialecki wrote:
> On Wed, 17 Mar 1999, Robert Nordier wrote:
>
> > Incidentally, while I'm in there and thinking about it, I'd quite
> > like to fix the boot code to boot from LS-120 drives at the same
> > time. So if anyone has one of these, and wouldn't mind spending
> > some time runni
Poul-Henning Kamp wrote:
>
> I think you are missing the point. We will not chuck the old
> wd* driver until people have crashed all MFM, RLL, ESDI and !ATA
> IDE drives.
>
> So we WANT to be able to tell the difference...
The point here is just naming. Right now, we have:
wd0, ...
ad0, ...
da
"Søren Schmidt" wrote:
>
> Well, that breaks somewhere else, as the mount code is clever enough
> to look at the name of the driver in this case "ad" which doesn't
> match the specified #0 ie "wd".
> I kindof tried this by having my driver put itself in both the
> wd & ad majors in the table, but
Jay Tribick wrote:
>
> > There is a way to overflow / filesystem even is quota is enabled.
> >
> > Just make many hard links (for example /bin/sh) to /tmp/
> >
> > for ($q=0;$q<10;$q++){
> > system ("ln /bin/sh /tmp/ln$q");
> > }
> >
> > Because /tmp directory usually owned by root that why qu
Dmitry Valdov wrote:
>
> Hi!
>
> I think that there is only one way to fix it - it's to disable making
> *hard*links to directory with mode 1777.
*IF* you are using quotas.
Otherwise, it could break things for people.
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@fre
On Wed, 17 Mar 1999, Robert Nordier wrote:
> Incidentally, while I'm in there and thinking about it, I'd quite
> like to fix the boot code to boot from LS-120 drives at the same
> time. So if anyone has one of these, and wouldn't mind spending
> some time running a few bits of test code, I'd appr
On Wed, 17 Mar 1999, Dmitry Valdov wrote:
> I think that there is only one way to fix it - it's to disable making
> *hard*links to directory with mode 1777.
I'm wondering: are you concerned this is possible, or that you really have
a user doing it? I have kicked users off the system for less when
On Wed, 17 Mar 1999, Fernando Schapachnik wrote:
> Are you aware that, due to nature of hardlinks the only extra space is
> same that for an empty file? Due to this, how many empty files do you
> think it takes to eat the whole space of / ?
They take *less* space than an empty file, just the direc
> > Incidentally, while I'm in there and thinking about it, I'd quite
> > like to fix the boot code to boot from LS-120 drives at the same
> > time. So if anyone has one of these, and wouldn't mind spending
> > some time running a few bits of test code, I'd appreciate it.
>
> I have a ZIP if that
nope
/dev/da1e 17235735 7414244 844263347%/mnt/arc
/dev/da2e 8617355 1724705 689265020%/mnt/spool1
/dev/da3e 8617355 1723638 689371720%/mnt/spool2
On Wed, Mar 17, 1999 at 08:29:54AM -0800, Matthew Dill
:
:I.e. I could've agreed with that this could be really doomed directory, but
no,
:it's not that way, squid's allocating objects in memory, when it reaches the
:limit it'd swap it to the spool (as per LRU and such rules) and then, after
:it dies, I find that ~1 recursive swap file (2 disksx9gb,
Dmitry Valdov wrote:
> There is a way to overflow / filesystem even is quota is enabled.
>
> Just make many hard links (for example /bin/sh) to /tmp/
>
> for ($q=0;$q<10;$q++){
> system ("ln /bin/sh /tmp/ln$q");
> }
>
> Because /tmp directory usually owned by root that why quotas has no effe
On Wed, 17 Mar 1999, Jon Hamilton wrote:
> } touch big_file
> } chmod 777 big_file
> } chown root:wheel big_file
> } cat /dev/zero >>big_file
> } This joke used to work on HPUX 10.something which kept the
> } owner-may-chown semantics even in presence of quotas. It was not fun
In message <97a8ca5bf490d211a94ff6c2e55d097...@s-lmh-wi-900.corpnet.at>, La
davac Marino wrote:
} BTW, has chown been "fixed" to the ludicrous SysV semantics that
} the root and owner can chown a file? If so, the latter has to be
} disabled in presence of quotas on the volume--otherwis
I think you are missing the point. We will not chuck the old
wd* driver until people have crashed all MFM, RLL, ESDI and !ATA
IDE drives.
So we WANT to be able to tell the difference...
Poul-Henning
In message , Matthew Jacob w
rites:
>
>I asked Soren just this kind of question, and he declin
On Wed, 17 Mar 1999, Ladavac Marino wrote:
> Date: Wed, 17 Mar 1999 14:37:32 +0100
> From: Ladavac Marino
> To: 'Dmitry Valdov' , freebsd-current@freebsd.org,
> freebsd-secur...@freebsd.org
> Subject: RE: disk quota overriding
>
> > -Original Message-
> > From: Dmitry Valdov
=I think that there is only one way to fix it - it's to disable making
=*hard*links to directory with mode 1777.
Would not it be easier and more practical to make those directories belong
to, say, nobody? And make sure nobody's quota is small enough?
=> Because /tmp directory usually owned by roo
> -Original Message-
> From: Dmitry Valdov [SMTP:d...@dv.ru]
> Sent: Wednesday, March 17, 1999 1:37 PM
> To: freebsd-current@freebsd.org; freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Hi!
>
>
> I think that there is only one way to fix it - it's to disable
It seems Robert Nordier wrote:
> OK, I'll add it to the bootblocks.
>
> Incidentally, while I'm in there and thinking about it, I'd quite
> like to fix the boot code to boot from LS-120 drives at the same
> time. So if anyone has one of these, and wouldn't mind spending
> some time running a few
It seems Matthew Jacob wrote:
>
> I asked Soren just this kind of question, and he declined to answer. I
> doan geddit...
WHAT ??
I replied with this:
#From sos Wed Mar 17 08:51:14 1999
#Subject: Re: How to add a new bootdevice to the new boot code ???
#In-Reply-To: from Matthew
Jacob at "Mar
**
** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.1-RELEASE **
**
You can retrieve the complete ERRATA from:
ftp://ftp.freebsd.org/pub/FreeBSD/3.1-RELEASE/ERRA
> > I assume at some stage that some stage the new driver will take over
> > completely, and the older driver will disappear. Before that, as
> > people grow accustomed to thinking "ad" rather than "wd", it will
>
> Not likely, as long as we need support for MFM/RLL/ESDI disk, wd.c
> will stay ar
I asked Soren just this kind of question, and he declined to answer. I
doan geddit...
On Wed, 17 Mar 1999, David O'Brien wrote:
> > Boot from an ata disk on major# 30, device name "ad", plain and simple.
>
> Does this mean ata disks won't come under CAM/da ?
> If not, can we PLEASE rename SCSI
I don't know what frames 10-12 are supposed to be, but I can give you the short
answer on why it crashed: you have INVARIANTS on (good!), so free()ing stuffs
memory with 0xdeadc0de. Whatever frame 10 was doing tried to dereference
previously freed memory.
Brian Feldman
Hi!
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
On Wed, 17 Mar 1999, Dmitry Valdov wrote:
> Date: Wed, 17 Mar 1999 14:42:46 +0300 (MSK)
> From: Dmitry Valdov
> To: freebsd-current@freebsd.org, freebsd-secur...@freebsd.org
> Sub
On Wed, Mar 17, 1999 at 12:54:40PM +1030, Greg Lehey wrote:
# On Tuesday, 16 March 1999 at 22:41:22 +0300, Mikhail A. Sokolov wrote:
# > Hello,
# > the box is the same as in previous mail of mine which described ufs_dirbad()
# > panics on 4.0-C. Panics are reproducable (run squid 2.1-pl2 with some
Hello !
Before of all I want to make sure that you understand the conditions
here:
I have reinstalled fresh 3.1-RELEASE to the machine in question,
before swapped out two memory DIMM's to the single new 32MB one, just
to be sure it's not some kind of memory error. Installation went
fine, the
On Wed, Mar 17, 1999 at 12:51:12PM +1030, Greg Lehey wrote:
# On Tuesday, 16 March 1999 at 22:36:38 +0300, Mikhail A. Sokolov wrote:
# > Hello,
# >
# > we're experiencing repeated 4.0-C (as of today, something around 12:00
# > GMT, 1999-03-16) ufs_dirbad() panics, which are the
# > following (belo
> > Boot from an ata disk on major# 30, device name "ad", plain and simple.
>
> Does this mean ata disks won't come under CAM/da ?
> If not, can we PLEASE rename SCSI disks back to ``sd''?
Agreed. I see no justification for the sd -> da change if the ATA disks
won't (eventually) be included.
Ste
It seems David O'Brien wrote:
> > Boot from an ata disk on major# 30, device name "ad", plain and simple.
>
> Does this mean ata disks won't come under CAM/da ?
Not if I can help it :)
It could be done by slamming a translation layer ontop of the existing
wd driver or of cause on top of the new I
On Wed, 17 Mar 1999, Fernando Schapachnik wrote:
> Date: Wed, 17 Mar 1999 08:50:50 -0300 (GMT)
> From: Fernando Schapachnik
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Are you aware that, due to nature of hardlin
On Wed, 17 Mar 1999, Jay Tribick wrote:
> Date: Wed, 17 Mar 1999 11:49:32 +
> From: Jay Tribick
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Hi
>
> > There is a way to overflow / filesystem even is quota is e
Are you aware that, due to nature of hardlinks the only extra space is
same that for an empty file? Due to this, how many empty files do you
think it takes to eat the whole space of / ?
I'm I loosing something?
Regards.
En un mensaje anterior, Dmitry Valdov escribió:
> Hi!
>
> There is a way
Hi
> There is a way to overflow / filesystem even is quota is enabled.
>
> Just make many hard links (for example /bin/sh) to /tmp/
>
> for ($q=0;$q<10;$q++){
> system ("ln /bin/sh /tmp/ln$q");
> }
>
> Because /tmp directory usually owned by root that why quotas has no effect.
> *Directory*
Hi!
There is a way to overflow / filesystem even is quota is enabled.
Just make many hard links (for example /bin/sh) to /tmp/
for ($q=0;$q<10;$q++){
system ("ln /bin/sh /tmp/ln$q");
}
Because /tmp directory usually owned by root that why quotas has no effect.
*Directory* size of /tmp can b
> Boot from an ata disk on major# 30, device name "ad", plain and simple.
Does this mean ata disks won't come under CAM/da ?
If not, can we PLEASE rename SCSI disks back to ``sd''?
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
wi
It seems Robert Nordier wrote:
> Søren Schmidt wrote:
>
> > OK, easy enough, this is what I want to do:
> >
> > Boot from an ata disk on major# 30, device name "ad", plain and simple.
>
> I'd be inclined to handle this outside the boot code, by treating the
> passed in major# as describing the
Søren Schmidt wrote:
> OK, easy enough, this is what I want to do:
>
> Boot from an ata disk on major# 30, device name "ad", plain and simple.
I'd be inclined to handle this outside the boot code, by treating the
passed in major# as describing the device rather than specifying
the driver.
The
The fault seems to be reproducable.
mount /cdrom
find /cdrom -type f -exec cat \{\} >/dev/null \; -ls
and pop it goes. Same stack trace. We could do a try-this-game this weekend (up
to
then I'm covered in work) if that would be helpfull.
Let me know what information you need.
"Søren Schmidt" wrote:
>
> So here I am with our new boot code and a new device, how the
> @Â$ am I supposed to boot from that with the glory new
> boot blocks, forth and what have we ???
The glory new boot blocks rely on the good old BIOS to boot.
Anything else is a chicken&egg problem.
--
Da
It seems Robert Nordier wrote:
> If the problem is the bootblocks, why not send a message to Robert
> Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And
> say, "This is what I want to do, what are we going to do about it?"
> or something similar?
OK, easy enough, this is what I want
69 matches
Mail list logo
