when I log into free bsd I am in the sh shell. i type history at the command
line and the machine says history not found. If I type h at the command line it
works like i expect the history command to work. In the csh or tcsh shells
history works as well as h. why does entering history at the
I want to see the changes made to a specific kernel source file
between Freebsd 4.9 and 4.10. I seem to recall seeing a web page
where you can check the revision history for the kernel source tree,
but I can't seem to find it. Can anyone pass me the url or another
way to view the rev
On 9/19/13 3:36 PM, william benton wrote:
> when I log into free bsd I am in the sh shell. i type history at the
> command line and the machine says history not found. If I type h at
> the command line it works like i expect the history command to work.
> In the csh or tcsh shells hist
On Thu, 19 Sep 2013 19:36:43 +, william benton wrote:
> when I log into free bsd I am in the sh shell. i type history
> at the command line and the machine says history not found.
> If I type h at the command line it works like i expect the
> history command to work.
That is str
Tomoki Taniguchi wrote:
I want to see the changes made to a specific kernel source file
between Freebsd 4.9 and 4.10. I seem to recall seeing a web page
where you can check the revision history for the kernel source tree,
but I can't seem to find it. Can anyone pass me the url or another
w
I have some 6.1 stable systems that I would like to enforce password
histories on. pam_unix, pam_passwdqc and login.conf do not seem to support
this functionality. Does anyone have any suggestions? Thanks.
-Joshua
___
freebsd-questions@freebsd.org ma
Aloha,
I have been trying the new FreeBSD 8 Current, Head and Beta* on an AMD64
box with 2 CPU's. The OS loads and everything works under all versions
including i386, but the key stroke history on csh does not survive over
a reboot or shutdown.
I have never seen this happen before
I'm working on a machine learning project and I'd like to use the FreeBSD
src CVS commit history as a datasource. Is there a resource-friendly way
for me to download some or all of it? Format isn't too big an issue.
I tried a few "cvs history" commands against the anon
I can run kbdcontrol -h 500 or vidcontrol -h 500 to set the
scroll back keyboard history buffer to 500 lines for the
virtual terminal I'm using. How can I make that happen at
boot, in the same manner as I run allscreens_flags in
rc.conf to set other terminal parameters? I don't nee
Hi, all
I'm now interested in BSD's history and have read
some of article from INTERNET. But because English
isn't my mother language so I havn't cleared
in the point of
1. What is the result of lawsuit between BSDi (maybe
include UC Berkeley) and USL in the early
Allthough I'm not familiar with the particular problem you
described, I observed that the history sometimes (!) does
not survive a reboot. It may have to do with a situation
where more than one shell is running. Idea: The last shell
closed (even forced) saves its history, so the history o
Polytropon wrote:
Allthough I'm not familiar with the particular problem you
described, I observed that the history sometimes (!) does
not survive a reboot. It may have to do with a situation
where more than one shell is running. Idea: The last shell
closed (even forced) saves its histor
Al Plant wrote:
Polytropon wrote:
Allthough I'm not familiar with the particular problem you
described, I observed that the history sometimes (!) does
not survive a reboot. It may have to do with a situation
where more than one shell is running. Idea: The last shell
closed (even forced)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Nielsen wrote:
> I'm working on a machine learning project and I'd like to use the FreeBSD
> src CVS commit history as a datasource. Is there a resource-friendly way
> for me to download some or all of it? Format isn't
John Nielsen wrote:
> I'm working on a machine learning project and I'd like to use the FreeBSD
> src CVS commit history as a datasource. Is there a resource-friendly way
> for me to download some or all of it? Format isn't too big an issue.
>
> I tried a few &quo
On Fri, 24 Apr 2009 05:35:34 -0400, John Nielsen wrote:
> I'm working on a machine learning project and I'd like to use the
> FreeBSD src CVS commit history as a datasource. Is there a
> resource-friendly way for me to download some or all of it? Format
> isn't too big
On Saturday 25 April 2009 09:12:50 pm Giorgos Keramidas wrote:
> On Fri, 24 Apr 2009 05:35:34 -0400, John Nielsen
wrote:
> > I'm working on a machine learning project and I'd like to use the
> > FreeBSD src CVS commit history as a datasource. Is there a
> >
On Mon, 27 Apr 2009 11:23:32 -0400, John Nielsen wrote:
> On Saturday 25 April 2009 09:12:50 pm Giorgos Keramidas wrote:
>> On Fri, 24 Apr 2009 05:35:34 -0400, John Nielsen
> wrote:
>> > I'm working on a machine learning project and I'd like to use the
>>
; > and possibly diff size information, etc. I don't know anything about
> > the "history" file in particular other than that's what cvs
> > complained about when I tried the "cvs history" commands against
> > anoncvs. It looks like the /pub/FreeBSD/deve
On Mon, 27 Apr 2009 15:03:30 -0400, John Nielsen wrote:
> I installed the subversion-freebsd port and pulled in "src" from "head".
> This lets me do e.g. "svn log -g --xml" locally and get an XML list of
> commits along the main (head/current) development line going back to
> 1993.
>
> For files c
On Monday 27 April 2009 03:29:03 pm Giorgos Keramidas wrote:
> On Mon, 27 Apr 2009 15:03:30 -0400, John Nielsen
wrote:
> > I installed the subversion-freebsd port and pulled in "src" from
> > "head". This lets me do e.g. "svn log -g --xml" locally and get an
> > XML list of commits along the main
It doesn't work for me when placed in rc.conf, with either
a direct command or attempting to use allscreens_flags.
I run 5.2.1 myself, but if anything I write is incorrect
for 4.10 someone will surely correct me shortly.
It looks to me like you've been putting your parameter in
the wrong string; as
Jan Christian Meyer wrote:
> If you still need to do shell stuff on startup, slapping
> together a script and putting it in rc.d is the way to go.
> The man pages of rc explain the works, and include a
> template script which you can copy and fill in.
Wow! There's a lot there, in man rc. I'll pla
hi,
does anyone know how the "history" output can display date/timestamps?
rgds
ernest
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Monday 21 July 2003 12:15 am, Supote Leelasupphakorn wrote:
> Hi, all
>
>I'm now interested in BSD's history and have read
> some of article from INTERNET. But because English
> isn't my mother language so I havn't cleared
> in the point of
Please post
I read from
http://www.extremetech.com/article2/0,3973,555398,00.asp.
Thank you very much,
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/
_
>
> I read from
> http://www.extremetech.com/article2/0,3973,555398,00.asp.
Here are some more sites.
http://www.levenez.com/unix/
http://www.levenez.com/unix/history.html
http://scnc.k12.mi.us/websites/bsdtree.html/
http://www.asandler.com/jokes/computer/c.shtml/
The
Jerry McAllister wrote:
> > I read from
> > http://www.extremetech.com/article2/0,3973,555398,00.asp.
>
> Here are some more sites.
>
> http://www.levenez.com/unix/
>
> http://www.levenez.com/unix/history.html
>
> http://scnc.k12.mi.us/websites/bsdtree.html/
>
> http://www.asand
I'm not sure what's going on, as I've never had an issue like this in my
years of using FreeBSD nor Linux. Each time I login, my history file is
empty! I'm not sure what could be causing this, but below [1] is my
.bashrc. I had ". ~/.bashrc" in ~/.profi
. Almost all
commands I enter in a login session are forgotten in the next session. Using
the Up and Down arrow keys navigates a mangled and incomlete command
history. Even using Ctrl-r for a reverse find almost never fetches a command
I had actually typed in previously.
The following are the
In the last episode (May 06), Clement Twine said:
> does anyone know how the "history" output can display
> date/timestamps?
If you use zsh, run "history -i". If you want timestamps in your
~/.history file as well, add "setopt extendedhistory" to your zsh
sta
On Monday 07 January 2013 7:01:09 pm Andre Goree wrote:
> I'm not sure what's going on, as I've never had an issue
> like this in my years of using FreeBSD nor Linux. Each
> time I login, my history file is empty! I'm not sure
> what could be causing this, but b
On Tue, 08 Jan 2013 07:59:51 -0500, Dimitri Yioulos
wrote:
Hope I'm not offending you if the following are things
you've tried as a matter-of-course:
After booting up, is history started, or do you have to do
that manually? Have you run "set -o" to see if history is
e
On Tue, 8 Jan 2013 09:05-0500, Andre Goree wrote:
> On Tue, 08 Jan 2013 07:59:51 -0500, Dimitri Yioulos
> wrote:
>
> >
> > Hope I'm not offending you if the following are things
> > you've tried as a matter-of-course:
> >
> > After booting up,
;ve tried as a matter-of-course:
>>>
>>> After booting up, is history started, or do you have to do
>>> that manually? Have you run "set -o" to see if history is
>>> enabled? If it isn't, then "set -o history". Is a "clear"
&g
> I think I've found the culprit, however:
> [agoree@desktop ~]$ echo $HISTFILESIZE
> 1024000
> [agoree@desktop ~]$ echo $HISTFILE
> /home/agoree/.bash_history
> [agoree@desktop ~]$ ll /home/agoree/.bash_history
> -rw--- 1 agoree agoree12k Jan 5 14:09 /home/agoree/.bash_history
> [agore
On Tue, 8 Jan 2013 18:49-0500, Andre Goree wrote:
>
> > I think I've found the culprit, however:
> > [agoree@desktop ~]$ echo $HISTFILESIZE
> > 1024000
> > [agoree@desktop ~]$ echo $HISTFILE
> > /home/agoree/.bash_history
> > [agoree@desktop ~]$ ll /home/agoree/.bash_history
> > -rw--- 1 ago
Hello there
Could someone would like to describe that how we can disable to show last
executed commands by pressing Up Arrow?
--
Thanks!
BR / vj
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Jay O'Brien wrote:
> I can run kbdcontrol -h 500 or vidcontrol -h 500 to set the
> scroll back keyboard history buffer to 500 lines for the
> virtual terminal I'm using. How can I make that happen at
> boot, in the same manner as I run allscreens_flags in
> rc.c
On 08/18/04 12:01 AM, Jay O'Brien sat at the `puter and typed:
> Jay O'Brien wrote:
>
> > I can run kbdcontrol -h 500 or vidcontrol -h 500 to set the
> > scroll back keyboard history buffer to 500 lines for the
> > virtual terminal I'm using. How can I mak
s to work with
either it's ksh, or ksh93 (which I thought would be the same as the ATT&T
version, since it's code is now free). But so far I've not been able to get
this to work.
To be specific, what I want is to be able to press [ESC} and be in the ex
(line mode) editor on the co
Title: Soul-Patrol Newsletter # 4: Black History Month, Soul,
Jazz, Slow Jams, Black Rock, Funk, Doo Wop, Neo Soul, Tom Joyner,
Jazzhole, Victor Wooten, Harptones, Michael B Sutton,
Issue #4
Click Here to
Subscribe/Unsubscribe For
Your Free Bi-Monthly Issue!
Soul-Patrol.Com
VeeJay wrote:
Hello there
Could someone would like to describe that how we can disable to show last
executed commands by pressing Up Arrow?
That would depend on which shell you are running. Can you run the
following command and post the results here?
echo $SHELL
-- Chris
--
__o
following command and post the results here?
echo $SHELL
By default most of the shells like bash, zsh, ksh have history option.
But you can avoid writing the history of the current session to the
history file by unsetting the HISTFILE environment variable.
So next time when you login the hi
gt;
>> That would depend on which shell you are running. Can you run the
>> following command and post the results here?
>>
>> echo $SHELL
>
> By default most of the shells like bash, zsh, ksh have history option.
> But you can avoid writing the history of
in message
<[EMAIL PROTECTED]>, wrote
sac thusly...
>
> > VeeJay wrote:
> > >
> > > Could someone would like to describe that how we can disable
> > > to show last executed commands by pressing Up Arrow?
...
> By default most of the shells like bash,
That would depend on which shell you are running. Can you run the
>> following command and post the results here?
>>
>> echo $SHELL
>
> By default most of the shells like bash, zsh, ksh have history option.
> But you can avoid writing the history of the current session t
e (honestly!) thought that
/bin/sh _when called as such_ would save
a history*.
Glancing at man sh cured me of that notion.
* I mean, it's a primitive piece of crap, in its
own special way, but that's how /bin/sh is
supposed to respond, AFIK? Syntax confu-
sing is, never the sam
on, see if sh looks for ~/.logout. If
it does, have it remove ~/.history and clear the screen. Or, if the
order of that doesn't work (if .logout is read /before/ .history is
written), 'chmod 000 .history'.
Best of luck,
Kevin
___
freebsd-questio
hings to worry about.
good point. I do have this done in my laptop, only because I can :D (and a bit
harder for someone to know what u're supposed to do to mount the encrypted
drives big deal :D )
anyway, I just linked ~/.bash_history to /dev/null - history works within the
current shell,
I have a 4.8 installation with a root account and one user account. The root
account up-arrow history retrieve feature works fine, while on my user
account it doesn't, displaying instead
$ ^[[A^[[C^[[B^[[D
when I press the arrow keys in order (up, right, down, left)
What is missing to hav
Aloha,
Terminal history gone.
I cannot get any recent version of FreeBSD 8.* to keep the csh or tcsh
history across a "reboot" in root or usr. It stays after "exit" and a
new login however. This happens on several machines that previously ran
FreeBSD 7* with no issues. On
stan <[EMAIL PROTECTED]> writes:
> I've now got a 4.7 STABLE machine, and I'm trying to get this to work with
> either it's ksh, or ksh93 (which I thought would be the same as the ATT&T
> version, since it's code is now free). [...]
"No cost", lest anyone misunderstand. The ksh93 license has lot
"Marty Landman" <[EMAIL PROTECTED]> writes:
> I have a 4.8 installation with a root account and one user account. The root
> account up-arrow history retrieve feature works fine, while on my user
> account it doesn't, displaying instead
>
> $ ^[[A^[[C^[[B^[[
in message <[EMAIL PROTECTED]>,
wrote Lowell Gilbert thusly...
>
> "Marty Landman" <[EMAIL PROTECTED]> writes:
>
> > I have a 4.8 installation ... The root account up-arrow
> > history retrieve feature works fine, while on my user account it
> &g
Hey thanks, I added that line to my .profile and am in like Flynn now.
Marty
On 7/11/06, Lowell Gilbert <[EMAIL PROTECTED]> wrote:
"Marty Landman" <[EMAIL PROTECTED]> writes:
> $ ^[[A^[[C^[[B^[[D
>
> when I press the arrow keys in order (up, right, down, left)
They are using different shells
I want to be able to define groups of interactive
shells (preferably even across different users)
so they have one single shared command history.
Any command executed in one of them should be
available through all history mechanisms in the
other ones.
I imagine some ways to do it in tcsh. I&#
On Wed, 19 Aug 2009, Al Plant wrote:
Aloha,
Terminal history gone.
I cannot get any recent version of FreeBSD 8.* to keep the csh or tcsh
history across a "reboot" in root or usr. It stays after "exit" and a new
login however.
Does the history stick around if you
Warren Block wrote:
On Wed, 19 Aug 2009, Al Plant wrote:
Aloha,
Terminal history gone.
I cannot get any recent version of FreeBSD 8.* to keep the csh or tcsh
history across a "reboot" in root or usr. It stays after "exit" and a
new login however.
Does the history st
On Wed, 19 Aug 2009, Al Plant wrote:
Warren Block wrote:
On Wed, 19 Aug 2009, Al Plant wrote:
Terminal history gone.
I cannot get any recent version of FreeBSD 8.* to keep the csh or tcsh
history across a "reboot" in root or usr. It stays after "exit" and a new
login
What can I do to get the history to remain in memory across a
reboot? Changing the capicity of set history to greater than 100
does not affect it.
How about:
shutdown -r +1
logout
-Reko
___
freebsd-questions@freebsd.org mailing list
http
ing a "zpool history" I started thinking that a ZFS
create and destroy being performed every minute would add up to a lot over
the course of a few years (current estimate is 62MB/year for the naming scheme
of my snapshots).
>From what I understand, ZFS compresses metadata by defaul
the normal output of the history command resembles:
1 env
2 ssh system1.somedomain.com
3 scan cur
etc.
On occasion, I have seen a history output that shows the
list of commands plus the time they were executed. I am not sure
exactly how I got that output as I couldn&#
Hi guys,
I've been trying to delete one line from my user tcsh history cause i made a
su and it seems didnt hit enter very well so i typed the password on the
console...Now anyone that can look my history will see my pass...
I tried to edit and delete a few lines but it all comes again
Hello!
I've long wondered where this error message comes from:
"hostname nor servname provided, or not known"
So I grepped my FreeBSD source code and found out it actually belongs to BIND9.
It has to be the worst written error message in history.
Any chance you can change
=?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes:
> It has to be the worst written error message in history.
Not even close. I commend to you the Amiga's BSOD:
Software Guru
Meditatio
On 11/29/06, Andrew Pantyukhin <[EMAIL PROTECTED]> wrote:
I want to be able to define groups of interactive
shells (preferably even across different users)
so they have one single shared command history.
Any command executed in one of them should be
available through all history mechani
On Wed, 29 Nov 2006, Andrew Pantyukhin wrote:
> I want to be able to define groups of interactive
> shells (preferably even across different users)
> so they have one single shared command history.
> Any command executed in one of them should be
> available through all history me
On 11/30/06, Jan Grant <[EMAIL PROTECTED]> wrote:
On Wed, 29 Nov 2006, Andrew Pantyukhin wrote:
> I want to be able to define groups of interactive
> shells (preferably even across different users)
> so they have one single shared command history.
> Any command executed in one
of what you're after).
Combine this with a shared .history file and you should get the
effect
you're after.
I think, I'll follow your advice. It's high time I forgot about
csh, but I wonder if you tried to change root's shell to zsh?
ZSH is a remarkably good cho
On Thu, 30 Nov 2006, Andrew Pantyukhin wrote:
> I think, I'll follow your advice. It's high time I forgot about
> csh, but I wonder if you tried to change root's shell to zsh?
You can; I haven't. ("exec zsh" is simple to type.) sudo works well for
single commands. I don't tend to spend much time
On 11/30/06, Jan Grant <[EMAIL PROTECTED]> wrote:
On Thu, 30 Nov 2006, Andrew Pantyukhin wrote:
> I think, I'll follow your advice. It's high time I forgot about
> csh, but I wonder if you tried to change root's shell to zsh?
You can; I haven't. ("exec zsh" is simple to type.) sudo works well fo
ith hard drive sizes being what they
> are these days, but after running a "zpool history" I started
> thinking that a ZFS create and destroy being performed every minute
> would add up to a lot over the course of a few years (current
> estimate is 62MB/year for the naming s
ailable for a given window of time.
> >
> > This may seem a trivial concern with hard drive sizes being what they
> > are these days, but after running a "zpool history" I started
> > thinking that a ZFS create and destroy being performed every minute
>
Martin McCormick wrote:
the normal output of the history command resembles:
1 env
2 ssh system1.somedomain.com
3 scan cur
etc.
On occasion, I have seen a history output that shows the
list of commands plus the time they were executed. I am not sure
exactly how I got
At 2009-04-23T15:31:51-05:00, Martin McCormick wrote:
> On occasion, I have seen a history output that shows the
> list of commands plus the time they were executed. I am not sure
> exactly how I got that output as I couldn't duplicate it on
> demand. Any ideas on what
Matthew Seaman writes:
> tcsh(1) includes timestamps in it's .history. bash(1) doesn't.
> Not sure about other shells, but the historical (ahem!) behaviour
>
> of csh(1) was not to use timestamps, and I think most shells subsequently
> developed have carried on the
At 2009-04-24T08:35:22-05:00, Martin McCormick wrote:
> Thanks to you and "N. Raghavendra"
> for your help. That has got to be what I did.
You are welcome :-)
Raghavendra.
--
N. Raghavendra | http://www.retrotexts.net/
Harish-Chandra Research Institute | http://www.mri.ernet.in/
See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Agus wrote:
| Hi guys,
|
| I've been trying to delete one line from my user tcsh history cause i
made a
| su and it seems didnt hit enter very well so i typed the password on the
| console...Now anyone that can look my history will see my
Agus wrote:
> I've been trying to delete one line from my user tcsh history cause i made a
> su and it seems didnt hit enter very well so i typed the password on the
> console...Now anyone that can look my history will see my pass...
>
> I tried to edit and delete a few li
2008/5/15 Pietro Cerutti <[EMAIL PROTECTED]>:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
> Agus wrote:
> | Hi guys,
> |
> | I've been trying to delete one line from my user tcsh history cause i
> made a
> | su and it seems didnt hit enter
On Thu, 31 May 2007 08:38:41 -0400
Robert Huff <[EMAIL PROTECTED]> wrote:
>
> =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes:
>
> > It has to be the worst written error message in history.
>
> Not even close. I comm
> > > It has to be the worst written error message in history.
> >
> >Not even close. I commend to you the Amiga's BSOD:
> >
> > Software Guru
> >Meditation Number
&
>
>
> > > > It has to be the worst written error message in history.
> > >
> > > Not even close. I commend to you the Amiga's BSOD:
> > >
> > >Software Gur
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Robert Huff
> Sent: Thursday, May 31, 2007 5:39 AM
> To: [EMAIL PROTECTED]
> Subject: The worst error message in history belongs to... BIND9!
>
>
>
> =?iso-8859-1?Q?Kyrre_Ny
On Thursday 31 May 2007, Tom Wilson wrote:
> I always liked one of the messages from an old version of the VMS (4 or 5?)
> C compiler(may not be exactly it, but this was included):
>
> Bad Code
Or the Level I BASIC error messages on a TRS-80.
What?
How?
Sorry?
And that's all folks. The entire
At 14:38 31/05/2007, Robert Huff wrote:
=?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes:
> It has to be the worst written error message in history.
Not even close. I commend to you the Amiga's BSOD:
Softw
On Jun 5, 2007, at 4:39 PM, Eduardo Morras wrote:
At 14:38 31/05/2007, Robert Huff wrote:
=?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes:
> It has to be the worst written error message in history.
Not even close. I commend to you the Amiga
Jeffrey Goldberg writes:
> I still remember as a newcomer to Unix a long long time ago getting
>
> "Bad magic number"
>
>
> In retrospect, I suspect that I'd typed "ld" where I'd meant to type "ls".
I have been doing things on Unix systems since about
1990 and the thing I run across
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Martin
> McCormick
>
> Then, there is the ultimate, the "Check engine." light on the
> modern car.
Check engine - CEL
> It would be so nice if it said some indication as to
> the seriousness of the pr
Reminds me of a typical windows user i dealt with who saw an error about
explorer.exe and how it could not "be read" and let it slide. :-P
using my wicked non user friendly skillz of the damned, i personally
like the concept of a simple "pebkac error" when bind refuses to start
due to a named
On Mon, Jul 02, 2007 at 03:11:56PM -0500, Martin McCormick wrote:
>
> #! /bin/sh
> a = 5
>
> that's enough to make it happen. Run that, and you get:
>
> a: not found
>
> Interestingly enough, if you run that same script in a
> Debian Linux environment, you get:
>
> ./testfile: line 2: a:
Paul Chvostek writes:
> This is actually just the difference between sh and bash. You'll see
> the latter error if you type `a = 5` in bash in any OS. It just so
> happens that most Linux distributions don't have a real sh:
I kind of thought that was the real issue. While
something like
On Tue, 03 Jul 2007 08:44:14 -0500
Martin McCormick <[EMAIL PROTECTED]> wrote:
> Paul Chvostek writes:
> > This is actually just the difference between sh and bash. You'll
> > see the latter error if you type `a = 5` in bash in any OS. It
> > just so happens that most Linux distributions don't h
o:[EMAIL PROTECTED]
> Sent: Tuesday, July 03, 2007 2:24 AM
> To: Ted Mittelstaedt
> Cc: freebsd-questions@freebsd.org
> Subject: Re: The worst error message in history belongs to... BIND9!
>
>
> Reminds me of a typical windows user i dealt with who saw an error about
> expl
On Tue, Jul 03, 2007, Martin McCormick wrote:
>Paul Chvostek writes:
>> This is actually just the difference between sh and bash. You'll see
>> the latter error if you type `a = 5` in bash in any OS. It just so
>> happens that most Linux distributions don't have a real sh:
>
> I kind of tho
On Tue, 2007-07-03 at 09:36 -0700, Bill Campbell wrote:
> On Tue, Jul 03, 2007, Martin McCormick wrote:
> >Paul Chvostek writes:
> >> This is actually just the difference between sh and bash. You'll see
> >> the latter error if you type `a = 5` in bash in any OS. It just so
> >> happens that most
> >> This is actually just the difference between sh and bash ...
> >
> >differences in, say, arithmetic handling and loops can sometimes
> >mean rewriting parts of shell scripts depending on whether it is
> >going to run in BSD or Linux.
>
> That's a major argument for doing things in python or pe
On Tue, Jul 03, 2007 at 07:34:20PM -0700, [EMAIL PROTECTED] wrote:
> > >> This is actually just the difference between sh and bash ...
> > >
> > >differences in, say, arithmetic handling and loops can sometimes
> > >mean rewriting parts of shell scripts depending on whether it is
> > >going to run
Chad Perrin writes:
> Isn't Perl part of the base system these days?
Perl has not been part of the base system for several years and
was deprecated for some time before that.
Robert Huff
___
freebsd-questions@freebsd.
1 - 100 of 152 matches
Mail list logo
