had set a cron job long, long ago to do daily
> snapshots. So I have a snapshot from before the upgrade - There are
> indeed two different loaders. The newer one matches "zfs" when
> grepped, the older one does not... But, since it was working before, I
> restored the older
der loader and tried to boot again. No dice - it still
sticks at that screen where all I see is "/" in the upper left.
I also tried putting the older zfsboot and zfsloader back in place
(with the old loader) to try and get a different error - still no
dice. I'm still stuck wonderi
On 25. sep. 2013, at 06:59, Tyler Sweet wrote:
> I tried reinstalling the boot blocks from both
> the fixit live filesystem and also mounting zroot and using the files
> there in case they were different.
Disclaimer: I haven't gotten (enough) morning-coffee yet, but...
Disclaim
off, as it wasn't accepting key strokes at
the console.
When it boots back up, it gets past POST and then goes to a black
screen with just a spinner in the upper left-hand corner. No text, no
logo, nothing else. The spinner used to spin around a few times, now
it does nothing.
I've manage
Polytropon wrote:
On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote:
When I try to boot FreeBSD from a USB stick, it stuck during the
boot process. But if I boot it in safe mode, it succeeds to boot.
How can I figure out what's wrong with the standard boot process?
I can't even lo
On Tue, Sep 17, 2013 at 9:47 AM, atar wrote:
> Polytropon wrote:
>
>> On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote:
>>>
>>> When I try to boot FreeBSD from a USB stick, it stuck during the
>>> boot process. But if I boot it in safe mode, it succeeds
On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote:
> When I try to boot FreeBSD from a USB stick, it stuck during the
> boot process. But if I boot it in safe mode, it succeeds to boot.
> How can I figure out what's wrong with the standard boot process?
> I can't even log the b
Hi there!!
When I try to boot FreeBSD from a USB stick, it stuck during the boot process.
But if I boot it in safe mode, it succeeds to boot. How can I figure out what's
wrong with the standard boot process? I can't even log the boot messages since
the computer stuck and not respon
n (logo) has been around for many years
> in the past. >>It's a movie reference ("Die Hard"). >>The Beastie logo is
> still there, in the /boot directory, if you want it. Or the standard "orb",
&g
e ("Die Hard"). >>The Beastie logo is still
there, in the /boot directory, if you want it. Or the standard "orb", by
setting it in /boot/loader.conf:
loader_logo="orb"
Thanks for the info.
___
freebsd-questions@f
On Wed, 4 Sep 2013, Lowell Gilbert wrote:
Patrick Dung writes:
Do you know what is this logo means, or the story behind it?
I thought the BSD daemon (logo) has been around for many years in the past.
It's a movie reference ("Die Hard").
The Beastie logo is still ther
Oh I see. I have found that the logo was mentioned in news group
org.freebsd.freebsd-chat back in 1997.
From: Lowell Gilbert
To: Patrick Dung
Cc: "freebsd-questions@freebsd.org"
Sent: Wednesday, September 4, 2013 11:45 PM
Subject: Re: The lo
Patrick Dung writes:
> Do you know what is this logo means, or the story behind it?
> I thought the BSD daemon (logo) has been around for many years in the past.
It's a movie reference ("Die Hard").
The Beastie logo is still there, in the /boot dire
2013/9/4 Patrick Dung
> Hello,
>
> Do you know what is this logo means, or the story behind it?
> I thought the BSD daemon (logo) has been around for many years in the past.
>
> Thanks and regards,
> Patrick Dung
>
http://en.wikipedia.org/wiki/BSD_Daemon
--
Hello,
Do you know what is this logo means, or the story behind it?
I thought the BSD daemon (logo) has been around for many years in the past.
Thanks and regards,
Patrick Dung
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mail
On Mon, 29 Jul 2013 13:34:10 +0930, Shane Ambler wrote:
> On 29/07/2013 08:23, Polytropon wrote:
> > On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote:
> >> In this case, sade is (or was) a direct by-product of the death
> >> of sysinstall(8). It only exists in 9 or higher.
> >
> > % which sad
On Mon, 29 Jul 2013 01:04:04 +0200 (CEST), Conny Andersson wrote:
> Hi Devin,
>
> Apropos sade (sysadmins disk editor). I have it at /usr/sbin/sade and I am
> running a FreeBSD 8.3. I also mounted FreeBSD 8.1 and FreeBSD 8.2 and found
> sade at /usr/sbin/ even in these older FreeBSDs.
I can'
On 29/07/2013 08:23, Polytropon wrote:
On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote:
In this case, sade is (or was) a direct by-product of the death
of sysinstall(8). It only exists in 9 or higher.
% which sade
/usr/sbin/sade
System is FreeBSD 8.2-STABLE of August 2011. I think sade
Hi Devin,
Apropos sade (sysadmins disk editor). I have it at /usr/sbin/sade and I am
running a FreeBSD 8.3. I also mounted FreeBSD 8.1 and FreeBSD 8.2 and found
sade at /usr/sbin/ even in these older FreeBSDs.
Regards,
Conny
On Sun, 28 Jul 2013, Teske, Devin wrote:
In this case, sade is (
On Sun, 28 Jul 2013 22:23:38 +, Teske, Devin wrote:
> In this case, sade is (or was) a direct by-product of the death
> of sysinstall(8). It only exists in 9 or higher.
% which sade
/usr/sbin/sade
System is FreeBSD 8.2-STABLE of August 2011. I think sade has
been introduced in a v8 version of
led hard disks. The first disk,
>> > ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three year
>> > warranty of the workstation as Dell techs mostly speak the Microsoft
>> > language).
>>
>> Yes, best humour adherents of the Almighty Bill - keep
On Sun, 28 Jul 2013, Conny Andersson wrote:
Hi Warren and Polytropon,
A few minutes ago I booted up from a FreeBSD-8.4-RELEASE-amd64-memstick.img
to experience that it is sysinstall that is used in that release.
Next, I did a 'dummy' custom installation. And, as I supposed sysinstall
recogn
by probes, defaulting to disk0:
at boot time.
The strange thing is that when I boot the system from a FreeBSD 9.1
(AMD64) USB key, I can mount and read the file system on the hard
drive that will not boot. There doesn't seem to be any problem with
it. I've tried copying /boot/loader o
Block wrote:
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option "Install the FreeBSD
Boot Manager" detects that I have a FreeBSD 8.3 and detect it as slice 2
on
disk
e configured the BIOS to boot from the MBR on the second disk
> as I most of the time (99%) use FreeBSD. The MBR on ada1 was installed with
> sysinstall's option "Install the FreeBSD Boot Manager", when I installed
> the FreeBSD 8.3-RELEASE.
Right. sysinstall(8) - or
tation with two factory installed hard disks. The first
disk, ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three
year warranty of the workstation as Dell techs mostly speak the Microsoft
language).
Instead I have configured the BIOS to boot from the MBR on the second disk
as I most
e three year
> warranty of the workstation as Dell techs mostly speak the Microsoft
> language).
Yes, best humour adherents of the Almighty Bill - keeps them sweet.
> Instead I have configured the BIOS to boot from the MBR on the second disk
> as I most of the time (99%) use Free
On Sun, 28 Jul 2013, Polytropon wrote:
On Sun, 28 Jul 2013 08:18:39 -0600 (MDT), Warren Block wrote:
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option "Install the Fr
On Sun, 28 Jul 2013 08:18:39 -0600 (MDT), Warren Block wrote:
> On Sun, 28 Jul 2013, Polytropon wrote:
> > On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
>
> >> A very important question is if sysinstall's option "Install the FreeBSD
> >
On Sun, 28 Jul 2013, Polytropon wrote:
On Sat, 27 Jul 2013 19:39:30 +0200 (CEST), Conny Andersson wrote:
A very important question is if sysinstall's option "Install the FreeBSD
Boot Manager" detects that I have a FreeBSD 8.3 and detect it as slice 2 on
disk 1?
I'm no
ostly speak the Microsoft
> language).
It's just a series of pictures, not a language. ;-)
> Instead I have configured the BIOS to boot from the MBR on the second disk
> as I most of the time (99%) use FreeBSD. The MBR on ada1 was installed with
> sysinstall's option "
chs mostly speak the Microsoft
> language).
>
> Instead I have configured the BIOS to boot from the MBR on the second disk
> as I most of the time (99%) use FreeBSD. The MBR on ada1 was installed with
> sysinstall's option "Install the FreeBSD Boot Manager", when I in
Hi,
I have a workstation with two factory installed hard disks. The first disk,
ada0, is occupied by a Windows 7 Pro OS (mainly kept for the three year
warranty of the workstation as Dell techs mostly speak the Microsoft
language).
Instead I have configured the BIOS to boot from the MBR on
On Thu, 25 Jul 2013 12:01:10 +0300, Erhan Gulsen
wrote:
> Hi,
> I am Erhan,i have a problem,i read your all definition but i can not
> create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want to
> create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try
>
On 2013-07-25 11:01, Erhan Gulsen wrote:
Hi,
I am Erhan,i have a problem,i read your all definition but i can not
create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want to
create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try
this,it shows ''boot error'
> Hi,
> I am Erhan,i have a problem,i read your all definition but i can not
> create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want
> to create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try
> this,it shows ''boot error''.Can you he
On Thu, 25 Jul 2013 12:01:10 +0300, Erhan Gulsen wrote:
> Hi,
> I am Erhan,i have a problem,i read your all definition but i can not
> create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want to
> create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try
>
Hi,
I am Erhan,i have a problem,i read your all definition but i can not
create usb boot FreeBSD,i have a ubuntu 12.04 operating system.I want to
create it with FreeBSD-9.1-RELEASE-amd64-disc1.iso but when i try
this,it shows ''boot error'&#
seems that some notebooks the bios loads
part of the boot from the HD first before
trying to boot from the CD, so when the CD boots,
the system expects some windows stuff, when
it "sees" FreeBSD, it reboots...
Solution I found:
1) get/buy another HD for notebook (here a 320GB costs
Hi
On Fri, 12 Jul 2013 14:56:12 +0200
Martin Siebel wrote:
>
> Any ideas about BIOS settings I may change?
>
find out how how the CD drive is connected and then play with the
settings fir this interface
Erich
> I burnt the CD twice by the way, with different burning software, to
> avoid dam
;Blue"]Ashampoo
Burning Studio 2013[/COLOR][/I].
Now, if I select "Boot from CD-ROM" in my notebooks BIOS it detects the
CD, starts to boot from, it but only for about 1 second. After this the
screen blackens, the notebook reboots and boots normally from HDD (even
tough I still h
On Mon, Jul 8, 2013 at 8:31 PM, Polytropon wrote:
> On Mon, 8 Jul 2013 16:21:28 + (UTC), jb wrote:
> > I hope FreeBSD (and other OSs) luminaries, devs and users will find a
> way not
> > to harm themselves.
>
> A massive problem I (personally) have is that with Re
arm themselves.
> >
> > A massive problem I (personally) have is that with Restricted Boot
> > (this is what "Secure Boot" basically is) you are no longer able
> > to _ignore_ MICROS~1 and their products. A restrictive boot loader
> > mechanism that requires
On Tue, 9 Jul 2013 02:31:40 +0200
Polytropon wrote:
> On Mon, 8 Jul 2013 16:21:28 + (UTC), jb wrote:
> > I hope FreeBSD (and other OSs) luminaries, devs and users will find a way
> > not
> > to harm themselves.
>
> A massive problem I (personally) have is that w
On Mon, 8 Jul 2013 16:21:28 + (UTC), jb wrote:
> I hope FreeBSD (and other OSs) luminaries, devs and users will find a way not
> to harm themselves.
A massive problem I (personally) have is that with Restricted Boot
(this is what "Secure Boot" basically is) you are no longer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/8/2013 6:28 PM, Teske, Devin wrote:
Not entirely correct. Microsoft licensing requires UEFI Secure boot
for PCs sold with preinstalled Win8 and the "Windows 8" logo.
Win8 itself boots and runs fine on legacy hardware without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/8/2013 6:28 PM, Teske, Devin wrote:
> On Jul 8, 2013, at 3:24 PM, Sergio de Almeida Lenzi wrote:
>
> [snip]
>
>>
>> So the question:
>> Why or when will I need an secure UEFI boot???
>>
>
> Fro
On Mon, 08 Jul 2013 19:24:38 -0300
Sergio de Almeida Lenzi wrote:
> I could not find only a one user that wants to use FreeBSD and/or
> LInux AND windows
Some people don't want to delete a preinstalled copy of Windows so they
can buy another and install it in a virtual server.
There are also fa
On Jul 8, 2013, at 3:24 PM, Sergio de Almeida Lenzi wrote:
[snip]
>
> So the question:
> Why or when will I need an secure UEFI boot???
>
>From what I've read of UEFI Secure boot, I've parceled out into these nuggets:
(correct any nuggets I got wrong)
1. UEFI Sec
FreeBSD does "diskless" stations too..
So the question:
Why or when will I need an secure UEFI boot???
Thank you for ANY comment...
Sergio
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-qu
it. Since Microsoft will have already vetted
the shim loader code, we hope that there will be little trouble getting them
to sign our version for us.""
http://www.itwire.com/business-it-news/open-source/60498-freebsd-begins-process-to-support-secure-boot
I am just wondering why Linus
On Sat, 6 Jul 2013, Simon wrote:
On Fri, 5 Jul 2013 19:43:02 -0600 (MDT), Warren Block wrote:
I booted the 9.1 install CD, executed "gpart destroy -F ada0", and
installed. After completing the install, boot fails with:
ERROR: No boot disk has been detected or the disk has failed.
On Fri, 5 Jul 2013 19:43:02 -0600 (MDT), Warren Block wrote:
>> I booted the 9.1 install CD, executed "gpart destroy -F ada0", and
>> installed. After completing the install, boot fails with:
>>
>> ERROR: No boot disk has been detected or the disk has failed.
&
On Fri, 5 Jul 2013, James Pace wrote:
You, sir, are a wizard. You magical incantations worked, and I now have a bootable FreeBSD 9.1 system.
?
?> Use 'gpart destroy' again, and set up an MBR partitioning scheme:
> http://forums.freebsd.org/showpost.php?p=149210&postcount=13
I really, really ap
You, sir, are a wizard. You magical incantations worked, and I now have a
bootable FreeBSD 9.1 system.
> Use 'gpart destroy' again, and set up an MBR partitioning scheme:
> http://forums.freebsd.org/showpost.php?p=149210&postcount=13
I really, really appreciate your help.
James
_
Seagate 1.5 TB SATA drive and 12 GB of memory, shipped with
Windows 8.
[...]
I am able to complete the install of FreeBSD 9.1/amd64 from the CD without
any problems. However, when I attempt to boot, it doesn't.
[...]
After an install, I get to the boot0 (the F1 boot menu thing) screen, but
wh
TA drive and 12 GB of memory, shipped with
>> Windows 8.
[...]
>> I am able to complete the install of FreeBSD 9.1/amd64 from the CD without
>> any problems. However, when I attempt to boot, it doesn't.
[...]
>> After an install, I get to the boot0 (the F1 boot menu thin
On Fri, 5 Jul 2013, James E. Pace wrote:
I bought an HP Pavilion p7-1597c [1] system last week. It is Intel Core
i5-3330, with a Seagate 1.5 TB SATA drive and 12 GB of memory, shipped with
Windows 8.
I have disabled Secure Boot and enabled Legacy device booting.
That says the disk is GPT
Hi,
I bought an HP Pavilion p7-1597c [1] system last week. It is Intel Core
i5-3330, with a Seagate 1.5 TB SATA drive and 12 GB of memory, shipped with
Windows 8.
I have disabled Secure Boot and enabled Legacy device booting.
I am able to complete the install of FreeBSD 9.1/amd64 from the CD
Is it the task of:
1. mergemaster, or
2. make installkernel, or
3. make installworld, or
4. the user by manually copying from /usr/src/sys/boot/forth/menu.rc?
I upgraded a 9.0-STABLE VM yesterday, it was last touched late in
August last year. The VM previously used CVSup for updating /usr/src
th no mention of BSD.
The installation to 16Gb SCSI ID:0 on a Dell PowerEdge
Scalable Disk Subsystem 100 appears to go well, but always
results in "Boot Error".
Any help would be appreciated, especially directing me to most
appropriate discussion list/archive.
Tks,
-- Gary
I have tracked down the issue. Not sure whether this is a PR issue or not...
On 2013-06-06, at 11:18 AM, Polytropon wrote:
> On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
>>
>> Strangely, it seems that I cannot boot single user, either
>> using &q
On Sun, 23 Jun 2013, Doug Hardie wrote:
On 23 June 2013, at 20:39, Warren Block wrote:
On Sun, 23 Jun 2013, Doug Hardie wrote:
I had to convert a system from GPT to MBR. All went fine till I tried to
reboot the system. It gets to mountroot and dies trying to mount from
ufs:/dev/ada0p2.
On Sun, 23 Jun 2013 21:35:20 -0700, Doug Hardie wrote:
>
> On 23 June 2013, at 20:39, Warren Block wrote:
> > The loader should be getting that information from /etc/fstab. Have the
> > entries there been changed?
>
> That was the problem. The system used GPT before and I can't
> believe I fo
>> If I enter ufs:/dev/ada0s1a then the system boots fine and runs. I need to
>> alter mountroot so it tries the right partition/slice. How do I do that? I
>> couldn't find anything in the handbook on that.
>
> http://www.freebsd.org/
You need to install the GPT boot code, e. g.
# gpart add -t freebsd-boot -l gpboot -b 40 -s 512K ad0
Why the offset? Why 512k?
Block 40 is the first 4K-aligned block after the 32 blocks occupied by
the GPT. It won't hurt anything if the drive is not a 4K "Advanced
Forma
On Mon, 24 Jun 2013, Polytropon wrote:
On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:
I need to alter mountroot so it tries the right partition/slice.
How do I do that? I couldn't find anything in the handbook on that.
You need to install the GPT boot code, e. g.
#
e the
entries there been changed?
If I enter ufs:/dev/ada0s1a then the system boots fine and runs. I
need to alter mountroot so it tries the right partition/slice. How do
I do that? I couldn't find anything in the handbook on that.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/han
On Sun, Jun 23, 2013 at 4:12 PM, Polytropon wrote:
> On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:
>> I need to alter mountroot so it tries the right partition/slice.
>> How do I do that? I couldn't find anything in the handbook on that.
>
> You need to insta
On Sun, 23 Jun 2013 15:47:53 -0700, Doug Hardie wrote:
> I need to alter mountroot so it tries the right partition/slice.
> How do I do that? I couldn't find anything in the handbook on that.
You need to install the GPT boot code, e. g.
# gpart add -t freebsd-boot -l gpbo
I had to convert a system from GPT to MBR. All went fine till I tried to
reboot the system. It gets to mountroot and dies trying to mount from
ufs:/dev/ada0p2. That won't work. If I enter ufs:/dev/ada0s1a then the system
boots fine and runs. I need to alter mountroot so it tries the right
Hi Everyone,
On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
>
> Strangely, it seems that I cannot boot single user, either
> using "boot -s" from the boot loader, or using the boot menu.
> When I get to the point where the root filesystem is mounted,
.org/doc/handbook/kernelconfig-building.html
> >
> > I need to keep several kernels installed, not
> > just the current and the previous. How to achive this?
> >
>
> KODIR=/boot/testkernel
This parameter can be used to the "make installkernel" command,
for
talled, not
> just the current and the previous. How to achive this?
>
KODIR=/boot/testkernel
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any ma
I think there is an option for this.
But I cannot find it under
9.5. Building and Installing a Custom Kernel
http://www.freebsd.org/doc/handbook/kernelconfig-building.html
I need to keep several kernels installed, not
just the current and the previous. How to achive this?
Thaknks
Anton
_
On Wed, Jun 12, 2013 at 9:56 PM, Chris Whitehouse wrote:
> On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote:
>>>>
>>>>> Since I updated to 9.1-RELEASE my boot process seems to stall for a
>>>>> while. Booting in verbose mode shows message
On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote:
Since I updated to 9.1-RELEASE my boot process seems to stall for a
while. Booting in verbose mode shows messages like these ones:
Opening device da0 -> 6 (repeated like 30 times or so)
Opening device da1 -> 6 (repeated l
On Wed, Jun 12, 2013 at 1:10 AM, Adam Vande More wrote:
> On Tue, Jun 11, 2013 at 4:43 PM, Fernando Apesteguía
> wrote:
>>
>> I recompiled the GENERIC kernel and changed SCSI_DELAY to 2000 instead
>> the default 5000.
>> Still no luck. It doesn't make any difference so I suppose something
>> else
On Tue, Jun 11, 2013 at 4:43 PM, Fernando Apesteguía <
fernando.apesteg...@gmail.com> wrote:
> I recompiled the GENERIC kernel and changed SCSI_DELAY to 2000 instead
> the default 5000.
> Still no luck. It doesn't make any difference so I suppose something
> else changed.
>
> Any ideas?
>
> Thanks
On Tue, Jun 11, 2013 at 8:19 AM, Fernando Apesteguía
wrote:
> On Fri, Jun 7, 2013 at 11:04 PM, Polytropon wrote:
>> On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote:
>>> Since I updated to 9.1-RELEASE my boot process seems to stall for a
>>> while. Bo
On Fri, Jun 7, 2013 at 11:04 PM, Polytropon wrote:
> On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote:
>> Since I updated to 9.1-RELEASE my boot process seems to stall for a
>> while. Booting in verbose mode shows messages like these ones:
>>
>> Opening dev
On Fri, 7 Jun 2013 19:38:34 +0200, Fernando Apesteguía wrote:
> Since I updated to 9.1-RELEASE my boot process seems to stall for a
> while. Booting in verbose mode shows messages like these ones:
>
> Opening device da0 -> 6 (repeated like 30 times or so)
> Opening device da1 -
Hi,
Since I updated to 9.1-RELEASE my boot process seems to stall for a
while. Booting in verbose mode shows messages like these ones:
Opening device da0 -> 6 (repeated like 30 times or so)
Opening device da1 -> 6 (repeated like 30 times or so)
Opening device da2 -> 6 (repeated like 30
the expected reboot process.
>> I am rebooting the machine at the moment as I wish to ensure
>> that I know which physical disk is ada2, so want to boot the
>> machine without it plugged in.
>
> A suggestion: I tend to keep a tendency to use labels instead
> of device name
On Thu, 6 Jun 2013 10:24:52 -0300, Andrew Hamilton-Wright wrote:
>
> Strangely, it seems that I cannot boot single user, either
> using "boot -s" from the boot loader, or using the boot menu.
> When I get to the point where the root filesystem is mounted,
> it hangs
Strangely, it seems that I cannot boot single user, either using "boot -s" from
the boot loader, or using the boot menu. When I get to the point where the
root filesystem is mounted, it hangs right after printing the message:
Trying to mount root from ufs:/dev/ada0s1a
Interestin
hello all,
i have a question about root partition. i want to know when this partition
is mounted in bootstrap process? is root mounted before kernel loading?
more over, i heard that root partition is mounted read-only in boot process
before loading kernel. after that kernel is loaded and all
language information in it.
>
>
>
> > > But as you're asking about USB, there is a way. But this way
> > > depends on how the manufacturer cooperates. Let's discuss that.
> >
> > USB was only meant as the boot device.
>
> Okay, then I m
se, it's about the keyboard controller. This interface usually
is "in parallel" with a PS/2 connector (if present). There is
no language information in it.
> > But as you're asking about USB, there is a way. But this way
> > depends on how the manufacturer cooperates. L
et the keyboard to German; as the system in question is on an USB
> > key for boot and sometimes used in other laptops with QWERTY layout, I
> > would like to have it adapt itself to the actual layout without changing
> > anything before booting in rc.conf and without asking the use
On Wed, 15 May 2013 09:35:54 +0200, Matthias Apitz wrote:
>
> Hello,
>
> I have in /etc/rc.conf a line
>
> keymap="german.iso"
>
> to set the keyboard to German; as the system in question is on an USB
> key for boot and sometimes used in other laptops with
On Wed, 2013-05-15 at 09:35 +0200, Matthias Apitz wrote:
> is there some way to detect the actual keyboard layout
> automagically?
I suspect it's impossible to request what keyboard is used, since some
Linux installers ask the user to type some keys, after that
auto-detection does work. Perhaps yo
Hello,
I have in /etc/rc.conf a line
keymap="german.iso"
to set the keyboard to German; as the system in question is on an USB
key for boot and sometimes used in other laptops with QWERTY layout, I
would like to have it adapt itself to the actual layout without changing
anything befo
How to configure FreeBSD so that an iSCSI initiator will mount a
filesystem on an iSCSI target at boot time?
The /boot/loader.conf file has 'iscsi_initiator_load="YES"' but
iscontrol does not run at boot time.
I believe iscontrol needs to run after the kernel module is
On Mon, May 13, 2013 at 11:22:41AM +0200, Wolfgang Riegler wrote:
> Hi,
>
> since last freebsd-update fetch install I always get this message after
> freebsd-update fetch:
>
> The following files will be updated as part of updating to 9.1-RELEASE-p3:
> /boot/kernel/linker.h
Hi,
since last freebsd-update fetch install I always get this message after
freebsd-update fetch:
The following files will be updated as part of updating to 9.1-RELEASE-p3:
/boot/kernel/linker.hints
but freebsd-update install doesn't install anything.
Is there something wrong with my s
guide https://wiki.freebsd.org/RootOnZFS/ZFSBootPartition but it
> >> does not boot at all. The loader does not show up after choosing
> >> FreeBSD in the boot0 loader.
> >>
> >> The _ prompt appears but nothing starts. I've found many people over
> >> t
>>> requires the freebsd-zfs partition to be the first, so make sure you
>>> add if first, before your swap partition.
>>>
>>> Cheers,
>>> Giorgos
>>
>> What? I've been using this set up for years.
>>
>>
der is important. It seems that zfsboot
>> requires the freebsd-zfs partition to be the first, so make sure you
>> add if first, before your swap partition.
>>
>> Cheers,
>> Giorgos
>
> What? I've been using this set up for years.
>
> =>
add if first, before your swap partition.
Cheers,
Giorgos
What? I've been using this set up for years.
=> 34 976773101 ada1 GPT (465G)
34128 1 freebsd-boot (64k)
1628388608 2 freebsd-swap (4.0G)
8388770 968384365 3 fre
1 - 100 of 4513 matches
Mail list logo
