I cannot make mergemaster work. Tried twice earlier in the year and
took several hours to recover... Don't know what my problem is.
However, I have a script that compares and lists diffs in /etc/rc* and
/etc/defaults/* to those in src/etc. Normally, I manually copy those
files to /etc.
# grep
> Did I miss something on the /dev/random hang?
I don't know...
> During a `shutdown -r now`, the boot process hangs for more than an
> hour. I thought this was supposed to work. However, jwd's receipe
> for recovery works. I repeated this three times, although I only
> waited an hour the las
Did I miss something on the /dev/random hang?
During a `shutdown -r now`, the boot process hangs for more than an
hour. I thought this was supposed to work. However, jwd's receipe
for recovery works. I repeated this three times, although I only
waited an hour the last time (dinner!).
I am run
> > Hello FreeBSD-hackers.
> >
> > I had my first CVSup-ed source tre d/loaded today. It compiled correctly
> > (make buildworld) and installed correctly (make installworld).
>
> Mistake #1 was CVSuping -CURRENT.
[...]
> NOTE #3. Your machine is probably totaly broke. And you will need to
> rein
> I had my first CVSup-ed source tre d/loaded today. It compiled correctly
> (make buildworld) and installed correctly (make installworld).
>
> But on rebooting the box, the loader fails to find a bootable kernel. It
> seems my loader.conf got trashed somewhere ... I get the list of the /
> parti
Hello FreeBSD-hackers.
I had my first CVSup-ed source tre d/loaded today. It compiled correctly
(make buildworld) and installed correctly (make installworld).
But on rebooting the box, the loader fails to find a bootable kernel. It
seems my loader.conf got trashed somewhere ... I get the list of
Thanks for the updates. A few questions below.
-John
- Mark Hittinger's Original Message -
>
> It does look like an updating entry is needed for this badly.
>
> I did the following things, some of which may not be needed, and now my
> -current boxes boot OK.
>
> 1. update MAKEDEV fr
It does look like an updating entry is needed for this badly.
I did the following things, some of which may not be needed, and now my
-current boxes boot OK.
1. update MAKEDEV from /usr/src/etc, run MAKEDEV all
2. update /etc/rc /etc/rc.* /etc/defaults/rc.conf from /usr/src/etc
3. add ran
On Mon, 23 Oct 2000, John W. De Boskey wrote:
> I'm beginning to think we need an updating entry.
>
> 1. Make sure /dev/random exists 'cd /dev && sh MAKEDEV std'
Unless you are using devfs.
> 2. Make sure your kernel includes:
>
> devicerandom # Entropy device
You need to put
random_load="YES"
into /boot/loader.conf.
Optionally, you can load random.ko during the boot process.
John W. De Boskey wrote:
> It didn't work without the device line when I tested it
> last week(Thursday/Friday).
>
> - David O'Brien's Original Message -
> > On Mon, O
It didn't work without the device line when I tested it
last week(Thursday/Friday).
-John
- David O'Brien's Original Message -
> On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote:
> > 2. Make sure your kernel includes:
> >
> > device random # Entrop
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote:
> 2. Make sure your kernel includes:
>
> devicerandom # Entropy device
Are you implying the random.ko module is broken?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
In message <[EMAIL PROTECTED]> Leif Neland
writes:
: > Hi there,
: >
: > I've done a very recent week's make world(S) on -current, making
: > and installing world and kernel go fine, but all hang on boot,
: > with no error codes or msgs.
: >
: Solution: Due to changes in the random/entropy
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote:
>
> 5. At this time, remove ALL MFS filesystems from /etc/fstab.
>They can be hand mounted after bootup or via a local rc
>startup script.
You can leave them in, with option "noauto", and mount them later with
"mount -a -
- Makoto MATSUSHITA's Original Message -
>
> jwd> 5. At this time, remove ALL MFS filesystems from /etc/fstab.
> jwd>They can be hand mounted after bootup or via a local rc
> jwd>startup script.
>
> Is there any chance to mount MFS filesystem listed in /etc/fstab just
> after the
jwd> 5. At this time, remove ALL MFS filesystems from /etc/fstab.
jwd>They can be hand mounted after bootup or via a local rc
jwd>startup script.
Is there any chance to mount MFS filesystem listed in /etc/fstab just
after the /dev/random reseeding is done ? I cannot put up with that we
c
I'm beginning to think we need an updating entry.
1. Make sure /dev/random exists 'cd /dev && sh MAKEDEV std'
2. Make sure your kernel includes:
device random # Entropy device
3. Make sure /etc/rc is at rev 1.237 or higher.
4. Make sure /etc/rc.shutdown is at rev 1.13 or 1.1
On Sun, Oct 22, 2000 at 07:35:39PM -0400, John W. De Boskey wrote:
> - David O'Brien's Original Message -
> > On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote:
> > > with the mfs enable, it hangs there right after FILESYSTEM
> > > checking, and with random_load set to YES, it ha
On Mon, Oct 23, 2000 at 01:38:36AM +0200, [EMAIL PROTECTED] wrote:
> Randomized file generation numbers to make NFS attacks more difficult,
> as far as I can remember.
>From p. 315 of the "red devil book":
A generation number is assigned to an inode each time that the latter is
allocated to repr
In reply:
> On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote:
> > with the mfs enable, it hangs there right after FILESYSTEM
> > checking, and with random_load set to YES, it hangs at ldconfig.
>
> mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*.
quick fix, wo
>Anyone know the history on the '#ifdef FSIRAND' code?
Randomized file generation numbers to make NFS attacks more difficult,
as far as I can remember.
Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
- David O'Brien's Original Message -
> On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote:
> > with the mfs enable, it hangs there right after FILESYSTEM
> > checking, and with random_load set to YES, it hangs at ldconfig.
>
> mount_mfs is blocking on "rndblk". Our /dev/*random
On Sun, Oct 22, 2000 at 04:14:08PM +0800, Donny Lee wrote:
> with the mfs enable, it hangs there right after FILESYSTEM
> checking, and with random_load set to YES, it hangs at ldconfig.
mount_mfs is blocking on "rndblk". Our /dev/*random is fubar'ed *again*.
--
-- David ([EMAIL PROTECTED]
On Sun, Oct 22, 2000 at 12:14:03PM +0800, Donny Lee wrote:
> /dev/da0s1e: FILESYSTEM CLEAN, SKIPPING CHECK
> /dev/da0s1e: clean, 92565 free (125 frags, 11555 blocks,
> 0.1%fragmentation)
>
> then no more,
Next time hit control-T to find out what is hanging and why.
--
-- David ([EMAIL P
Leif Neland wrote:
> > Does this make any different?
> > shutdown is fine, but ctrl-alt-del is not so good,
> > whenever I did this, the next boot takes a long time on
> > fixing filesystems.
> You mean your system doesn't unmount the disks at ctrl-alt-del?
> Does it a hard reset instead?
> Leif Neland wrote:
> > > do you mean one should use "shutdown -r now" or Ctrl-Alt-Del
> > > instead of "reboot" right after make world and kernel?
> > Exactly. Except not just after make world/kernel, every time you
> > want to reboot/halt.
>
> Does this make any different?
>
> shutdow
Leif Neland wrote:
> > do you mean one should use "shutdown -r now" or Ctrl-Alt-Del
> > instead of "reboot" right after make world and kernel?
> Exactly. Except not just after make world/kernel, every time you
> want to reboot/halt.
Does this make any different?
shutdown is fine, but c
- Original Message -
From: "Donny Lee" <[EMAIL PROTECTED]>
To: "Leif Neland" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, October 22, 2000 10:59 AM
Subject: Re: -current hangs during boot
> Leif Neland wrote:
> > > I'
- Leif Neland's Original Message -
>
>
> On Sun, 22 Oct 2000, Donny Lee wrote:
>
> >
> > Hi there,
> >
> > I've done a very recent week's make world(S) on -current, making
> > and installing world and kernel go fine, but all hang on boot,
> > with no error codes or msgs.
> >
> So
Leif Neland wrote:
> > I've done a very recent week's make world(S) on -current, making
> > and installing world and kernel go fine, but all hang on boot,
> > with no error codes or msgs.
> Solution: Due to changes in the random/entropy stuff, you have to reboot
> the machine with "shutdown -r
On Sun, 22 Oct 2000, Donny Lee wrote:
>
> Hi there,
>
> I've done a very recent week's make world(S) on -current, making
> and installing world and kernel go fine, but all hang on boot,
> with no error codes or msgs.
>
Solution: Due to changes in the random/entropy stuff, you have to reb
leifn> My hangs at loading ldconf. I can continue with ^C.
Are you using MFS ? I suppose you are not.
I've found that:
- if /etc/fstab has 'mfs' line, system stops during mounting
filesystem. Interrupting with CTRL-C works (and system goes to
single user mode).
- if /etc/fstab does not ha
John W. De Boskey noticed me some points to check out,
I now can boot my fbsd box with the recent built kernel.
I disabled mfs, and random_load, these 2 made my fbsd box
hangs (not really hangs, it looks like waiting for some
jobs done) 2 times at boot.
with the mfs enable, it hangs
On Sun, 22 Oct 2000, Donny Lee wrote:
>
> Hi there,
>
> I've done a very recent week's make world(S) on -current, making
> and installing world and kernel go fine, but all hang on boot,
> with no error codes or msgs.
>
> When boot, all go fine at the beginning, and stop right after
> s
Hi there,
I've done a very recent week's make world(S) on -current, making
and installing world and kernel go fine, but all hang on boot,
with no error codes or msgs.
When boot, all go fine at the beginning, and stop right after
showing the msg:
:
:
/dev/da0s1e: FILESYSTEM CLE
On Mar 3, 11:16am, "Matthew N. Dodd" wrote:
} Subject: Re: 4.0-CURRENT hangs in ex_isa_identify() (was: current hangs du
} On Fri, 3 Mar 2000, Don Lewis wrote:
} > What really sucks is that there is no way to disable the ex driver
} > at boot time, so the standard install floppies can no longer be
On Mar 2, 4:09am, Don Lewis wrote:
} Subject: current hangs during boot if ET/5025-16 card is installed
}
} I happened to try to install 4.0-CURRENT on a box that has an
} Emerging Technologies ET/5025-16 ISA card installed and found that
} the kernel wedges during boot. It hangs hard and
I happened to try to install 4.0-CURRENT on a box that has an
Emerging Technologies ET/5025-16 ISA card installed and found that
the kernel wedges during boot. It hangs hard and won't respond to
anything except the reset switch. The motherboard is an Asus P3B-F
and I believe I have the BIOS pro
38 matches
Mail list logo