On Nov 28 at 19:16, Stephen Montgomery-Smith spoke:
> Would it be possible to add a variable "show_beastie" to be put in
> /boot/loader.conf, which would default to "YES", but users could add in
> show_beastie="NO" if they didn't want it, but only want the menu.
If you would like the menu app
On Nov 29 at 10:28, Michael Nottebrock spoke:
> Hanspeter Roth wrote:
> >
> >http://www.freebsd.org/cgi/query-pr.cgi?pr=70231
>
> I would much prefer seeing this patch getting committed after instead of
> completely disabling the bootmenu as recently committed.
The p
On Nov 30 at 06:16, Seahawk spoke:
> I'd hope that this is only a temporary measure until someone can get
> around to rewriting the boot menu to load minus beastie as the default,
> and I'd hope there's the option to enable loading with beastie enabled in
> either b&w or color.
http://www.freeb
On Dec 01 at 10:21, Edwin Groothuis spoke:
> beastie_disable
> (``NO'') If set to ``YES'', it will not show the ASCII
> Beastie in the boot menu.
This does not just make the Beastie right to the menu disappear but
will not present the menu at all.
-Hanspeter
___
Hello,
I've upgraded to 5.4-RC1 and I'd like to access an Mpman MP3 Player
via USB.
When I attach the USB device several messages appear and the Mpman
displays "Starting" but then /dev/da0 is not available.
The messages look like this:
11:12:22: umass0: vendor 0x10d6 Generic USB Disk Device, re
Hello,
The Beastie menu makes it convenient choosing boot options.
The Beastie decorating space right to the menu reflects the
preference of the majority or all of the FreeBSD developers.
Their opinion is documented in
http://www.freebsd.org/copyright/daemon.html .
However there are users which h
it was precise.
> On Mon, 11 Apr 2005, Hanspeter Roth wrote:
>
> > - or have an convenient flag in loaders.conf that allows to
> > run Beastie menu but display some other decoration?
>
> I I have an idea and the patch in PR 74577 is about halfway there. I
> suggest provi
On Apr 14 at 10:13, Doug White spoke:
> I I have an idea and the patch in PR 74577 is about halfway there. I
> suggest providing a script that forth-ifies a provided ASCII logo, and a
> loader option to load a banner file from disk. This way, if, say, an OEM
> wanted to put contact information
Hello,
as always there is also with 6.0-Release-i386 a disk1.iso and a
disk2.iso.
Is the disk2.iso a plain fixit CD or are there additional packages?
If it is only a fixit CD does one need the
6.0-Release-i386-disk2.iso if one already has an 5.3-Release one?
-Hanspeter
___
On May 14 at 11:16, JJ Behrens spoke:
> > i've always started X with -bpp 24 in /usr/X11R6/lib/X11/xdm/Xservers to
> > get the correct depth for xdm. it's not taken from XF86Config, iirc.
>
> Hmm:
>
> # From XF86Config
> Section "Screen"
> DefaultDepth 16 # <-
>
> has always worked f
On May 15 at 02:59, Aidan Skinner spoke:
> Yeah. I tried it with startx -- -depth 24, which fixed the 16 colours
> problem (thanks!).
>
> I had thought about that, but changing my XF86Config to *only* have
> 24bpp @ 1024x786 didn't seem to make a difference. I would have
> thought this would h
Hello,
I frequently store some files on a floppy. Thus my fstab contains
/dev/fd0/floppy msdos rw,noauto 0 0
This usually allows me to write on the floppy.
Sometimes I insert a floppy that's writeprotected.
If I forget to mount it readonly explicitly (-r) the system thi
On Jan 22 at 17:55, Barry Pederson spoke:
> Brooks Davis wrote:
>
> >You missed the line four lines below options IPFILTER:
> >
> >options PFIL_HOOKS #required by IPFILTER
>
> Can we put PFIL_HOOKS in the GENERIC kernel config, so a person doesn't
> have to recompile the ker
Hello,
I have upgraded from 4.1-Release to 4.2-Beta.
I've built a GENERIC kernel and run MAKEDEV all.
But MAKEDEV didn't recreate the devices which are listed in fstab
such as da0s1a.
The new kernel failes to mount the root filesystem.
The messages are:
Mounting root from ufs:/dev/da0s1a
no such
14 matches
Mail list logo
