Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
I may be completely off piste here, but here goes From memory and not having an x86 system booted at the moment to double check: You don't need to mess around with partitioning at all. You do need to label the disk though (which is annoying). So your first format, when it asked you whether or not to label, just say yes, write the label and exit. Assuming your rpool is currently running as a single disk (it's an x86 system and you have physically removed the old disk prior to boot), you just attach a mirror to the rpool. I'm not entirely sure if writing a bootblock is required, I have always done so, but am wondering if the mirror attach already does that for you, but as someone else pointed out earlier, it doesn't hurt to re-write it. HTH Eric On 2021-01-17 23:43, Bob Friesenhahn wrote: On Sun, 17 Jan 2021, Gary Mills wrote: On Sun, Jan 17, 2021 at 02:11:18PM -0600, Bob Friesenhahn wrote: I assume your replacement succeeded. I hope so! There are more details in the detail section, but perhaps I must assume that all is ok with the boot loader. It is even possible that zfs arranged to install the boot loader on the disk automatically. To be sure all is okay, try booting from one disk and then the other. The BIOS on this SuperMicro system is not terribly helpful so I am not quite sure how to do that other than pulling drives. After a power outage where the system was down for maybe 15 minutes, it failed to boot properly. There was a failing boot drive still installed which I had mostly ignored other than disabling it. But the BIOS and boot loader did not seem to know that it was disabled and tried to slowly boot from it. Another anomally was that it appeared that the BIOS (or something) was causing all of the data on all the disks to be read in turn before booting. I have never seen anything like it before. By physically removing the flaky boot drive and popping out the hot-swap drives, I got the system to boot. I found that one of the hot-swap drives no longer spun up. The BIOS and boot loader did not handle this well. Bob -- / . Eric A. Bautsch /-- __ _____ / // / / (_/(___(__/ email: eric.baut...@pobox.com ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, 17 Jan 2021, Gary Mills wrote: On Sun, Jan 17, 2021 at 02:11:18PM -0600, Bob Friesenhahn wrote: I assume your replacement succeeded. I hope so! There are more details in the detail section, but perhaps I must assume that all is ok with the boot loader. It is even possible that zfs arranged to install the boot loader on the disk automatically. To be sure all is okay, try booting from one disk and then the other. The BIOS on this SuperMicro system is not terribly helpful so I am not quite sure how to do that other than pulling drives. After a power outage where the system was down for maybe 15 minutes, it failed to boot properly. There was a failing boot drive still installed which I had mostly ignored other than disabling it. But the BIOS and boot loader did not seem to know that it was disabled and tried to slowly boot from it. Another anomally was that it appeared that the BIOS (or something) was causing all of the data on all the disks to be read in turn before booting. I have never seen anything like it before. By physically removing the flaky boot drive and popping out the hot-swap drives, I got the system to boot. I found that one of the hot-swap drives no longer spun up. The BIOS and boot loader did not handle this well. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Could you update your sysroot, jclulow?
On Sun, 17 Jan 2021 at 05:24, Peter Tribble wrote: > On Sun, Jan 17, 2021 at 11:15 AM Hung Nguyen Gia via openindiana-discuss < > openindiana-discuss@openindiana.org> wrote: > > I wanted to use your sysroot here to build a cross compiler for OI from > > Linux: > > > > https://github.com/illumos/sysroot > > > > But it seemed you didn't include the C++ part. I couldn't find them. There > > is no C++ headers, e.g: cmath, iostream,... nor the C++ standard library > > itself. > Those are supplied by the toolchain, in our case usually gcc. And you would > normally > need to ensure that the versions in the sysroot are compatible (for > whatever definition of > compatible you're interested in) with the toolchain you're using. Right. The official illumos sysroot contains, as much as possible, only things that are delivered directly from illumos-gate. A small exception is made for libssp and libgcc_s, after an extensive survey was undertaken to determine if compatible versions of those libraries were available in basically all shipping distributions. As described in the release notes, the copies of these libraries included within the archive are stubs: they contain no executable code, and would not actually _work_ if you attempted to use them on an illumos system. They're just for cross-compilation. Unlike libgcc_s and libssp, there aren't sufficiently strong backwards compatibility guarantees made about any of the C++ runtimes, or OpenSSL, or many other commonly used components. On that basis, they're not good candidates for an illumos sysroot. You could, on the other hand, select a specific distribution (and presumably a specific version) to create a different sort of sysroot. That sysroot archive could then include anything that was guaranteed to be available within the distribution; a process of selection that would depend a lot on the policies of that specific distribution and on your goals. > > This sysroot is also a bit old, too. > A sysroot can be used for a variety of uses. This one is targetted at > building software on > a current host that will still run correctly on an older system. More specifically than that, it was built almost exclusively at the time with Rust in mind. The Rust project uses this sysroot archive within a Linux docker container to cross-compile the Rust toolchain (including Cargo, etc) for illumos. Selecting the specific version here was a balance between the widest possible audience (thus, the oldest contents) and the inclusion of the getrandom(2) public API. More details on our choice are in the release notes: https://github.com/illumos/sysroot/releases/tag/20181213-de6af22ae73b-v1 We will likely at some point select a new version of the gate to create a new sysroot. This will probably not happen until we need to use a new interface of some kind that was added some time after December 2018. When we get there, it will likely _still_ seem to be an old version -- the 20181213 sysroot was, after all, created in April 2020. If we were to create a new sysroot in April 2021, it may well be from gate bits towards the end of 2019 or very early 2020. Any newer and it is unlikely to result in binaries that can be used on, as much as possible, all supported distribution releases. You can see from the release schedule at OmniOS that some of their LTS releases are supported for a long time, and we want the sysroot to produce binaries that can be used there: https://omniosce.org/schedule The current LTS release is r151030, which was released in May 2019 and will be supported until May 2022. That makes it unlikely that the released sysroot would advance past May 2019 until 2022, unless we could find a way around the problem. > Generally I would expect anyone using a sysroot to have a pretty specific > target in mind. > It's not that hard to create, either simply copying an existing system that > has the bits you > want, or using packaging - pkg has the image-create functionality designed > for exactly > this purpose. Yes, you could definitely use "pkg image-create" to install any set of OpenIndiana packages into a directory tree. This is, as it happens, basically what the Distribution Constructor does today to create the install media. The OmniOS folks also use this approach to build cloud images in their Kayak tools. You could also use the tools we included in the "illumos/sysroot" repository, with minor configuration or modification, to make your own sysroot from any built copy of illumos. Cheers. -- Joshua M. Clulow http://blog.sysmgr.org ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, Jan 17, 2021 at 02:11:18PM -0600, Bob Friesenhahn wrote: > I assume your replacement succeeded. > So now (trusting that we should use modern documented methods rather than > the antique methods described by the Wiki) I used > > /sbin/bootadm install-bootloader > > and no errors were reported. Adding the '-v' option also does not reveal > significant issues and I see it referring to both disks. I did that a year ago. Here's my transcript: # /sbin/bootadm install-bootloader -Mfv -P rpool be_do_installboot: device mirror-0 be_do_installboot: device c5t0d0s0 Command: "/usr/sbin/installboot -F -m -f //boot/pmbr //boot/gptzfsboot /dev/rdsk/c5t0d0s0" Output: bootblock written for /dev/rdsk/c5t0d0s0, 323 sectors starting at 1024 (abs 26112) stage1 written to slice 1 sector 0 (abs 12544) stage1 written to master boot sector be_do_installboot: device c5t1d0s0 Command: "/usr/sbin/installboot -F -m -f //boot/pmbr //boot/gptzfsboot /dev/rdsk/c5t1d0s0" Output: bootblock written for /dev/rdsk/c5t1d0s0, 323 sectors starting at 1024 (abs 26112) stage1 written to slice 1 sector 0 (abs 12544) stage1 written to master boot sector My root mirror looks like this: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0ONLINE 0 0 0 c5t0d0s0 ONLINE 0 0 0 c5t1d0s0 ONLINE 0 0 0 > This is the > relevant high-level description of the bootadm install-bootloader option: > >This subcommand can be used to install, update, and repair the boot >loader on a ZFS pool intended for booting. When disks in the ZFS pool >used for booting the system have been replaced, one should run bootadm >install-bootloader to ensure that all disks in that pool have the >system boot loader installed. > > There are more details in the detail section, but perhaps I must assume that > all is ok with the boot loader. It is even possible that zfs arranged to > install the boot loader on the disk automatically. To be sure all is okay, try booting from one disk and then the other. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, 17 Jan 2021, Bob Friesenhahn wrote: It is my understanding that the partitioning/format of the existing disk came from a from-scratch OpenIndiana Hipster install done perhaps a year ago. If this EFI partitioning is what is done now, the Wiki does not seem to reflect it. The new disk is being resilvered into the root pool now. It seems that there are new issues (or at least unexpected things) that I don't see addressed anywhere in the OpenIndiana documentation or Wiki: I did this after adding my replacement disk to the root pool: weerd:~# /usr/sbin/installboot -m /boot/pmbr /boot/gptzfsboot /dev/rdsk/c5t1d0s0 Booting pcfs from EFI labeled disks requires the boot partition. So, now after adding this disk to the root pool, the partitioning info has entirely changed and there is no boot partition! Existing disk: = Total disk sectors available: 1953508717 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0 systemwm 256 256.00MB 524543 1usrwm524544 931.26GB 1953508750 2 unassignedwm 000 3 unassignedwm 000 4 unassignedwm 000 5 unassignedwm 000 6 unassignedwm 000 8 reservedwm1953508751 8.00MB 1953525134 weerd:~# prtvtoc /dev/rdsk/c5t0d0s2 * /dev/rdsk/c5t0d0s2 partition map * * Dimensions: * 512 bytes/sector * 1953525168 sectors * 1953525101 accessible sectors * * Flags: * 1: unmountable * 10: read-only * * Unallocated space: * First SectorLast * Sector CountSector * 34 222 255 * * First SectorLast * Partition Tag FlagsSector CountSector Mount Directory 0 1200256524288524543 1 400 524544 1952984207 1953508750 8 1100 1953508751 16384 1953525134 Replacement for failed second disk: === partition> print Current partition table (original): Total disk sectors available: 1953508717 + 16384 (reserved sectors) Part TagFlag First Sector Size Last Sector 0 systemwm 256 256.00MB 524543 1usrwm524544 931.26GB 1953508750 2 unassignedwm 000 3 unassignedwm 000 4 unassignedwm 000 5 unassignedwm 000 6 unassignedwm 000 8 reservedwm1953508751 8.00MB 1953525134 weerd:~# prtvtoc /dev/rdsk/c5t1d0s2 * /dev/rdsk/c5t1d0s2 partition map * * Dimensions: * 512 bytes/sector * 1953525168 sectors * 1953525101 accessible sectors * * Flags: * 1: unmountable * 10: read-only * * Unallocated space: * First SectorLast * Sector CountSector * 34 222 255 * * First SectorLast * Partition Tag FlagsSector CountSector Mount Directory 0 1200256524288524543 1 400 524544 1952984207 1953508750 8 1100 1953508751 16384 1953525134 Now if I enter 'fdisk' for either disk it claims EFI partioning! It seems that adding the disk to the zfs pool has converted its partioning from SMI to EFI. So now (trusting that we should use modern documented methods rather than the antique methods described by the Wiki) I used /sbin/bootadm install-bootloader and no errors were reported. Adding the '-v' option also does not reveal significant issues and I see it referring to both disks. This is the relevant high-level description of the bootadm install-bootloader option: This subcommand can be used to install, update, and repair the boot loader on a ZFS pool intended for booting. When disks in the ZFS pool used for booting the system have been replaced, one should run bootadm install-bootloader to ensure that all disks in that pool have the system boot loader installed. There are more details in the detail section, but perhaps I must assume that all is ok with the boot loader. It is even possible that zfs arranged to install the boot loader on the disk automatically. Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
Am 17.01.21 um 19:59 schrieb Bob Friesenhahn:
On Sun, 17 Jan 2021, Gary Mills wrote:
On Sun, Jan 17, 2021 at 10:56:58AM -0600, Bob Friesenhahn wrote:
One of my root pool mirror disks (c5t1d0) on an Intel system failed
but it
is currently booted using the other disk (c5t0d0). This happened to
me many
years before on the same system and I did successfully replace the
disk.
The zpool man page should be helpful to you, in particular the `zpool
replace' command, if the failed disk is still installed. Otherwise,
you may have to use a different command or a combination of commands.
The disk may not need to be initialized with fdisk or format or some
other command if you are using the whole disk. You can tell that from
`zpool status'. If you are using slices, you will need to use format
to make it the same as the other disk.
I used part of some old notes from yourself at
https://wiki.openindiana.org/oi/How+to+migrate+the+root+pool and
manually updated the Solaris partition table to look more like the
original one and also the partition tables on OmniOS systems I have
here. However, the partition table type is of type Solaris ('SMI')
whereas the partition table type of the peer existing disk is 'EFI'.
After configuring the Solaris partitions, I executed 'label' at which
time it asked me if I wanted to use a SMI or EFI label. This happened:
partition> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Warning: This disk has an SMI label. Changing to EFI label will erase all
current partitions.
Continue? n
partition> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]:
Ready to label disk, continue? y
So I am using the SMI label type rather than the EFI label type.
The above does not occur in your Wiki article so it must be a more
modern 'fdisk' feature.
It is my understanding that the partitioning/format of the existing
disk came from a from-scratch OpenIndiana Hipster install done perhaps
a year ago. If this EFI partitioning is what is done now, the Wiki
does not seem to reflect it.
The new disk is being resilvered into the root pool now.
If I have made a mistake, I can remove the device from the pool and
try again.
FYI: It appears that the Wiki server must be down again.
Bob
The wiki still works for me.
Andreas
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, 17 Jan 2021, Gary Mills wrote:
On Sun, Jan 17, 2021 at 10:56:58AM -0600, Bob Friesenhahn wrote:
One of my root pool mirror disks (c5t1d0) on an Intel system failed but it
is currently booted using the other disk (c5t0d0). This happened to me many
years before on the same system and I did successfully replace the disk.
The zpool man page should be helpful to you, in particular the `zpool
replace' command, if the failed disk is still installed. Otherwise,
you may have to use a different command or a combination of commands.
The disk may not need to be initialized with fdisk or format or some
other command if you are using the whole disk. You can tell that from
`zpool status'. If you are using slices, you will need to use format
to make it the same as the other disk.
I used part of some old notes from yourself at
https://wiki.openindiana.org/oi/How+to+migrate+the+root+pool and
manually updated the Solaris partition table to look more like the
original one and also the partition tables on OmniOS systems I have
here. However, the partition table type is of type Solaris ('SMI')
whereas the partition table type of the peer existing disk is 'EFI'.
After configuring the Solaris partitions, I executed 'label' at which
time it asked me if I wanted to use a SMI or EFI label. This
happened:
partition> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]: 1
Warning: This disk has an SMI label. Changing to EFI label will erase
all
current partitions.
Continue? n
partition> label
[0] SMI Label
[1] EFI Label
Specify Label type[0]:
Ready to label disk, continue? y
So I am using the SMI label type rather than the EFI label type.
The above does not occur in your Wiki article so it must be a more
modern 'fdisk' feature.
It is my understanding that the partitioning/format of the existing
disk came from a from-scratch OpenIndiana Hipster install done perhaps
a year ago. If this EFI partitioning is what is done now, the Wiki
does not seem to reflect it.
The new disk is being resilvered into the root pool now.
If I have made a mistake, I can remove the device from the pool and
try again.
FYI: It appears that the Wiki server must be down again.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, Jan 17, 2021 at 10:56:58AM -0600, Bob Friesenhahn wrote: > One of my root pool mirror disks (c5t1d0) on an Intel system failed but it > is currently booted using the other disk (c5t0d0). This happened to me many > years before on the same system and I did successfully replace the disk. The zpool man page should be helpful to you, in particular the `zpool replace' command, if the failed disk is still installed. Otherwise, you may have to use a different command or a combination of commands. The disk may not need to be initialized with fdisk or format or some other command if you are using the whole disk. You can tell that from `zpool status'. If you are using slices, you will need to use format to make it the same as the other disk. -- -Gary Mills--refurb--Winnipeg, Manitoba, Canada- ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
On Sun, 17 Jan 2021, Andreas Wacknitz wrote: The wiki should be online again. Thanks! Now that I see the Wiki page at https://wiki.openindiana.org/oi/2.1+Post-installation Looking back in my terminal history I see that I did speculatively follow the instructions (guessed) and did this: " format> fdisk No fdisk table exists. The default partition for the disk is: a 100% "SOLARIS System" partition Type "y" to accept the default partition, otherwise type "n" to edit the partition table. y " For some reason the previously existing disk says that it is using a partition of type EFI (which it seems that fdisk creates when given the -E option) rather than Solaris. The partitioning is clearly different. So I got an error when I did this: weerd:~# prtvtoc /dev/rdsk/c5t0d0s2 | fmthard -s - /dev/rdsk/c5t1d0s2 Partition 0 not aligned on cylinder boundary: " 0 1200 256524288524543" It seems that either I need to make this new disk also use EFI partitioning, or manually create compatible partitioning in the Solaris fdisk partition so that it can support the boot record and zfs pool. What is the best approach to solve this? Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] How to replace failed rpool mirror disk?
Am 17.01.21 um 17:56 schrieb Bob Friesenhahn: One of my root pool mirror disks (c5t1d0) on an Intel system failed but it is currently booted using the other disk (c5t0d0). This happened to me many years before on the same system and I did successfully replace the disk. It seems that the notes I left for myself are incorrect or insufficient. It seems that the OpenIndiana Wiki is still down so I can not refer to the information there. I don't trust that documentation from modern Solaris applies, and it seems to assume knowledge that I don't have. The only notes I left for myself is this: " To replace a failed mirror disk: 1. 'format -e' and use the 'fdisk' option for whole disk. 2. pfexec prtvtoc /dev/rdsk/c3t0d0s2 | pfexec fmthard -s - /dev/rdsk/c3t1d0s2 where /dev/rdsk/c3t0d0s2 is good partitioned disk and /dev/rdsk/c3t1d0s2 is new disk. 3. Use format to be sure that partition tables are ok. " When I enter the 'fdisk' program I am not sure of what to do. At the moment it says (without me doing anything, but I am unsure of the full history of this disk): " Total disk size is 60800 cylinders Cylinder size is 32130 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == = === == === 1 Active Solaris2 1 60799 60799 100 SELECT ONE OF THE FOLLOWING: 1. Create a partition 2. Specify the active partition 3. Delete a partition 4. Change between Solaris and Solaris2 Partition IDs 5. Edit/View extended partitions 6. Exit (update disk configuration and exit) 7. Cancel (exit without updating disk configuration) Enter Selection: " If I enter fdisk using the already formatted/in-use disk, it says " Total disk size is 60800 cylinders Cylinder size is 32130 (512 byte) blocks Cylinders Partition Status Type Start End Length % = == = === == === 1 EFI 0 60800 60801 100 " Can someone who is familiar with the steps appropriate for modern OpenIndiana please share them with me, or refer me to useful instructions on a site which is still up? Thanks, Bob The wiki should be online again. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] How to replace failed rpool mirror disk?
One of my root pool mirror disks (c5t1d0) on an Intel system failed but it is currently booted using the other disk (c5t0d0). This happened to me many years before on the same system and I did successfully replace the disk. It seems that the notes I left for myself are incorrect or insufficient. It seems that the OpenIndiana Wiki is still down so I can not refer to the information there. I don't trust that documentation from modern Solaris applies, and it seems to assume knowledge that I don't have. The only notes I left for myself is this: " To replace a failed mirror disk: 1. 'format -e' and use the 'fdisk' option for whole disk. 2. pfexec prtvtoc /dev/rdsk/c3t0d0s2 | pfexec fmthard -s - /dev/rdsk/c3t1d0s2 where /dev/rdsk/c3t0d0s2 is good partitioned disk and /dev/rdsk/c3t1d0s2 is new disk. 3. Use format to be sure that partition tables are ok. " When I enter the 'fdisk' program I am not sure of what to do. At the moment it says (without me doing anything, but I am unsure of the full history of this disk): " Total disk size is 60800 cylinders Cylinder size is 32130 (512 byte) blocks Cylinders Partition StatusType Start End Length% = == = === == === 1 ActiveSolaris2 1 6079960799100 SELECT ONE OF THE FOLLOWING: 1. Create a partition 2. Specify the active partition 3. Delete a partition 4. Change between Solaris and Solaris2 Partition IDs 5. Edit/View extended partitions 6. Exit (update disk configuration and exit) 7. Cancel (exit without updating disk configuration) Enter Selection: " If I enter fdisk using the already formatted/in-use disk, it says " Total disk size is 60800 cylinders Cylinder size is 32130 (512 byte) blocks Cylinders Partition StatusType Start End Length% = == = === == === 1 EFI 0 6080060801100 " Can someone who is familiar with the steps appropriate for modern OpenIndiana please share them with me, or refer me to useful instructions on a site which is still up? Thanks, Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Could you update your sysroot, jclulow?
On Sun, Jan 17, 2021 at 11:15 AM Hung Nguyen Gia via openindiana-discuss < openindiana-discuss@openindiana.org> wrote: > I wanted to use your sysroot here to build a cross compiler for OI from > Linux: > > https://github.com/illumos/sysroot > > But it seemed you didn't include the C++ part. I couldn't find them. There > is no C++ headers, e.g: cmath, iostream,... nor the C++ standard library > itself. > Those are supplied by the toolchain, in our case usually gcc. And you would normally need to ensure that the versions in the sysroot are compatible (for whatever definition of compatible you're interested in) with the toolchain you're using. > This sysroot is also a bit old, too. > A sysroot can be used for a variety of uses. This one is targetted at building software on a current host that will still run correctly on an older system. (This is also the way that Oracle built Java for Solaris, I believe, using a Solaris 10 sysroot on a Solaris 11 build system so that the resulting binaries will still run on Solaris 10.) Generally I would expect anyone using a sysroot to have a pretty specific target in mind. It's not that hard to create, either simply copying an existing system that has the bits you want, or using packaging - pkg has the image-create functionality designed for exactly this purpose. Please correct me if I'm wrong. > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss > -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Building packages from source
Is it possible to take programs such as Chromium and build them in Openindiana? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Could you update your sysroot, jclulow?
I wanted to use your sysroot here to build a cross compiler for OI from Linux: https://github.com/illumos/sysroot But it seemed you didn't include the C++ part. I couldn't find them. There is no C++ headers, e.g: cmath, iostream,... nor the C++ standard library itself. This sysroot is also a bit old, too. Please correct me if I'm wrong. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] How to expand the live usb to use all of the space on the device?
My usb is 16 GB. The live image after dd-ed into it only consumes about 1.9 GB. I want to be able to use the remaining space, from the live system. How to do this? Thanks. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] OpenIndiana Developer Edition
Sorry because I had caused all of this misunderstanding. I'm not good at English. The product of Google Translate + poor human skills created this. My choice of words is unwise or could be plain wrong. Due to affect of mental drugs I have to take, I did many weirded things on this list. Sorry everyone. Let me describe what I want to do: I'm not going to create a fork. The current OI Desktop doesn't include build tools by default. I suggest to add the build-essential package, so it's possible to build illumos-gate using the live image, without having to install to HDD, given we had enough RAM and external disk space. Given my experience so far, I think this will not be accepted. So I'm going to create my own live image of OI, I would called OI Developer Edition, if I'm allowed to use the name OI. I would use this image for myself, but could share with others, too. Perhaps I will upload it to my Google Drive. I had read about Distribution Constructor. But have no experience with it so far. So I'm asking for a guide how to use this tool to create my own image of OI. I think I will pull packages from OI's repo but not build anything myself if it's possible. What I wanted to do is nothing other than remastering OI. Remastering a distro is what we do very regular on Linux. We have tools to do this, e.g: https://github.com/MX-Linux/mx-snapshot and https://github.com/MX-Linux/mx-remaster I think Distribution Constructor is the equivalent tool on OI. Correct me if I'm wrong. The packages listed other than build-essential is for building Pale Moon. Yes, Pale Moon again. Your project refused to package it. Atenian200 after the clash with you also no longer provide prebuilt binary. The last version he provided is here: https://forum.palemoon.org/viewtopic.php?f=40=24613 which is a very outdated one. If someone wanted to get Pale Moon, they have to compile from source. OI currently has problems with my UEFI firmware. I can only run OI as a live usb but the installed OI I still keep on my SSD is unable to boot. Everything I did is seeking for a workaround for this: a live system with all of the tools needed. I'm going to provide up to date prebuilt binary of Pale Moon. Of course, via my Google Drive. But it's all cheap talks if I can't run OI itself. I used to think about cross compile from Linux. But I can only has the C cross compiler working. Everything C++ failed. Cross compiling a complex software like Pale Moon also means asking for troubles. On Sun, 17 Jan 2021 00:14:51 +0700 Adam Števko wrote > Hello, > > out or curiosity, what exactly is the point and added of your proposed fork? > Those packages can be easily installed any time after installing OI. > > I am not sure which exact changes were rejected, but if your raise a > discussion and explain clearly why they are needed, OI developers are more > than happy to accept. > > So, instead of forking and creating a “new distribution”, further > fragmenting the illumos distribution market, cooperate and help us improve > the existing project. There are lot of gaps where improvements are needed > and extra manpower is more than welcome. At the end, I can’t tell you want > to do, but can try and nicely ask you to collaborate. Please, collaborate > with OI team to improve the current experience, more people will benefit > from it! > > P.S: Keeping python-27 around is quite dangerous as the upstream ended any > kind of support of Python 2.x and without proper experience you are just put > potential users in danger. > > Thanks for understanding, > Adam > > > > > On 16 Jan 2021, at 11:02, Hung Nguyen Gia via oi-dev > > wrote: > > > > Someone on this list challenged me of forking OpenIndiana in order for my > > changes to be accepted. This is exactly what I'm going to do now. But I > > will do it moderately, according to my skills. > > > > I wanted to build something like in the title. > > > > It's the normal desktop OI plus the following packages: > > > > build-essential > > cmake > > ninja > > meson > > yasm > > autoconf-213 > > header-audio > > sunpro > > motif > > python-27 > > > > More packages would be included in the future, if needed. > > > > My computer power doesn't allow me to build everything myself, so I think > > I will just pull the packages from OI repo. > > > > The goal is to have a live ISO/USB images contain these additional > > packages. > > > > I have come across this wiki: > > > > http://docs.openindiana.org/dev/distribution-constructor/ > > > > But it's still not very clear to me. Any help would be appreciated. > > > > ___ > > oi-dev mailing list > > oi-...@openindiana.org > > https://openindiana.org/mailman/listinfo/oi-dev > ___ openindiana-discuss mailing list
