Sorry, I hadn't checked back in for a few days.
I confirm the single quotes in CMDLINE.TXT works correctly.
Thank you for the help, everybody.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9327ef41fef3598f-Mc323d2834f0c74ce3bb174ba
Deli
experiment...@gmail.com: my mail delivery from this list is delayed so forgive
if you have already confirmed it works. This was my cmdline.txt on my pi4 which
worked:
console=0 sysname=pipi service=cpu nvram=/dev/sdU5888f/nvram
bootargs='local!/dev/sdU5888f/fscache -a tcp!*!564'
So as has been
no, the raspberry pi bootloader is a special snowflake, so we need
to use commandline.txt there.
The solution is to quote the arguments in commandline.txt. As Paul
said:
nobootprompt='local!/dev/sdN0/fs -A'
is most likely the way you do that. I don't currently have a
raspberry pi set up
I'm afraid I'm still 36 hours away from being able to test this for real,
but you should be able to, in your command line, just put that argument in
single quotes:
>
> nobootprompt='local!/dev/sdN0/fs -A'
If even doing it in your plan9.ini didn't work, then there's likely
something more than jus
On Sunday, June 01, 2025, at 5:40 PM, flux wrote:
> The workaround, such as it is, is to put the offending nobootargs into a
> plan9.ini file
If I understand you correctly, the part of cmdline.txt with
nobootprompt=local!/dev/sdN0/fs -A should be moved to a newly created file
called plan9.ini in
We'll, there's a code walk I should have taken to the next level.
Paul
On Sun, Jun 1, 2025, 2:44 p.m. Steve Simon wrote:
> if its the libc tokenize(2) then it does shell like tokenizing (rc that
> is) so you can use single quotes to quote stuff, and a double single quote
> to embed one single q
if its the libc tokenize(2) then it does shell like tokenizing (rc that is) so you can use single quotes to quote stuff, and a double single quote to embed one single quote.-SteveOn 1 Jun 2025, at 8:41 am, f...@p9f.org wrote:
I just reviewed the code that handles the command line on rpi where sys/
I just reviewed the code that handles the command line on rpi where
sys/src/9/arm64/bootargs.c:/^plan9iniinit handles the command line by calling
tokenize(). That splits the command line at spaces, without any sort of
quoting.
The workaround, such as it is, is to put the offending nobootargs in
I haven't been able to find anything that implies it's possible to incorporate
a space into a command by any means. If this is the case it's a little
troubling.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T9327ef41fef3598f-Ma28f62c42
Quoth experiment...@gmail.com:
> So I have no idea what happened to it but many of the system executables were
> missing. Too much functionality was lost so I backed up the files I'd changed
> and reinstalled. Same issue so we might as well pretend it didn't happen. it
> just caused a delay in m
So I have no idea what happened to it but many of the system executables were
missing. Too much functionality was lost so I backed up the files I'd changed
and reinstalled. Same issue so we might as well pretend it didn't happen. it
just caused a delay in my replying.
ori, cmdline.txt has:
conso
When you do rm /srv/gefs* you also need to kill the running gefs or
it'll hang around hoarding its 1GB of memory or whatever it is. So
something like
cd proc
grep gefs */args
echo kill | sed '
w 210/ctl
w 211/ctl
[etc]'
(sed w being the closest thing to tee).
---
what are the contents of your commandline.txt(?) (I think that's
the place where you configure your command line). The '-A' that
you're adding there should be present.
from what I remember, the commandline.txt format puts all args
on one line, so perhaps there's some quoting needed?
Quoth experim
The only way I can get my Pi4 to boot from the gefs partition is to delete
everything from /srv/gefs first.
Using -Ac or even just -c doesn't help. It just churns through entries then
after a couple of pages fails with a broken pipe.
This is what I'm faced with every boot. I haven't got a clue
> On May 5, 2018, at 1:49 PM, Lyndon Nerenberg wrote:
>
> Has anyone has managed to boot any of the plan9 variants under FreeBSD's
> bhyve hypervisor? Just curious to hear about any success/fail experiences.
>
> --lyndon
>
>
I have 9front 6350 that I successfully booted under bhyve on fre
On Sat, 05 May 2018 12:49:34 -0700 Lyndon Nerenberg wrote:
> Has anyone has managed to boot any of the plan9 variants under FreeBSD's
> bhyve hypervisor? Just curious to hear about any success/fail
> experiences.
Matthew Veety on 9fans on 27-Jan-2016:
> I have a 9front cpu server running in bhyv
Has anyone has managed to boot any of the plan9 variants under FreeBSD's bhyve
hypervisor? Just curious to hear about any success/fail experiences.
--lyndon
hiro <23h...@gmail.com> writes:
> Extract a Plan9 root file system (ISOs from official plan9, 9atom or
> 9front all should work) into your directory of choice "/path/to/plan9"
> (9vx defaults to the directory /usr/local/plan9vx)
Thanks Hiro, extracting the rootfs from the ISO makes 9vx work. I wa
Extract a Plan9 root file system (ISOs from official plan9, 9atom or
9front all should work) into your directory of choice "/path/to/plan9"
(9vx defaults to the directory /usr/local/plan9vx)
On 3/2/16, Vasudev Kamath wrote:
>
> Hi,
>
> I was reading the Arch wiki on 9vx ¹ which said 9vx should/m
Hi,
I was reading the Arch wiki on 9vx ¹ which said 9vx should/might boot 9atom
and 9front ISO also. So I thought of trying this out and executed the
following command.
9vx -r ../images/9front-4796.018cb441d1b5.iso -u glenda "CWD=#Z`pwd`"
"nvram=#Z`pwd`/9front.nvr"
But I got the following err
> If I choose 9front machine as for network file/auth/cpu server (cwfs),
> and try to boot Richard's 9pi terminal (fossil) but root from the server,
> can I do it?
Yes.
sl
If I choose 9front machine as for network file/auth/cpu server (cwfs),
and try to boot Richard's 9pi terminal (fossil) but root from the server,
can I do it?
Kenji
> On 2014-02-16 13:26, Aram Hăvărneanu wrote:
> > I don't have any other machines to test this on. I *think* the same
> > problem happens with a T410[3], but I might remember wrong. I can't
> > test T410 right now.
>
> I own a T410 and tried Plan 9 on it a while ago. I there must be a
> thread fro
On Mon, Feb 17, 2014 at 12:05 PM, wrote:
> I own a T410 and tried Plan 9 on it a while ago. I there must be a
> thread from back then on the mailing list. I was able to boot into
> a live environment, but failed to install to disk.
Yes, 32-bit Labs Plan 9 and 32-bit non-PAE 9atom Plan 9 work on
On 2014-02-16 13:26, Aram Hăvărneanu wrote:
I don't have any other machines to test this on. I *think* the same
problem happens with a T410[3], but I might remember wrong. I can't
test T410 right now.
I own a T410 and tried Plan 9 on it a while ago. I there must be a
thread from back then on th
As a comparison, the new pc64 9front kernel works fine on these machines.
--
Aram Hăvărneanu
On Sun, Feb 16, 2014 at 1:46 PM, erik quanstrom wrote:
> are there any bios knobs that will change acpi settings on
> either of these boxes?
No, there are not, unfortunately.
--
Aram Hăvărneanu
On Sun Feb 16 07:28:11 EST 2014, ara...@mgk.ro wrote:
> I am trying to boot Erik's amd64 USB install image[0] on a ThinkPad
> R60[1] and T400[2].
>
> Boot process hangs after printing:
> cpu0: spurious interrupt 51, last 50
> cpu1: spurious interrupt 51, last 50
>
> R60 picture: http://i.
I am trying to boot Erik's amd64 USB install image[0] on a ThinkPad
R60[1] and T400[2].
Boot process hangs after printing:
cpu0: spurious interrupt 51, last 50
cpu1: spurious interrupt 51, last 50
R60 picture: http://i.imgur.com/jaGOIbe.jpg
T400 picture: http://i.imgur.com/WaYgrYM.jpg
So
On 09/15/2011 10:56 PM, Sasha and Tanya Kapshuk wrote:
On 09/15/2011 12:57 AM, Richard Miller wrote:
i want to boot plan9 using grub.
My /boot/grub/menu.lst includes these lines:
title Plan 9
root(hd0,1)
chainloader +1
and the corresponding partition has /386/pbslba as a boot bl
On 09/15/2011 12:57 AM, Richard Miller wrote:
i want to boot plan9 using grub.
My /boot/grub/menu.lst includes these lines:
title Plan 9
root(hd0,1)
chainloader +1
and the corresponding partition has /386/pbslba as a boot block --
see format(8).
thanks for the tip, R
Not yet, if you're willing to be a test subject head over to nix-dev
and we can work through the steps for you and add a document
explaining the process.
Noah
On Thu, Sep 15, 2011 at 4:08 PM, Christian Neukirchen
wrote:
> quans...@quanstro.net (erik quanstrom) writes:
>
>> does 9load do enough
> > does 9load do enough to boot the nix 64-bit kernel?
> And are there instructions for bootstrapping such a nix system?
> It builds fine here now, but I have no idea how/what to put on disk to
> make it boot.
The PXE bootloader seems to be in /sys/src/nix/w/pxeload.
--
David du Colombier
No. Compile an npxeload from /sys/src/nix/w/pxeload. That should work.
If it doesn't file an issue.
Noah
On Thu, Sep 15, 2011 at 3:27 PM, erik quanstrom wrote:
> does 9load do enough to boot the nix 64-bit kernel?
>
> - erik
>
>
quans...@quanstro.net (erik quanstrom) writes:
> does 9load do enough to boot the nix 64-bit kernel?
>
> - erik
And are there instructions for bootstrapping such a nix system?
It builds fine here now, but I have no idea how/what to put on disk to
make it boot.
--
Christian Neukirchenhttp://
does 9load do enough to boot the nix 64-bit kernel?
- erik
thanks a lot.
i'll give that a try.
On Thu, Sep 15, 2011 at 12:57 AM, Richard Miller <9f...@hamnavoe.com> wrote:
> > i want to boot plan9 using grub.
>
> My /boot/grub/menu.lst includes these lines:
>
> title Plan 9
> root(hd0,1)
> chainloader +1
>
> and the corresponding partitio
> i want to boot plan9 using grub.
My /boot/grub/menu.lst includes these lines:
title Plan 9
root(hd0,1)
chainloader +1
and the corresponding partition has /386/pbslba as a boot block --
see format(8).
howdy,
i've installed plan9 on a separate partition of my hard drive alongside
debian linux.
i'm not 100% clear on what boot option is best for a setting like this.
i want to boot plan9 using grub.
if that's not doable, can anyone please suggest an alternative way of
doing it.
sasha kapsh
I've played with booting the plan9 kernel on OLPC a little and
simplified the boot process and the kernel changes needed.
Here are the patches and instructions:
http://www.thenewsh.com/~newsham/x/9/olpc/
And a question -- is it possible to use a usb key as a root
filesystem? What's involved?
> I'd like to check this out, but the server doesn't want to
> talk to me. Is there a copy available elsewhere?
Oops, that's rather embarrassing, sorry about that, that server has a
few issues (oddly enough, it's sysvinit is broken). I posted tarball for
the time begin at http://andy753421.ath.cx/
I'd like to check this out, but the server doesn't want to
talk to me. Is there a copy available elsewhere?
My friend Mike and I were talking a while back about Unix init systems
and came to the conclusion that mk's dependency tracking could come in
handy. I decided to implement it a few days ago using plan9port and
thought that some of the folks here might be interested. Although, I
still haven't decide
> Great idea, I like it :) I'll have a look at the code later.
> You're using it on old unix/linux not plan 9 I guess? thanks.
Yep, I'm running it on my ~4 year old laptop. I'm curious to see how it
would compare on something newer though. I think it would still be I/O
bound, so I'm not sure ho
Great idea, I like it :) I'll have a look at the code later.
You're using it on old unix/linux not plan 9 I guess? thanks.
On Fri, Oct 16, 2009 at 05:54:12AM +, Andy Spencer wrote:
> My friend Mike and I were talking a while back about Unix init systems
> and came to the conclusion that mk's
thanks for that. it is neat!
My friend Mike and I were talking a while back about Unix init systems
and came to the conclusion that mk's dependency tracking could come in
handy. I decided to implement it a few days ago using plan9port and
thought that some of the folks here might be interested. Although, I
still haven't decide
On Mon, Jun 29, 2009 at 2:11 PM, Lyndon Nerenberg wrote:
> I accidentally installed a FreeBSD drive in my MacBook. To my surprise,
> it just worked. If you install a boot drive with the "usual" PC disk
> partitioning the Macs will boot in what seems to be a fairly complete
> BIOS emulation.
>
> How
I accidentally installed a FreeBSD drive in my MacBook. To my surprise,
it just worked. If you install a boot drive with the "usual" PC disk
partitioning the Macs will boot in what seems to be a fairly complete
BIOS emulation.
How far Plan9 gets is another story, but my guess is that even if it
se
2009/6/29 David Leimbach :
> On Mon, Jun 29, 2009 at 9:20 AM, Devon H. O'Dell
> wrote:
>>
>> 2009/6/29 Brad Frank :
>> > What kinds of modifications would be necessary to get plan9 booting on
>> > intel macs? The latest releases don't seem to boot, they just hang.
>>
>> EFI, at a minimum.
>>
>
> W
On Mon, Jun 29, 2009 at 9:20 AM, Devon H. O'Dell wrote:
> 2009/6/29 Brad Frank :
> > What kinds of modifications would be necessary to get plan9 booting on
> > intel macs? The latest releases don't seem to boot, they just hang.
>
> EFI, at a minimum.
>
>
What of rEFIt or Boot Camp? They have BIOS
2009/6/29 Brad Frank :
> What kinds of modifications would be necessary to get plan9 booting on
> intel macs? The latest releases don't seem to boot, they just hang.
EFI, at a minimum.
What kinds of modifications would be necessary to get plan9 booting on
intel macs? The latest releases don't seem to boot, they just hang.
Hello
I just need to boot the kenel, this machine is rented, i can't change
any hardware configuration, i can just try to get plan9 running there
with the help of qemu. . .
I installed a fossil terminal, now i need to instruct 9load to read
the kernel from /dev/sdB0, and if the kernel lo
Hi !
Use 9P instead of iSCSI. In My setup, I use small IDE Flash drives (128Mb)
They works just fine ! :)
2008/10/20 <[EMAIL PROTECTED]>
> Hola,
>
> Has anyone done this?
>
> I have access to a cheap hardware which could be a nice plan9 cpu server,
> the only thing does not work
> is the iSCSI d
Hola,
Has anyone done this?
I have access to a cheap hardware which could be a nice plan9 cpu server, the
only thing does not work
is the iSCSI disk (or i think so, look at the lspci below)
I suppose the bios of the machine supports booting from iSCSI, so i think i
could put a 9load or
9pxel
56 matches
Mail list logo
