Re: vinum or gvinum

2005-09-09 Thread David Magda

On Sep 9, 2005, at 07:31, Michael Butler wrote:


Swap is the first slice which is not
mirrored and the second slice contains the bootable file-system which 
is

mirrored.


What happens to a running system if the disk dies and swap suddenly 
disappears? :)


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


Message ("The distribution of your message dated Fri, 9 Sep...")

2005-09-09 Thread L-Soft list server at Sun Microsystems Inc. (1.8e)
The distribution of your message dated  Fri, 9 Sep 2005 18:42:31 +0200 with
no subject has been postponed because  the JAVATV-INTEREST list is held. No
action is required from you; your message will be reprocessed automatically
once the list owner releases the list.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: serial terminal direct connection to remote host at login

2005-09-09 Thread Torfinn Ingolfsen
On Fri, 09 Sep 2005 16:56:19 +0200
"Karl M. Joch" <[EMAIL PROTECTED]> wrote:

> Hi,
> 
> i have some 4.10 systems with local connected serial terminals. now
> the problem is, that the terminal should connect to a remote host when
> they are switched on and prompt for the login at the romote host.

perhaps you can use conserver for that, even if it is designed to do the
opposite (ie. manage remote attacjed serial consoles)?
It's in ports, see
ports/comms/conserver
ports/comms/conserver-com

If not, you will have to look for a way to set up someting like the
following:
- automatic login on local machine (as an unprivileged user)
- automatic connection to remote host (perhaps via .profile or somesuch

Hmm, there is an 'autologin' entry in my /etc/gettytab, and gettytab(5)
explains about the 'al' capability. This allows you to to autologin as a
specified user, at least.

There is also the 'lo' capability, which controls the program to execute
once a name is obtained, usually '/usr/bin/login'. I don't know it it is
possible to change this into, say ssh and have the teminal automatically
connect to another machine.

HTH
 -- 
Yours, 
Torfinn Ingolfsen,
Norway

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


serial terminal direct connection to remote host at login

2005-09-09 Thread Karl M. Joch
Hi,

i have some 4.10 systems with local connected serial terminals. now the
problem is, that the terminal should connect to a remote host when they
are switched on and prompt for the login at the romote host.

the way of loging in at the local host and then do a telnet to
remote-host is not a real good solution, because all users have to enter
their password twice and furthermore all users have to be created on the
local system with the terminals too.

is there any way to hardwire the terminal to a remote host? i already
searched all of the ttys aso man pages, but had no luck findig a
solution.


many thanks,

best regards,

karl



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


RE: vinum or gvinum

2005-09-09 Thread Tomas Palfi
Stijn,

I think I am almost there as the disks are now sincing.  Thank you for
your help, it has been really appreciated.  I am still going fiddle with
the mirror with the gvinum.

Tomas
--
tp




-Original Message-
From: Stijn Hoop [mailto:[EMAIL PROTECTED] 
Sent: 09 September 2005 12:12
To: Tomas Palfi
Subject: Re: vinum or gvinum

Hi,

On Fri, Sep 09, 2005 at 12:04:42PM +0100, Tomas Palfi wrote:
> Thanks for this update, I am configuring the gmirror as per the
> instructions, however, there is one thing which bothers me a bit.
> 
> bsdlabel -e /dev/mirror/gm0s1 when editing the new layout, it
> advices me to start "a" partition at offset 16, and "c" as per default
> at offset 0.  do I have to retain the offset 16 for the "a" partition
> where my root is located or can i have another offset + 16 and start
> swap at 0 offset?  In this case the swap would start with offset 0 as
> "b".

Sounds fine. In the past there have been troubles with old BIOSes not
booting from root partitions that were located "far" on the disk (>2G
I believe). I don't think that limitation exists anymore, but keep it
in mind. Other than that, FreeBSD will be happy.

> this is my exiting layout on /dev/da0s1
> 
> a: 10485760  10485760   that's /root
> b: 10485760 0   swap
> c: 1433639970
> d: 20911520  20911520  /home
> e: 14680064  41943040  /tmp
> f: 14680064  56623104  /var
> g: 72060829  71303168  /usr/local
> 
> 
> and this is what I would lay it as on the /dev/mirror/gm0s1
> 
> |-|-|-|---||||
> 16 swap  /root   /home   /tmp /var   /usr/local
> 
> 
> 
> a: 10485760  (10485760 + 16)  that's /root
> b: (10485760 - 16)  16  swap
> c: 1433639970
> d: 20911520  20911520  /home
> e: 14680064  41943040  /tmp
> f: 14680064  56623104  /var
> g: 72060829  71303168  /usr/local
> 
> in this case the swap would be offset by those 16??

Yes, I would definitely offset things by 16 sectors. I don't really know
what's stored there but you don't lose much and it probably makes sense.

Also keep in mind that you need to make sure that /dev/ad0s1 does NOT
cover the ENTIRE disk, but rather leaves a few sectors spare at the
end. This is to make sure that gmirror does not confuse /dev/ad0 and
/dev/ad0s1 as providers for the mirror (it stores it's metadata in the
last sector). All of this is described in the article, although maybe
not very clear. Note also that by default, FreeBSD leaves a few sectors
spare when runnign fdisk, so it's not an issue most of the time unless
you 'dangerously dedicate' your disks.

Hopefully it'll all work out today ;-)

--Stijn

-- 
It's harder to read code than to write it.
-- Joel Spolsky,

http://www.joelonsoftware.com/articles/fog69.html

PRIVACY & CONFIDENTIALITY

This e-mail is private and confidential.  If you have, or suspect you have 
received this message in error please notify the sender as soon as possible and 
remove from your system.  You may not copy, distribute or take any action in 
reliance on it. Thank you for your co-operation.

Please note that whilst best efforts are made, neither the company nor the 
sender accepts any responsibility for viruses and it is your responsibility to 
scan the email and attachments (if any).

This e-mail has been automatically scanned for viruses by MessageLabs.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: vinum or gvinum

2005-09-09 Thread Michael Butler

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tommi Lätti wrote:

| I have to vouch for gmirror system. I have three production machines
| here running and booting from gmirror on since 5.3-REL and they're  all
| doing fine. Even after I upgraded 5.3 -> 5.4 and during the first  boot
| I saw the "updating metadata" -message. Made me sweat for a few  seconds.

I have a similar experience with gmirror in the second configuration (by
slice) descibed on that web-page. Swap is the first slice which is not
mirrored and the second slice contains the bootable file-system which is
mirrored. Just sits there and works - which is how I like 'em to be ;-)

Michael
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDIXJ1iJykeV6HPMURAqgjAJ9hmURdl+P+aGHow1e4oF+z8heKewCg0NCH
NsIlAnpU8uBlKqN1dHbPTg0=
=xVzL
-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]"


boot error 16 lba 191

2005-09-09 Thread DvG
Hi all,

After the power loss, i started the system and it gives such a message:
boot error 16 lba 191
The system is Freebsd 5.4. How should i boot the system?
Vitali.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: SiI 3114 woes

2005-09-09 Thread Mars G. Miro
On 9/9/05, Jon Dama <[EMAIL PROTECTED]> wrote:
> Yes, but only in a configuration <=3GB.  But I thought those problems were
> ironed out?  I've been looking to switch that machine back to
> FreeBSD/amd64 but haven't had a chance yet.  Would love to know if there
> are issues ahead.
> 


This machine only has 2G of RAM. See my previous post on the full dmesg.

Thanks.

> -Jon
> 
> On Thu, 8 Sep 2005, Mars G. Miro wrote:
> 
> > Yo list/Soren!
> >
> >  Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
> > ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
> >  using the onboard SiI 3114 SATA controller? This mobo is supposedly
> > supported:
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
> >
> >  But I have never been able to successfully install
> > FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
> >
> > In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
> >
> >  ad4: FAILURE - WRITE_DMA status=51 error=4
> > LBA=105819039
> >  g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
> >
> >   at the debugging console
> >
> >  and
> >
> >  panic:bundirty: buffer 0x9a7faff0 still on queue 1
> >  cpuid = 0
> >  KDB: enter: panic
> >  [ thread pid 3 tid 100021 ]
> >  Stopped at kdb_enter+0x2f: nop
> >  db> trace
> >  Tracing pid 3 tid 100021 td 0xff007ba14be0
> >  kdb_enter() at kdb_enter+0x2f
> >  panic() at panic+0x249
> >  bundirty() at bundirty+0x128
> >  brelse() at brelse+0x831
> >  bufdone() at bufdone+0x225
> >  ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
> >  bufdone() at bufdone+0x2ad
> >  g_vfs_done() at g_gvfs_done+0x63
> >  g_io_schedule_up() at g_io_schedule_up+0xd4
> >  g_up_procbody() at g_up_procbody+0x7a
> >  fork_exit() at fork_exit+0xbb
> >  fork_trampoline() at fork_tramploine+0xe
> >  --- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
> >  db>
> >
> >  Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
> > using PATA IDE drives, and no problems whatsoever, so I think this has
> > something to do w/ the SiI 3114 driver.
> >
> >  Any help is much appreciated.
> >
> >  I do apologize for cross-posting but this concerns -stable and -amd64.
> >
> >  Thanks!
> >
> >
> > cheers
> > mars
> > ___
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> >
> 


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