Hey all,
I have done a bit of system level programming on linux distros like Fedora,
RHCE, debian but now i am faced with doing some kernel level network
programming on FreeBSD.
I had googled for some kernel programming tutorials. But mostly i could find
only linux kernel programming guides. I d
Jeremy Chadwick wrote:
...
Is there something I'm missing?
I can't see anything missing there from the reproduction steps.
Was ad0s1g also ok? The slight differences I did here where
the following but I cant seem them being significant:
1. dump -a0uL -C 32 -f /nfs/usr.dmp /usr
2. restore rf u
On Fri, Mar 02, 2007 at 05:00:24PM -, Steven Hartland wrote:
> No problem if you have the resources / time to test this now
> thats great.
>
> Here's the steps I used, if you have any questions just shout:
> 1. Boot a normal 6.2 install
Done. Booted CD image #1, did a standard install, chose
On 03/02/07 12:22, Greg Larkin wrote:
Hey all,
Are there any known issues for installing FreeBSD on Vmware
on windows XP ?
I have never tried installiing FreeBSD earlier and i just saw
a mail in this
mailing list regarding some problems while installing on
vmware. Could not
make out much. Ca
ajay gopalakrishnan schreef:
> Hey all,
>
> Are there any known issues for installing FreeBSD on Vmware on windows XP ?
> I have never tried installiing FreeBSD earlier and i just saw a mail in
> this
> mailing list regarding some problems while installing on vmware. Could not
> make out much. Can
>
> Hey all,
>
> Are there any known issues for installing FreeBSD on Vmware
> on windows XP ?
> I have never tried installiing FreeBSD earlier and i just saw
> a mail in this
> mailing list regarding some problems while installing on
> vmware. Could not
> make out much. Can someone just elabo
Hello ajay,
I have FreeBSD4.9 and 6.2 running under vmware. It's been up and about
for a long time. No issues at all so far. The installation is pretty
straighforward I seem to remember chosing other/other among the OS
templates though.
Good luck!
ajay gopalakrishnan skrev:
Hey all,
Are
Hey all,
Are there any known issues for installing FreeBSD on Vmware on windows XP ?
I have never tried installiing FreeBSD earlier and i just saw a mail in this
mailing list regarding some problems while installing on vmware. Could not
make out much. Can someone just elaborate on the issues face
In the last episode (Mar 02), Steven Hartland said:
> Another observation from my recent dealings with using
> NFS based /usr is that the remote critical mounts via
> nfs dont always give the network enough time to
> initialise before running. The first error displayed
> is:
> Mounting NFS file sys
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed:
> Another observation from my recent dealings with using
> NFS based /usr is that the remote critical mounts via
> nfs dont always give the network enough time to
> initialise before running. The first error displayed
> is:
> Mounti
Jeremy Chadwick wrote:
Pardon my ignorance, but can you give me a step-by-step on how to
reproduce this? I have a couple VMware FreeBSD sessions up and
want to see if I can reproduce it there. I also have an actual
FreeBSD testbox at home which I can format and reinstall.
(I'm not denying the
Mike Meyer wrote:
You can make that happen:
# cd /usr
# mount /dev/ /usr
# vim
vim: not found
# ls /usr/bin
ls: /usr/bin: No such file or directory
# ls bin This will show the contents of /usr/bin before
the mount, because it looks in "./bin", and
"." is on the original /usr, not the new one.
#
Eric Anderson wrote:
So try the same test, with *only* the data partition, without messing
with the /usr stuff..
Will do, will be a little while need to wait for some new machines
to come in before I can test again.
Steve
This e.mail is pri
Another observation from my recent dealings with using
NFS based /usr is that the remote critical mounts via
nfs dont always give the network enough time to
initialise before running. The first error displayed
is:
Mounting NFS file systems:mount_nfs: nfs1: hostname nor servname provided, or
not k
On Fri, Mar 02, 2007 at 03:37:21PM -, Steven Hartland wrote:
> I've rerun the test just to confirm but there are definitely
> two seperate issues here:
> 1. The ufs created by sysinstall after a repartition is corrupt.
> This is totally unrelated to the overlay of /usr as both /usr
> and /data
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed:
> Mike Meyer wrote:
> > In <[EMAIL PROTECTED]>, Steven Hartland
> > As a general rule, deciding that something is "useless and dangerous"
> > and removing it isn't the Unix way of doing things. Just because you
> > can't see a use f
Hi Eric,
On 3/1/07, Eric Anderson <[EMAIL PROTECTED]> wrote:
On 02/24/07 05:44, ghozzy wrote:
> Hi,
>
> On 2/23/07, Greg Larkin <[EMAIL PROTECTED]> wrote:
>> Hi everyone,
>>
>> I'm creating a standard FreeBSD 6.2 ISO image that I can use to
>> perform unattended installations into VMware Server
On 03/02/07 09:56, Steven Hartland wrote:
Mike Meyer wrote:
In <[EMAIL PROTECTED]>, Steven Hartland
This is just a special case of mounting on a non-empty directory. It
should work right. The last mounted file system is the one you get
(unless you're using a file system that's designed to behave
On 03/02/07 09:37, Steven Hartland wrote:
Jeremy Chadwick wrote:
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and then
Mike Meyer wrote:
In <[EMAIL PROTECTED]>, Steven Hartland
This is just a special case of mounting on a non-empty directory. It
should work right. The last mounted file system is the one you get
(unless you're using a file system that's designed to behave another
way). If you unmount the directory
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed:
> 2. Once the blank /usr was mounted over the working nfs /usr
> apps under /usr couldnt be run e.g. vim gave me no such file..
This is correct behavior. If you want to see the files underneath a
mounted file system, you need to us
Jeremy Chadwick wrote:
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and then mount a different partition or
NFS over it
On 03/02/07 08:44, Jeremy Chadwick wrote:
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
Mounting an NFS share on top of a skimmed down /usr is very common, and
very desirable. You may mount /usr from a small read-only partition
(vnode file, etc) and then mount a different part
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed:
> Eric Anderson wrote:
> > I don't know about the fs corruption, but the double mounts is
> > something you asked it to do (maybe unknowingly). When you added
> > that partition, one of the options is to mount it.
> Clearly an easy
On Fri, Mar 02, 2007 at 08:11:52AM -0600, Eric Anderson wrote:
> Mounting an NFS share on top of a skimmed down /usr is very common, and
> very desirable. You may mount /usr from a small read-only partition
> (vnode file, etc) and then mount a different partition or NFS over it if
> you detect
On 03/02/07 08:37, Steven Hartland wrote:
Eric Anderson wrote:
On 03/02/07 07:46, Steven Hartland wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and then mount a different parti
Eric Anderson wrote:
On 03/02/07 07:46, Steven Hartland wrote:
Mounting an NFS share on top of a skimmed down /usr is very common,
and very desirable. You may mount /usr from a small read-only
partition (vnode file, etc) and then mount a different partition or
NFS over it if you detect the one y
On 03/02/07 07:46, Steven Hartland wrote:
Eric Anderson wrote:
I don't know about the fs corruption, but the double mounts is
something you asked it to do (maybe unknowingly). When you added
that partition, one of the options is to mount it.
Clearly an easy work around in that case then but p
Eric Anderson wrote:
I don't know about the fs corruption, but the double mounts is
something you asked it to do (maybe unknowingly). When you added
that partition, one of the options is to mount it.
Clearly an easy work around in that case then but personally
I would expect a mount to a direc
Sam Leffler wrote:
There's a debug flag you can turn on somewhere in the sysinstall
menus. It may help diagnose what sysinstall is doing wrong by
checking the log msgs. I find sysinstall is best diagnosed inside
qemu or vmware so you destructively operate on disk images w/o hosing
a real system.
On 03/01/07 17:42, Steven Hartland wrote:
I've been repartitioning some of our machines here and
found that using the following method sysinstall creates
corrupt filesystems.
1. Boot a machine using an nfs mounted /usr
2. Run: sysctl kern.geom.debugflags=16 to enable writing
to the disk mbr
3. r
Steven Hartland wrote:
> I've been repartitioning some of our machines here and
> found that using the following method sysinstall creates
> corrupt filesystems.
>
> 1. Boot a machine using an nfs mounted /usr
> 2. Run: sysctl kern.geom.debugflags=16 to enable writing
> to the disk mbr
> 3. run sy
32 matches
Mail list logo
