In message , Garance A Drosihn writes:
>I also have a partition with freebsd-current from two or three days
>ago, and all the latest versions of the ports. Every time I try to
>start vmware2 on the newer system, the hardware dies. Sometimes it
>automaticall
> I have found that if you create a jail in FreeBSD 4.6.2, and then log into
> that jail ... if you are root you can scp and ssh just fine. However if you
> are not root and you attempt to ssh or scp, you get this error:
>
> PRNG is not seeded
Hmmm.
> A few details - first, I created my jail
On Thu, Oct 03, 2002 at 09:04:04AM +0100, Ian Dowse wrote:
> See the patch I posted in:
>
>
>http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=0+6285+/usr/local/www/db/text/2002/freebsd-emulation/20020908.freebsd-emulation
>
> There may still be further issues, but it allowed me to use vmware2
In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
>On Thu, Oct 03, 2002 at 09:04:04AM +0100, Ian Dowse wrote:
>> There may still be further issues, but it allowed me to use vmware2
>> on a current from a week or two ago.
>
>That's only for virtual disks, and that is not where the problem is (
On Thu, 3 Oct 2002, Mark Santcroos wrote:
> I have an almost-ready patch that implements linux_read() syscall. This
> will check if we are reading from a raw disk and in that case it will
> enlarge the read() to the next sector boundary. I have it working in the
> kernel but I have problems retur
On Thu, Oct 03, 2002 at 09:50:45PM +1000, Bruce Evans wrote:
> Unbreaking block devices would be a better solution. Without buffering,
> reads of raw disks using an unbuffered linux_read() might be
> times slower than they should be.
You are right. The quick and dirty hack I had in mind was les
In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
>On Thu, Oct 03, 2002 at 09:50:45PM +1000, Bruce Evans wrote:
>> Unbreaking block devices would be a better solution. Without buffering,
>> reads of raw disks using an unbuffered linux_read() might be
>> times slower than they should be.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello freebsd-hackers,
Recently i spent almost two hours trying to find error in my
several shell and perl sripts. These scripts are to process
large list of ip addresses stored in text file and do some
stuff with boxes with given addresses on my
A company I am working fo has a problem with a FreeBSD-based 19" NFS
server called MaxAttach 4000.
We need to fiddle with their apparently home-grown striping/mirroring
system and I would like to talk to somebody who knows something about
this.
Thanks
Martin
To Unsubscribe: send mail t
On Thu, 3 Oct 2002, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Mark Santcroos writes:
> >On Thu, Oct 03, 2002 at 09:50:45PM +1000, Bruce Evans wrote:
> >> Unbreaking block devices would be a better solution. Without buffering,
> >>...
> >What was the reason for the removal of blo
In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>> If a buffered access-mode on block devices is desired, it should
>> be implemented either as an ioctl controllable feature, or as
>> a GEOM module. The latter is probably by far the easiest way.
>
>It was desired, and was sort of promised.
Ian Dowse wrote:
>
> In message , Garance A Drosihn writes:
> >I also have a partition with freebsd-current from two or three days
> >ago, and all the latest versions of the ports. Every time I try to
> >start vmware2 on the newer system, the hardware dies.
> It was desired, and was sort of promised.
I never understood why removal of block devices was allowed
in the first place. phk's reasons don't seem strong enough
to any unix wizard I have talked to. Did the majority of the
core really think the change was warranted? Removing
compatibility whe
At 10:11 AM +0200 10/3/02, Mark Santcroos wrote:
>On Thu, Oct 03, 2002 at 09:04:04AM +0100, Ian Dowse wrote:
>> See the patch I posted in:
>>
>>
>>
>http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=0+6285+/usr/local/www/db/text/2002/freebsd-emulation/20020908.freebsd-emulation
>>
>> There may
On Thu, Oct 03, 2002 at 09:37:07AM -0700, Bakul Shah wrote:
>
> Is there a write up somewhere on what GEOM is and its
> benefits? I'd hate to see it become the default without
> understanding it (and no, reading source code doesn't do it).
>
Bakul,
there's been ample discussion of what GEOM i
In message <[EMAIL PROTECTED]>, Bakul Shah writes:
>I never understood why removal of block devices was allowed
>in the first place.
You are welcome to peruse the mail-archives to find out such
historically interesting decisions.
You are not welcome to build another bikeshed over it.
>How hard
Ok, here you are - as a normal user (non root) inside the jail, I have run:
$ dd if=/dev/random of=/dev/stdout bs=512 count=1 | hexdump -C
dd: /dev/stdout: Permission denied
$ ls -asl /dev/stdout
0 crw--- 1 root wheel 22, 1 Sep 3 21:46 /dev/stdout
All of this was _after_ I ran the `
If you run a jail, and inside that jail is a /dev with the file /dev/null in
it, the normal 0666 permissions of /dev/null will often get changed to 0600.
I cannot see any reason why this would happen - I thought maybe there was
something in /etc/rc that would do it, but there is not. Further,
Hi,
I've experimented this when I've rebuilt my world just after the announce of
4.7-RC. mergemaster asked me if I wanted to run MAKEDEV since it had changed.
I think it's this which broke up /dev/null, then i re-runed sh ./MAKEDEV and
everything was fine :)
I don't know if my second run of MAKE
July - August 2002 Status Report
Introduction
Throughout July and August, the FreeBSD Project has been working on
pulling together the last few major pieces of new functionality for
FreeBSD 5.0-RELEASE. At this point, the releas
On Thu, 3 Oct 2002, Bakul Shah wrote:
> > It was desired, and was sort of promised.
>
> I never understood why removal of block devices was allowed
> in the first place. phk's reasons don't seem strong enough
> to any unix wizard I have talked to. Did the majority of the
> core really think
I'd like to acknowledge the help of Scott Long in getting the report out
this month--he did all that hard work :-).
The next status report will cover September-October, 2002, and reports
will be due around November 15. Depending on the 5.0 release process, we
might slip it slightly. :-)
Robe
Hi
You only sent me a third of what I asked for :-)
M
>
> Ok, here you are - as a normal user (non root) inside the jail, I have run:
>
> $ dd if=/dev/random of=/dev/stdout bs=512 count=1 | hexdump -C
> dd: /dev/stdout: Permission denied
>
> $ ls -asl /dev/stdout
> 0 crw--- 1 root whe
On Thu, Oct 03, 2002 at 04:00:26PM +0300, Artem Okounev wrote:
> To my great surprise I found out that:
> ping 192.168.0.26,
> ping 192.168.0.032,
> and even ping 192.168.0.0x1a - all correct commands doing
> the same thing: pinging 192.168.0.26.
Yep.
> That was my problem. IP addresses was sto
On 2002-10-03 15:38 -0400, Robert Watson <[EMAIL PROTECTED]> wrote:
>
> July - August 2002 Status Report
>
> --
>
> FreeBSD Security Officer Team
>
>URL: http://www.freebsd.org/security/
>
>
Well, what I am seeing is the /dev/null changing permissions _after_ the
build/installation of the jail.
That is, either it is changing at some random time while the jail is
running, or it changes after the jail is stopped, then started again.
And it happens over and over, that is, if I reset
Sorry, here is the rest:
Here is the output of the `dd` command using urandom:
dd if=/dev/urandom of=/dev/stdout bs=512 count=1 | hexdump -C
1+0 records in
1+0 records out
a0 69 1a 7c 8f 32 e5 21 ae 7a 33 14 68 0b 8e a6
|.i.|.2.!.z3.h...|
512 bytes transferred in 0.000472 secs (10
> Sorry, here is the rest:
>
> Here is the output of the `dd` command using urandom:
>
> dd if=/dev/urandom of=/dev/stdout bs=512 count=1 | hexdump -C
> 1+0 records in
> 1+0 records out
> a0 69 1a 7c 8f 32 e5 21 ae 7a 33 14 68 0b 8e a6
> |.i.|.2.!.z3.h...|
... etc. Looking good.
>
I can't seed it by banging on the keyboard - it is a headless server in a
rack thousands of miles from me :)
Perhaps there is another way to do it ?
>Date: Thu, 03 Oct 2002 21:54:30 +0100
>
> > Sorry, here is the rest:
> >
> > Here is the output of the `dd` command using urandom:
> >
> > dd i
On Mon, 30 Sep 2002, Sean Farley wrote:
> On Thu, 26 Sep 2002 21:14, Mike Silbersack wrote:
>
> > Rumor has it that newer drives cannot write a single sector at a time,
> > and instead must read a whole cluster of sectors, add in the new
> > sector, and write back the whole cluster. That behavi
> I can't seed it by banging on the keyboard - it is a headless server in a
> rack thousands of miles from me :)
>
> Perhaps there is another way to do it ?
Yes.
You need to find sources of entropy in interrupts. Look at a
dmesg, and note which IRQ's your network device(s) and mass
storage con
Ok, I am not sure how I can do that though - I cannot successfully run
`rndcontrol -s X` inside a jail.
On the other hand, I already have:
rand_irqs="9 10 11 13 14"
In my rc.conf on the underlying host machine, and have done several boots
with that in place. So presumably I should be seeded
On Thu, Oct 03, 2002 at 05:57:56PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Bruce Evans writes:
>
> >> If a buffered access-mode on block devices is desired, it should
> >> be implemented either as an ioctl controllable feature, or as
> >> a GEOM module. The latter is pr
On Fri, Oct 04, 2002 at 12:53:52AM +0200, Mark Santcroos wrote:
>
> So 'ignoring' the historic facts, and assuming that we just want block
> devices, we can do such a thing in GEOM in the future?
>
> Is this something you will be doing yourself Poul, or is it just that you
> are saying that it i
__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In a message written on Thu, Oct 03, 2002 at 12:55:15PM -0700, Crist J. Clark wrote:
> This is a feature not a bug since it is documented in inet_aton(3),
>
> All numbers supplied as ``parts'' in a `.' notation may be decimal,
> octal, or hexadecimal, as specified in the C language (i.e
On Fri, 2002-10-04 at 11:08, Leo Bicknell wrote:
> 0xff00 was hex,
> 0123456701234567 was octal,
> 010.010.010.010 was 4 decimal parts
>
> I was very surprised from the poster that 192.168.0.010 might actually
> be 192.168.0.8.
I would imagine this behaviour is like it is because that
In a message written on Fri, Oct 04, 2002 at 11:19:16AM +0930, Daniel O'Connor wrote:
> I would imagine this behaviour is like it is because that is how atoi
> and friends work..
Absolutely. I think this is the unintended consequence sort of
bug, not the programmer goofed sort of bug. :) I'd de
On Thu, 3 Oct 2002, Leo Bicknell wrote:
>In a message written on Thu, Oct 03, 2002 at 12:55:15PM -0700, Crist J. Clark wrote:
>> This is a feature not a bug since it is documented in inet_aton(3),
>>
>> All numbers supplied as ``parts'' in a `.' notation may be decimal,
>> octal, or hexa
I use jails intensively, but never give a possibility
for that type of changes.
2 ways:
- chflags schg /path/to/jail/dev/*
- mount -r /reduced_set_of_dev /path/to/jail/dev
first for full featured jails and second for
light weight jails.
(actually I always mount dev in jail directory
because of
phk writes:
> You are welcome to peruse the mail-archives to find out such
> historically interesting decisions.
I am aware of the technical arguments discussed via -arch,
-current & -hackers. I just don't agree with them (seems
like most hackers who are afraid to cross you).
> You are not welc
unsubscribe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
42 matches
Mail list logo