On Tue, 4 Jan 2005 06:30:26 +1100 Peter Jeremy
[EMAIL PROTECTED] wrote about Re: Strange networking problems
after update 5.2.1-5.3:
PJ ed0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
PJinet 130.75.117.37 netmask 0x broadcast 130.75.255.255
PJether
Hi,
I had following situation:
Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr
filesystem in a very broken state. During next bootup, there was indeed
the message telling 'not properly unmounted', but boot continued with
background fsck after 60 seconds; although I
* Rob [EMAIL PROTECTED] [0123 10:23]:
This scared me. What if /usr was such broken that even single user mode
would hang!?!
That won't happen, since /usr isn't mounted in single user mode.
--
'common sense is what tells you that the world is flat.'
-- Principia Discordia
In message: [EMAIL PROTECTED]
Robert Watson [EMAIL PROTECTED] writes:
: I've CC'd Warner Losh on the general principle that if it's a problem with
: a PCCARD ethernet adapter, he might be able to help (perhaps especially if
: it's possible to ship him one of the cards).
I think that I
In message: [EMAIL PROTECTED]
Gerrit Kühn [EMAIL PROTECTED] writes:
: Meanwhile I tried two further pcmcia cards which are 32bit (cardbus). Both
: (Xircom CBE2-100 and D-Link DFE-690-TXD) result in
:
: cbb0: CardBus card activation failed
:
: It seems it's rather the pcmcia bridge
In message: [EMAIL PROTECTED]
Gerrit Kühn [EMAIL PROTECTED] writes:
: I will do so if it's the support for the cards that is broken. However, I
: have tried 4 different cards now, and only one of them worked. So I'm
: tending to put the blame on the pcmcia bridge and it's driver.
Hi,
trying to import foomatic-rip, I found great changes under /dev/fd/
going from RELENG_4 to RELENG_5.
Seems that /dev/fd/3 is used by several pipe construct like foomatic-rip
to get a free backwards error channel.
Digging a bit, I found that now, I need mount fdescfs to get this. I
think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED]
wrote:
That won't happen, since /usr isn't mounted in single user mode.
Even if it were, there are always Live BSD CDROMs which should allow you
to boot and then fsck your disk
On Tue, 04 Jan 2005 03:36:53 -0700 (MST) M. Warner Losh [EMAIL PROTECTED]
wrote about Re: Strange networking problems after update 5.2.1-5.3:
MWL : I will do so if it's the support for the cards that is broken.
MWL However, I : have tried 4 different cards now, and only one of them
MWL worked.
Hi!
On Tue, Jan 04, 2005 at 02:23:33AM -0500, kalin mintchev wrote:
this is a few days old. i got a reply saying to try floppies but from the
INSTALL.txt under the amd64/5.3-REL it says:
1.3 Floppy Disk Image Instructions
Floppy disk based install is not supported on FreeBSD/amd64.
Godwin Stewart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Jan 2005 10:26:27 +, Dick Davies [EMAIL PROTECTED]
wrote:
That won't happen, since /usr isn't mounted in single user mode.
Even if it were, there are always Live BSD CDROMs which should allow you
to boot and then
On Tue, 2005-Jan-04 10:17:01 +0100, Gerrit Kühn wrote:
PJ ed0: flags=108843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
PJ inet 130.75.117.37 netmask 0x broadcast 130.75.255.255
PJ ether 01:d4:ff:03:00:20
PJ That's a multicast MAC address (the LSB of the first byte is 1). More
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this version when
1.875 was released 2 years ago
Hi!
On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote:
So I want to configure 5.3 similar to former 4.10: a full automatic fix of
all
filesystems at bootup, in case the system was not properly shutdown.
How can I do that?
You already mention it -- backgroung_fsck=NO at
On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote:
An automatic fsck could have fixed the system (I eventually did it manually
in single user mode), but the background check left the system broken.
So I want to configure 5.3 similar to former 4.10: a full automatic fix of
all
On Tuesday 04 January 2005 03:27 am, Godwin Stewart wrote:
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this
version when 1.875 was
Ceri Davies wrote:
On Tue, Jan 04, 2005 at 08:25:20PM +0900, Rob wrote:
An automatic fsck could have fixed the system (I eventually did it manually
in single user mode), but the background check left the system broken.
So I want to configure 5.3 similar to former 4.10: a full automatic fix
Godwin Stewart wrote:
Is there any particular reason why ports are sticking with
this version when 1.875 was released 2 years ago almost to
the day?
From the first commit comment of devel/bison1875:
Some grammars require the new version of Bison (such as
PostgreSQL), however the new
On Tue, 2005-01-04 at 18:10 +1100, Peter Jeremy wrote:
On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote:
i have tried to burn an iso of 26MB of size, and my system locks
up so i have to reboot.
/var/log/messages is unlikely to include the last 30 seconds or so of
logging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 4 Jan 2005 03:55:42 -0800, Kent Stewart [EMAIL PROTECTED] wrote:
If you have an uptodate port system you will find
Port: bison-1.875_4
Path: /usr/ports/devel/bison1875
Indeed.
That'll teach me to hit [tab] twice after typing
Rob [EMAIL PROTECTED] writes:
I had following situation:
Someone suddenly cut the power of a FreeBSD 5.3 PC, leaving the /usr
filesystem in a very broken state. During next bootup, there was indeed
the message telling 'not properly unmounted', but boot continued with
background fsck
Rob [EMAIL PROTECTED] wrote:
[...]
However, the main user of this particular PC is not at all a guru; on 4.10
I had rc.conf configured such that at bootup all filesystems would be
automatically fixed with: fsck_y_enable=YES.
With 4.10, this always worked nicely, whatever sudden power cut
On Tuesday 04 January 2005 04:13 am, Godwin Stewart wrote:
On Tue, 4 Jan 2005 03:55:42 -0800, Kent Stewart [EMAIL PROTECTED]
wrote:
If you have an uptodate port system you will find
Port: bison-1.875_4
Path: /usr/ports/devel/bison1875
Indeed.
That'll teach me to hit [tab] twice
Matthias Andree [EMAIL PROTECTED] writes:
OTOH, I am not convinced that fsck (particularly bgfsck) is bug-free,
I
Make that fsck and ufs are bug-free...
--
Matthias Andree
___
freebsd-stable@freebsd.org mailing list
test
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Tue, 04 Jan 2005 16:41:35 +0200, podenok wrote
test
Please send these kind of e-mails to [EMAIL PROTECTED] There you can do all
the testing you want :)
Jorn
___
freebsd-stable@freebsd.org mailing list
In message: [EMAIL PROTECTED]
Gerrit Kühn [EMAIL PROTECTED] writes:
: On Tue, 04 Jan 2005 03:36:53 -0700 (MST) M. Warner Losh [EMAIL PROTECTED]
: wrote about Re: Strange networking problems after update 5.2.1-5.3:
:
:
: MWL : I will do so if it's the support for the cards that is
On January 4, 2005 03:25 am, Rob wrote:
Thanks for your replies, but apparently I didn't make my point
clearly. Let me try again:
If the system ends with a bad filesystem, the background check may
leave the system unusable after bootup. For a FreeBSD guru this is
indeed easy to fix (single
On Tue, 04 Jan 2005 09:27:34 -0700 (MST) M. Warner Losh [EMAIL PROTECTED]
wrote about Re: Strange networking problems after update 5.2.1-5.3:
MWL : Please tell me which information you need.
MWL You've likely already sent this before... But can you send a full
MWL dmesg with hw.cbb.debug=1 and
We are starting to migrate stuff to FreeBSD 5 and one of my shell
scripts broke because rmdir -p doesn't work in 5.3.
It would be really nice to have the fix from CURRENT merged to
RELENG_5 and possibly even RELENG_5_3 if possible.
Thanks.
--
Christian Laursen
Am 04.01.2005 um 19:34 schrieb Christian Laursen:
We are starting to migrate stuff to FreeBSD 5 and one of my shell
scripts broke because rmdir -p doesn't work in 5.3.
It would be really nice to have the fix from CURRENT merged to
RELENG_5 and possibly even RELENG_5_3 if possible.
Appending /. to
Hi,
As far as I have tested pf(packet filter) on FreeBSD 5.3R,
NAT function with IPv6 does not work well. Log says conversion is
done. But source address is not translated. Though I asked
about it in freebsd-pf mailing list, we have not had any reponses yet.
Regard,
Hideki Yamamoto
From:
Hi,
I just upgraded to perl 5.6 using perl5 port. However some of
my scripts are not working due to compatibility problems. How do
I revert back to the system (base) version of perl that comes
with 4.10.
Tejas Kokje
___
freebsd-stable@freebsd.org mailing
On Wed, Jan 05, 2005 at 05:28:19AM +0900, Hideki Yamamoto wrote:
As far as I have tested pf(packet filter) on FreeBSD 5.3R,
NAT function with IPv6 does not work well. Log says conversion is
done. But source address is not translated. Though I asked
about it in freebsd-pf mailing list, we
Tejas Kokje wrote:
Hi,
I just upgraded to perl 5.6 using perl5 port. However some of
my scripts are not working due to compatibility problems. How do
I revert back to the system (base) version of perl that comes
with 4.10.
I think what you're looking for is /usr/local/bin/use.perl system
Tejas
Tejas Kokje wrote:
Hi,
I just upgraded to perl 5.6 using perl5 port. However some of
my scripts are not working due to compatibility problems. How do
I revert back to the system (base) version of perl that comes
with 4.10.
Tejas Kokje
1. Deinstall the perl 5.6 port
2. Type the command use.perl
Richard Coleman wrote:
Tejas Kokje wrote:
Hi,
I just upgraded to perl 5.6 using perl5 port. However some of
my scripts are not working due to compatibility problems. How do
I revert back to the system (base) version of perl that comes
with 4.10.
Tejas Kokje
1. Deinstall the perl 5.6 port
2. Type
Hello,
On Tue, Jan 04, 2005 at 12:32:32PM -0800 or thereabouts, Tejas Kokje wrote:
I just upgraded to perl 5.6 using perl5 port. However some of
my scripts are not working due to compatibility problems. How do
I revert back to the system (base) version of perl that comes
with 4.10.
On Tue, Jan 04, 2005 at 12:27:32PM +0100, Godwin Stewart wrote:
Ports cvsup'ed yesterday,
$ cat /usr/ports/devel/bison/Makefile
{snip}
PORTNAME= bison
PORTVERSION=1.75
PORTREVISION= 2
{snip}
Is there any particular reason why ports are sticking with this version when
1.875
In message [EMAIL PROTECTED], Mark Knight
[EMAIL PROTECTED] writes
With RELENG_5 from yesterday, as well from a week or so ago I'm finding
that dump is failing. Must admit, this is the first time I've tried to
run a backup since migrating from RELENG_4 to RELENG_5.
fsck -f / marks the file
Hi,
Can anybody tell me how to downgrade the ports. I upgraded p5-GD port to
2.16 . However some of our applications require p5-GD 2.07 version.
So I need to roll back to 2.07 from 2.16.
Tejas Kokje
___
freebsd-stable@freebsd.org mailing list
On Tue, Jan 04, 2005 at 02:16:47PM -0800, Tejas Kokje wrote:
Hi,
Can anybody tell me how to downgrade the ports. I upgraded p5-GD port to
2.16 . However some of our applications require p5-GD 2.07 version.
So I need to roll back to 2.07 from 2.16.
This can be a slightly tricky business
On Fri, Dec 31, 2004 at 05:28:48PM -0800, Kris Kennaway wrote:
The port index under www.freebsd.org/ports *does* know that frontpage
will not appear in packages, and doesn't provide a link to it.
http://www.freebsd.org/ports/www.html
I beg to differ
On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote:
It provides a link to where the package would be if it exists. The
web frontend has no knowledge of which packages are available at any
given point in time because this set fluctuates on a daily basis, so
the frontend is always
On Tue, Jan 04, 2005 at 02:30:14PM -0800, Joe Rhett wrote:
On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote:
It provides a link to where the package would be if it exists. The
web frontend has no knowledge of which packages are available at any
given point in time because this
On 2005.01.04 14:30:14 -0800, Joe Rhett wrote:
On Fri, Dec 31, 2004 at 05:22:00PM -0800, Kris Kennaway wrote:
It provides a link to where the package would be if it exists. The
web frontend has no knowledge of which packages are available at any
given point in time because this set
0n Tue, Jan 04, 2005 at 02:01:22PM +0100, Oliver Fromme wrote:
By the way, you can map a key combination (Ctrl-Alt-Del or
something else) to the »halt« or »power-down« functions,
using kbdcontrol, so it's very easy and intuitive to shut
down the machine properly. See the
On Wed, Jan 05, 2005 at 01:59:01PM +1030, Wilkinson, Alex wrote:
This inspires me to ask this question:
Is it possible to set up FreeBSD to do a clean shutdown upon a pressing
the power button ? i.e. in the same fashion as Solaris does out of the
box. Is this an ATX feature or a kernel
0n Tue, Jan 04, 2005 at 09:50:10PM -0600, Craig Boston wrote:
Yes, in FreeBSD 5.3 if ACPI is enabled and working properly, pressing
the power button will initiate a graceful shutdown (similar to shutdown
-p). This feature is enabled by default if it is available, so you
On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote:
How can I confirm that ACPI has been setup to do this ?
Hmm, well, the easiest thing to check is to run
sysctl hw.acpi.power_button_state
and see if that sysctl exists and if so, what it's set to (mine is S5, which
IIRC is complete
0n Tue, Jan 04, 2005 at 10:17:47PM -0600, Craig Boston wrote:
On Tuesday 04 January 2005 9:57 pm, Wilkinson, Alex wrote:
How can I confirm that ACPI has been setup to do this ?
Hmm, well, the easiest thing to check is to run
sysctl hw.acpi.power_button_state
On Tue, Jan 04, 2005 at 12:37:48PM -0800, Brooks Davis wrote:
On Wed, Jan 05, 2005 at 05:28:19AM +0900, Hideki Yamamoto wrote:
As far as I have tested pf(packet filter) on FreeBSD 5.3R,
NAT function with IPv6 does not work well. Log says conversion is
done. But source address is not
52 matches
Mail list logo
