Doug White wrote:
Maxtor has a diag tool that goes onto a floppy that you could run. I have
this exact disk in my sparc64 here and the first time I used it, it kept
running over bad sectors and generally causing mayhem. Running the full
scan with the tool, it prompted to fix some problems, then th
On Wed, 3 Dec 2003, Dan Naumov wrote:
> causing this bizarre behavior ? If this is of any help, the exact model
> number of the HD is "MAXTOR 4K040H2" and I was using UFS2 on both
> drives. Thanks in advance.
Maxtor has a diag tool that goes onto a floppy that you could run. I have
this exact dis
Dan Naumov wrote:
What follows is a description of a problem I used to have when running
FreeBSD 5.0 and 5.1. [...] After the installation of the OS (usually
about 8-12 days of running non-stop) I start getting "Bad File
Descriptor" errors on random files all around the Maxtor drive and I
have
On Wed, Dec 03, 2003 at 05:55:29PM +0200, Dan Naumov wrote:
> Kris Kennaway wrote
>
> >You get that error from what command(s)? Have you tried with 5.2,
> >which has a new ATA driver?
> >
> >Kris
> >
> >
> I usually "discover" that I am having data corruption when trying to
> update ports. A fi
Kris Kennaway wrote
You get that error from what command(s)? Have you tried with 5.2,
which has a new ATA driver?
Kris
I usually "discover" that I am having data corruption when trying to
update ports. A file that has a "Bad File Descriptor" refuses to let
cvsup overwrite and/or remove itsel
On Wed, Dec 03, 2003 at 01:43:57PM +0200, Dan Naumov wrote:
> Hello
>
> What follows is a description of a problem I used to have when running
> FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am
> considering going back to it but I need to figure out how to prevent
> this issue
Hello
What follows is a description of a problem I used to have when running
FreeBSD 5.0 and 5.1. I am not running FreeBSD right now, but I am
considering going back to it but I need to figure out how to prevent
this issue from happening again. My system has 2 harddrives, a 16 GB
Seagate that
>Submitter-Id: current-users
>Originator:Vyacheslav I. Ivanchenko
>Confidential: no
>Synopsis: Port emulators/vmware3 + FreeBSD 5.x = kernel panic
>Severity: critical
>Priority: high
>Category: ports
>Class: sw-bug
>Release:
On Sat, Feb 08, 2003 at 01:23:58PM +0100, taxman wrote:
> Very detailed information for every commit can be found at:
> http://www.freebsd.org/cgi/cvsweb.cgi/
Adrian,
For your FreeBSD news article, if you want to get in contact with developers
who have added new things to FreeBSD, I recommend yo
on the new technologies introduced in FreeBSD
> 5.x.
excellent, the advocacy is welcome
> Where can I find a (preferrably detailed) list of the new technologies
> introduced with FreeBSD 5.x ?
http://www.freebsd.org/releases/5.0R/relnotes.html
for your given architecture is designed to give
[ Bcc'd to -current following initial crosspost. Followups to -hackers
or directly to Mr. Penisoara. ]
On Thu, Feb 06, 2003 at 03:17:15PM +0200, Adrian Penisoara wrote:
>
> Where can I find a (preferrably detailed) list of the new technologies
> introduced with FreeBSD 5.x ?
Gr
Hi,
I'm about to write an article on FreeBSD for PC Magazine Romania and I
would like to concentrate on the new technologies introduced in FreeBSD
5.x.
Where can I find a (preferrably detailed) list of the new technologies
introduced with FreeBSD 5.x ? I would also like, if possible, t
On 20-Jan-02 Robert Watson wrote:
>
> On Sat, 19 Jan 2002, Alp Atici wrote:
>
>> Is gcc 3.x going to be the default compiler starting from FBSD 5.x
>> series? Is the development on current branch compiled using gcc 3.0 (or
>> up)?
>>
>> Is 5.x series going to be based on a preemptible kernel?
Terry Lambert wrote:
>
> Jason Andresen wrote:
> > Odd, I can't reproduce that under RedHat:
>
> I guess you are saying there is a conspiracy to make GCC work
> only on RedHat?
>
> I could believe that... 8-) 8-) 8-).
>
> Actually, that was against 3.0 at -O2.
>
> If that's been fixed, I gues
On 23 Jan, Terry Lambert wrote:
>> [gcc 3.0.x bug]
>> > Actually, that was against 3.0 at -O2.
>> >
>> > If that's been fixed, I guess we can cut over, as soom as the
>> > non-x86 code generation for our other supported platforms
>> > works again (tried compiling your RedHat for Alpha lately?).
>
Alexander Leidinger wrote:
> [gcc 3.0.x bug]
> > Actually, that was against 3.0 at -O2.
> >
> > If that's been fixed, I guess we can cut over, as soom as the
> > non-x86 code generation for our other supported platforms
> > works again (tried compiling your RedHat for Alpha lately?).
>
> gcc 3.0.
Terry Lambert wrote:
>
> Alp Atici wrote:
> > Is gcc 3.x going to be the default compiler starting from
> > FBSD 5.x series? Is the development on current branch
> > compiled using gcc 3.0 (or up)?
>
> I think that the cut over will happen after the compiler
> no longer core dumps on:
Odd, I ca
Dan Nelson <[EMAIL PROTECTED]> writes:
> In the last episode (Jan 19), Terry Lambert said:
> > Alp Atici wrote:
> > > Is gcc 3.x going to be the default compiler starting from FBSD 5.x
> > > series? Is the development on current branch compiled using gcc 3.0
> > > (or up)?
> >
> > I think that th
In the last episode (Jan 19), Terry Lambert said:
> Alp Atici wrote:
> > Is gcc 3.x going to be the default compiler starting from FBSD 5.x
> > series? Is the development on current branch compiled using gcc 3.0
> > (or up)?
>
> I think that the cut over will happen after the compiler
> no longer
Alp Atici wrote:
> Is gcc 3.x going to be the default compiler starting from
> FBSD 5.x series? Is the development on current branch
> compiled using gcc 3.0 (or up)?
I think that the cut over will happen after the compiler
no longer core dumps on:
main()
{
int i;
On Sat, 19 Jan 2002, Alp Atici wrote:
> Is gcc 3.x going to be the default compiler starting from FBSD 5.x
> series? Is the development on current branch compiled using gcc 3.0 (or
> up)?
>
> Is 5.x series going to be based on a preemptible kernel?
Can't answer the gcc question, but yes, John
[-hackers removed from CC. One list is enough.]
Alp Atici <[EMAIL PROTECTED]> writes:
> Is gcc 3.x going to be the default compiler starting from
> FBSD 5.x series? Is the development on current branch
> compiled using gcc 3.0 (or up)?
Yes. Not yet.
> Is 5.x series going to be based on a pree
Is gcc 3.x going to be the default compiler starting from
FBSD 5.x series? Is the development on current branch
compiled using gcc 3.0 (or up)?
Is 5.x series going to be based on a preemptible kernel?
Thanks,
Alp
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
23 matches
Mail list logo
