headers
soralx | 1 Nov 2006 04:21

Re: [patch] rm can have undesired side-effects


> Having cleared my head a bit more, I realise most of
> this can be done with consecutive runs of 'dd'.
> I think I've reached a conclusion here.

that is, install "ports/sysutils/obliterate/"?

> Tim.

[SorAlx]  ridin' VN1500-B2
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Mohacsi Janos | 2 Nov 2006 09:53
Picon
Favicon

Re: sockstat tcp/udp switches

Hi,
 	I haven't tested yet, but I think in the options structure you 
should use :

+                             {"ipv6", 0, NULL, '6'},

instead of:
+                             {"ipv6", 0, NULL, 0},

also for portability you should use:
no_argument or required_argument as a second field....

Regards,
 	Janos Mohacsi

On Tue, 31 Oct 2006, Josh Carroll wrote:

> All,
>
> I have added two options to the sockstat command to list tcp and/or udp 
> sockets.
>
> -t  ([-]-tcp)  :    display tcp sockets
> -d ([-]-udp)  :   display udp sockets
>
> The previous command line options are unchanged, although I did change
> the use of getopt to getopt_long_only and added long options for the
> other command line switches.
>
> I know the same effect can be accomplished with grep, but figured it'd
(Continue reading)

Permalink | Reply | 18 comments |
headers
Julian Stacey | 2 Nov 2006 11:50
Favicon

NFS on 6.1 limits at 4 Gig

NFS fails on files >= 4 Gig	 Can someone confirm please. 

uname -r	# 6.1-RELEASE 	(both hosts)
		# echo "1024 1024 * 4 * 1 + p" | dc	# 4194305	
dd if=/dev/zero of=junk bs=1k count=4194305 
ls -l junk	# 4294968320 bytes
rsh an_nfs_host ls -l /host/`hostname -s`/usr/tmp/junk # 1024 byte size!
				# with count=4194304, ls shows 0 bytes.

It's not AMD failing, but NFS, as with an /etc/amd.map with a
non NFS entry for my host "laps" for efficiency (in case some
shell on host laps mounts itself), the full size 4294968320 is seen.
	/etc/amd.map 
		/defaults       type:=host;fs:=${autodir}/${rhost};rhost:=${key}
		laps            type:=link;fs:=..

It's not just ls, cmp fails too, ( as also does my
	http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/cmpd.c )
cmp -z junk /host/laps/usr/tmp/junk # junk /host/laps/usr/tmp/junk differ: size

Is send-pr appropriate ?

Julian
--

-- 
Julian Stacey.  BSD Unix C Net Consultancy, Munich/Muenchen  http://berklix.com
Mail Ascii, not HTML.		Ihr Rauch = mein allergischer Kopfschmerz.
		http://berklix.org/free-software
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
(Continue reading)

Permalink | Reply | 4 comments |
headers
Jan Grant | 2 Nov 2006 11:52
Picon
Picon
Favicon

Re: [patch] rm can have undesired side-effects

On Tue, 31 Oct 2006, Daniel Valencia wrote:

> if the file is not writable, return with error.
> if the file has multiple links, and option -f was not specified, 
> return with error.
> overwrite the file.
> optionally, unlink the file.
> 
> Additionally, -P should either be rm'ed from rm, or added as a
> backwards compatibility hack that calls "shred" and returns with error 
> every time the latter does.
> 
> These are my 1.99 cents.

You might as well just truncate the file before removing it.

--- Bakul Shah <bakul <at> bitblocks.com> wrote:

> If you are that concious about scrubbing why not add
> scrubbing as a mount option (suggested option: -o paranoid)
> then at least it will be handled consistently.

This is, I reckon, the only sensible suggestion thus far: if the FS 
doesn't help you then you are implicitly depending on the FS 
implementation to ensure you are writing over the original data blocks 
anyway.

--

-- 
jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/
Tel +44 (0)117 3317661   http://ioctl.org/jan/
(Continue reading)

Permalink | Reply | 2 comments |
headers
Maxim A. Zhuravlev | 2 Nov 2006 17:03
Picon
Favicon

[call for comments] l2sched

What is l2sched?
l2sched is a mechanism that allows multiple third-party thread schedulers
collaborate. These schedulers are to be implemented as loadable kernel
modules aka KLD (kernel loadable driver).
l2sched is being designed to to make it possible to provide a complicated
software system with a scheduler meeting the system's requirements. l2sched
is going to increase the portability of a software, dependant on an
OS-specific scheduler's behavior (e.g.. the software, requiring the POSIX
real-time schedulers). Currently the POSIX real-time schedulers are
implemented as a part of the system schedulers. l2sched should let to
implement them independently.
l2schd should provide an scheduling policy-independent interface for the
thread/process-scheduler interaction. The interface is be based on
/usr/src/sys/sys/sched.h. The policy-specific calls like
void sched_prio(struct thread , u_char);
are to be replaced by
void sched_set_param(void*, void*).
l2sched is to give scheduler access to the cpu on a priority-based,
proportional basis (here we come - level 2 scheduling -l2sched). As the
l2sched is being designed for a general-purpose OS FreeBSD, it should
provide an adequate experience. So idle process' schedulers should act only
if no time-sharing threads' schedulers have runnable threads. The latest
should act only when no real-time schedulers are active. A scheduler can
schedule any subset of process types. With two given schedulers, the one
that hosts more threads should be provided with a bigger portion of
processor's time.
The author believes that the performance overhead can be minimized provided
a well-designed internal calls interface.

Any descussion/comments are wellcome.
(Continue reading)

Permalink | Reply | 5 comments |
headers
John Baldwin | 2 Nov 2006 18:02
Picon
Favicon

Re: NFS on 6.1 limits at 4 Gig

On Thursday 02 November 2006 05:50, Julian Stacey wrote:
> NFS fails on files >= 4 Gig	 Can someone confirm please. 
> 
> uname -r	# 6.1-RELEASE 	(both hosts)
> 		# echo "1024 1024 * 4 * 1 + p" | dc	# 4194305	
> dd if=/dev/zero of=junk bs=1k count=4194305 
> ls -l junk	# 4294968320 bytes
> rsh an_nfs_host ls -l /host/`hostname -s`/usr/tmp/junk # 1024 byte size!
> 				# with count=4194304, ls shows 0 bytes.
> 
> It's not AMD failing, but NFS, as with an /etc/amd.map with a
> non NFS entry for my host "laps" for efficiency (in case some
> shell on host laps mounts itself), the full size 4294968320 is seen.
> 	/etc/amd.map 
> 		/defaults       type:=host;fs:=${autodir}/${rhost};rhost:=${key}
> 		laps            type:=link;fs:=..
> 
> It's not just ls, cmp fails too, ( as also does my
> 	http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/cmpd.c )
> cmp -z junk /host/laps/usr/tmp/junk # junk /host/laps/usr/tmp/junk differ: size
> 
> Is send-pr appropriate ?

Are you using NFS v2 or v3?  v2 doesn't support large files.

--

-- 
John Baldwin
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
(Continue reading)

Permalink | Reply | 3 comments |
headers
Daniel Eischen | 2 Nov 2006 18:50
Picon
Favicon

Re: [call for comments] l2sched

On Thu, 2 Nov 2006, Maxim A. Zhuravlev wrote:

> What is l2sched?

Did you forget to post a link to the patches or code?  Or
include an attachment?

--

-- 
DE
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 4 comments |
headers
Maxim A. Zhuravlev | 2 Nov 2006 19:03
Picon
Favicon

Re: [call for comments] l2sched

> Did you forget to post a link to the patches or code?  Or
> include an attachment?

Well, working on them currently. I'd like to get some comments on the 
design.

--

-- 
JID: thIOretic <at> jabber.icn.bmstu.ru

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 3 comments |
headers
Coleman Kane | 2 Nov 2006 19:34
Picon

Re: [call for comments] l2sched

On 11/2/06, Maxim A. Zhuravlev <thIOretic <at> yandex.ru> wrote:
>
> > Did you forget to post a link to the patches or code?  Or
> > include an attachment?
>
>
> Well, working on them currently. I'd like to get some comments on the
> design.
>
> --
> JID: thIOretic <at> jabber.icn.bmstu.ru
>
> _______________________________________________
> freebsd-hackers <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

It sounds interesting. If you have access to publish HTML or PDF somewhere,
that would be appealing. Perhaps you could post a better formatted version
of the previous email up as a wepage somewhere. Optionally, you could post a
blog entry of it and allow for comments...

--
Coleman Kane
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 2 comments |
headers
Maxim A. Zhuravlev | 2 Nov 2006 20:18
Picon
Favicon

Re: [call for comments] l2sched

>Optionally, you could post a
> blog entry of it and allow for comments...
> 

http://mzhuravlev.blogspot.com/

--

-- 
JID: thIOretic <at> jabber.icn.bmstu.ru

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |

Gmane