date:20061216

Hi,

I need to run X ... or in some way gain access to the display output on a 
remote box that has neither mouse, keyboard, or console.

Is this even possible?

I've been looking at the handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html#AEN6864

But it doesn't jump out at me how I should make this work.

I've edited /usr/X11R6/lib/X11/xdm/xdm-config and Xaccess to listen for the 
connection, but when I run 

xdm

on the remote box it fails with No core pointer

So I followed the limited instructions on the X wiki and added 

Section ServerFlags
option AllowMouseOpenFail
EndSection

But now I get 

Fatal error: no screens found.

Is it even possible to have the remote headless box host an X session?

thanks,

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

Re: New style with Fluxbox


On 12/16/06, Olivier Regnier [EMAIL PROTECTED] wrote:

Hello,

Yesterday, i installed by the ports, fluxbox version 0.1.14_2


Please try the newer version, x11-wm/fluxbox-devel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: xorg on a headless, mouseless, keyboardless box


On 12/16/06, Lane [EMAIL PROTECTED] wrote:

Hi,

I need to run X ... or in some way gain access to
the display output on a remote box that has neither
mouse, keyboard, or console.


Can you tell us what you really need?

Try ssh -X [EMAIL PROTECTED] and running gui apps or
even startx there.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: xorg on a headless, mouseless, keyboardless box

2006-12-16 Thread Lonnie Cumberland

Alternately you can also run an NX server and NX client or even TightVNC 
to access GDM, KDM, or XDM remotely as well.


Cheers,
Lonnie

Andrew Pantyukhin wrote:


On 12/16/06, Lane [EMAIL PROTECTED] wrote:


Hi,

I need to run X ... or in some way gain access to
the display output on a remote box that has neither
mouse, keyboard, or console.



Can you tell us what you really need?

Try ssh -X [EMAIL PROTECTED] and running gui apps or
even startx there.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
[EMAIL PROTECTED]



--
Thanks and have a good day,

Lonnie T. Cumberland
OutStep Technologies Incorporated

Email: [EMAIL PROTECTED]
  [EMAIL PROTECTED] 


Open Source.. opening the doors for the future in the world of today

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

Re: compilation problems with some code from Linux

2006-12-16 Thread Andrew Falanga


On 12/8/06, Lane [EMAIL PROTECTED] wrote:


On Friday 08 December 2006 11:21, Andrew Falanga wrote:
 Hi,

 I'm trying to port some code from Linux to FreeBSD and I've got an issue
 that revolves around something I've never dealt with before.  The code
 includes the following header:

 #include sys/ucred.h

 Apparently, program is attempting to make use of the xucred structure
 defined in there, because the rest of the stuff in the file seems to be
for
 the kernel.  However, when I try to compile, gcc continually bails with
the
 following error (among others), NGROUPS was not declared in this
scope.
 The NGROUPS appears to be a macro, but it's not defined earlier
on.  Would
 anyone here know where it's defined so I can include that file too?

 Secondly, I'm also getting errors because gcc can't find sys/vfs.h
 either.  True enough, there isn't any vfs.h file in /usr/include/sys.
 Since this file is in Linux, what should I include for FreeBSD?

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

I won't pretend to know exactly which header files correspond for your
port,
but in the past I've found some things that work for me:

use

locate vfs.h

to find similar file names.  On 6.x and 5.x I see that these are possible
candidates:

/usr/X11R6/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs.h
/usr/include/fs/devfs/devfs.h
/usr/include/sys/statvfs.h
/usr/local/include/af_vfs.h
/usr/src/sys/compat/svr4/svr4_statvfs.h
/usr/src/sys/fs/devfs/devfs.h
/usr/src/sys/nfs4client/nfs4_vfs.h
/usr/src/sys/sys/statvfs.h


But you'd have to compare the functions and structures defined in
sys/vfs.h on
linux to determine which is your best match up.

There is /usr/ports/devel/mipsel-linux-kernel-headers/ which, according to
pkg-plist will install mipsel-linux/include/linux/vfs.h.  That may be
exactly
what you need (although it may be overkill).  Or it may be the LAST thing
you
need :)

Sometimes a porter will simply create a patch file
in /usr/ports/portname/files that will create a skeleton version of the
file which includes only the items you need.  I've done this for
development
on my own system.

As far as the NGROUP or other macros ... yikes!  You may have to recreate
that
functionality entirely.

I ran this:

#!/bin/sh
for each in `locate  .h | grep '\.h$'`
do
if [ -f $each ]; then
MYF=`cat $each | grep -i ngroups`
if [ x$MYF != x ]; then
echo $each : $MYF
fi
MYF=
fi
done


It could probably be done more easily with sed and some elbow grease, but
it
does show NGROUPS defined here:

/usr/X11R6/include/X11/Xos.h : #define NGROUPS 16

and

/usr/include/sys/param.h

among other places.

Good luck!

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





Thank you everyone.  I'm sorry that I didn't reply sooner.  I did get this
worked out, but unfortunately I don't remember the include file I had to
use.  I found in a different file than the one I was editing at the time I
wrote this a nice comment explaining why the #include sys/vfs.h
preprocessor directive was there.  I found that function in a different
include file for FreeBSD, changed the code and all was well.

Thanks again.

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

Re: xorg on a headless, mouseless, keyboardless box

On Saturday 16 December 2006 12:34, Andrew Pantyukhin wrote:
 On 12/16/06, Lane [EMAIL PROTECTED] wrote:
  Hi,
 
  I need to run X ... or in some way gain access to
  the display output on a remote box that has neither
  mouse, keyboard, or console.

 Can you tell us what you really need?

 Try ssh -X [EMAIL PROTECTED] and running gui apps or
 even startx there.
Andrew,

What I need is a tall order :)

What I'd like is an understanding of how X can be used for remote connections, 
such as is described here:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html#AEN6864

I'd like to be able to work on the remote box in a graphical environment and 
not have to mount_nfs the devices I need to work with ...

I'd also like to be able to start qemu on the remote machine with a Windows 
client and be able to invoke safe mode.  I have a problem with a remote W2K 
image that is 4Gig compressed, and it is going to take 12 or more hours for 
me to get it copied to my local machine to fix it ... then another 12 hours 
to copy it back out there.

There are probably some switches that I can use in qemu that I may discover 
over the next 12 hours, but an understanding of how X can help might actually 
save me some time.

I've used this ssh -X that you mention. This works fine for userland 
programs, but in order to troubleshoot my particular issue I'd need to be 
logged in as root.  When I try to su remotely to run the command I get:

X11 connection rejected because of wrong authentication.
X connection to localhost:10.0 broken (explicit kill or server shutdown).

I might try logging in locally as root and see what happens  

But in the long run I think that if I could understand how to grant myself an 
actual X session on the remote box then I could figure out how to do this and 
potentially other stuff.

Thanks for any information you might share.

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

Re: New style with Fluxbox

2006-12-16 Thread Olivier Regnier

I installed fluxbox-devel and it's ok. Im' happy :)

Thank you ;)

On Sat, 16 Dec 2006 21:31:03 +0300
Andrew Pantyukhin [EMAIL PROTECTED] wrote:

 On 12/16/06, Olivier Regnier [EMAIL PROTECTED] wrote:
  Hello,
 
  Yesterday, i installed by the ports, fluxbox version 0.1.14_2
 
 Please try the newer version, x11-wm/fluxbox-devel
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Translate job number from atq to commands that will run

2006-12-16 Thread JAMES T RIENDEAU

Does anybody know how I could translate the job # into the commands  
that will run from the output of the atq command?  For example, here  
is my current atq:


DateOwner   Queue   Job #
Mon Dec 18 09:00:00 CST 2006rootc   34
Wed Dec 20 09:00:00 CST 2006rootc   35
Fri Dec 22 09:00:00 CST 2006rootc   36
Wed Dec 27 09:00:00 CST 2006rootc   37
Sat Dec 30 09:00:00 CST 2006rootc   38
Wed Jan  3 09:00:00 CST 2007rootc   39
Sat Jan  6 09:00:00 CST 2007rootc   40
Mon Dec 18 09:00:00 CST 2006rootc   41
Wed Dec 20 09:00:00 CST 2006rootc   42
Fri Dec 22 09:00:00 CST 2006rootc   43
Wed Dec 27 09:00:00 CST 2006rootc   44
Sat Dec 30 09:00:00 CST 2006rootc   45
Wed Jan  3 09:00:00 CST 2007rootc   46
Sat Jan  6 09:00:00 CST 2007rootc   47

I checked the /var/at/spool and /var/at/jobs, but it isn't obvious  
which job is scheduled to run when.


Thank you,

James Riendeau
MMI Computer Support Technician
1300 University Ave
Rm. 436, Dept. of MedMicro
Madison, WI  53706

Phone: (608) 262-3351
Email: [EMAIL PROTECTED]



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

Re: xorg on a headless, mouseless, keyboardless box

2006-12-16 Thread Garrett Cooper


On Dec 16, 2006, at 10:24 AM, Lane wrote:


Hi,

I need to run X ... or in some way gain access to the display  
output on a

remote box that has neither mouse, keyboard, or console.

Is this even possible?

I've been looking at the handbook:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x- 
xdm.html#AEN6864


But it doesn't jump out at me how I should make this work.

I've edited /usr/X11R6/lib/X11/xdm/xdm-config and Xaccess to listen  
for the

connection, but when I run

xdm

on the remote box it fails with No core pointer

So I followed the limited instructions on the X wiki and added

Section ServerFlags
option AllowMouseOpenFail
EndSection

But now I get

Fatal error: no screens found.

Is it even possible to have the remote headless box host an X session?

thanks,

lane


Lane,
	Did you by chance remove keyboard / mouse support from your kernel?  
kldstat(8) may hold the answers, unless you have the mouse compiled  
directly into the kernel. Sounds like that may be your problem:  
http://www.mail-archive.com/linux-newbie@vger.kernel.org/ 
msg06918.html.
	So you could try commenting out the mouse and keyboard references,  
just to see what happens..
	Another solution that you may want to look into as an alternative to  
using xdm is X11 forwarding via SSH.

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

Re: xorg on a headless, mouseless, keyboardless box

On Saturday 16 December 2006 17:11, Garrett Cooper wrote:
 On Dec 16, 2006, at 10:24 AM, Lane wrote:
  Hi,
 
  I need to run X ... or in some way gain access to the display
  output on a
  remote box that has neither mouse, keyboard, or console.
 
  Is this even possible?
 
  I've been looking at the handbook:
 
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-
  xdm.html#AEN6864
 
  But it doesn't jump out at me how I should make this work.
 
  I've edited /usr/X11R6/lib/X11/xdm/xdm-config and Xaccess to listen
  for the
  connection, but when I run
 
  xdm
 
  on the remote box it fails with No core pointer
 
  So I followed the limited instructions on the X wiki and added
 
  Section ServerFlags
  option AllowMouseOpenFail
  EndSection
 
  But now I get
 
  Fatal error: no screens found.
 
  Is it even possible to have the remote headless box host an X session?
 
  thanks,
 
  lane

 Lane,
   Did you by chance remove keyboard / mouse support from your kernel?
 kldstat(8) may hold the answers, unless you have the mouse compiled
 directly into the kernel. Sounds like that may be your problem:
 http://www.mail-archive.com/linux-newbie@vger.kernel.org/
 msg06918.html.
   So you could try commenting out the mouse and keyboard references,
 just to see what happens..
   Another solution that you may want to look into as an alternative to
 using xdm is X11 forwarding via SSH.
 -Garrett
Garrett, 

Thanks for responding.

No, it's an SMP kernel which includes GENERIC.

Do you mean commenting out references to mouse and keyboard 
in /sys/i386/conf/GENERIC?

Like these:

device  atkbdc  # AT keyboard controller
device  atkbd   # AT keyboard
device  psm # PS/2 mouse

That seems a little extreme  - recompiling the kernel to get X to work?  I'll 
certainly do it if the technique is endorsed by anyone ... but I'm not so 
much ready to see what happens, as the server is thirty miles away behind a 
locked door, and I may not like what happens, at all :)

Yeah, the ssh -X trick works great for userland stuff.  But I haven't yet 
fingered out how to run a gui process on the remote as root and get by the 
authentication issues.

Do you have any experience with that?

Thanks, again.

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

Re: xorg on a headless, mouseless, keyboardless box

2006-12-16 Thread Christopher Cowart

 I've used this ssh -X that you mention. This works fine for userland 
 programs, but in order to troubleshoot my particular issue I'd need to be 
 logged in as root.  When I try to su remotely to run the command I get:
 
 X11 connection rejected because of wrong authentication.
 X connection to localhost:10.0 broken (explicit kill or server shutdown).

I think what's going on is that X puts some authentication information
in your home directory: ~/.Xauthority. You might try:
$ su -m

That will preserve your environment (including $HOME). Now when X goes
looking for the ~/.Xauthority, it will find the one sshd set up in your
user home directory.

 
 I might try logging in locally as root and see what happens  
 
 But in the long run I think that if I could understand how to grant myself an 
 actual X session on the remote box then I could figure out how to do this and 
 potentially other stuff.
 
 Thanks for any information you might share.
 
 lane
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

-- 
Chris Cowart
Network and Infrastructure Systems Administrator
RSSP-IT, UC Berkeley
May all your pushes be popped


signature.asc
Description: Digital signature

Re: xorg on a headless, mouseless, keyboardless box

On Saturday 16 December 2006 17:32, you wrote:
  I've used this ssh -X that you mention. This works fine for userland
  programs, but in order to troubleshoot my particular issue I'd need to be
  logged in as root.  When I try to su remotely to run the command I get:
 
  X11 connection rejected because of wrong authentication.
  X connection to localhost:10.0 broken (explicit kill or server shutdown).

 I think what's going on is that X puts some authentication information
 in your home directory: ~/.Xauthority. You might try:
 $ su -m

 That will preserve your environment (including $HOME). Now when X goes
 looking for the ~/.Xauthority, it will find the one sshd set up in your
 user home directory.

Well, Chris, that was a great suggestion!

I can, in fact, run a gui root process on the remote machine, now.

Unfortunately I still can't run qemu so that I can get the console.  I get:

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  25 (X_SendEvent)
  Resource id in failed request:  0x3e
  Serial number of failed request:  18
  Current serial number in output stream:  21


Any advice on how to setup the remote (headless, mouseless, and keyboardless) 
server to run X?  My brain is fried trying to track down a HOWTO, and the 
wiki is just a half millimeter left of useless.

Thanks for your input!

Lane
  I might try logging in locally as root and see what happens 
 
  But in the long run I think that if I could understand how to grant
  myself an actual X session on the remote box then I could figure out how
  to do this and potentially other stuff.
 
  Thanks for any information you might share.
 
  lane
  ___
  freebsd-questions@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to
  [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

1440x900

2006-12-16 Thread dsikorsky

I just orderd a widescreen 19 inch, I have a radeon x300se 128mb card, and
am using freebsd 6.1, gnome 2.16, and x11 6.9  (xorg)

how do I use this resolution?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: 1440x900


On 12/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

I just orderd a widescreen 19 inch, I have a radeon x300se 128mb card, and
am using freebsd 6.1, gnome 2.16, and x11 6.9  (xorg)

how do I use this resolution?


The same way you use any other one.

(a) autodetection
(b) xorg.conf
(c) gnome settings
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Unicode support on FreeBSD

2006-12-16 Thread Henry Lenzi


On 12/16/06, 文鳥 [EMAIL PROTECTED] wrote:

   It's worth noting that while this solution may work, it's an
 add-on.
   The question of Unicode is complex; you should check for
 relevant threads in the questions@ and i18n@ archives.
I am using FreeBSD 6.1. with locale set to ja_JP.UTF-8


I'm sorry, I'm not following this discussion. To get Unicode support,
I should set my system to ja_JP.UTF8?!
My problem is cyrillic fonts; any help is aprreciated.

Henry

PS: Oh, and don't write back to me in Russian, please. I'm not there yet :-))
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Unicode support on FreeBSD


On 12/16/06, Garrett Cooper [EMAIL PROTECTED] wrote:

Just wondering if and how I would go about getting Unicode
support setup on FreeBSD. Any links I could get would be more than
appreciated.


Not very helpful, but still:
http://infofarmer.blogspot.com/2006/12/unicodifying-freebsd.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Interrupt storm on an MS-1029 (AMD Turion 64)

2006-12-16 Thread [EMAIL PROTECTED]

Is anyone aware of problems with FreeBSD on the MS-1029 notebook or is
this a bona fide bug?

-Robert Johnson, [EMAIL PROTECTED]

STATEMENT OF PROBLEM

FreeBSD 6.1 runs very slowly out of the box on my MS-1029 AMD Turion
notebook computer. The first line from the output of 'ps -aux' tells
that interrupt 19, in use by the ohci and cardbus systems, is consuming
80% of the CPU time:

USERPID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
root 21 79.1 0.0 016 ?? LL 11:52AM 25:48.51 [irq19:
cbb0 ohci

ATTEMPTED RESOLUTIONS
=
I attempted to disable the affected devices in the boot configuration
file /boot/device.hints. In all cases my 'hints' were ignored and
the device drivers were loaded as normal. I also tried to do the
equivalent with sysctls, also to no avail (though I might be doing the
Wrong Thing):

hint.ohci.0.disabled=1
hint.usb.0.disabled=1
hint.cardbus.0.disabled=1
hint.pccard.0.disabled=1

Booting in safe mode and with ACPI disabled did not help.

I rebuilt the kernel with the cardbus driver disabled. This caused the
cardbus to disappear from the problem process in 'ps' but the ohci
driver was still using irq19 and was having an interrupt storm. In the
compromised state of my computer it takes 48 hours to compile a kernel,
I don't have access to another computer and I want to run with USB
support, so I don't want to recompile again without USB support.

I installed FreeBSD 6.0 and the problem was the same. I installed
FreeBSD 5.3 and there was no problem (except that I needed to disable
ACPI), nor was there a problem with NetBSD 3.0, nor Linux 2.4 or 2.6.
OpenBSD 3.9 also appears to suffer from an interrupt problem.

DETAILED INFORMATION

The computer is a Microstar MS-1029 with an AMD MT-37 Turion processor
running at 2.0ghz.
The Motherboard uses an ATI Radeon Xpress 200P Chipset (North Bridge
RX480M, South Bridge SB400).
The Graphics Card is an ATI Mobility Radeon X700 with 128 MB of
dedicated RAM.
The system has 1024 MB of memory. The BIOS is A1029AMS v2.70

I used the minimal installation from 6.1-RELEASE-amd64-disc1.iso

# uname -a
FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:04:14 UTC
2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64

Windows XP reports the following information regarding IRQ 19:
IRQ 19 Standard OpenHCD USB Host ControllerOK
IRQ 19 Standard OpenHCD USB Host ControllerOK
IRQ 19 Standard Enhanced PCI to USB Host ControllerOK
IRQ 19 Ricoh R/RL/5C476(II) or Compatible CardBus Controller OK

The results of running other operating systems on the computer:
FreeBSD 6.1 -! ohci (USB) and cardbus interrupt storm on IRQ 19
FreeBSD 6.0 -! identical problem
FreeBSD 5.3 -- ACPI crashes on boot. No interrupt storm when booted
without ACPI, kernel ignores spurious interrupt on IRQ 7
NetBSD 3.0 -- no problem
OpenBSD 3.9 -! Apparently the same problem as with the FreeBSD 6
kernels... interrupts use 80+% of the cpu; the individual
interrupts are not listed by ps... I don't know much about
OpenBSD so I can't say more.
Slackware 9.1 with Linux 2.4 kernel -- no interrupt problem (but disk
access is slow, probably an old ATA driver)
Slackware 11 with Linux 2.6 kernel -- no problem
WindowsXP Professional with SP2 -- occasional spurious 'data'
returned by ACPI hardware, runs fine otherwise.

When I first installed FreeBSD 6.1, the install program ran fine, and
at the end of the install process I checked the state of the processes
using the holographic shell; there was no interrupt storm.

I noticed in the boot process that the computer appears to run fine
through the initial boot, but at around the point that it begins
processing the rc files it slows down.

# dmesg -a
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.1-RELEASE #0: Sun May 7 04:04:14 UTC 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Turion(tm) 64 Mobile Technology MT-37 (1989.82-MHz K8-class CPU)
Origin = AuthenticAMD Id = 0x20f42 Stepping = 2

Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
Features2=0x1SSE3
AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow
AMD Features2=0x1LAHF
real memory = 536084480 (511 MB)
avail memory = 505630720 (482 MB)
ACPI APIC Table: MSIOEMAPIC
ioapic0: Changing APIC ID to 1
ioapic0 Version 2.1 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: MSI 1029 on motherboard
acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21
acpi0: Power Button (fixed)
acpi_ec0: Embedded Controller: GPE 0x6 port 0x62,0x66 on acpi0
Timecounter ACPI-fast frequency 3579545 Hz

Re: How can I fix Cannot find file system superblock problem?

2006-12-16 Thread Antony Mawer


On 16/12/2006 6:25 AM, FK wrote:
...

But ... I will lose one-month-long-worthing data,
which is horrible since I have modified a lot of data for the time.

Do I have any practical ways to back up the data without mounting it,
given that I could not fix the superblock?


Have you tried a Linux Live CD, to see whether or not it can read the 
disk? I had a drive that FreeBSD choked on trying to mount, yet a Linux 
Live CD was able to boot and read from the UFS filesystem fine 
(presumably it only implements the bare essentials to be able to read 
the UFS filesystem, and perhaps omitted some of the other sanity checks..


It sounds like it would be at least worth while trying...

Cheers
Antony


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

upgrade of portupgrade fails

I did a portupgrade -R on sysutils/portupgrade, and it started upgrading ruby.

Unfortunately, it failed.

No definition for sock_s_unpack_sockaddr_un

 stringio.c:
c.
  strscan.c:
cc.
 zlib.c:
mcc...
Generating RI...
Killed
*** Error code 137

Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5.
*** Error code 1

Stop in /usr/ports/lang/ruby18.
*** Error code 1

Stop in /usr/ports/lang/ruby18.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade12405.0
make PORT_UPGRADE=yes reinstall
egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory
---  Restoring the old version

Any ideas why?

Thanks,
Mike
-- 
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert Einstein


pgpslScfnxpX3.pgp
Description: PGP signature

Re: upgrade of portupgrade fails

On Saturday 16 December 2006 20:24, Michael P. Soulier wrote:
 I did a portupgrade -R on sysutils/portupgrade, and it started upgrading
 ruby.

 Unfortunately, it failed.

 No definition for sock_s_unpack_sockaddr_un

  stringio.c:
 c.
   strscan.c:
 cc.
  zlib.c:
 mcc
... Generating RI...
 Killed
 *** Error code 137

 Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5.
 *** Error code 1

 Stop in /usr/ports/lang/ruby18.
 *** Error code 1

 Stop in /usr/ports/lang/ruby18.
 ** Command failed [exit code 1]: /usr/bin/script -qa
 /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall
 egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory
 ---  Restoring the old version

 Any ideas why?

 Thanks,
 Mike
I had this problem as well after going from 6.1 to -CURRENT

I fixed it by doing

cd /usr/ports/lang/ruby18
make -DFORCE_PKG_REGISTER install

and then rebuilt sysutils/portupgrade

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

Re: upgrade of portupgrade fails

On Saturday 16 December 2006 20:24, Michael P. Soulier wrote:
 I did a portupgrade -R on sysutils/portupgrade, and it started upgrading
 ruby.

 Unfortunately, it failed.

 No definition for sock_s_unpack_sockaddr_un

  stringio.c:
 c.
   strscan.c:
 cc.
  zlib.c:
 mcc
... Generating RI...
 Killed
 *** Error code 137

 Stop in /usr/ports/lang/ruby18/work/ruby-1.8.5.
 *** Error code 1

 Stop in /usr/ports/lang/ruby18.
 *** Error code 1

 Stop in /usr/ports/lang/ruby18.
 ** Command failed [exit code 1]: /usr/bin/script -qa
 /tmp/portupgrade12405.0 make PORT_UPGRADE=yes reinstall
 egrep: /var/db/pkg/ruby-1.8.4_9,1/+CONTENTS: No such file or directory
 ---  Restoring the old version

 Any ideas why?

 Thanks,
 Mike
I had this problem as well after going from 6.1 to -CURRENT

I fixed it by doing

cd /usr/ports/lang/ruby18
make -DFORCE_PKG_REGISTER install

and then rebuilt sysutils/portupgrade

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

Re: upgrade of portupgrade fails

On 16/12/06 Lane said:

 I had this problem as well after going from 6.1 to -CURRENT
 
 I fixed it by doing
 
 cd /usr/ports/lang/ruby18
 make -DFORCE_PKG_REGISTER install
 
 and then rebuilt sysutils/portupgrade

Well, it seemed to be a problem in building the ruby rdocs, so I removed that
option for now. I upgraded portupgrade on its own, and then upgraded ruby, and
that seems to have worked.

Mike
-- 
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert Einstein


pgpQMapgaKZAz.pgp
Description: PGP signature

mailman upgrade problem

I just did a portupgrade on mailman, and now it's doing this.

Dec 16 22:05:27 kanga Mailman mail-wrapper: Group mismatch error.  Mailman
expected the mail wrapper script to be executed as group nobody, but the
system's mail server executed the mail script as group mailman.  Try
tweaking the mail server to run the script as group nobody, or re-run
configure,  providing the command line option `--with-mail-gid=mailman'.
Dec 16 22:05:27 kanga postfix/local[87645]: 830DE6E: to=[EMAIL PROTECTED],
relay=local, delay=0, status=bounced (Command died with status 2:
/usr/local/mailman/mail/mailman post opag. Command output: Group mismatch
error.  Mailman expected the mail wrapper script to be executed as group
nobody, but the system's mail server executed the mail script as group
mailman.  Try tweaking the mail server to run the script as group nobody,
or re-run configure,  providing the command line option
`--with-mail-gid=mailman'. )

I guess I need to rebuild it...

Mike
-- 
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert Einstein


pgpt72TmULpn9.pgp
Description: PGP signature

Re: Translate job number from atq to commands that will run

2006-12-16 Thread Dan Nelson

In the last episode (Dec 16), JAMES T RIENDEAU said:
 Does anybody know how I could translate the job # into the commands  
 that will run from the output of the atq command?  For example, here  
 is my current atq:
 
 Date  Owner   Queue   Job #
 Mon Dec 18 09:00:00 CST 2006  rootc   34
...
 Sat Jan  6 09:00:00 CST 2007  rootc   47
 
 I checked the /var/at/spool and /var/at/jobs, but it isn't obvious  
 which job is scheduled to run when.

at -c n will list the commands to be run for job n.

The filenames in /var/at/jobs are of the format qn, where
q is the queue, n is the job number in hex, and t is the time the job
is scheduled in hex (in minutes from the Epoch, so multiply by 60 to
get the more-standard seconds from Epoch).  For more info, see at at
manpage and /usr/src/usr.bin/at/at.c .

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

Re: mailman upgrade problem

On 16/12/06 Michael P. Soulier said:

 I just did a portupgrade on mailman, and now it's doing this.
 
 Dec 16 22:05:27 kanga Mailman mail-wrapper: Group mismatch error.  Mailman
 expected the mail wrapper script to be executed as group nobody, but the
 system's mail server executed the mail script as group mailman.  Try
 tweaking the mail server to run the script as group nobody, or re-run
 configure,  providing the command line option `--with-mail-gid=mailman'.
 Dec 16 22:05:27 kanga postfix/local[87645]: 830DE6E: to=[EMAIL PROTECTED],
 relay=local, delay=0, status=bounced (Command died with status 2:
 /usr/local/mailman/mail/mailman post opag. Command output: Group mismatch
 error.  Mailman expected the mail wrapper script to be executed as group
 nobody, but the system's mail server executed the mail script as group
 mailman.  Try tweaking the mail server to run the script as group nobody,
 or re-run configure,  providing the command line option
 `--with-mail-gid=mailman'. )

This is odd though, considering the wrapper program is group ownership
mailman, with the sgid bit set. 

Plus, if I change the group ownership to nobody, it complains about the
opposite.

Mike
-- 
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert Einstein


pgpZquDne2NCc.pgp
Description: PGP signature

Re: mailman upgrade problem

On 16/12/06 Michael P. Soulier said:

 This is odd though, considering the wrapper program is group ownership
 mailman, with the sgid bit set. 
 
 Plus, if I change the group ownership to nobody, it complains about the
 opposite.

I had to build it this way to fix the issue.

MAIL_GID=mailman make

I'm using postfix as my MTA.

Mike
-- 
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction. --Albert Einstein


pgpCpqIihQ126.pgp
Description: PGP signature

openssh security issues