From-To: open-closed
By: nwhitehorn
When: Sun Oct 23 15:18:39 UTC 2011
Why: There is help throughout, in particular in the partition editor,
which shows help in the bottom line of the screen. More verbose help
(e.g. pressing F1 to open a help screen) will likely come later.
ead...@freebsd.org wrote:
Synopsis: 9.0 burncd error caused by change to cd0 from acd0
State-Changed-From-To: open-analyzed
State-Changed-By: eadler
State-Changed-When: Mon Sep 26 23:24:00 UTC 2011
State-Changed-Why:
requires only a release notes entry; use cdrecord instead of burncd
On 09/26/2011 17:59, Fbsd8 wrote:
Your solution is very un-professional.
Good thing we're all volunteers. :)
What your solution purposes to do
is do nothing. I think your judgment is flawed and a larger group of
your peers need to review your judgment in this case.
Ok, done. Eitan is
On 09/26/2011 18:43, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and confused end-users.
It doesn't fail to work on
On Mon, Sep 26, 2011 at 6:28 PM, Doug Barton do...@freebsd.org wrote:
burncd has been part of the system utilities included in the basic
release since release 4.0 and cdrecord is a port. The professional
solution is to remove burncd from the 9.0 system release and add the
cdrecord command to
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 6:58 PM, Doug Barton do...@freebsd.org wrote:
I have used burncd on many releases of FreeBSD, on many machines
without problem. I can see the fact that burncd suddenly failing to
work on ATAPI hardware could annoy and
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that your kernel is built with acd(4) and the
On Mon, 26 Sep 2011, Craig Rodrigues wrote:
On Mon, Sep 26, 2011 at 8:30 PM, Garrett Cooper yaneg...@gmail.com wrote:
...
Please fix it and move on.
Thanks,
-Garrett
$ usr.sbin/burncd/burncd -f /dev/cd0 blank
burncd: device provided not an acd(4) device: /dev/cd0.
Please verify that
.. and if someone would like to contribute patches to burncd to update
it, I think there'd be at least one committer here who would be happy
to help you get your changes into the tree.
:-)
Adrian
___
freebsd-questions@freebsd.org mailing list
Dan Naumov wrote:
What exactly is gart and where do I find it's manpage,
http://www.freebsd.org/cgi/man.cgi comes up with nothing? Also, does
this mean that GPT is _NOT_ in fact fixed regarding this bug?
That's gpart(8). With a 'p'. gpart has had significant amounts of
work put into it for
Hi Frank,
Am Donnerstag, 05. Mär 2009, 04:15:05 + schrieb Frank Shute:
On Wed, Mar 04, 2009 at 04:08:03PM +0100, Bertram Scharpf wrote:
from man sh:
Invocation
[...] the shell inspects
argument 0, and if it begins with a dash (`-'), the shell is also
consid-
On Thu, Mar 05, 2009 at 02:23:52PM +0100, Bertram Scharpf wrote:
Hi Frank,
Hi Bertram,
Am Donnerstag, 05. Mär 2009, 04:15:05 + schrieb Frank Shute:
On Wed, Mar 04, 2009 at 04:08:03PM +0100, Bertram Scharpf wrote:
from man sh:
Invocation
[...] the shell inspects
Good evening Betram et al.
I've read the discussion thread as far as it went and would like
to share my own solution to a similar problem, mapped onto the
sh topic. Maybe it works.
A little background:
First of all, because my standard dialog shell is the system's
C shell, the files important
On Wed, Mar 4, 2009 at 4:08 PM, Bertram Scharpf
li...@bertram-scharpf.de wrote:
Hi,
from man sh:
Invocation
[...] When first starting, the shell inspects
argument 0, and if it begins with a dash (`-'), the shell is also consid-
ered a login shell. This is normally done
I first wondered why none of my commands in /etc/profile and
~/.profile got executed. Finally, I modified
/usr/src/bin/sh/main.c to trace what files are read, recompiled
the sh command and: the only file that is executed is ~/.shrc.
I just cannot believe that FreeBSD has such a severe bug.
On Thu, 5 Mar 2009 18:11:18 -0800 (PST), Peter Steele pste...@maxiscale.com
wrote:
I have a similar problem, but with bash. I have both my personal
account and root set to use bash instead of sh and when I login
the .bashrc file is not read. My system does not have an X
environment, it's
On Thu, Mar 05, 2009 at 06:11:18PM -0800, Peter Steele wrote:
I first wondered why none of my commands in /etc/profile and
~/.profile got executed. Finally, I modified
/usr/src/bin/sh/main.c to trace what files are read, recompiled
the sh command and: the only file that is executed is
On Wed, Mar 04, 2009 at 04:08:03PM +0100, Bertram Scharpf wrote:
Hi,
from man sh:
Invocation
[...] When first starting, the shell inspects
argument 0, and if it begins with a dash (`-'), the shell is also consid-
ered a login shell. This is normally done
On Wed, 13 Feb 2008 08:58:01 +0100 Roland Smith [EMAIL PROTECTED]
wrote:
On Wed, Feb 13, 2008 at 12:59:41AM -0600, Scott Bennett wrote:
% cat show
#! /bin/csh
set delay=3D3D2
set pixlist=3D3D(09 08 07 05 04 03 02 01)
foreach i ($pixlist)
(nice xv $i.jpg )
sleep
On Tue, 12 Feb 2008 16:01:26 +0100 Roland Smith [EMAIL PROTECTED]
wrote:
On Tue, Feb 12, 2008 at 08:02:49AM -0600, Scott Bennett wrote:
I just set up a GELI partition for the first time a while ago (not
counting the swap partition). After initializing the GELI device file,
filling it
On Tue, 12 Feb 2008 16:06:45 +0100 [EMAIL PROTECTED]@mgEDV.net [EMAIL
PROTECTED]
wrote:
Subject: /bin/csh script in GELI partition crashes 6.3-STABLE
things i ran into with GELI/UFS2+S:
- geli partition sector size larger than 4KB caused panics on one of our
boxes
Ah. Okay. I had
On Tue, Feb 12, 2008 at 03:46:56PM -0600, Scott Bennett wrote:
On Tue, 12 Feb 2008 16:01:26 +0100 Roland Smith [EMAIL PROTECTED]
wrote:
On Tue, Feb 12, 2008 at 08:02:49AM -0600, Scott Bennett wrote:
I just set up a GELI partition for the first time a while ago (not
counting the
On Tue, 12 Feb 2008 15:16:59 +0100 Ivan Voras [EMAIL PROTECTED]
wrote:
Scott Bennett wrote:
It does it every time, so it is certainly repeatable. Is this a
known problem? Or is there some feature of GELI-encrypted file systems
that is expected to have problems running scripts? (I
Subject: /bin/csh script in GELI partition crashes 6.3-STABLE
things i ran into with GELI/UFS2+S:
- geli partition sector size larger than 4KB caused panics on one of our
boxes
- fs sector size any than 512 sometimes caused hangs/watchdog reboots
try setting up a kernel with debug-flags and
On Tue, Feb 12, 2008 at 08:02:49AM -0600, Scott Bennett wrote:
I just set up a GELI partition for the first time a while ago (not
counting the swap partition). After initializing the GELI device file,
filling it from /dev/random, running newfs, and copying over a couple of
directory
Scott Bennett wrote:
It does it every time, so it is certainly repeatable. Is this a
known problem? Or is there some feature of GELI-encrypted file systems
that is expected to have problems running scripts? (I do not know whether
the problem is limited to /bin/csh scripts. After
On Tue, 12 Feb 2008 23:51:41 +0100 Roland Smith [EMAIL PROTECTED]
wrote:
On Tue, Feb 12, 2008 at 03:46:56PM -0600, Scott Bennett wrote:
On Tue, 12 Feb 2008 16:01:26 +0100 Roland Smith [EMAIL PROTECTED]
wrote:
On Tue, Feb 12, 2008 at 08:02:49AM -0600, Scott Bennett wrote:
I just
On Wed, Feb 13, 2008 at 12:59:41AM -0600, Scott Bennett wrote:
% cat show
#! /bin/csh
set delay=3D2
set pixlist=3D(09 08 07 05 04 03 02 01)
foreach i ($pixlist)
(nice xv $i.jpg )
sleep $delay
end
=20
The delay is simply to ensure the windows get opened in the
On Wed, Nov 14, 2007 at 09:08:57AM -0600, Martin McCormick wrote:
I am ashamed to admit that I have been writing shell
scripts for about 15 years but this problem has me stumped. $0
is the shell variable which contains the script name or at least
what name is linked to the script. The
In response to Martin McCormick [EMAIL PROTECTED]:
I am ashamed to admit that I have been writing shell
scripts for about 15 years but this problem has me stumped. $0
is the shell variable which contains the script name or at least
what name is linked to the script. The string in $0 may
Martin McCormick wrote:
I am ashamed to admit that I have been writing shell
scripts for about 15 years but this problem has me stumped. $0
is the shell variable which contains the script name or at least
what name is linked to the script. The string in $0 may or may
not contain a path,
The basename utility does the trick. Thanks to all of you
who answered.
Martin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Martin McCormick [EMAIL PROTECTED] writes:
I am ashamed to admit that I have been writing shell
scripts for about 15 years but this problem has me stumped. $0
is the shell variable which contains the script name or at least
what name is linked to the script. The string in $0 may or may
I wasn't able to reproduce what you explained...maybe I missed something?
i just do the following:
clear
/bin/sh
EDITOR=vi
export EDITOR
set -o $EDITOR
echo 1
echo 2
echo 3
echo 4
ESC-.
and this is the output:
test# /bin/sh
test# EDITOR=vi
export EDITOR
set -o $EDITOR
echo 1
echo 2
echo 3
i just do the following:
clear
/bin/sh
EDITOR=vi
export EDITOR
set -o $EDITOR
echo 1
echo 2
echo 3
echo 4
ESC-.
I tested the command sequence you gave and the result was as you
explained. What caught my attention, however, was that all the
commands were builtin. I tested with
i just do the following:
clear
/bin/sh
EDITOR=vi
export EDITOR
set -o $EDITOR
echo 1
echo 2
echo 3
echo 4
ESC-.
I tested the command sequence you gave and the result was as you
explained. What caught my attention, however, was that all the
commands were builtin. I tested with non-builtin
As far as I know, ESC-. (in fact hitting '.' when in command mode)
repeats your very last action whether it was an editing action or
executing a command.
yes, that's true for vi, but not for /bin/sh in vi-mode. at least
on my 6.2-RELEASE.
;)
___
I wasn't able to reproduce what you explained...maybe I missed something?
Bahman
On 8/28/07, [EMAIL PROTECTED]@mgedv.net [EMAIL PROTECTED] wrote:
As far as I know, ESC-. (in fact hitting '.' when in command mode)
repeats your very last action whether it was an editing action or
executing
As far as I know, ESC-. (in fact hitting '.' when in command mode)
repeats your very last action whether it was an editing action or
executing a command.
Bahman
On 8/27/07, [EMAIL PROTECTED]@mgedv.net [EMAIL PROTECTED] wrote:
hi folks,
when someone uses set -o vi to put /bin/sh into vi-mode
*heh*
DONT remove that.its normal.
On 8/26/07, Jim Stapleton [EMAIL PROTECTED] wrote:
Sorry if you get this question a lot - a few searches didn't find
results for me.
I have a /bin/[ file in my system - I just want to make sure it's
not a sign of someone having hacked my machine.
If you look at /etc/rc, the shell script that boots your system, you'll
notice [ being called quite often. For better understanding, look at
`man 1 [`.
On Aug 26, 2007, at 3:57 PM, Jim Stapleton wrote:
Sorry if you get this question a lot - a few searches didn't find
results for me.
I have
Jeff Mohler wrote:
*heh*
DONT remove that.its normal.
On 8/26/07, Jim Stapleton [EMAIL PROTECTED] wrote:
Sorry if you get this question a lot - a few searches didn't find
results for me.
I have a /bin/[ file in my system - I just want to make sure it's
not a sign of someone having
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Stapleton wrote:
Sorry if you get this question a lot - a few searches didn't find
results for me.
I have a /bin/[ file in my system - I just want to make sure it's
not a sign of someone having hacked my machine.
No -- that's perfectly
Thanks everyone for the help. I tried using man, but it didn't find
anything. Glad to know my system isn't compromised.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
Jim Stapleton wrote:
Thanks everyone for the help. I tried using man, but it didn't find
anything. Glad to know my system isn't compromised.
When searching for many shell sensitive commands and characters ('['
included), single-quoting the query will help you find what you need to
find.
From: Viktoras Veitas [EMAIL PROTECTED]
Hello.
I suddenly cannot run cat command as /bin/cat file appears to be without
execute permissions (all other files in /bin directory are with them) and I
get /bin/cat: Permission denied error.
I had a misfortune to chmod 555 /bin/cat, then my
jdow wrote:
From: Viktoras Veitas [EMAIL PROTECTED]
Hello.
I suddenly cannot run cat command as /bin/cat file appears to be
without
execute permissions (all other files in /bin directory are with them)
and I
get /bin/cat: Permission denied error.
I had a misfortune to chmod 555
Incidentally, it is operating as documented (pathname expansion isn't
listed as performed on redirection targets), and explicitly allowed by
the POSIX standard.
but /bin/sh could accept *txt until there's more than one file matching
after expansion. if that's the case, an error like *blabla:
[EMAIL PROTECTED]@mgEDV.net [EMAIL PROTECTED] writes:
i know things like cat *lst|wc, but i don't want to type them.
when i try to use wildcards with or in /bin/sh, it fails:
my input (only one file with this name exists in the current dir):
wc *lst
Which is equivalent to wc *lst, so I'm
Dan Nelson wrote:
In the last episode (Feb 16), Tim Daneliuk said:
Here is a shell function that behaves quite strangely:
#!/bin/sh
#
# Execute A Command, Noting Start/Stop Time, Logging Output
# Args:
# $1 Command Name
# $2 Log Directory
# $3 Command String To Execute
Dan Nelson wrote:
In the last episode (Feb 16), Tim Daneliuk said:
Here is a shell function that behaves quite strangely:
#!/bin/sh
#
# Execute A Command, Noting Start/Stop Time, Logging Output
# Args:
# $1 Command Name
# $2 Log Directory
# $3 Command String To Execute
In the last episode (Feb 17), Tim Daneliuk said:
Dan Nelson wrote:
Could your $3 command be returning a nonzero exit code? You probably
want something more like
touch $2/.$1-begin { eval $3 21 $log ; touch $2/.$1-end }
so your end timestamp always gets created whether or not $3
In the last episode (Feb 16), Tim Daneliuk said:
Here is a shell function that behaves quite strangely:
#!/bin/sh
#
# Execute A Command, Noting Start/Stop Time, Logging Output
# Args:
# $1 Command Name
# $2 Log Directory
# $3 Command String To Execute
#
George Dew wrote:
After upgrading to BSD 4.11, I've been having all sorts of problems.
Please help!
- The shell no longer supports the up cursor key, which gives a history of
commands that you type.
Which shell you were using before upgrade ? And which one do u use now ?
Just change it to one,that
On Fri, 19 Nov 2004, Dennis Koegel wrote:
find /foo/bar -type f -maxdepth 1 | xargs rm -n100
Although xargs is the most versatile solution for when having too many
items listed, for just deleting find itself can do it..
find /foo/bar -n mask -delete
___
On Fri, Nov 19, 2004 at 09:58:40AM +0100, Mipam wrote:
I tried to delete all files from a dir, however I got this message:
/bin/rm: Argument list too long.
You probably did rm *, and * expanded to too many files.
One way is to simply remove the directory completely (rm -r /foo/bar),
but this
Mipam wrote:
Hi,
I tried to delete all files from a dir, however I got this message:
/bin/rm: Argument list too long.
So, no go. newfs is also no option, because the dir is not a seperate fs.
Any hints exept for manual labour?
Bye,
Mipam.
I gather it's rm * that's not working?
If so, try a
On Fri, Nov 19, 2004 at 10:19:39AM +0100, Dennis Koegel typed:
snip
find /foo/bar -type f -maxdepth 1 | xargs rm -n100
or just
ls | xargs rm
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
I mean the binaries distributed by freebsd community (available via FTP),
not those I compile, do they have any optimization?
-Original Message-
From: Paul Everlund [mailto:[EMAIL PROTECTED]
Sent: Friday, July 09, 2004 6:00 PM
To: Kyryll Mirnenko
Subject: Re: bin. packages compilation
Kyryll Mirnenko wrote:
I mean the binaries distributed by freebsd community (available via FTP),
not those I compile, do they have any optimization?
Yes, the standard CFLAGS are something close to -O -pipe. There is work in
progess to fix some coding problems within the base system and have -O2
On Wed, Jan 07, 2004 at 11:03:22AM +, gffds fsdff wrote:
How would I go about executing hlds_l_1120_full.bin (STEAM) in order to
extract it. I have also tried non-steam hlds_l_3110_full.bin with no
success, however due to STEAM taking impact on modifications I must now use
STEAM.
From
the method used by FBSD 2.2.7 seems the most sane to me,
where execve's argv[] is loaded by each whitespace
seperated element after the shebang,
then by command line options.
1. it is flexible.
2. it functions intuitively.
3. i don't think it breaks less flexible methods.
It
Oh boy! Deja-vu...
On 2003-02-28 18:32, [EMAIL PROTECTED] wrote:
This concerned how to load execve()'s argv[] array when parsing the
'shebang' line of a script, ie: whether to pass everything after
'#!/interpeter'
1. as one string into execve()'s argv[] array, as some systems do, or
2.
On Tue, Feb 25, 2003 at 12:19:45PM +0100, dick hoogendijk wrote:
For bash I can use .bash_profile and .bash_logout to get things done at
login/logout time.
On my fbsd machine I use /bin/sh and I can't find how to execute things
at logout time (login is set in .profile). I.e. I want to remove
PROTECTED]
Subject: Re: /bin/sh logout script
On Tue, Feb 25, 2003 at 12:19:45PM +0100, dick hoogendijk wrote:
For bash I can use .bash_profile and .bash_logout to get things done at
login/logout time.
On my fbsd machine I use /bin/sh and I can't find how to execute things
at logout time
On 2003-02-08 21:58, [EMAIL PROTECTED] wrote:
this does seem to be an ambiguous area.
it seems more sane to allow arguments to a script given to an
interpreter on the shebang line, passing everything after
#!/interpreter [arg] off for eval or sh -c type parsing.
This is something that can be
it seems more sane to allow arguments to a script given to an
interpreter on the shebang line, passing everything after
#!/interpreter [arg] off for eval or sh -c type parsing.
This is something that can be bth good and bad though. As you have
pointed out, if a limited sort of parsing is
Please don't remove me from the Cc: list when you reply to posts that
you want me to see. Otherwise, I might miss one of your replies and
give you the false impression that I'm somehow ignoring your posts.
On 2003-02-10 01:18, [EMAIL PROTECTED] wrote:
Giorgos Keramidas wrote:
[EMAIL
minor correction/addition to previous post:
instead of infinitely recursive, i should've
said that it would break things if script
re-exec's the same file with a
different interpreter.
--
#!/bin/sh
. script
this won't work if script is going to do something
before exec'ing the
On Sat, 8 Feb 2003 [EMAIL PROTECTED] wrote:
say i have 2 scripts, scriptA and scriptB.
scriptA
---
#!/bin/sh ./scriptB 1 2 3
scriptB
---
#!/bin/sh
echo 0:$0
echo 1:$1
echo 2:$2
echo 3:$3
--
$ ./scriptA
$0:./scriptB
$1:1
$2:2
$3:3
--
according to execve(2), only
this does seem to be an ambiguous area.
it seems more sane to allow arguments
to a script given to an interpreter on the
shebang line, passing everything after
#!/interpreter [arg] off for
eval or sh -c type parsing.
i don't know how it breaks anything to load execve's argv[]
with everything
72 matches
Mail list logo
