Re: What to use to get remote display from a amd64 machine?

[Axel Gonzalez]

On Monday 06 June 2005 21:26, Daniel O'Connor wrote:
> On Tue, 7 Jun 2005 11:21, Axel Gonzalez wrote:
> > If you using KDE, you can enable desktop sharing, it uses the vnc
> > protocol, you can connect using a standard vnc client. (this is reported
> > to work on AMD64)
>
> That works here.
>
> I tried net/vnc but starting up give..
> [foo64 2:25] /usr/ports/net/vnc >Xvnc :1
> Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
> Getting interface configuration (4): Device not configured
> 07/06/05 02:26:10 Xvnc version 3.3.7 - built Jun  7 2005 02:21:40
> 07/06/05 02:26:10 Copyright (C) 2002-2003 RealVNC Ltd.
> 07/06/05 02:26:10 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
> 07/06/05 02:26:10 All Rights Reserved.
> 07/06/05 02:26:10 See http://www.realvnc.com for information on VNC
> 07/06/05 02:26:10 Desktop name 'x11' (foo64.gsoft.com.au:1)
> 07/06/05 02:26:10 Protocol version supported 3.3
> 07/06/05 02:26:10 Listening for VNC connections on TCP port 5901
> failed to set default font path
> '/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6
>/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fon
>ts/100dpi/' Fatal server error:
> could not open default font 'fixed'
>
> And I don't know why since Xorg works fine..
>
> Personally I'd use X forwarding to run X apps on such a machine though.


See PR ports/71512

There is the complete description of the problem

There is a new version on ports... VNC 4.1.1, it starts the X display, but 
cant start any WM =\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Axel Gonzalez]

On Monday 06 June 2005 21:33, Jiawei Ye wrote:
> On 6/7/05, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
> > That works here.
> >
> > I tried net/vnc but starting up give..
> > [foo64 2:25] /usr/ports/net/vnc >Xvnc :1
> > Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
> > Getting interface configuration (4): Device not configured
>
> --SNIP--
>
> > failed to set default font path
> > '/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11
> >R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11
> >/fonts/100dpi/' Fatal server error:
> > could not open default font 'fixed'
> >
> > And I don't know why since Xorg works fine..
> >
> > Personally I'd use X forwarding to run X apps on such a machine though.
> >
> > --
> > Daniel O'Connor software and network engineer
>
> VNC has it's own startup script and hard coded fontpath. You need to
> manually edit them. It does not read Xorg/XFree86 config files :(
>
> Jiawei

This is not a config problem. this is related to a problem with AMD64
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Scott Robbins]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jun 07, 2005 at 10:33:40AM +0800, Jiawei Ye wrote:
> On 6/7/05, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
> > That works here.
> > 
> --SNIP--
> > failed to set default font path
> > '/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/'
> > Fatal server error:
> > could not open default font 'fixed'
> > 



> VNC has it's own startup script and hard coded fontpath. You need to
> manually edit them. It does not read Xorg/XFree86 config files :(
> 

I've always used tightvnc.  Upon running the command 

vncserver

the first time it requests a password.  After that, it Just Works (TM) 
However, if I want a different WM for the vnc session, or various
other changes, I do have to edit a few files that it places in my $HOME
directory. 


- -- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6



 Cordelia: If the world doesn't end, I'm gonna need a note.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCpQkL+lTVdes0Z9YRArVLAKC/HV+Nl2BeADVRu4B3B/IPA49/VQCfQTjX
cbIlUeulz2FQQls0CTmBoF4=
=31jD
-END PGP SIGNATURE-
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Jiawei Ye]

On 6/7/05, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
> That works here.
> 
> I tried net/vnc but starting up give..
> [foo64 2:25] /usr/ports/net/vnc >Xvnc :1
> Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
> Getting interface configuration (4): Device not configured
--SNIP--
> failed to set default font path
> '/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/'
> Fatal server error:
> could not open default font 'fixed'
> 
> And I don't know why since Xorg works fine..
> 
> Personally I'd use X forwarding to run X apps on such a machine though.
> 
> --
> Daniel O'Connor software and network engineer
VNC has it's own startup script and hard coded fontpath. You need to
manually edit them. It does not read Xorg/XFree86 config files :(

Jiawei
-- 
"Without the userland, the kernel is useless."
   --inspired by The Tao of Programming
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Daniel O'Connor]

On Tue, 7 Jun 2005 11:21, Axel Gonzalez wrote:
> If you using KDE, you can enable desktop sharing, it uses the vnc protocol,
> you can connect using a standard vnc client. (this is reported to work on
> AMD64)

That works here.

I tried net/vnc but starting up give..
[foo64 2:25] /usr/ports/net/vnc >Xvnc :1
Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
Getting interface configuration (4): Device not configured
07/06/05 02:26:10 Xvnc version 3.3.7 - built Jun  7 2005 02:21:40
07/06/05 02:26:10 Copyright (C) 2002-2003 RealVNC Ltd.
07/06/05 02:26:10 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
07/06/05 02:26:10 All Rights Reserved.
07/06/05 02:26:10 See http://www.realvnc.com for information on VNC
07/06/05 02:26:10 Desktop name 'x11' (foo64.gsoft.com.au:1)
07/06/05 02:26:10 Protocol version supported 3.3
07/06/05 02:26:10 Listening for VNC connections on TCP port 5901
failed to set default font path 
'/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/'
Fatal server error:
could not open default font 'fixed'

And I don't know why since Xorg works fine..

Personally I'd use X forwarding to run X apps on such a machine though.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C


pgpQmNgEx3QRE.pgp
Description: PGP signature

Re: What to use to get remote display from a amd64 machine?

[Axel Gonzalez]

there are several VNCs, buut either they are i386 or they are broken.

X forwarding is an option

If you using KDE, you can enable desktop sharing, it uses the vnc protocol, 
you can connect using a standard vnc client. (this is reported to work on 
AMD64)

This also will allow you to see the same X display on your desktop, and the 
remote machine.

I think gnome has something similar, but never tried it.


if you using another WM, cant think of more options, or wait till someone 
(with lots more time than me) can fix PR ports/71512 :)


On Monday 06 June 2005 17:03, Torfinn Ingolfsen wrote:
> Hello,
>
> I'm riunning FreeBSD 5.4-stable (amd64) on this amd64 machine.
> I would like to see the X display on this machine from another machine.
> My first thought was VNC (tightVNC) as I'm using this on my other boxes
> already. But alas, VNC isn't working on amd64.
>
> I then saw FreeNX in the ports tree. It requires nxserver 1.4.0) which
> is i386 only. No go there either.
>
> What are people using for remote X displays on amd64 machines?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4-RELEASE lockups on amd64 SMP

[Kris Kennaway]

On Mon, Jun 06, 2005 at 06:54:05PM -0500, Grooms, Matthew wrote:
> My appologies. With the debug options listed in my previous post ( should 
> have read 5.4 not 5.3 ), I got a lock order reversal. After a while, it 
> paniced and spat out this ...
> 
> lock order reversal
> 1st 0x80752ec0 pf task mtx (pf task mtx) @ 
> contrib/pf/net/if_pfsync.c:1621
> 2nd 0x8076e9f0 user map (user man) @ vm/vm_map.c:2998
> KDB: stack backtrace:
> witness_checkorder() at witness_checkorder+0x654
> _sx_xlock() at _sx_xlock+0x51
> vm_map_lookup() at vm_map_lookup+0x44
> vm_fault() at vm_fault+0xba
> trap() at trap+0x1c5
> alltraps_with_regs_pushed() at alltraps_with_regs_pushed+0x5
> pf_state_tree_lan_ext_RB_REMOVE() at pf_state_tree_lan_ext_RB_REMOVE+0x10c
> pf_purge_expired_states() at pf_purge_expired_states+0xab
> pfsync_input() at ip_input+0x10f
> netisr_processqueue() at netisr_processqueue+0x17
> swi_net() at swi_net+0xa8
> ithread_loop() at ithread_loop+0xd9
> fork_exit() at fork_exit+0xc3
> fork_trampoline() at fork_trampoline+0xe
> --- trap 0, rip = 0, rsp = 0xb44f9d00, rbp = 0 ---
> KDB: enter: withness_ckeckorder
> [thread pid 110 tid 100089]
> Stopped at  kdb_enter+0x2f: nop
> db> panic blockable sleep lock (sleep mutex) tty @ kern/kern_event.c:1453
> cpuid = 0
> boot() called on cpu#0
> Uptime: 10m40s
> Dumping 4864 mB
>  16 32 .
> 
> After a reboot, I received another panic.
> 
> Tracing pid 603 tid 100140 td 0xff012efda500
> kdb_enter() at kdb_enter+02f
> panic() at panic+0x249
> ffs_blkfree() at ffs_blkfree+0x483
> indir_trunc() at indir_trunc+0x190
> indir_trunc() at indir_trunc+0x1fb
> handle_workitem_freeblocks() at handle_workitem_freeblocks+0x228
> softdep_setup_freeblocks() at softdep_setup_freeblocks+0x730
> ffs_truncate() at ffs_truncate+0x1c9
> ffs_snapshot() at ffs_snapshot+0x717
> ffs_omount() at ffs_omount+0x16e
> vfs_domount() at vfs_domount+0x5a0
> mount() at mount+0xd8
> syscall() at syscall+0x1fb
> Xfast_syscall() at Xfast_syscall+0xa8
> --- syscall(21, FreeBSD ELF64, mount), rip = 0800697580, rsp = 
> 0x7fffec58, fbp = 0x515b10 ---
> 
> I am guessing this is related to background fsck processes being launched 
> because it happened consistently until I disabled background fsck and 
> performed one manually in single user mode. Now I can boot normally into 
> multi user mode.

You may have had disk corruption that was not repaired by bg fsck.

Kris


pgpyciqp1IuSQ.pgp
Description: PGP signature

5.4-RELEASE lockups on amd64 SMP

[Grooms, Matthew]

My appologies. With the debug options listed in my previous post ( should have 
read 5.4 not 5.3 ), I got a lock order reversal. After a while, it paniced and 
spat out this ...

lock order reversal
1st 0x80752ec0 pf task mtx (pf task mtx) @ 
contrib/pf/net/if_pfsync.c:1621
2nd 0x8076e9f0 user map (user man) @ vm/vm_map.c:2998
KDB: stack backtrace:
witness_checkorder() at witness_checkorder+0x654
_sx_xlock() at _sx_xlock+0x51
vm_map_lookup() at vm_map_lookup+0x44
vm_fault() at vm_fault+0xba
trap() at trap+0x1c5
alltraps_with_regs_pushed() at alltraps_with_regs_pushed+0x5
pf_state_tree_lan_ext_RB_REMOVE() at pf_state_tree_lan_ext_RB_REMOVE+0x10c
pf_purge_expired_states() at pf_purge_expired_states+0xab
pfsync_input() at ip_input+0x10f
netisr_processqueue() at netisr_processqueue+0x17
swi_net() at swi_net+0xa8
ithread_loop() at ithread_loop+0xd9
fork_exit() at fork_exit+0xc3
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xb44f9d00, rbp = 0 ---
KDB: enter: withness_ckeckorder
[thread pid 110 tid 100089]
Stopped at  kdb_enter+0x2f: nop
db> panic blockable sleep lock (sleep mutex) tty @ kern/kern_event.c:1453
cpuid = 0
boot() called on cpu#0
Uptime: 10m40s
Dumping 4864 mB
 16 32 .

After a reboot, I received another panic.

Tracing pid 603 tid 100140 td 0xff012efda500
kdb_enter() at kdb_enter+02f
panic() at panic+0x249
ffs_blkfree() at ffs_blkfree+0x483
indir_trunc() at indir_trunc+0x190
indir_trunc() at indir_trunc+0x1fb
handle_workitem_freeblocks() at handle_workitem_freeblocks+0x228
softdep_setup_freeblocks() at softdep_setup_freeblocks+0x730
ffs_truncate() at ffs_truncate+0x1c9
ffs_snapshot() at ffs_snapshot+0x717
ffs_omount() at ffs_omount+0x16e
vfs_domount() at vfs_domount+0x5a0
mount() at mount+0xd8
syscall() at syscall+0x1fb
Xfast_syscall() at Xfast_syscall+0xa8
--- syscall(21, FreeBSD ELF64, mount), rip = 0800697580, rsp = 0x7fffec58, 
fbp = 0x515b10 ---

I am guessing this is related to background fsck processes being launched 
because it happened consistently until I disabled background fsck and performed 
one manually in single user mode. Now I can boot normally into multi user mode.

Not sure where to go from here except to watch the system and wait for more 
kernel debug output.

BTW : To answer a reply to my previous post, I have 6 em interfaces.

-Matthew

-Original Message-
From: Grooms, Matthew
Sent: Mon 6/6/2005 12:06 PM
To: freebsd-stable@freebsd.org
Subject: Debug help - 5.3 lockups on amd64 SMP
 
All,

  I am experiencing lockups on a production 5.4 amd64 SMP system. 
Its lightly loaded and seems to last about 3-5 days before it stops 
responding to network or even console interaction. The system is acting 
as a firewall and runs a mostly stock kernel with IPV6 removed and SMP, 
PF, PFLOG, CARP and ALTQ added. The only other thing I can think to note 
is that tcpdump is running constantly on the pflog interface to coax 
human readable firewall logs out of pf.

 I have an identical hot spare server with SMP disabled that has 
taken over flawlessly every time the live lock occurs so I am willing to 
leave the primary in the production environment to do testing and gather 
debug info. I have added the following options to primary fw kernel 
config ...

# Debug Options
makeoptions DEBUG=-g
options DDB
options KDB
options BREAK_TO_DEBUGGER
options INVARIANT_SUPPORT
options INVARIANTS
options WITNESS
options WITNESS_KDB
options WITNESS_SKIPSPIN

... and the following to the rc.conf ...

dumpdev="/dev/amrd0s1h"
dumpdir="/var/crash"

Will this do it or should I add anything else?

Thanks in advance,

-Matthew



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SSHD and FTPD, can't connect

[Evan Dower]

I am reminded of Mon, Jun 06, 2005 at 06:40:23PM -0400 when Lowell Gilbert said:
> Please don't top-post.
> 
> "Matt Smith" <[EMAIL PROTECTED]> writes:
> 
> > Where is the sshd debugger?
> 
> There are a couple of ways to get extra logging information out of
> it.  See the "LogLevel" option in the manual for sshd_config(5) or the
> "-d" option in the manual for sshd(8).
> 

And don't forget the -v (or -vv or -vvv) option to ssh. Even that could be 
helpful. 

-- 
Evan Dower
Undergraduate, Computer Science
University of Washington
Public key: http://students.washington.edu/evantd/pgp-pub-key.txt
Key fingerprint = D321 FA24 4BDA F82D 53A9  5B27 7D15 5A4F 033F 887D
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Dick Davies]

* Kevin Oberman <[EMAIL PROTECTED]> [0626 23:26]:
> > Date: Mon, 6 Jun 2005 23:20:41 +0100
> > From: Dick Davies <[EMAIL PROTECTED]>
> > 
> > * Kevin Oberman <[EMAIL PROTECTED]> [0616 23:16]:
> > > > Date: Tue, 7 Jun 2005 00:11:14 +0200
> > > > From: Claus Guttesen <[EMAIL PROTECTED]>
> > > > Sender: [EMAIL PROTECTED]
> > > > 
> > > > > What are people using for remote X displays on amd64 machines?
> > > > 
> > > > What about 'ssh -X remote-machine'?
> > > 
> > > 'ssh -Y remote-machine' is more likely to be useful on more recent
> > > versions of ssh.
> > 
> > Not if you're sshing into a multi-user machine, unless I've misunderstood
> > what '-Y' does.
> 
> You understand fairly correctly. If the remote system is multi-user and
> all users are not trusted (by you, personally and by others if it is
> work related), -X should be used. The problem is that most X
> apps won't run with -X. :-(  Even a simple xclock would not work for me.

I've had success scping ~/.Xauthority over from the xserver/ssh-client end
to the xclient/ssh-server end.

But again, I only just found out about -Y so may well be getting the wrong end
of the stick here...

-- 
'That question was less stupid; though you asked it in a profoundly stupid way.'
-- Prof. Farnsworth
Rasputin :: Jack of All Trades - Master of Nuns
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: RELENG_5 minor src/obj glitches

[Kris Kennaway]

On Tue, Jun 07, 2005 at 02:43:15AM +0400, Dmitry Morozovsky wrote:
> Colleagues,
> 
> building RELENG_5 sources one can see the following local modifications 
> slipped 
> in:
> 
> ? usr.bin/lex/lib/.depend
> ? usr.bin/lex/lib/libmain.po
> ? usr.bin/lex/lib/libyywrap.po
> ? usr.sbin/pcvt/keycap/.depend
> ? usr.sbin/pcvt/keycap/keycap.po
> 
> you can see this after make buildworld and then cvs update. 

Are you sure they aren't stale files from an earlier build?

Kris


pgpnSCtKP41Ye.pgp
Description: PGP signature

RELENG_5 minor src/obj glitches

[Dmitry Morozovsky]

Colleagues,

building RELENG_5 sources one can see the following local modifications slipped 
in:

? usr.bin/lex/lib/.depend
? usr.bin/lex/lib/libmain.po
? usr.bin/lex/lib/libyywrap.po
? usr.sbin/pcvt/keycap/.depend
? usr.sbin/pcvt/keycap/keycap.po

you can see this after make buildworld and then cvs update. 

I tried to catch this via Makefiles but got a bit stuck; however, I'm afraid 
this would prevent building RELENG_5 and related when /usr/src is read-only.

Any clues?

Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]

*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SSHD and FTPD, can't connect

[Lowell Gilbert]

Please don't top-post.

"Matt Smith" <[EMAIL PROTECTED]> writes:

> Where is the sshd debugger?

There are a couple of ways to get extra logging information out of
it.  See the "LogLevel" option in the manual for sshd_config(5) or the
"-d" option in the manual for sshd(8).

>  Matt
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Lowell Gilbert
> Sent: Monday, June 06, 2005 5:36 PM
> To: Matt Smith; freebsd-stable@freebsd.org
> Subject: Re: SSHD and FTPD, can't connect
> 
> "Matt Smith" <[EMAIL PROTECTED]> writes:
> 
> > Did that, to no avail.  It was fine then it started doing this.  Any
> > other suggestions?
> 
> Plenty, but guessing is an inefficient way to solve this.  Turn on
> debugging for both the sshd on that system and the slogin invocations
> on the other machines, and let the computers tell you what is wrong.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Kevin Oberman]

> Date: Mon, 6 Jun 2005 23:20:41 +0100
> From: Dick Davies <[EMAIL PROTECTED]>
> 
> * Kevin Oberman <[EMAIL PROTECTED]> [0616 23:16]:
> > > Date: Tue, 7 Jun 2005 00:11:14 +0200
> > > From: Claus Guttesen <[EMAIL PROTECTED]>
> > > Sender: [EMAIL PROTECTED]
> > > 
> > > > What are people using for remote X displays on amd64 machines?
> > > 
> > > What about 'ssh -X remote-machine'?
> > 
> > 'ssh -Y remote-machine' is more likely to be useful on more recent
> > versions of ssh.
> 
> Not if you're sshing into a multi-user machine, unless I've misunderstood
> what '-Y' does.

You understand fairly correctly. If the remote system is multi-user and
all users are not trusted (by you, personally and by others if it is
work related), -X should be used. The problem is that most X
apps won't run with -X. :-(  Even a simple xclock would not work for me.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Dick Davies]

* Kevin Oberman <[EMAIL PROTECTED]> [0616 23:16]:
> > Date: Tue, 7 Jun 2005 00:11:14 +0200
> > From: Claus Guttesen <[EMAIL PROTECTED]>
> > Sender: [EMAIL PROTECTED]
> > 
> > > What are people using for remote X displays on amd64 machines?
> > 
> > What about 'ssh -X remote-machine'?
> 
> 'ssh -Y remote-machine' is more likely to be useful on more recent
> versions of ssh.

Not if you're sshing into a multi-user machine, unless I've misunderstood
what '-Y' does.

--
Well, how's his wife holding up? To shreds, you say...'
-- Prof. Farnsworth
Rasputin :: Jack of All Trades - Master of Nuns
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Kevin Oberman]

> Date: Tue, 7 Jun 2005 00:11:14 +0200
> From: Claus Guttesen <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
> 
> > What are people using for remote X displays on amd64 machines?
> 
> What about 'ssh -X remote-machine'?

'ssh -Y remote-machine' is more likely to be useful on more recent
versions of ssh.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]   Phone: +1 510 486-8634
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Steven Hartland]

X is a fully network aware display method just set your display
to the remote machine. If you worried about security either VNP
it or tunnel over SSH.
   
   Steve
- Original Message - 
From: "Torfinn Ingolfsen" <[EMAIL PROTECTED]>

To: 
Sent: Monday, June 06, 2005 11:03 PM
Subject: What to use to get remote display from a amd64 machine?



Hello,

I'm riunning FreeBSD 5.4-stable (amd64) on this amd64 machine.
I would like to see the X display on this machine from another machine.
My first thought was VNC (tightVNC) as I'm using this on my other boxes
already. But alas, VNC isn't working on amd64.

I then saw FreeNX in the ports tree. It requires nxserver 1.4.0) which
is i386 only. No go there either.

What are people using for remote X displays on amd64 machines?
--
Regards,
Torfinn Ingolfsen


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"






This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: What to use to get remote display from a amd64 machine?

[Claus Guttesen]

> What are people using for remote X displays on amd64 machines?

What about 'ssh -X remote-machine'?

Claus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

What to use to get remote display from a amd64 machine?

[Torfinn Ingolfsen]

Hello,

I'm riunning FreeBSD 5.4-stable (amd64) on this amd64 machine.
I would like to see the X display on this machine from another machine.
My first thought was VNC (tightVNC) as I'm using this on my other boxes
already. But alas, VNC isn't working on amd64.

I then saw FreeNX in the ports tree. It requires nxserver 1.4.0) which
is i386 only. No go there either.

What are people using for remote X displays on amd64 machines?
-- 
Regards,
Torfinn Ingolfsen


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: SSHD and FTPD, can't connect

[Matt Smith]

Where is the sshd debugger?

 Matt

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Lowell Gilbert
Sent: Monday, June 06, 2005 5:36 PM
To: Matt Smith; freebsd-stable@freebsd.org
Subject: Re: SSHD and FTPD, can't connect

"Matt Smith" <[EMAIL PROTECTED]> writes:

> Did that, to no avail.  It was fine then it started doing this.  Any
> other suggestions?

Plenty, but guessing is an inefficient way to solve this.  Turn on
debugging for both the sshd on that system and the slogin invocations
on the other machines, and let the computers tell you what is wrong.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SSHD and FTPD, can't connect

[Lowell Gilbert]

"Matt Smith" <[EMAIL PROTECTED]> writes:

> Did that, to no avail.  It was fine then it started doing this.  Any
> other suggestions?

Plenty, but guessing is an inefficient way to solve this.  Turn on
debugging for both the sshd on that system and the slogin invocations
on the other machines, and let the computers tell you what is wrong.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: SSHD and FTPD, can't connect

[Danny Cooper]

Do you see any traffic when you run 'tcpdump port 22' on the server?
Or if you just try telnet server.ip 22 do you get anything back?

I know I am stating basic's but its caught me out a few times before where a
firewall has caught the packets.

DC

-Original Message-
From: Matt Smith [mailto:[EMAIL PROTECTED] 
Sent: 06 June 2005 22:02
To: 'Danny Cooper'
Subject: RE: SSHD and FTPD, can't connect

Yep, timeout before auth.

  Matt

-Original Message-
From: Danny Cooper [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 06, 2005 4:43 PM
To: 'Matt Smith'
Subject: RE: SSHD and FTPD, can't connect

Have you checked 

/var/log/auth.log for any error messages with sshd

-Original Message-
From: Matt Smith [mailto:[EMAIL PROTECTED] 
Sent: 06 June 2005 20:56
To: 'Danny Cooper'; freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Did that, to no avail.  It was fine then it started doing this.  Any
other suggestions?

  Matt

-Original Message-
From: Danny Cooper [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 06, 2005 3:28 PM
To: 'Matt Smith'; freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Have you opened up the /etc/hosts.allow file to allow connections for
the
home lan?

e.g.

ALL : localhost : allow
ALL : 127.0.0.1 : allow
ALL : 192.68.0.0/255.255.255.255 : allow
sshd : all : allow
ftpd : all : allow
ALL : ALL : deny

Danny C


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt Smith
Sent: 06 June 2005 19:20
To: freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Hello,
you may remember the problems that my friends were having with
ssh/ftp timeouts.  Well now I have the same issue with my FBSD 4.10
install.  I can ping the box and use the Apache and telnet daemons, but
not the SSHD or FTPD.  I tried to upgrade the SSHD to no avail and I CAN
connect to the daemons from the loopback address, but not across my home
LAN.  Any suggestions?

 Matt 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"


smime.p7s
Description: S/MIME cryptographic signature

Re: 4.11 panic #2, need help decoding

[Charles Sprickman]

On Mon, 6 Jun 2005, Doug White wrote:


On Sun, 5 Jun 2005, Charles Sprickman wrote:


Here's what gdb has for me this time:


Can you go to frame 38 and print the value of "source"?  Comparing it to
NULL shouldn't cause a fault, but I suspect its another one of the cases
in that if statement.


I'm not handy with gdb, but I'm thinking this is what you might want?

#38 0xc026fc9e in vm_object_shadow (object=0xd73782e4, offset=0xd73782e8,
length=847873) at /usr/src/sys/vm/vm_object.c:1058
1058if (source != NULL &&
(kgdb) print source
$1 = 0x0

Is that correct?  Is there any additional information you would like from 
the previous panic?


Thanks,

Charles


--
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 4.11 panic #2, need help decoding

[Doug White]

On Sun, 5 Jun 2005, Charles Sprickman wrote:

> Hello,
>
> Second panic on this box in less than two weeks.  Can someone help me
> figure out whether this looks to be a hardware issue or not?  Am I on the
> correct list for this type of problem?

You're in the right spot all right...

> Previous info is at:
> http://thread.gmane.org/gmane.os.freebsd.stable/28428 (no followups)
>
> Here's what gdb has for me this time:

Can you go to frame 38 and print the value of "source"?  Comparing it to
NULL shouldn't cause a fault, but I suspect its another one of the cases
in that if statement.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 5.4 RELEASE atkbdc0 problem

[Doug White]

On Sun, 5 Jun 2005, Remi Regruson wrote:

> Hi,
>
> I put the folowing line in /boot/loader.conf :
> usb_load="yes"
> ukbd_load="yes"
> This haven't done what I exepted : my usb keyboard don't work during the 
> loader prompt and now I can't boot. The kernel message stop with this line:

If you want your USB keyboard to work in loader you need to enable "USB
Legacy" in the BIOS.

> atkbdc0:  port 0x64,0x60 irq 1 on acpi0
> I have the same log with or without : any keyboard(ps2 or usb), usb or apm 
> activating in the bios.

FreeBSD can only handle input from one keyboard at a time. By default the
first keyboard attached wins, which is atkbd.  You have a few options:

1. Edit /boot/device.hints and remove the hint.atkbd.0.flags line, reboot,
and unplug the PS/2 keyboard before the kernel starts. Unless your BIOS
fakes up a keyboard it should keep atkbd0 from attaching and therefore let
the USB keyboard take over kbd0.

2. Add a line to /etc/usbd.conf that calls

kbdcontrol -k kbd1 < /dev/console

when a USB keyboard is attached. This selects the USB keyboard as the
active keyboard. If kbd1 goes away (by unplugging the USB keyboard) it'll
fall back to the PS/2 keyboard.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: SSHD and FTPD, can't connect

[Matt Smith]

Did that, to no avail.  It was fine then it started doing this.  Any
other suggestions?

  Matt

-Original Message-
From: Danny Cooper [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 06, 2005 3:28 PM
To: 'Matt Smith'; freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Have you opened up the /etc/hosts.allow file to allow connections for
the
home lan?

e.g.

ALL : localhost : allow
ALL : 127.0.0.1 : allow
ALL : 192.68.0.0/255.255.255.255 : allow
sshd : all : allow
ftpd : all : allow
ALL : ALL : deny

Danny C


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt Smith
Sent: 06 June 2005 19:20
To: freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Hello,
you may remember the problems that my friends were having with
ssh/ftp timeouts.  Well now I have the same issue with my FBSD 4.10
install.  I can ping the box and use the Apache and telnet daemons, but
not the SSHD or FTPD.  I tried to upgrade the SSHD to no avail and I CAN
connect to the daemons from the loopback address, but not across my home
LAN.  Any suggestions?

 Matt 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: SSHD and FTPD, can't connect

[Jonathan Chen]

On Mon, Jun 06, 2005 at 02:20:06PM -0400, Matt Smith wrote:
> Hello,
> you may remember the problems that my friends were having with
> ssh/ftp timeouts.  Well now I have the same issue with my FBSD 4.10
> install.  I can ping the box and use the Apache and telnet daemons, but
> not the SSHD or FTPD.  I tried to upgrade the SSHD to no avail and I CAN
> connect to the daemons from the loopback address, but not across my home
> LAN.  Any suggestions?

Fix the IP lookups on your DNS.
-- 
Jonathan Chen <[EMAIL PROTECTED]>
--
 When all else fails, RTFM
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: SSHD and FTPD, can't connect

[Danny Cooper]

Have you opened up the /etc/hosts.allow file to allow connections for the
home lan?

e.g.

ALL : localhost : allow
ALL : 127.0.0.1 : allow
ALL : 192.68.0.0/255.255.255.255 : allow
sshd : all : allow
ftpd : all : allow
ALL : ALL : deny

Danny C


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt Smith
Sent: 06 June 2005 19:20
To: freebsd-stable@freebsd.org
Subject: RE: SSHD and FTPD, can't connect

Hello,
you may remember the problems that my friends were having with
ssh/ftp timeouts.  Well now I have the same issue with my FBSD 4.10
install.  I can ping the box and use the Apache and telnet daemons, but
not the SSHD or FTPD.  I tried to upgrade the SSHD to no avail and I CAN
connect to the daemons from the loopback address, but not across my home
LAN.  Any suggestions?

 Matt 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[jonathan michaels]

On Mon, Jun 06, 2005 at 10:25:51AM -0300, Maxi Combina wrote:

snipped for brevity

> combined with a stable system. I have no trouble with a "diffucult /
> unix-like" OS, but a lot of people do. And this a _fact_.They dont
> have time to spend learning to use a "dificult" OS. And I think that
> if we want to tell more and more people (friends, family, goverment,
> companies, etc) to move to an open source OS, we must do an effort. I

word of mouth advertising is teh best most reliable form of advertising
going ... good working examples performing well and in a stable manner
is the best way of showing pwople that an operating system is worth
concidering. especially if it is a college is using it (comfortably and
assuredly) to do the job at hand.

> think that there are a lot of linux distros out there that are really
> easy to use, and even more "friendly" or "beatiful" than windows.
> I dont think that FreeBSD has achieved this. I dont think there is
> need. FreeBSD is more suitable for a server station, but not for the
> desktop. I use linux both as server and desktop with excelent results.

servers can be managed by purpose built gui shells but they would needs
be a very complicated and very very deep multi-leveled, many menued
beast tehat would be an almost nightmare to navigate, eve if it were
designed "properly" !!!

user interfaces can be very well served by a text console or text
shell .. basically it depends on what you grew up with and it is this
dichotomy that is driving the current schism twix gui/non-gui users.
each side has valid arguemnts .. but the truth lies in between teh two
'extremes', or so it has been shown to me over these few decades that
i've watched this system develop, and so on.

> I am using FreeBSD since a few weeks ago, also with excelents resutls.
> But I see it is not desktop oriented (I repeat, this seems ok for me.
> FreeBSD is better for a server station, not for a desktop).

i've been using computers to solve problems and provide solutions since
os9 was a twinkle in its parents eyes (microware) and qnx was going
ultra reliable realtime unix(alike) operating systems and teh text
console was king .. then came novel os/2 and ms windows v3.11 each one
was really hard to adjust too and dificult to change from untill i came
to qwindows this was based upon an x11 distribution (forgot which one)
but it was quick clean comfortable to use and gave me direct access to
teh cli (command line interface) if it was needed and it was an easy
and simple switch. all of teh current crop of gui's are not !

what i'm trying to say is tha these days in an effort to become "easy
to use" the gui interface which sits on top off and between teh user
and the operating system propper has become a very complicated and
indeed very bloated and in some cases almost uslessly crippling "user
interface".

perhaps, we (at freebsd) should settle upon a clean easyish simple and
lightweight GUI that we accpet as the official freebsd gui and set up a
dev team to set it up as the gui that freebsd uses to provide teh 'ease
of use' most new users are looking for when they move from another
gui'fied platform be it microsoft window, mac, or some other custom
platform. thier whole task would be to work on integrating the freebsd
gui into/with the freebsd oprating system but keeping it seperate so
that it would be like a jacket one could put on when the weather turns
bad or one goes from one environment to another .. to use another
analogy. when one becomes aclimatised to teh new environment then to
get better performance, easier usage and so forth then you could then take
off the jecket (take out the gui environment) and use the "raw" or the
cli shell that is the basic way most all operating systems have by way
of teh users interoperating with the core of the "operating system".

> I dont think that there is an OS that is the best for all the
> purposes. Use windows if you want to play the latest games. Use *BSD
> if you want or need a really good unix. Use linux if .. ( fill in
> the blanks ;) )

> Please let me know if you dont agree, and why.

i disagree .. not so much with wghat you have said, maxi, rather with
the usage paterns that we have all sortof assumed are teh way things
were, work etc, etc, at teh end of teh line all operating systems are
really identicle, why ? because an operating system is the controls
built into the cpu systems command protocol structure that feeds
information to, retrieves information from, queue work streams for the
cpu to process, move around its varions media channels. now that
"shell" that we users see, use and or interface with this raw and basic
level protocol system/language.

now this interface level can be a direct 'text console' cli as in most
unix like shells or the ever more popular graphical user interface -
gui. over time the developers of these interface tools start to add
stuff that makes teh job 'easier' to use untill the point that the
whole system become 

RE: SSHD and FTPD, can't connect

[Matt Smith]

Hello,
you may remember the problems that my friends were having with
ssh/ftp timeouts.  Well now I have the same issue with my FBSD 4.10
install.  I can ping the box and use the Apache and telnet daemons, but
not the SSHD or FTPD.  I tried to upgrade the SSHD to no avail and I CAN
connect to the daemons from the loopback address, but not across my home
LAN.  Any suggestions?

 Matt 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Debug help - 5.3 lockups on amd64 SMP

[Vivek Khera]

On Jun 6, 2005, at 1:06 PM, Matthew Grooms wrote:


 I am experiencing lockups on a production 5.4 amd64 SMP system.



$subject says 5.3, message says 5.4.  which is it?  There was a  
"lockup fix" for SMP amd64 systems just before 5.4 was released.


Also, what ethernet driver are you using?  I had major problems with  
bge network cards (on the mobo) under heavy disk + network load.   
Many lockups and reboots.   I ended up putting in intel NICs and the  
problem went away.


Vivek Khera, Ph.D.
+1-301-869-4449 x806

Re: filesystems not properly unmounted [OT]

[Matthias Buelow]

Iulian M wrote:

> http://www.parashift.com/c++-faq-lite/big-picture.html#faq-6.5
> 
> it's about the best programing language ... but if you replace "programing 
> language" with "OS" it still applys.

>From the web page:

  "Anyone who argues in favor of one language over another in a purely
technical manner (i.e., who ignores the dominant business issues)
exposes themself as a techie weenie, and deserves not to be heard."

I wouldn't argue that the point the person wants to express doesn't have
some truth in it but imho anyone who talks in such a condescending tone
about "tech weenies" when they present logically sound arguments is
someone who deserves not to be heard.

mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Debug help - 5.3 lockups on amd64 SMP

[Matthew Grooms]

All,

 I am experiencing lockups on a production 5.4 amd64 SMP system. 
Its lightly loaded and seems to last about 3-5 days before it stops 
responding to network or even console interaction. The system is acting 
as a firewall and runs a mostly stock kernel with IPV6 removed and SMP, 
PF, PFLOG, CARP and ALTQ added. The only other thing I can think to note 
is that tcpdump is running constantly on the pflog interface to coax 
human readable firewall logs out of pf.


I have an identical hot spare server with SMP disabled that has 
taken over flawlessly every time the live lock occurs so I am willing to 
leave the primary in the production environment to do testing and gather 
debug info. I have added the following options to primary fw kernel 
config ...


# Debug Options
makeoptions DEBUG=-g
options DDB
options KDB
options BREAK_TO_DEBUGGER
options INVARIANT_SUPPORT
options INVARIANTS
options WITNESS
options WITNESS_KDB
options WITNESS_SKIPSPIN

... and the following to the rc.conf ...

dumpdev="/dev/amrd0s1h"
dumpdir="/var/crash"

Will this do it or should I add anything else?

Thanks in advance,

-Matthew

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Iulian M]

On Monday 06 June 2005 17:02, Oliver Fromme wrote:

>
> Yup, I know the usual freebsd-for-servers and linux-for-
> desktops arguments.  And to be honest, I'm fed up with
> them.  They're lies.  I'm running FreeBSD on my desktop
> at home, a lot of people are happily running Linux on
> their servers, and I've seen people successfully installing
> FreeBSD who have never even heard the word "unix" until
> that day.
>
>  > Please let me know if you dont agree, and why.
>

http://www.parashift.com/c++-faq-lite/big-picture.html#faq-6.5

it's about the best programing language ... but if you replace "programing 
language" with "OS" it still applys.

-- 
The sergeant walked into the shower and caught me giving myself a
dishonorable discharge.  Without missing a beat, I said, "It's my dick
and I can wash it as fast as I want!"


pgpUy6PTLo975.pgp
Description: PGP signature

Re: filesystems not properly unmounted [OT]

[Oliver Fromme]

Yuval Levy <[EMAIL PROTECTED]> wrote:
 > Oliver Fromme wrote:
 > > I do look carefully every day, because it's my job.  I work
 > > with various operating systems every day, including FreeBSD
 > > and Linux.
 > 
 >  From a professional I would expect a more mature and balanced approach, 
 > rather than "my favorite OS is the best one and the others have no 
 > advantages".

That's not what I wrote.  FreeBSD is not "the best".  There
is no such thing as "the best", in general.

 > Be real: there is a lot of diversity of OS out there and 
 > they all have advantages and disadvantages.

Right.  Everyone has to decide for himself which tool works
best for his job.

 > > Yup, I know the usual freebsd-for-servers and linux-for-
 > > desktops arguments.  And to be honest, I'm fed up with
 > > them.  They're lies.  I'm running FreeBSD on my desktop
 > > at home, a lot of people are happily running Linux on
 > > their servers, and I've seen people successfully installing
 > > FreeBSD who have never even heard the word "unix" until
 > > that day.
 > 
 > You can run FreeBSD on your desktop at home because you have the skills, 
 > the time, the dedication.

For most "standard" applications it doesn't require any
more skills (or time, or dedication) than with any other
OS.  In fact, getting some applications to work correctly
under, say, Windows requires more skills (and time, and
dedication) sometimes.

 > You are special. Every human being is special

Right.  I don't disagree with you there.

 > [...]  They do not share your view. 
 > I do not share your view. This does not make us liars.

Uhm, what are you talking about?  I've never called you a
liar.  But those people who claim that FreeBSD is only
suitable for servers and Linux is only suitable for desk-
tops -- those are liars.  There are plenty of counter-
examples.

 > I am moving my servers from Linux to FreeBSD, because FreeBSD gives me 
 > the manageability, stability and security that are more important to my 
 > clients than the bleeding edge features that often make it into Linux first.
 > 
 > I am generally inclined toward Open Source software over proprietary 
 > one, but will pragmatically mix and match to obtain what works best for 
 > me rather than dogmatically pretend that my favorite OS is the best and 
 > its filesystem is the brightest and its license is the only acceptable 
 > distribution form.

I agree 100%.  

Most of "my" machines (i.e. the machines which I own or
which I'm responsible for to operate) run FreeBSD, but some
also run Linux (Debian), Solaris or Windows.  I used to
have OpenBSD, too, but it stopped working for me (a long
story).  And currently I'm evaluating to move one of my
privat machines from FreeBSD to DragonFly BSD, because
some of its features would be very useful.

Still, of all of those systems, FreeBSD is (currently) my
favourite.  It's particularly versatile to work well for
all kinds of different purposes, including servers _and_
desktops.

 > Which brings me back to the topic of this thread: is there anybody out 
 > there with the skills to cleanly solve this shameful situation in which 
 > rebooting FreeBSD results in unclean mounting of ext2 (and potentially 
 > other) volumes?

A umount command in rc.shutdown should be a feasible
work-around.

Fixing the driver is probably not a high-priority, because
not many users are affected by the problem, I guess.
(But then again:  It's open source, so you can try to fix
it yourself.)

Best regards
   Oliver

PS:  I think this should rather move to the -chat list.

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"And believe me, as a C++ programmer, I don't hesitate to question
the decisions of language designers.  After a decent amount of C++
exposure, Python's flaws seem ridiculously small." -- Ville Vainio
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Wilko Bulte]

Can the two of you please take this bikeshed to -chat or
wherever?

Thank you,
Wilko


On Mon, Jun 06, 2005 at 11:00:41AM -0400, Yuval Levy wrote..
> Oliver Fromme wrote:
> 
> >I do look carefully every day, because it's my job.  I work
> >with various operating systems every day, including FreeBSD
> >and Linux.
> > 
> >
> From a professional I would expect a more mature and balanced approach, 
> rather than "my favorite OS is the best one and the others have no 
> advantages". Be real: there is a lot of diversity of OS out there and 
> they all have advantages and disadvantages. For as much as I love 
> FreeBSD, it is not (and probably can't be) better than all OS on all 
> comparisons. Diversity is good, most existing OS have their rightful 
> place in the IT ecosystem.
> 
> >> Just to mention the first thing that comes to my mind: several linux
> >> distros have achieved a difficult goal: ease of installation-use
> >> combined with a stable system.
> >
> >Yup, I know the usual freebsd-for-servers and linux-for-
> >desktops arguments.  And to be honest, I'm fed up with
> >them.  They're lies.  I'm running FreeBSD on my desktop
> >at home, a lot of people are happily running Linux on
> >their servers, and I've seen people successfully installing
> >FreeBSD who have never even heard the word "unix" until
> >that day.
> > 
> >
> You can run FreeBSD on your desktop at home because you have the skills, 
> the time, the dedication. You are special. Every human being is special 
> and there are plenty of us out there that have other skills and want to 
> dedicate their time to something else (like 
> ). They do not share your view. 
> I do not share your view. This does not make us liars.
> 
> I am moving my servers from Linux to FreeBSD, because FreeBSD gives me 
> the manageability, stability and security that are more important to my 
> clients than the bleeding edge features that often make it into Linux first.
> 
> I am generally inclined toward Open Source software over proprietary 
> one, but will pragmatically mix and match to obtain what works best for 
> me rather than dogmatically pretend that my favorite OS is the best and 
> its filesystem is the brightest and its license is the only acceptable 
> distribution form.
> 
> Which brings me back to the topic of this thread: is there anybody out 
> there with the skills to cleanly solve this shameful situation in which 
> rebooting FreeBSD results in unclean mounting of ext2 (and potentially 
> other) volumes?
> 
> Yuv
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--- end of quoted text ---

-- 
Wilko Bulte [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kadmin (heimdal port) ignores the ldap backend

[Boris Samorodov]

On Mon, 06 Jun 2005 13:59:48 +0200 fandino wrote:

> Scot Hetzel wrote:
> > I believe you have to set NO_KERBEROS in /etc/make.conf.  Then rebuild
> > & install the FreeBSD sources in /usr/src.  Then after the
> > installworld, you'll need to go to the /usr/lib directory and
> > move/remove all libs that are older than the date of the install.

> ok, I see two possibles fixes:

> 1) set NO_KERBEROS in /etc/make.conf, it seems more painless solution
> than making wrapper scripts around kadmin, kdc, kpasswd and all
> kerberized programs.

You'll get non-kerberized apps. One of the most important is
sshd. Those from port uses imho MIT Kerberos implementation.

> 2) also setting HEIMDAL_HOME=/usr at /etc/make.conf can be another solution.

> Now, to send a problem report to the heimdal maintainer port I think 2) is 
> better
> because it's easier overwrite the base system than locate and remove several 
> files.

This one is better.

> what do you think about this?

And what about doing as-is now but changing LD_SEARCH order?


WBR
-- 
bsam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Yuval Levy]

Oliver Fromme wrote:


I do look carefully every day, because it's my job.  I work
with various operating systems every day, including FreeBSD
and Linux.
 

From a professional I would expect a more mature and balanced approach, 
rather than "my favorite OS is the best one and the others have no 
advantages". Be real: there is a lot of diversity of OS out there and 
they all have advantages and disadvantages. For as much as I love 
FreeBSD, it is not (and probably can't be) better than all OS on all 
comparisons. Diversity is good, most existing OS have their rightful 
place in the IT ecosystem.



> Just to mention the first thing that comes to my mind: several linux
> distros have achieved a difficult goal: ease of installation-use
> combined with a stable system.

Yup, I know the usual freebsd-for-servers and linux-for-
desktops arguments.  And to be honest, I'm fed up with
them.  They're lies.  I'm running FreeBSD on my desktop
at home, a lot of people are happily running Linux on
their servers, and I've seen people successfully installing
FreeBSD who have never even heard the word "unix" until
that day.
 

You can run FreeBSD on your desktop at home because you have the skills, 
the time, the dedication. You are special. Every human being is special 
and there are plenty of us out there that have other skills and want to 
dedicate their time to something else (like 
). They do not share your view. 
I do not share your view. This does not make us liars.


I am moving my servers from Linux to FreeBSD, because FreeBSD gives me 
the manageability, stability and security that are more important to my 
clients than the bleeding edge features that often make it into Linux first.


I am generally inclined toward Open Source software over proprietary 
one, but will pragmatically mix and match to obtain what works best for 
me rather than dogmatically pretend that my favorite OS is the best and 
its filesystem is the brightest and its license is the only acceptable 
distribution form.


Which brings me back to the topic of this thread: is there anybody out 
there with the skills to cleanly solve this shameful situation in which 
rebooting FreeBSD results in unclean mounting of ext2 (and potentially 
other) volumes?


Yuv
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Oliver Fromme]

Maxi Combina <[EMAIL PROTECTED]> wrote:
 > 
 > > > I do not seed the need of insult other OS.
 > May be you need to look more carefully. I am not talking _only_ about
 > this thread.

You replied specifically to my mail, and you didn't mention
any other threads.

 > > Well, I don't see any.  But everybody is free to have his
 > > own opinion.
 > Well, I insist: maybe you should look more carefully :)

I do look carefully every day, because it's my job.  I work
with various operating systems every day, including FreeBSD
and Linux.

 > Just to mention the first thing that comes to my mind: several linux
 > distros have achieved a difficult goal: ease of installation-use
 > combined with a stable system.

Yup, I know the usual freebsd-for-servers and linux-for-
desktops arguments.  And to be honest, I'm fed up with
them.  They're lies.  I'm running FreeBSD on my desktop
at home, a lot of people are happily running Linux on
their servers, and I've seen people successfully installing
FreeBSD who have never even heard the word "unix" until
that day.

 > Please let me know if you dont agree, and why.

I don't agree, but I won't tell you why, because it is
probably a waste of time.  I've had this a thousand times
before.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"I invented Ctrl-Alt-Delete, but Bill Gates made it famous."
-- David Bradley, original IBM PC design team
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Matthias Buelow]

Maxi Combina wrote:

> companies, etc) to move to an open source OS, we must do an effort. I
> think that there are a lot of linux distros out there that are really
> easy to use, and even more "friendly" or "beatiful" than windows.
> I dont think that FreeBSD has achieved this. I dont think there is
> need. FreeBSD is more suitable for a server station, but not for the
> desktop. I use linux both as server and desktop with excelent results.

If you want a Unix desktop, like most likely many people on this mailing
list want, or need, you can use FreeBSD aswell as Linux but not Windows
(even with things like UWin or Cygwin, it's a pain).

I don't understand this "we need to compete with Windows on the desktop"
thing. I've never considered Windows to be particularly useful as a
desktop environment, why should the Unix systems compete with it?

[And btw., please let's move this discussion to -advocacy, since it
doesn't really belong on this list.]

mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Maxi Combina]

>  > I do not seed the need of insult other OS.
May be you need to look more carefully. I am not talking _only_ about
this thread.
As I said, I dont wanna flame, just reflecting (or trying to :) )

>  > Even worse if the other OS is open source (as linux).
> 
> Being open source doesn't mean that a piece of software is
> any good.  In fact, I've seen a lot of open source which
> is just plain crap.  (OK, now _this_ is an insult, but I
> didn't mention any specific software in particular.)
Totally agree.

> Well, I don't see any.  But everybody is free to have his
> own opinion.
Well, I insist: maybe you should look more carefully :)
Just to mention the first thing that comes to my mind: several linux
distros have achieved a difficult goal: ease of installation-use
combined with a stable system. I have no trouble with a "diffucult /
unix-like" OS, but a lot of people do. And this a _fact_.They dont
have time to spend learning to use a "dificult" OS. And I think that
if we want to tell more and more people (friends, family, goverment,
companies, etc) to move to an open source OS, we must do an effort. I
think that there are a lot of linux distros out there that are really
easy to use, and even more "friendly" or "beatiful" than windows.
I dont think that FreeBSD has achieved this. I dont think there is
need. FreeBSD is more suitable for a server station, but not for the
desktop. I use linux both as server and desktop with excelent results.
I am using FreeBSD since a few weeks ago, also with excelents resutls.
But I see it is not desktop oriented (I repeat, this seems ok for me.
FreeBSD is better for a server station, not for a desktop).
I dont think that there is an OS that is the best for all the
purposes. Use windows if you want to play the latest games. Use *BSD
if you want or need a really good unix. Use linux if .. ( fill in
the blanks ;) )
Please let me know if you dont agree, and why.

Best regards,
Maxi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: filesystems not properly unmounted [OT]

[Oliver Fromme]

Maxi Combina <[EMAIL PROTECTED]> wrote:
 > 
 > > Personally, I have used the ext2fs driver for exactly one
 > > reason:  to migrate data from Linux to FreeBSD on machines
 > > which are being converted from the Dark Side.  And that
 > 
 > I do not seed the need of insult other OS.

And I do not see any insult.

(If you're referring to the "Dark Side" pun, then maybe you
should check whether /dev/irony is working correctly for
you.  I really thought it wouldn't be necessary to add a
smiley in that place, but unfortunately I seemed to be
wrong.)

 > Even worse if the other OS is open source (as linux).

Being open source doesn't mean that a piece of software is
any good.  In fact, I've seen a lot of open source which
is just plain crap.  (OK, now _this_ is an insult, but I
didn't mention any specific software in particular.)

 > Linux has its _really_ good points.

Well, I don't see any.  But everybody is free to have his
own opinion.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.

"IRIX is about as stable as a one-legged drunk with hypothermia
in a four-hundred mile per hour wind, balancing on a banana
peel on a greased cookie sheet -- when someone throws him an
elephant with bad breath and a worse temper."
-- Ralf Hildebrandt
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: kadmin (heimdal port) ignores the ldap backend

[fandino]

Scot Hetzel wrote:

I believe you have to set NO_KERBEROS in /etc/make.conf.  Then rebuild
& install the FreeBSD sources in /usr/src.  Then after the
installworld, you'll need to go to the /usr/lib directory and
move/remove all libs that are older than the date of the install.


ok, I see two possibles fixes:

1) set NO_KERBEROS in /etc/make.conf, it seems more painless solution
   than making wrapper scripts around kadmin, kdc, kpasswd and all
   kerberized programs.

2) also setting HEIMDAL_HOME=/usr at /etc/make.conf can be another solution.

Now, to send a problem report to the heimdal maintainer port I think 2) is 
better
because it's easier overwrite the base system than locate and remove several 
files.

what do you think about this?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: wine HEAP_CreateSystemHeap error still not solved/back in?

[Simon Barner]

c.f. http://www.freebsd.org/cgi/query-pr.cgi?pr=81940 (submitted by
Holger Kipp)


pgp9HqpZVl7WO.pgp
Description: PGP signature

Re: Logitech Cordless Internet Pro Desktop

[Riv Octovahriz]

Ruben van Staveren wrote:

>
> On 18 May 2005, at 9:20, Paig Chong Woo wrote:
>
>>>
>>> It seems that FreeBSD already detect the mouse as ums0, and the 
>>> keyboard
>>> as ukbd0, but my mouse didn't work.
>>> usbd already attach my mouse as ums0, and still nothing happens
>>>
>>> Anyone had the similar problem? Or even better, does anyone has any
>>> solution for this :-)
>>
>
> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=63837 for a fix.
>
> Works for my Logitech Cordless Desktop.
>
> Regards,
> Ruben
>
>
>
thank you so much, it works perfectly :)


signature.asc
Description: OpenPGP digital signature