Re: The question of moving vi to /bin

2009-06-29 Thread Charlie Kester
Of RW Sent: Sunday, June 28, 2009 10:21 PM To: freebsd-questions@freebsd.org Subject: Re: The question of moving vi to /bin On Thu, 25 Jun 2009 16:15:12 -0500 "Gary Gatten" wrote: I like M$ "Notepad" - is there a version of that for FBSD? Actually, there is. Wine implements

RE: The question of moving vi to /bin

2009-06-29 Thread Gary Gatten
-questions@freebsd.org Subject: Re: The question of moving vi to /bin On Thu, 25 Jun 2009 16:15:12 -0500 "Gary Gatten" wrote: > I like M$ "Notepad" - is there a version of that for FBSD? Actually, there is. Wine implements it&#

Re: The question of moving vi to /bin

2009-06-29 Thread Manish Jain
Daniel Underwood wrote: How did "The question of moving vi to /bin" end up as two different conversations for me in gmail? Hello Daniel, When I did a 'Reply to All', the moderator blocked the posting claiming too high a number of recipients. I cancelled the posting,

Re: The question of moving vi to /bin

2009-06-28 Thread Glyn Millington
Polytropon writes: > When Bill G. arrives at the pearly gate, ol' Pete won't ask > him what he did do, instead send him to MICROS~1 C:\HELL.EXE > with the advice to click on the devil to start the everlasting > pain. :-) Brilliant!! atb Glyn

Re: The question of moving vi to /bin

2009-06-28 Thread RW
On Thu, 25 Jun 2009 16:15:12 -0500 "Gary Gatten" wrote: > I like M$ "Notepad" - is there a version of that for FBSD? Actually, there is. Wine implements it's own version of notepad. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.

Re: The question of moving vi to /binHi,

2009-06-28 Thread Glen Barber
On Fri, Jun 26, 2009 at 1:23 AM, Gary Kline wrote: [snip] > >        what about j, k [down, up].  and h,l  [left, right]? >        why reach over for the arrow keys!  oh, and o, and O >        [open line below/Above], and > >        \search > >        and that's 97 and 44/100ths of what you'll

Re: The question of moving vi to /binHi,

2009-06-28 Thread Gary Kline
On Fri, Jun 26, 2009 at 06:11:57AM +0200, Polytropon wrote: > On Fri, 26 Jun 2009 12:03:21 +0800, Erich Dollansky > wrote: > > What kind of editor do you need for rescue? Just edit one or two > > lines in some config file to allow the full system to start > > again. > > > > Rescue does not nee

Re: The question of moving vi to /bin

2009-06-28 Thread Gary Kline
On Fri, Jun 26, 2009 at 08:01:02AM +0200, Polytropon wrote: > On Thu, 25 Jun 2009 22:23:17 -0700, Gary Kline wrote: > > what about j, k [down, up]. and h,l [left, right]? > > why reach over for the arrow keys! oh, and o, and O > > [open line below/Above], and > > > > \search >

Re: The question of moving vi to /bin

2009-06-28 Thread Erich Dollansky
Hi, On 26 June 2009 pm 14:01:02 Polytropon wrote: > On Thu, 25 Jun 2009 22:23:17 -0700, Gary Kline wrote: > have a "vi keyboard reference" in my "extremely important > documentation folder" - and yes, it is a real folder, not a > directory. :-) So if everything fails, there's still vi and > the

Re: The question of moving vi to /bin

2009-06-28 Thread Polytropon
On Thu, 25 Jun 2009 22:23:17 -0700, Gary Kline wrote: > what about j, k [down, up]. and h,l [left, right]? > why reach over for the arrow keys! oh, and o, and O > [open line below/Above], and > > \search > > and that's 97 and 44/100ths of what you'll ever need.

Re: The question of moving vi to /bin

2009-06-28 Thread Polytropon
On Thu, 25 Jun 2009 16:15:12 -0500, "Gary Gatten" wrote: > I like M$ "Notepad" - is there a version of that for FBSD? You are on the wrong list. Correct your inner state of mind and try again. :-) No, seriously: Maybe gnotepad+ appeals to you? > Actually the old "edit" from dos is sweet too..

Re: The question of moving vi to /binHi,

2009-06-28 Thread Chris Rees
2009/6/28 Mark E Doner : > Erich Dollansky wrote: >> >> On 26 June 2009 am 10:02:30 Polytropon wrote: >> >>> >>> Polytropon >>> From Magdeburg, Germany >>> >> >> big brother is watching me. >> >> An xterm just came up with this message: >> >> "The default editor in FreeBSD is vi, which is efficient

Re: The question of moving vi to /binHi,

2009-06-28 Thread Mark E Doner
Erich Dollansky wrote: On 26 June 2009 am 10:02:30 Polytropon wrote: Polytropon From Magdeburg, Germany big brother is watching me. An xterm just came up with this message: "The default editor in FreeBSD is vi, which is efficient to use when you have learned it, but somewhat user-un

Re: The question of moving vi to /bin

2009-06-27 Thread Manish Jain
Hi, I agree that vi is nowhere as easy to use as ee. Since a lot of people seem to be happy with ee, why not make it available under /bin so that that there is an easy-to-use, readily-working editor always available, even if you are in single-user mode ? That in fact was the essence of this

Re: The question of moving vi to /bin

2009-06-26 Thread Daniel Underwood
> That's a very good suggestion. But let's take into mind that we > do need the most advanced and modern MICROS~1 technology, so > FreeBSD should include a pirated copy of "Windows 7" in order > to run the latest and most expensive pirated copy of "Office", > programmed in Java, running through "Fl

Re: The question of moving vi to /bin

2009-06-26 Thread Erich Dollansky
Hi, On 27 June 2009 am 07:08:01 Polytropon wrote: > On Fri, 26 Jun 2009 15:40:50 +0800, Erich Dollansky wrote: > > On 26 June 2009 pm 14:01:02 Polytropon wrote: > > > Maybe this is because vi scared me when using WEGA (which > > > is the GDR's equivalent of UNIX System III, run on the > > > P800

Re: The question of moving vi to /bin

2009-06-26 Thread Polytropon
On Fri, 26 Jun 2009 15:40:50 +0800, Erich Dollansky wrote: > On 26 June 2009 pm 14:01:02 Polytropon wrote: > > Maybe this is because vi scared me when using WEGA (which is > > the GDR's equivalent of UNIX System III, run on the P8000 > > was this the russian PDP-11? I'm not sure if there was a P

Re: Editor in minimal system (was Re: The question of moving vi to /bin)

2009-06-26 Thread Gary Kline
On Fri, Jun 26, 2009 at 09:59:28AM +0200, Jonathan McKeown wrote: > This whole thread only really got started because I questioned Manish Jain's > assertion that there was no editor available in /bin. > > To summarise: > > There are several editors available ranging from ed (49604 bytes) and ee

Re: The question of moving vi to /binHi,

2009-06-26 Thread Chris Rees
2009/6/26 Glen Barber : > On Fri, Jun 26, 2009 at 12:11 AM, Polytropon wrote: >> On Fri, 26 Jun 2009 12:03:21 +0800, Erich Dollansky >> wrote: >>> What kind of editor do you need for rescue? Just edit one or two >>> lines in some config file to allow the full system to start >>> again. >>> >>> Re

Editor in minimal system (was Re: The question of moving vi to /bin)

2009-06-26 Thread Jonathan McKeown
This whole thread only really got started because I questioned Manish Jain's assertion that there was no editor available in /bin. To summarise: There are several editors available ranging from ed (49604 bytes) and ee (60920 bytes) (both with two library dependencies) to emacs (in ports; 59926

Re: The question of moving vi to /bin

2009-06-26 Thread Chris Rees
2009/6/25 Gary Gatten : > I like M$ "Notepad" - is there a version of that for FBSD? Actually the old > "edit" from dos is sweet too > I'll humour you... gedit is similar and better than notepad for BSD, but there's nothing like 'edit' (actually a stripped down QBasic) AFAIK. Maybe you should

Re: The question of moving vi to /bin

2009-06-25 Thread Gary Kline
On Fri, Jun 26, 2009 at 12:31:37PM +0800, Erich Dollansky wrote: > Hi, > > On 26 June 2009 pm 12:19:32 Gary Kline wrote: > > On Fri, Jun 26, 2009 at 09:50:31AM +0800, Erich Dollansky wrote: > > > > > > On 26 June 2009 am 09:06:49 Giorgos Keramidas wrote: > > > > On Fri, 26 Jun 2009 08:20:19 +0800,

Re: The question of moving vi to /bin

2009-06-25 Thread Gary Kline
On Thu, Jun 25, 2009 at 09:09:56PM -0400, John L. Templer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > per...@pluto.rain.com wrote: > >> ed is an interactive program, and it has always been considered as > >> such, at least since BSD 4.2. Way back then there were three main > >> e

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 26 June 2009 pm 12:19:32 Gary Kline wrote: > On Fri, Jun 26, 2009 at 09:50:31AM +0800, Erich Dollansky wrote: > > > > On 26 June 2009 am 09:06:49 Giorgos Keramidas wrote: > > > On Fri, 26 Jun 2009 08:20:19 +0800, Erich Dollansky > > > > wrote: > > > >On 25 June 2009 pm 19:13:14 Konrad Heue

Re: The question of moving vi to /bin

2009-06-25 Thread Gary Kline
On Fri, Jun 26, 2009 at 09:50:31AM +0800, Erich Dollansky wrote: > Hi, > > On 26 June 2009 am 09:06:49 Giorgos Keramidas wrote: > > On Fri, 26 Jun 2009 08:20:19 +0800, Erich Dollansky > wrote: > > >On 25 June 2009 pm 19:13:14 Konrad Heuer wrote: > > >> Maybe you're right, maybe not. > > >> > > >

Re: The question of moving vi to /binHi,

2009-06-25 Thread Glen Barber
On Fri, Jun 26, 2009 at 12:11 AM, Polytropon wrote: > On Fri, 26 Jun 2009 12:03:21 +0800, Erich Dollansky > wrote: >> What kind of editor do you need for rescue? Just edit one or two >> lines in some config file to allow the full system to start >> again. >> >> Rescue does not need an editor prog

Re: The question of moving vi to /binHi,

2009-06-25 Thread Polytropon
On Fri, 26 Jun 2009 12:03:21 +0800, Erich Dollansky wrote: > What kind of editor do you need for rescue? Just edit one or two > lines in some config file to allow the full system to start > again. > > Rescue does not need an editor programmers are used to edit their > source files. I won't sa

Re: The question of moving vi to /binHi,

2009-06-25 Thread Erich Dollansky
Hi, On 26 June 2009 am 10:58:08 Polytropon wrote: > On Fri, 26 Jun 2009 10:33:56 +0800, Erich Dollansky wrote: > > On 26 June 2009 am 10:02:30 Polytropon wrote: > > > Polytropon > > > From Magdeburg, Germany > > > > big brother is watching me. > > Yes, Dr. Schäuble does so. :-) > yeah, he rolls

Re: The question of moving vi to /binHi,

2009-06-25 Thread Polytropon
On Fri, 26 Jun 2009 10:33:56 +0800, Erich Dollansky wrote: > > On 26 June 2009 am 10:02:30 Polytropon wrote: > > Polytropon > > From Magdeburg, Germany > > big brother is watching me. Yes, Dr. Schäuble does so. :-) > An xterm just came up with this message: > > "The default editor in FreeBS

Re: The question of moving vi to /binHi,

2009-06-25 Thread Erich Dollansky
On 26 June 2009 am 10:02:30 Polytropon wrote: > Polytropon > From Magdeburg, Germany big brother is watching me. An xterm just came up with this message: "The default editor in FreeBSD is vi, which is efficient to use when you have learned it, but somewhat user-unfriendly. To use ee (an easi

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 26 June 2009 am 10:02:30 Polytropon wrote: > On Fri, 26 Jun 2009 09:55:48 +0800, Erich Dollansky wrote: > > this is not what I mean. I wanted to say, as long as the boot > > disk come up, I also have /usr available when I have the > > space to have it all on the same disk. > > I see. The

Re: The question of moving vi to /bin

2009-06-25 Thread Polytropon
On Fri, 26 Jun 2009 09:55:48 +0800, Erich Dollansky wrote: > this is not what I mean. I wanted to say, as long as the boot disk > come up, I also have /usr available when I have the space to have > it all on the same disk. I see. The fact that /usr isn't available after booting in maintenance m

Re: The question of moving vi to /bin

2009-06-25 Thread Giorgos Keramidas
On Fri, 26 Jun 2009 09:50:31 +0800, Erich Dollansky wrote: > On 26 June 2009 am 09:06:49 Giorgos Keramidas wrote: >> As far as 16 years back, VT220/VT320 terminals were in wide use >> in universities. Some of us learned our first regexp stuff by > > not only there, but ed was not the editor of ch

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 26 June 2009 am 09:07:00 Polytropon wrote: > On Fri, 26 Jun 2009 08:24:13 +0800, Erich Dollansky wrote: > > To be honest, I never have had a problem with /usr since > > disks are large enough to have all on only one. > > Mostly, partitioning according to directory structures has > nothing

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 26 June 2009 am 09:06:49 Giorgos Keramidas wrote: > On Fri, 26 Jun 2009 08:20:19 +0800, Erich Dollansky wrote: > >On 25 June 2009 pm 19:13:14 Konrad Heuer wrote: > >> Maybe you're right, maybe not. > >> > >> 20 years ago, I've written and edited voluminous fortran > >> code on a silly rs2

Re: The question of moving vi to /bin

2009-06-25 Thread John L. Templer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 per...@pluto.rain.com wrote: >> ed is an interactive program, and it has always been considered as >> such, at least since BSD 4.2. Way back then there were three main >> editors, ex, vi, and ed. > > ed goes back at least as far as the Bell Labs 6th

Re: The question of moving vi to /bin

2009-06-25 Thread Polytropon
On Fri, 26 Jun 2009 08:24:13 +0800, Erich Dollansky wrote: > To be honest, I never have had a problem with /usr since disks are > large enough to have all on only one. Mostly, partitioning according to directory structures has nothing to do with disk space, but with intention. There are many man

Re: The question of moving vi to /bin

2009-06-25 Thread Giorgos Keramidas
On Fri, 26 Jun 2009 08:20:19 +0800, Erich Dollansky wrote: >On 25 June 2009 pm 19:13:14 Konrad Heuer wrote: >> Maybe you're right, maybe not. >> >> 20 years ago, I've written and edited voluminous fortran code >> on a silly rs232 terminal using ed. So, it is possible, and one > > I do not believe

Re: The question of moving vi to /bin

2009-06-25 Thread John L. Templer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ruben de Groot wrote: > On Thu, Jun 25, 2009 at 01:36:31AM -0400, John L. Templer typed: >> ed is an interactive program, and it has always been considered as such, >> at least since BSD 4.2. Way back then there were three main editors, >> ex, vi, and

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Ho, On 26 June 2009 am 04:32:31 Erik Osterholm wrote: > On Thu, Jun 25, 2009 at 01:28:54PM +0800, Erich Dollansky wrote: > > On 25 June 2009 pm 13:03:01 Manish Jain wrote: > > > > If you want to make a case for replacing ed(1), you're > > > > isn't there ee in the base system? > > ee is in /usr/bi

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 25 June 2009 pm 19:13:14 Konrad Heuer wrote: > On Thu, 25 Jun 2009, Manish Jain wrote: > > Maybe you're right, maybe not. > > 20 years ago, I've written and edited voluminous fortran code > on a silly rs232 terminal using ed. So, it is possible, and one I do not believe you. This must have

Re: The question of moving vi to /bin

2009-06-25 Thread Gary Gatten
Jun 25 15:50:01 2009 Subject: Re: The question of moving vi to /bin > 20 years ago, I've written and edited voluminous fortran code on a silly > rs232 terminal using ed. So, it is possible, and one can learn basics of > ed in less than a hour. Don't you think so? > Not whe

Re: The question of moving vi to /bin

2009-06-25 Thread Tim Judd
> 20 years ago, I've written and edited voluminous fortran code on a silly > rs232 terminal using ed. So, it is possible, and one can learn basics of > ed in less than a hour. Don't you think so? > Not when editors like ee and vi are available and more spoken of in today's topics. And I know it

Re: The question of moving vi to /bin

2009-06-25 Thread Erik Osterholm
On Thu, Jun 25, 2009 at 01:28:54PM +0800, Erich Dollansky wrote: > Hi, > > On 25 June 2009 pm 13:03:01 Manish Jain wrote: > > > If you want to make a case for replacing ed(1), you're going > > > to have to come up with some concrete reasons for doing so, > > > not just make a (long and hyperbolic)

Re: The question of moving vi to /bin

2009-06-25 Thread Polytropon
On Thu, 25 Jun 2009 14:20:42 -0400, "ill...@gmail.com" wrote: > 2009/6/24 Manish Jain : > > everyone has hundreds of GB's > > on the disk > > No. No they don't. Please hang up and try again. If you need > to make a collect call, please dial zero to speak with an oper- > ator. Dial all the num

Re: The question of moving vi to /bin

2009-06-25 Thread ill...@gmail.com
2009/6/24 Manish Jain : > everyone has hundreds of GB's > on the disk No. No they don't. Please hang up and try again. If you need to make a collect call, please dial zero to speak with an oper- ator. -- -- ___ freebsd-questions@freebsd.org mailing

Re: The question of moving vi to /bin

2009-06-25 Thread Manish Jain
Ruben de Groot wrote: On Thu, Jun 25, 2009 at 01:36:31AM -0400, John L. Templer typed: ed is an interactive program, and it has always been considered as such, at least since BSD 4.2. Way back then there were three main editors, ex, vi, and ed. If you had a nice video terminal then you used vi

Re: The question of moving vi to /bin

2009-06-25 Thread Konrad Heuer
On Thu, 25 Jun 2009, Manish Jain wrote: If you want to make a case for replacing ed(1), you're going to have to come up with some concrete reasons for doing so, not just make a (long and hyperbolic) statement that you don't like it. Any Unix tool has to clearly fall either under the category

Re: The question of moving vi to /bin

2009-06-25 Thread Ruben de Groot
On Thu, Jun 25, 2009 at 01:36:31AM -0400, John L. Templer typed: > > ed is an interactive program, and it has always been considered as such, > at least since BSD 4.2. Way back then there were three main editors, > ex, vi, and ed. If you had a nice video terminal then you used vi. But > if you

Re: The question of moving vi to /bin

2009-06-25 Thread Manish Jain
John L. Templer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manish Jain wrote: If you want to make a case for replacing ed(1), you're going to have to come up with some concrete reasons for doing so, not just make a (long and hyperbolic) statement that you don't like it. Any Unix t

Re: The question of moving vi to /bin

2009-06-25 Thread perryh
> ed is an interactive program, and it has always been considered as > such, at least since BSD 4.2. Way back then there were three main > editors, ex, vi, and ed. ed goes back at least as far as the Bell Labs 6th Edition (PDP-11), where it was the only editor in the distribution. ex and vi (and

Re: The question of moving vi to /bin

2009-06-25 Thread Erich Dollansky
Hi, On 25 June 2009 pm 13:03:01 Manish Jain wrote: > > If you want to make a case for replacing ed(1), you're going > > to have to come up with some concrete reasons for doing so, > > not just make a (long and hyperbolic) statement that you > > don't like it. > > requirements of being interactive.

Re: The question of moving vi to /bin

2009-06-24 Thread John L. Templer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Manish Jain wrote: >> >> If you want to make a case for replacing ed(1), you're going to have >> to come up with some concrete reasons for doing so, not just make a >> (long and hyperbolic) statement that you don't like it. >> > > Any Unix tool has

Re: The question of moving vi to /bin

2009-06-24 Thread Manish Jain
If you want to make a case for replacing ed(1), you're going to have to come up with some concrete reasons for doing so, not just make a (long and hyperbolic) statement that you don't like it. Any Unix tool has to clearly fall either under the category of non-interactive (grep, sed, ex) or

Re: The question of moving vi to /bin

2009-06-24 Thread Bruce Cran
On Wed, 24 Jun 2009 06:13:49 -0700 "b. f." wrote: > ??? Who is giving them that credit? This isn't new. You already have > some control over swapping via several oids: > > vm.swap_enabled > vm.disable_swapspace_pageouts > vm.defer_swapspace_pageouts > vm.swap_idle_enabled > vm.swap_idle_thresh

Re: The question of moving vi to /bin

2009-06-24 Thread Chad Perrin
On Wed, Jun 24, 2009 at 06:13:49AM -0700, b. f. wrote: > > On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: > > >That's the whole problem of /rescue/vi. When you suddenly find yourself > >in single-user mode, the last thing you want to do is realise that > >tweaking is needed for something whic

Re: The question of moving vi to /bin

2009-06-24 Thread Chad Perrin
On Wed, Jun 24, 2009 at 04:22:19PM +0200, Jonathan McKeown wrote: > > You also suggested doing away with ed and /rescue/vi altogether. You may not > need statically-linked tools very often, but when you do need them, you > *REALLY* need them. Don't suggest throwing them away without thinking thr

Re: The question of moving vi to /bin

2009-06-24 Thread Jonathan McKeown
On Wednesday 24 June 2009 12:59:13 Manish Jain wrote: > About ed first. I might annoy a few people (which would gladden me in > this particular case), but ed was just one of Ken Thompson's nightmares > which he managed to reproduce in Unix with great precision. By no > stretch of imagination would

Re: The question of moving vi to /bin

2009-06-24 Thread Chris Rees
2009/6/24 cpghost : > On Wed, Jun 24, 2009 at 06:13:49AM -0700, b. f. wrote: >> > On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: >> >> >About ed first. I might annoy a few people (which would gladden me in >> >this particular case), but ed was just one of Ken Thompson's nightmares >> >which he

Re: The question of moving vi to /bin

2009-06-24 Thread cpghost
On Wed, Jun 24, 2009 at 06:13:49AM -0700, b. f. wrote: > > On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: > > >About ed first. I might annoy a few people (which would gladden me in > >this particular case), but ed was just one of Ken Thompson's nightmares > >which he managed to reproduce in U

Re: The question of moving vi to /bin

2009-06-24 Thread b. f.
> On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: ... >About ed first. I might annoy a few people (which would gladden me in >this particular case), but ed was just one of Ken Thompson's nightmares >which he managed to reproduce in Unix with great precision. By no >stretch of imagination woul

The question of moving vi to /bin

2009-06-24 Thread Manish Jain
On Tuesday 23 June 2009 15:41:48 Manish Jain wrote: > I hope the next release will address these problems, as well as a pretty > reasonable request from me much earlier to move vi from /usr/bin to > /bin. Even in single-user mode, you almost always need an editor. Which is why you have ed(

Re: To file a PR, or not to file a PR. That is the question.

2009-05-04 Thread Bill Moran
In response to Doug Poland : > Hello, > > A server running 7.1-RELEASE(i386) recently starting deadlocking when > multiple UFS2 snaphosts are being manipulated (via sysutil/freebsd-snapshot). > > Upon searching the PR database, I found a problem repart that appears > similar (kern/94769) but wit

To file a PR, or not to file a PR. That is the question.

2009-05-04 Thread Doug Poland
Hello, A server running 7.1-RELEASE(i386) recently starting deadlocking when multiple UFS2 snaphosts are being manipulated (via sysutil/freebsd-snapshot). Upon searching the PR database, I found a problem repart that appears similar (kern/94769) but with my level of expertise, I'm not certain. My

RE: The question about Broadcom BCM5721 ethernet adapter integrated in motherboard, on PCIe and FreeBSD6.3

2008-01-27 Thread Ted Mittelstaedt
There is no difference for this driver. Ted > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Leonid > Satanovsky > Sent: Sunday, January 27, 2008 2:11 AM > To: Ted Mittelstaedt > Cc: freebsd-questions@freebsd.org > Subject

Re: The question about Broadcom BCM5721 ethernet adapter integrated in motherboard, on PCIe and FreeBSD6.3

2008-01-27 Thread Leonid Satanovsky
IL PROTECTED] Behalf Of Leonid Satanovsky Sent: Saturday, January 26, 2008 4:13 AM To: freebsd-questions@freebsd.org Subject: The question about Broadcom BCM5721 ethernet adapter integrated in motherboard, on PCIe and FreeBSD6.3 Hi all! ---- The question is: wil

RE: The question about Broadcom BCM5721 ethernet adapter integrated in motherboard, on PCIe and FreeBSD6.3

2008-01-26 Thread Ted Mittelstaedt
ginal Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Leonid > Satanovsky > Sent: Saturday, January 26, 2008 4:13 AM > To: freebsd-questions@freebsd.org > Subject: The question about Broadcom BCM5721 ethernet adapter integrated > in motherboard, on

The question about Broadcom BCM5721 ethernet adapter integrated in motherboard, on PCIe and FreeBSD6.3

2008-01-26 Thread Leonid Satanovsky
Hi all! The question is: will FreeBSD 6.3 support Broadcom BCM5721 ethernet adapter integrated in motherboard (it's on PCIe bus) ? The motherboard is ASUSTeK P5M2-M

Re: The question that wont die: What size partitions should I make?

2005-12-07 Thread Martin Cracauer
I made a little guide about why and when to make seperate partitions here: http://cracauer-forum.cons.org/forum/partitions.html This is starting from the assumption that as few partitions as possible is the way to go, it lists reasons why you would want additional ones. Martin -- %%

Re: The question that wont die: What size partitions should I make?

2005-12-07 Thread Jerry McAllister
> > > I have dual-boot laptop, 30GB Fat32 Win2000 and 70GB FreeBSD 6.0-R. I > plan to use this for normal home desktop use (not as a server). I have > 512MB RAM. > > According to this page: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html > > I should us

Re: The question that wont die: What size partitions should I make?

2005-12-04 Thread wrangled
I'd make /home into a separate slice. Easier for backups. You can easily reinstall ports, but if you loose your personal data... Thats a good idea. I will digest what eveveryone said, and post what I did. Currently I'm installing Win2k, since this will be a dual-boot machine. FreeBSD is

Re: The question that wont die: What size partitions should I make?

2005-12-04 Thread Roland Smith
On Sun, Dec 04, 2005 at 01:40:01PM -0500, wrangled wrote: > > I have dual-boot laptop, 30GB Fat32 Win2000 and 70GB FreeBSD 6.0-R. I > plan to use this for normal home desktop use (not as a server). I have > 512MB RAM. > > According to this page: > > > http://www.freebsd.org/doc/en_US.ISO885

Re: The question that wont die:  What size parti tions should I         make?

2005-12-04 Thread Uncle Deejy-Pooh
> >I have dual-boot laptop, 30GB Fat32 Win2000 and 70GB FreeBSD 6.0-R. I > >plan to use this for normal home desktop use (not as a server). I have > >512MB RAM. > > According to this page: > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html > > I should use:

Re: The question that wont die: What size partitions should I make?

2005-12-04 Thread Subhro
wrangled sat at his 'puter and typed on 12/5/2005 0:10: I have dual-boot laptop, 30GB Fat32 Win2000 and 70GB FreeBSD 6.0-R. I plan to use this for normal home desktop use (not as a server). I have 512MB RAM. According to this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handboo

The question that wont die: What size partitions should I make?

2005-12-04 Thread wrangled
I have dual-boot laptop, 30GB Fat32 Win2000 and 70GB FreeBSD 6.0-R. I plan to use this for normal home desktop use (not as a server). I have 512MB RAM. According to this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html I should use: / = 100MB /swap

Re: The question about storege

2004-11-02 Thread Jeremy Faulkner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 捷洲資訊Kevin wrote: | Hallow Sir | | Can you tell me about tke FreeBSD can get how much maxma space in | partition. | I have one storege 15 BAYS and every BAY have 250GB HDD | When I greating 7 BAYS HDD in RAID5 | But I just only get 1TB | Can you tell m

The question about storege

2004-11-02 Thread 捷洲資訊Kevin
Hallow Sir Can you tell me about tke FreeBSD can get how much maxma space in partition. I have one storege 15 BAYS and every BAY have 250GB HDD When I greating 7 BAYS HDD in RAID5 But I just only get 1TB Can you tell me why??? Tks a lot B.R By Kevin JEH-CHOW INFORMATION CO., LTD ADD

Re: the question

2003-10-09 Thread Lowell Gilbert
reiser <[EMAIL PROTECTED]> writes: > I trying to install version 5.1 on my machine, wich is MSI mother of > 2002, GeForce-4, AMD AthlonXP, > HDD IBM Deskstar-60Gb, RAM 256 DDR, CDROM Samsung, CDRW Yamaha F1 > and after when system starts to copying files on a hard drive,-every > time the same tro

the question

2003-10-08 Thread reiser
Hi FreeBSD team! I trying to install version 5.1 on my machine, wich is MSI mother of 2002, GeForce-4, AMD AthlonXP, HDD IBM Deskstar-60Gb, RAM 256 DDR, CDROM Samsung, CDRW Yamaha F1 and after when system starts to copying files on a hard drive,-every time the same trouble, in 70% system says: