Re: mount_nfs/df bug?
Alexander Langer <[EMAIL PROTECTED]> writes: > Today I wanted to add a new NFS to my /etc/fstab, but forgot to add it > to /etc/exports on the server. > However, I did mount -a several times and always got a "Permission > denied" for the last one. why there isn't an exportfs command as most unices have ? Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount_nfs/df bug?
David Malone <[EMAIL PROTECTED]> writes: > On Wed, Jun 21, 2000 at 02:35:51AM +0200, Cyrille Lefevre wrote: > > > why there isn't an exportfs command as most unices have ? > > "killall -HUP mountd" or "mount -u /" both work. This is mentioned > in the mountd man page, but should probably also be mentioned in > the exports man page. well, what about exporting a directory w/o exporting a filesystem ? which is usefull somethimes. possible too ? Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel config format migration script
Brian Fundakowski Feldman <[EMAIL PROTECTED]> writes: > I made a sed script to ease migration of kernel configuration files from > the few-weeks-ago-CURRENT to current-CURRENT, and thought I might as well > share it since it makes things easy (autonomous :) > > You can find it at > http://people.freebsd.org/~green/oldconfig2new > It requires extended regular expression support (because old regexps > are so cumbersome to actually _use_), so for example: > mv GREEN GREEN.old > perl gethints.pl GREEN > sed -Ef oldconfig2new GREEN.old > GREEN well, at 4.x, FreeBSD sed doesn't support -E, is that GNU sed which support this option or 5.x FreeBSD sed ? for instance, GNU sed port doesn't exists ! Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel config format migration script
Brian Fundakowski Feldman <[EMAIL PROTECTED]> writes:
> I made a sed script to ease migration of kernel configuration files from
> the few-weeks-ago-CURRENT to current-CURRENT, and thought I might as well
> share it since it makes things easy (autonomous :)
>
> You can find it at
> http://people.freebsd.org/~green/oldconfig2new
> It requires extended regular expression support (because old regexps
> are so cumbersome to actually _use_), so for example:
> mv GREEN GREEN.old
> perl gethints.pl GREEN
> sed -Ef oldconfig2new GREEN.old > GREEN
this one seems to be working w/ a standard sed :
==--== CUT HERE ==--==
#!/usr/bin/sed -f
# since ata[0-9] requires ata alone, delete them.
/^#*[ \t]*device[ \t]\{1,\}ata[0-9]\{1,\}/d
# delete fd[0-9] and fd alone.
/^#*[ \t]*device[ \t]\{1,\}fd[0-9]\{1,\}/d
/^#*[ \t]*device[ \t]\{1,\}fd$/d
# get rid of terminal spaces
s/[ \t]\{1,\}$//
# hints stuffs
/^ident[ \t]\{1,\}/ {
h
s/^ident\([ \t]\{1,\}\)\([a-zA-Z0-9_]\{1,\}\)/hints\1"\2.hints"/
# ^^ I'm not sure about this
# are underscore and digits valid characters here ?
H
x
}
s/^\(#*[ \t]*\)pseudo-device\([ \t]\{1,\}\)/\1device\2/
s/^\(#*[ \t]*\)device\([ \t]\{1,\}\)\([a-zA-Z_]\{1,\}\)\([0-9]\{1,\}\)\([
\t]*\)\([^#]*\)\(.*\)$/\1device\2\3\5\7/
# ^^^ also, here ?
==--== CUT HERE ==--==
\t need to be replaced w/ real tabs (under vi, :%s/\\t//g)
just in case, I put them here to be reliable (and visible :) via email.
Cyrille.
--
home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre.
work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: /etc/rc.shutdown calls local scripts now
Jonathan Smith <[EMAIL PROTECTED]> writes:
> Quickie question:
[snip]
> To my (limited) understanding of this subject, it's not going to make hour
> long boot-ups. It may increase shutdown time to do things, but, sometimes
> you need to properly shut things down. If that were not the case, one
> could flip the power switch instead of typing shutdown..
what about reimplementing a fast{boot|halt} which don't runs thoses scripts
a shutdown and don't runs fsck at bootup ?
Cyrille.
--
home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre.
work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
Paul Herman <[EMAIL PROTECTED]> writes: > On Thu, 6 Jul 2000, Bill Fumerola wrote: > [snip] > Filesystem1K-blocks UsedAvail Capacity Mounted on > /dev/ad0s2a 44650330922 379861 8%/ > /dev/ad0s9e 1453615 758910 57841657%/usr > /dev/ad0s9f 968983 357403 53406240%/usr/local > /dev/ad0s9g 242239 9945 212915 4%/var > /dev/ad0s9h 2013515 1242447 60998767%/u01 > procfs440 100%/proc > Heh? What's this?242239 9945 212915 4%/mnt > total 1581144 505684 99514034%/mnt2 > total 1391380 414168 90652831%/mnt3 > bash-2.03# > > Hee, hee. Yes, this is probably no big deal (and not put forth as any > strong argument for not commiting this) but who knows what some > cronjob scripts might expect. Hmmm, let me give constructive > criticism a shot and see how far it goes: humm! you are looking for a small bug (the beast :) this problem also exists w/ du -c... # cp -rp /etc/defaults total # du -c total 69 total 69 total so, your argumentation isn't "viable" (in french, don't know the translation in english, sorry). if you prefer, say "total:" inseatd of just "total" since it's not possible to remote mount something like this. but what about du -c in this case... > Perhaps if it were expected that the "df -c" output were completly > different? Then "total" would be less likely to be counted as some > other filesystem by mistake? Perhaps something along the lines: > > bash-2.0.3# df -c /usr /usr/local > Totals for: /usr /usr/local > 1K-Blocks:2422598 > Used: 1116313 > Avail:1306285 > Capacity: 46% > > Dunno how that would go over with the purists, though... after all > 'df' is in one of the holiest of directories... /bin. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
Sheldon Hearn <[EMAIL PROTECTED]> writes: > On Tue, 04 Jul 2000 15:47:25 -0400, Will Andrews wrote: > > > On Tue, Jul 04, 2000 at 04:06:46PM +0200, Sheldon Hearn wrote: > > > My only objection is that it seems to produce useless values. Can you > > > think of a use for these grand totals? > > > > They are helpful for monitoring total space; I would use them in > > administrative scripts to watch my space. > > Okay, then. Let me be more specific. How is the notion of "total > space" useful? :-) statistics for backup tapes needed. for instance, at work, there is a big restructuration of departements. so, there are 10 gigs (about 300 GB) to move from servers to others. of course, I use some kind of awk scripts to do the same things. but, under FreeBSD, I saw that du has a -c option to do that job. why df couln't have the same option to do the same job ? for every scripts I write, I do it the more portable as possible I can. but if I can optimize the job, I'll do it. another way to say that is : how is it possible you don't like this option to df for any reason, while you have accepted the same option to du ? Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /sys hierarchy
Warner Losh <[EMAIL PROTECTED]> writes: > In message <[EMAIL PROTECTED]> Robert >Watson writes: > : On Wed, 5 Jul 2000, John Baldwin wrote: > : > : > The headers will always be installed in the right place in > : > /usr/include: Makefile's are editable. As far as kernel > : > compiles, symlinks can be created in the work directory as > : > one possible solution. For example, > : > sys/compile/i386/GENERIC/netinet -> ../../../../net/inet. > : > This would most likely result in netinet _not_ being split > : > up. > : > : As much as I'd love a complete cleanup of sys/, this cure seems to be > : worse than the problem. :-) Take this as another vote to leave net/ as > : is, if only to keep the includes in kernel code in sync with includes in > : userland code :-). > > The proposed change also breaks the ability to have /usr/include/* be > symbolic links to your real source tree. I don't understand where is the problem to split net* to net/* ? could you explain ? please. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "no-spam." pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "no-spam." to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d & things...
Mike Meyer <[EMAIL PROTECTED]> writes: > > By all means, use start/stop args, but hard link the .sh files into seperate > > directories or something so that the order can be tweaked.. > > If all you want is to make sure that shutdown happens in the reverse > order of startup, that can be done by reversing the list in > rc.shutdown. But how about going a step further, and starting towards > a user-friendly configuration process? > > Instead of being globbed at init time, etc/rc.d is a repository for > things that take start/stop arguments. They are symlinked to > /etc/init.d with numeric prefixes to control order at initialization > time. Likewise, they can be symlinked to /etc/down.d (or shutdown.d) > with numeric prefixes to control order at shutdown time. > > Note that the directories full of symlinks are in /etc, not in > /usr/X11R6/etc, etc. The rc.d's in those are also treated as > repositories, so you can symlink to files in those asd well. These > should save a bit of time at boot; no need to fool with lists of > directories, etc. - just one directory. > > The real work will be adding a one-line description near the start of > the file: > > # Init: 300. Shutdown: -1. Description: Standard smtp (mail) daemon. > > (indicating that it should be installed as /etc/init.d/300sendmail.sh, > and no shutdown installation is necessary). I guess you would like to says that scripts.sh lives in /etc/init.d while XXXscripts.sh lives in /etc/rc.d and /etc/shutdown.d. if not, you are at the oposite of the SystemV semantic ! and would be a pain for system administrators. why not to simply adopt the SystemV semantic ? not all is bad in System V :) > Later, we can add a tool that globs the etc/rc.d directories for files > with those lines, and provides a nice visual "system process > configuration" tool, allowing you to click on these things to move > them back and forth. Some rules regarding the shutdown/startup > priorites might be needed for ports. Given some prodding, I might even > be talked into taking a crack at the tool (an X tool, maybe) before > there's a commitment to supporting this structure. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d & things...
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes: > Mike Meyer wrote: > > > > Yes, that's correct. And yes, not all is bad in SysV. In particular, > > having a directory where you can find scripts to stop (and restart) > > subsystems is very nice. I think the multiple levels (rc?.d) is a bit > > of overkill. Either the system is up (meaning everything is turned > > on), or it's down, and the sysadmin who brought it down can start the > > subsystems s/he needs. Having a single init.d to look in for those > > things helps in that process. > > The multiple levels are there to deal with changes in state. In BSD, for > instance, we have single user/multi-user. A number of other variations > can exist, both in heavy duty servers where you might want to bring > certain services down for upgrade and then back up, and "desktop" > machines, such as notebooks where you can be stand-alone, docked into > different networks (eg. home/work). > > Thing is, SysV does it in a very ugly way, and not flexible enough > either. > > This has been talked to death. Look at these: > > http://www.freebsd.org/~dfr/devices.html off topic. > http://www.freebsd.org/~eivind/newrc.html well. what about a mix of the SystemV approach (ala HP-UX) and the IRIX one (using something like chconfig). HP-UX : /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not enough possible choises, such as status, restart, config, command, etc.) /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script linked to /sbin/init.d/script /sbin/rc (+ /sbin/rc.util) sources /etc/rc.config then runs /sbin/rc?.d startup files /etc/rc.config.d/services are configuration files (ala bourne shell). /sbin/rc.config sources /etc/rc.config.d configuration files. /usr/sbin/ch_rc is not so easy to use to modify /etc/rc.config.d/services. IRIX : oops, don't remember how works startup scripts. I just remember me configurations files : /sbin/chconfig [on|off] service or something like that. (don't remember if it's possible to change options through chconfig, but I guess no). /etc/config/services enable or disable services. /etc/config/services.options just contains arguments to services. so, a mix of both w/o the levels stuffs + a /etc/rc.default.d (a synonym to /etc/defaults/rc.conf but in separate files between HP-UX and IRIX configuration files) would be a begining. please, don't do something like AIX :) they use a binary database to stock there things... > and my favorite substitute proposal: > > http://www.roguetrader.com/~brandon/sas/. effectively, the last one is interresting. a major problem w/ this one is the use of "perl" which is not available a boot time since it is located in /usr. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d & things...
Andrzej Bialecki <[EMAIL PROTECTED]> writes: > On 10 Jul 2000, Cyrille Lefevre wrote: > > > > and my favorite substitute proposal: > > > > > > http://www.roguetrader.com/~brandon/sas/. > > > > effectively, the last one is interresting. a major problem w/ this one is the > > use of "perl" which is not available a boot time since it is located in /usr. > > If we find out that it's very interesting, it should be implemented as > part of init(8). (hint: init is NOT Perl based ;-) sould be a too big job for init ? mush better to be an external program a la /etc/rc, no ? Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d & things...
"Daniel C. Sobral" <[EMAIL PROTECTED]> writes: > Cyrille Lefevre wrote: > > > > HP-UX : > > > > /sbin/init.d/script start_msg|stop_msg|start|stop (FMPOV, there isn't not > > enough possible choises, such as status, restart, config, command, etc.) > > /sbin/rc[S0-5].d/[SK][0-9][0-9][0-9]script linked to /sbin/init.d/script > ^^ > This is confusing and difficult ot manage. I'm just explaining HP-UX and IRIX implementations for someone who don't know them. > > /sbin/rc (+ /sbin/rc.util) sources /etc/rc.config then runs /sbin/rc?.d > > startup files > > /etc/rc.config.d/services are configuration files (ala bourne shell). > > Non-centralized configuration is frowned upon. Having to find which file > has something, or having to read through multiple files to understand > how the system is configured is a disadvantage wrt to the present > system. not so difficult if a command do that for you. (show, change, start and stop) Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: APM and SCSI : suspend
Cyrille Lefevre <[EMAIL PROTECTED]> writes: > why it's not possible to suspend SCSI drives like the ATA/IDE ones ? > > I'm not talking about camcontrol suspend feature. if you have a mounted > filesystem, and access a file onto that filesystem while the drive is > suspended in this manner, the system gives up. and it is not so good > (at all :) to do the same thing if you have some swap space onto that > drive, crash... > > also, I experienced suspended SCSI drives under windows, then warm boot. > the boot loader is not able to wake up the drives. so it complains about > drive not found and you have to power off/on your machine to wake up the > drives. > > is that feature, suspend/wake up of SCSI drives, programmed in the future ? > > PS : maybe -arch should be in this thread ? from -fs and -hackers w/ no answers ? so, I try -current. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Request for comments: new `lpd' suite feature
Christopher Masto <[EMAIL PROTECTED]> writes: > On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote: > > < said: > > > > > Huh? Security through ignorance? > > > > Remember that `lpr' is setuid-root and uses a ``privileged'' port for > > its communications. Many sites may still be using trusted-host > > ``authentication'' internally, and LPRng's ``feature'' may enable a > > compromise of some such service. (Got enough scare quotes there?) > > That is indeed something I failed to consider. I suppose it would be > necessary to have some control over that feature in some environments. > I just find it incredibly convenient to be able to install LPRng on > a bunch of client machines and just rm /etc/printcap, set $PRINTER, > and be done with it. as I remeber me, the same thing is possible under newer Solaris boxes. Cyrille. -- home:mailto:[EMAIL PROTECTED] Supprimer "%no-spam" pour me repondre. work:mailto:[EMAIL PROTECTED] Remove "%no-spam" to answer me back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Makoto Matsushita wrote: > > Userconfig was gone in 5-current, so we can safely remove kget() from > sysinstall. Attached below is a patch to do (kget.c should be remove > also). I don't know -current. what is the feature which replace kget ? does boot -c (or whatever) still exists ? is it possible to edit .hints at boot time ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: sysinstall to remove userconfig code
John Baldwin wrote: > On 13-Nov-01 Cyrille Lefevre wrote: > > Makoto Matsushita wrote: > >> > >> Userconfig was gone in 5-current, so we can safely remove kget() from > >> sysinstall. Attached below is a patch to do (kget.c should be remove > >> also). > > > > I don't know -current. what is the feature which replace kget ? > > does boot -c (or whatever) still exists ? is it possible to > > edit .hints at boot time ? > > You can use kenv and just save the ones starting with 'hint' to kernel.conf. > kenv dumps the entire kernel environment. We still need a utility written in well, kenv is a userland program (which also exists under -stable... forgot about it) but it is really not comparable to boot -c ! I don't remember if I already use sysinstall to change any kernel value ? > Forth that the loader can run for the user to modify the hints in the > environment. not for me ;^) thanks anyway for the answer. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to mount UDF file system?
Long, Scott wrote: > This is not possible yet under FreeBSD. I have a UDF work-in-progress at > http://people.freebsd.org/~scott/udf, but it cannot do CD-RW yet. FreeBSD.org - Document not found ! Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How to mount UDF file system?
Garrett Rooney wrote: > On Thu, Nov 15, 2001 at 03:15:50AM +0100, Cyrille Lefevre wrote: > > Long, Scott wrote: > > > This is not possible yet under FreeBSD. I have a UDF work-in-progress at > > > http://people.freebsd.org/~scott/udf, but it cannot do CD-RW yet. > > > > FreeBSD.org - Document not found ! > > try http://people.freebsd.org/~scottl/udf works fine, thanks :) Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Cyrille Lefevre writes: > : I don't know -current. what is the feature which replace kget ? > : does boot -c (or whatever) still exists ? is it possible to > : edit .hints at boot time ? > > set/unset works. > > I've removed ISA devices at boot time by unsetting the 'at' hint. thanks for the trick. but show/set/unset are really less intuitive than boot -c, specifically to novice users. unfortunately, I'm not forth aware at all, so, don't ask me about writting such tool using forth :P Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: sysinstall to remove userconfig code
Warner Losh wrote: [snip] > Actually, now that I think about it, the module I saw was in 'C'. So > someone needs to learn forth to do this. :-) what are you waiting for ? :P it's still possible to install gforth (don't know if it's compatible w/ loader ?) and to begin to read the gforth info files (don't know if they are really accurate ?). well, I'm the maintainer, but that's all :-)) I still know nothing to forth ! Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld breakage during "make depend" at usr.bin/kdump
Dag-Erling Smorgrav wrote: > "David O'Brien" <[EMAIL PROTECTED]> writes: > > because `echo' nicely removes \n's from env vars when it prints them. > > des@des ~% foo='bar > quote> baz' > des@des ~% echo $foo > bar > baz > des@des ~% /bin/echo $foo > bar > baz > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] humm! what shell ($SHELL) are you using ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
adding athlon xp to bsd.cpu.mk
Hi,
how about the following patch (untested) regarding the newer athlon xp
processor type ? if needed, I could submit a PR.
Index: bsd.cpu.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.cpu.mk,v
retrieving revision 1.2.2.4
diff -u -r1.2.2.4 bsd.cpu.mk
--- bsd.cpu.mk 2001/03/21 11:43:20 1.2.2.4
+++ bsd.cpu.mk 2001/10/27 19:56:42
@@ -17,6 +17,8 @@
CPUTYPE = i686
. elif ${CPUTYPE} == "pentium"
CPUTYPE = i586
+. elif ${CPUTYPE} == "athlonxp"
+CPUTYPE = xp
. elif ${CPUTYPE} == "athlon"
CPUTYPE = k7
. endif
@@ -28,8 +30,10 @@
.if !defined(NO_CPU_CFLAGS) || !defined(NO_CPU_COPTFLAGS)
. if ${MACHINE_ARCH} == "i386"
-. if ${CPUTYPE} == "k7"
+. if ${CPUTYPE} == "xp"
_CPUCFLAGS = -march=k6 # gcc doesn't support athlon yet, but it will
+. elif ${CPUTYPE} == "k7"
+_CPUCFLAGS = -march=k6 # gcc doesn't support athlon yet, but it will
. elif ${CPUTYPE} == "k6-2"
_CPUCFLAGS = -march=k6
. elif ${CPUTYPE} == "k6"
@@ -79,7 +83,9 @@
# presence of a CPU feature.
.if ${MACHINE_ARCH} == "i386"
-. if ${CPUTYPE} == "k7"
+. if ${CPUTYPE} == "xp"
+MACHINE_CPU = k7 3dnow sse mmx k6 k5 i586 i486 i386
+. elif ${CPUTYPE} == "k7"
MACHINE_CPU = k7 3dnow mmx k6 k5 i586 i486 i386
. elif ${CPUTYPE} == "k6-2"
MACHINE_CPU = 3dnow mmx k6 k5 i586 i486 i386
Cyrille.
--
Cyrille Lefevre mailto:[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: adding athlon xp to bsd.cpu.mk
Peter Wemm wrote: > Jerry A! wrote: > > On Sat, Oct 27, 2001 at 10:00:44PM +0200, Cyrille Lefevre wrote: > > : Hi, > > : > > : how about the following patch (untested) regarding the newer athlon xp > > : processor type ? if needed, I could submit a PR. > > > > Shouldn't Athlons and AthlonXPs be able to use i686 (pentiumpro) > > instruction set optimizations? > > No. They are different cpu cores that have different optimization > strategies. > > The patch doesn't include the AthlonMP which has the same core with > both SSE and MMX. Athlon XP (commercial name) == Athlon MP (core name) Athlon (alias k7) already has MMX. the objective of this patch was to add SSE to the set of XP (alias MP) processors. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Posix feature tests update
Garrett Wollman <[EMAIL PROTECTED]> writes: > I have almost completely finished this work. Please join the > [EMAIL PROTECTED] mailing-list, where the patches were > posted several months ago, and where hopefully more discussion can > still take place. I have not had time recently to update the patches please, how to subscribe to this mailing list ? where are the archives ? thanks in advance. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp -u patch
Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> writes: > Question is, do we want to add this to our cp? > > I found it handy for stuff like: please, what is the difference between this : > cp -Ruv mozilla mozilla-test and that : cd mozzila; find . | cpio -pdm ../mozzila-test ? thanks. > so that my mozilla CVS tree [not touched] only overwrites the > mozilla-test files which are older. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile.inc1
Bruce Evans <[EMAIL PROTECTED]> writes: > > Debian CDs on FreeBSD with linux emulation way better than you can build > > say a -STABLE release on a -CURRENT box... ) > > I just tried a Linux fdisk binary built in 1997 under FreeBSD-current. > It seemed to run perfectly except it couldn't determine the disk geometry > automatically. some times ago, I've ported linux fdisk to native freebsd. if you really need it, I could make it a port ? Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile.inc1
Bruce Evans <[EMAIL PROTECTED]> writes: > > Debian CDs on FreeBSD with linux emulation way better than you can build > > say a -STABLE release on a -CURRENT box... ) > > I just tried a Linux fdisk binary built in 1997 under FreeBSD-current. > It seemed to run perfectly except it couldn't determine the disk geometry > automatically. some times ago, I've ported linux fdisk to native freebsd. if you really need it, I could make it a port ? Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src Makefile.inc1
Bruce Evans wrote: > On 21 May 2001, Cyrille Lefevre wrote: [snip] > I don't need it myself (I only ran it to see if it supported Linux > extended partitions (it didn't, at least in it's list of known partition > types)). This is for the old Linux fdisk with a dumb terminal interface > which hadn't changed much (in 1997) since it was first implemented in > 1991 or 1992. It doesn't have a good interface, but I rather like it > since most of it was apparently copied from the one I implemented in > Minix fdisk in 1988 or 1989 :-). Others might prefer a more graphical > interface. Which version did you port? the ones from util-linux-2.10s.tar.gz (or .src.rpm?) cfdisk and fdisk seems to work good. for instance, sfdisk make a core! I did need it in the past, but in fact, I've done what I want w/ the bsd one. it was when I upgrade MaxBlast which is a software BIOS to see large drives. it changed the IDs of all (DOS?) primary and partitions to 0x55 and FreeBSD didn't like it at all. the problem is that ID didn't make a difference between primary (0xC) and extended (0xF) partitions... CC shortened. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1)does
"Brad Knowles" <[EMAIL PROTECTED]> writes: > At 9:21 PM -0400 2000/7/3, Will Andrews wrote: > > > Does anyone else here think this is a good idea? > > If you're looking for votes, you've got mine. > > BTW, will this play nicely with -h? Consider me stupid if you yes since all internal values are counted in bytes as I remember me. juste the output is affected by -h or whatever option. -c just add a summary line. PS : take care, my email address have changed. no more citeweb.net (not reliable) nor poboxe.com (no more free). thanks. Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can a program ignore all signals?
Riccardo Torrini <[EMAIL PROTECTED]> writes: [snip] > Only shutdown stop it, but with message: >"some processes would not die; ps axl advised" > After reboot all partitions are clean, no need of fsck. precisely, this is what we could call a driver (kernel?) deadlock. what's the ps axl output ? specificaly the wchan field would say what is happen. IMHO, this shouldn't arrive and probably is a driver bug or hardware failure not handled by some driver which is a driver bug in fact. I am wrong ? Cyrille. -- home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RFC: /dev/console -> /var/log/messages idea/patch
Alexander Leidinger <[EMAIL PROTECTED]> writes: > On 22 Nov, Ashley Penney wrote: > > >> The attached patch is a "proof-of-concept" on which I would like > >> to get some comments: > > > > I'm only a moronic user, but this would make my life easier. My machine > > switches into 132x43 on startup, and I always lose the output. So this > > Its in the scrollback buffer. and how do you access the scroll-back buffer if you are not front to the console (read remote) ? Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: INVARIANTS and -current
Steve Kargl <[EMAIL PROTECTED]> writes: > Eivind Eklund wrote: > > (Based on suggestion from Robert Watson.) > > > > I want to enable INVARIANTS by default in -current. This result in some > > slowdown, but it also makes it more likely that we'll find bugs quickly. > > People that want to run -current should know enough to disable it if it is > > in the way, anyway. > > I support your proposal. But, have a question: Has > anyone actually measured the performance impact of > INVARIANTS? I'm tempted to suggest that INVARIANTS > should be the default in not only -current in 5.0 > when she's released. Anyone interested in performance > in 5.0 will build custom kernels, and so he can turn > INVARIANTS off. sorry for the late answer. well, I'm not at all w/ you to enable INVARIANTS in -stable. the reason is simple. I had INVARIANTS for months (years?), but in september, I got plenty of "TRAP FAULT 12 and calcru: monotonisation" because of this. after disabling INVARIANTS, no problems anymore. I've posted a message about that in -stable w/ no answer, as I remember me. so, before to enable INVARIANTS in -stable or anywhere, the code should be much better checked, at least around kern_resource.c. Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RFC: /dev/console -> /var/log/messages idea/patch
Alexander Leidinger <[EMAIL PROTECTED]> writes: > On 24 Nov, Cyrille Lefevre wrote: > > >> >> The attached patch is a "proof-of-concept" on which I would like > >> >> to get some comments: > >> > > >> > I'm only a moronic user, but this would make my life easier. My machine > >> > switches into 132x43 on startup, and I always lose the output. So this > >> > >> Its in the scrollback buffer. > > > > and how do you access the scroll-back buffer if you are not front to the > > console (read remote) ? > > You can't. > > I didn't see the relationship between my answer to Ashley and your > question, can you please give me a hint? I just want to say that I'm full about doing something which logs what's happen at boot time, and that the scrollback buffer isn't sufficient. in other words, something like PR#14931 until this work is commited. Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RFC: /dev/console -> /var/log/messages idea/patch
"David O'Brien" <[EMAIL PROTECTED]> writes: > On Fri, Nov 24, 2000 at 01:08:37AM +0100, Cyrille Lefevre wrote: > > > Its in the scrollback buffer. > > > > and how do you access the scroll-back buffer if you are not front to the > > console (read remote) ? > > Do you mean remotely loged in across the network, or a serial [remote] > console? If you mean the later the comconsole port logs all console > output to a file. remotly logged. at my job, I manage around 160 machines (unfortunaly, there is no FreeBSD) and I appreciate HP-UX boxes which have this feature. if something doesn't start at boot time, I've just to look at /var/adm/rc.log and search the FAIL keyword. don't rememeber about IRIX boxes, nothing exists under Solaris boxes. Cyrille. -- Cyrille Lefevre 12, Rue de Bizerte 75017 Paris tel/fax: +33 (0)1 45 22 83 85 home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] icq: mailto:[EMAIL PROTECTED] http://wwp.icq.com/17089123 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
hi everybody and Happy New Year, anybody to commit http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19635 ? one of the reasons it was not commited was due to an overflow problem which has been fixed since. thanks by advance.. Cyrille. -- home: mailto:[EMAIL PROTECTED] work: mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: ports/palm/pilot-link Makefile
"Akinori MUSHA" <[EMAIL PROTECTED]> writes:
> However, if I put either:
>
> CXXFLAGS+=-fPIC
>
> or:
>
> CFLAGS!= ${ECHO} "${CFLAGS}" | ${SED} -e 's/-O[0-9a-z]*//g'
IMHO, this could be rewritten as ${CFLAGS:N-O*} which is more clean
than forking a subshell.
Cyrille.
--
home: mailto:[EMAIL PROTECTED] UNIX is user-friendly; it's just particular
work: mailto:[EMAIL PROTECTED] about who it chooses to be friends with.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ps seems broken
On Wed, Jun 05, 2002 at 10:24:07AM -0700, J. Mallett wrote: > * From David Wolfskill <[EMAIL PROTECTED]> [snip] > > g1-9(5.0-C)[2] ps -ax > > ps: pid tt state time command: keyword not found > > ps: no valid keywords > > g1-9(5.0-C)[3] > > This is due to me un-breaking seperation of keywords and not testing > enough. Sorry. Give me five minutes. Hi, may I ask you what kind of changes are you doing to ps ? since I've worked a lot on ps to make it SUSV3 complian and don't want to redo all the job I've done. some days ago, I've asked to be recorded to the `FreeBSD C99 & POSIX Conformance Project' (http://www.FreeBSD.org/projects/c99/) as the ps maintainer but the page has not been updated yet. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Add a Makefile.user on /usr/src and /usr/ports
On Fri, Jun 07, 2002 at 12:25:09AM +0200, Riccardo Torrini wrote:
> To support fancy user and they own targets would be nice an
> infrastructure that check and (if it exist) include a file
> (named Makefile.user or .local or similar) with personal
> targets either under /usr/src than /usr/ports.
>
> This can save a lot of typing building various things (for
> example timing build phase or saving logs) only migrating
> this file from a machine to another.
maybe the attached Makefile may help you in the process.
I use it for months to build everything.
Cyrille.
--
Cyrille Lefevre mailto:[EMAIL PROTECTED]
#!/usr/bin/make -f
#
# @(#) etc:Makefile 1.6 ([EMAIL PROTECTED]) Wed Jun 5 23:08:17 CEST 2002
#
# Copyright (c) 2000-2002 Cyrille Lefevre. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
# FOR ANY _DIRECT, IN_DIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
# OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
# HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
# OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
# SUCH DAMAGE.
# TODO : rel target and maybe dump target
# make release RELEASETAG=RELENG_4 CHROOT_DIR=/disk1/release/root \
# LOCAL_PATCHES=/disk1/release/patches LOCAL_SCRIPT=/disk1/release/script \
# NOPORTS=YES NODOC=YES NOSRC=YES # NOSHARED=YES RELEASENOUPDATE=YES
# ftp://current.jp.FreeBSD.org/pub/FreeBSD/snapshots/i386/ISO-IMAGES/
.MAKEARGS: .dl
# Custom
#
NCVS?= true
RELENG?=-r RELENG_4
CUSTOM?=CUSTOM
GENERIC?= GENERIC
DEBUG?= -g
JOBS?= -j4
NOJOBS?=-B
# NOEXEC?= -n
AT?=@
FORCE_LBA?= # --force-lba # -> CHS ?
# Commands
#
CHFLAGS?= chflags
CONFIG?=config
CP?=cp
CPIO?= cpio
CVS?= cvs
CVS_ARGS?=
CAP_MKDB?= cap_mkdb
DATE?= date
DISKLABEL?= disklabel
DISKLABEL_ARGS?=-wB
DISKLABEL_TYPE?=fd1440
ECHO?= echo
FIND?= find
GREP?= grep
GREP_ARGS?= -B 2
GRUB?= grub
GRUB?= --batch
GRUB_INSTALL?= grub-install
GRUB_INSTALL_ARGS?= ${FORCE_LBA}
KGZIP?= kgzip
MAKE?= make
MAKE_ARGS?=
MAKEDEV?= MAKEDEV
MAKEDEV_ARGS?= all
MAKEDEV_LOCAL?= MAKEDEV.local
MAKEDEV_LOCAL_ARGS?=all
MERGEMASTER?= mergemaster
MERGEMASTER_ARGS?= -svia -vir # -s
MK_DIR?=mkdir -p
MOUNT?= mount
MV?=mv
NEWALIASES?=newaliases
NEWFS?= newfs
NEWFS_ARGS?=-m 5 -o space
PKGDB?= pkgdb
PKGDB_ARGS?=-u
PORTSDB?= portsdb
PORTSDB_ARGS?= -u
PWD_MKDB?= pwd_mkdb
RM?=rm
SLEEP?= sleep
SH?=sh
TEE?= tee
TEE_ARGS?=
TR?=tr
TOUCH?= touch
UMOUNT?=umount
ZZZ?= zzz
# Directories
#
OBJ_DIR?= /usr/obj
SRC_DIR?= /usr/src
SHDOC_DIR?= ${SRC_DIR}/share/doc
SYSINSTALL_DIR?=${SRC_DIR}/release/sysinstall
KERNCONF_DIR?= ${SRC_DIR}/sys/${MACHINE_ARCH}/conf
KERNBUILD_DIR?= ${SRC_DIR}/sys/compile
KERNMOD_DIR?= ${SRC_DIR}/sys/modules
DEV_DIR?= /dev
MAIL_DIR?= /etc/mail
DOC_DIR?= /usr/doc
DOC_ARGS?= Makefile README share ${DOC_LANG}
WEB_DIR?= /usr/www
WEB_ARGS?= www/Makefile www/Makefile.inc www/share www/tools www/en
PORTS_DIR?= /usr/ports
# Files
#
KERNEL?=kernel
LOGIN_CONF?=/etc/login.conf
MASTER_PASSWD?= /etc/master.passwd
FSTAB?= /etc/fstab
# Boot
#
BOOT_DIR?= /boot
GRUB_DIR?= ${BOOT_DIR}/grub
ALTBOOT_DEV?= /dev/ad0s3
ALTBOOT_DIR?= /grub
FLOP_DEV?= /dev/fd0
FLOP_DIR?= /flop
BOOT_FILES?=boot0 mbr \
${FLOP_FILES:N*.map:Nstage*} ${SPLASH_FILES:%=splash/%}
FLOP_FILES?=boot[12] defaults/loader.conf \
grub/device.map grub/menu.lst ${GRUB_FILES:N*1_5:%=grub/%} \
loader loader.4th loader.help loader.rc support.4th \
kernel.conf loader.conf loader.conf.local
Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs
On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote: > Dan Nelson wrote: [snip] > According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug: > ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess > it qualifies as a "non-trivial program". :-) FYI, the current pax implementation is able to handle the following archives from ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/ : 100char_longlink.tar gtarfail.tar gtarfail2.tar but miserably fail on this one : long.ustar.gz $ uname -a FreeBSD gits 4.6-RC FreeBSD 4.6-RC #7: Sun Jun 2 16:33:05 CEST 2002 root@gits:/disk2/4.x-stable/src/sys/compile/CUSTOM i386 $ pax -zvf -rw-r--r-- 1 486 cvs4 Apr 19 2000 ___ ___D_099 /___ __100644 746 0003720 004 07077317140 0055507 0 $ star -zvtf 4 -rw-r--r-- jes/cats Apr 19 13:54 2000 __ D_099/__ ___100 I'll try to fix this... Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Looking for comments on a new utility...
On Tue, Jun 11, 2002 at 05:15:17AM -0700, Juli Mallett wrote:
> Hej,
>
> As some of you may have noticed, I've done some poking of ps(1) lately, and
> this has brought attention of people who have ideas for things that they
> would like to see done to ps(1) :) The most notable request was for a
> feature I've missed having in our ps(1) for a while, the ability to get a
> tree of processes printed so you can tell who is whose child, etc.
>
> ps(1)'s internals, however, didn't seem quite right to me, but after about
> 10 minutes reading kvm(3) manpages and recalling some tricks with recursive
> programming to produce an N-level tree with as many as N-1 elements, I had
> come up with a simple utility to print out a "process tree".
>
> You can find the code here:
> http://people.freebsd.org/~jmallett/.proctree/proctree.c
>
> And some example output from a cluster machine here:
> http://people.freebsd.org/~jmallett/.proctree/proctree.out
> Lots of people have given feedback that they don't care much for the \_
> formatting of the tree, and I'm willing to look at patches that provide
> noticably more readable output.
how about this one ?
1 ?0 \_ init
2814 ttyp00 \_ sh
2816 ttyp00 | \_ sh
57423 ?0 | \_ sleep
2596 ?0 \_ inetd
24834 ?0 | \_ rlogind
24838 ttyp00 | | \_ ksh
24912 ttyp00 | | \_ ksh
57504 ?0 | \_ telnetd
^^ command tree
standard ps fields
taken from ast-open `ps -T'. see http://www.research.att.com/~gsf/download/tgz/
for details (maybe one I'll will finish this !@#$%^&* port which is still
broken in some way ?)
for fun, how about a simple awk script like the one in attachment ;^)
Cyrille.
--
Cyrille Lefevre mailto:[EMAIL PROTECTED]
#!/bin/sh
# was ps -ef
ps axwo "user pid ppid start tt time command" |
awk '
BEGIN {
getline
}
{
if (! nchild[$3])
nchild[$3] = 0
father[$2] = $3
children[$3, nchild[$3]] = $2
nchild[$3] ++
start[$2] = $4
tty[$2] = $5
time[$2] = $6
cmd[$2] = $7
for (i = 8; i <= NF; i++)
cmd[$2] = cmd[$2] " " $i
}
function print_parents(pid) {
if (pid != 1)
prefix = " " print_parents(father[pid])
else
prefix = " "
printf "%6i %6i %7s %s %s %s\\_ %s\n", \
pid, father[pid], start[pid], tty[pid], time[pid], \
substr(prefix, 1, length(prefix)-2), cmd[pid]
return " " prefix
}
function print_children (pid, prefix, child) {
printf "%6i %6i %7s %s %s %s\\_ %s\n", \
pid, father[pid], start[pid], tty[pid], time[pid], \
substr(prefix, 1, length(prefix)-2), cmd[pid]
if (! nchild[pid])
return
for (child = 0; child < nchild[pid] - 1; child ++)
print_children(children[pid, child], prefix " | ")
print_children(children[pid, child], prefix "")
}
END {
if (! whichpid)
whichpid = 1
if (! cmd[whichpid])
exit
if (father[whichpid])
prefix = " " print_parents(father[whichpid])
else
prefix = " "
print_children(whichpid, prefix)
}' whichpid=$1
pax fix (was Re: WARNING! New GNU Tar in 5-CURRENT could erroneouslycreate world writeable dirs)
On Jun 7, 2002 01:27:31 pm +0200, Cyrille Lefevre wrote: > On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote: > > Dan Nelson wrote: > [snip] > > According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug: > > ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess > > it qualifies as a "non-trivial program". :-) > > FYI, the current pax implementation is able to handle the following > archives from ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/ : > > 100char_longlink.tar > gtarfail.tar > gtarfail2.tar > > but miserably fail on this one : > > long.ustar.gz > > $ uname -a > FreeBSD gits 4.6-RC FreeBSD 4.6-RC #7: Sun Jun 2 16:33:05 CEST 2002 >root@gits:/disk2/4.x-stable/src/sys/compile/CUSTOM i386 > $ pax -zvf > -rw-r--r-- 1 486 cvs4 Apr 19 2000 ___ > ___D_099 > /___ > __100644 746 0003720 004 07077317140 0055507 0 > > $ star -zvtf > 4 -rw-r--r-- jes/cats Apr 19 13:54 2000 __ > D_099/__ > > ___100 > > I'll try to fix this... done, here is the patch which may be integrated to 4.6 -release ? Index: /tmp/src/bin/pax/tar.c === RCS file: /home/ncvs/src/bin/pax/tar.c,v retrieving revision 1.19 diff -u -r1.19 tar.c --- /tmp/src/bin/pax/tar.c 16 May 2002 01:57:13 - 1.19 +++ /tmp/src/bin/pax/tar.c 11 Jun 2002 23:39:16 - @@ -758,7 +758,7 @@ *dest++ = '/'; cnt++; } - arcn->nlen = cnt + l_strncpy(dest, hd->name, sizeof(arcn->name) - cnt); + arcn->nlen = cnt + l_strncpy(dest, hd->name, MIN(TNMSZ + 1, sizeof(arcn->name) +- cnt) - 1); arcn->name[arcn->nlen] = '\0'; /* PS : I've finished to merge diffs from OpenBSD last week, but diffs w/ NetBSD are really big... so, be patient :P Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pax fix (was Re: WARNING! New GNU Tar in 5-CURRENT could erroneously create world writeable dirs)
On Wed, Jun 12, 2002 at 03:07:45AM +0200, Bjoern Fischer wrote: > > PS : I've finished to merge diffs from OpenBSD last week, but diffs > > w/ NetBSD are really big... so, be patient :P > > What about bin/35886? already done using the NetBSD way. the problem is that they use LC_TIME (hugh!) to pass the format string to strftime while LC_TIME isn't suppose to contain any format strings but a locale name. so, I don't know yet how to handle this case. whatever, I'm not sure that adding a yet another non portable option would be good. how about using env var PAX_TIMEFMT instead ? something is missing in the SUSV3 standard. -o can't be use for reading (not extracting -- aka no -r nor -w) archive. in other way, I would like to say something like this : pax -o freebsd.timefmt=... -f archive but I can't w/o breaking the standard! grrr. search for the VENDOR keyword in the the following URL for details : http://www.opengroup.org/onlinepubs/007904975/utilities/pax.html Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Perl scripts that need rewiting - Any volunteers?
On Mon, Jun 24, 2002 at 08:46:22PM +0100, Jonathan Belson wrote: > Mark Murray wrote: > >o Please do not use mktemp(); use mkstemp() instead. > > I used mktemp() to get a filename to redirect to, eg. > > /* Improvised example */ > char *cmd; > asprintf(cmd, "prog > %s", mktemp(blah)); > system(cmd); > free(cmd); > > I couldn't see a simple way around this, any clues? int fd = mkstemp (blah); asprintf(cmd, "prog > /dev/fd/%d", fd); I don't look at the code, but how about popen(3) ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mysterious dead-locks with system ssh
On Sun, Jul 14, 2002 at 11:08:07PM +0200, Marc Recht wrote: > I'm getting strange dead-locks/complete lookups when I use the system > ssh with port forwarding. Using something like: > ssh -L8080:remote:8080 account@remote > to forward a remote apache to my local box. When I access > http://localhost:8080/ not later than the third click on link (or > pressing reload) my box locks up completely. I don't even get into the > debugger or get a crash dump. The box is just plain dead. Though I had a similar problem w/ netscape-4 configured to use a local (non started) proxy in -stable. w/ the proxy, no problem, w/o it, plain dead-lock. don't know where is the lockup ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Updating GNU Tar in the base system
On Mon, Jun 03, 2002 at 03:49:49PM -0700, Kris Kennaway wrote: > On Mon, Jun 03, 2002 at 03:14:23PM -0700, Paul Herman wrote: > > On Mon, 3 Jun 2002, Maxim Sobolev wrote: > > > > > However, before proceeding I would like to get an advice with regard > > > to the most appropriate procedure for doing the upgrade. > > > > This came up in another list somewhere (don't know off hand), but > > you might also consider having tar wrap around pax. > > > > OpenBSD has already done this, so your work might be already done! > > :-) > > Our pax (which I merged from NetBSD and bits of OpenBSD last year) has > a pretty good tar compatibility mode (i.e. when invoked as tar), but > it doesn't support most of the gtar longopts. last week, I've began to comlete your work done last year by resyncing FreeBSD pax w/ the NetBSD/OpenBSD ones. would be done by the end of this week... Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps(1) -o peculiarity in CURRENT
On Tue, Jun 04, 2002 at 03:13:21PM -0700, J. Mallett wrote: > Aphex% ps -ouser= > ?? > jmallett > jmallett > jmallett I remember to see something like that when a kernel dependent command, such as ps, is out of sync w/ the running kernel. did you upgrade your kernel recently w/o syncing your world ? also, are your world sources in sync w/ the kernel sources ? did you reboot since your last kernel/world installation ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVS removal from the base
Le 05/12/2011 03:00, Randy Bush a écrit : BIND OTOH is something different. what's bind? :) http://www.isc.org/software/bind Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
