-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anyone know if this guide still works for noble? #61
Comments
This tutorial also last updates two years ago, but it still works. Even little complicated, you just need change it into Noble. I'd using this tutorial and change the value from Jammy into Noble. |
I also have used this tutorial and had to change some settings in the build.sh, chroot._build.sh and my config.sh file. |
You had block an Snapd installation with APT rule look like what Linux Mint do ? And you know, Ubiquity are still good even now Ubuntu had no more cares and priority new installer than improve what the best thing ever they develop and make user satisfied. And I think this original repo are being olds and may incompatible with newest LTS version or incompatible with Ubuntu Devel (rolling version of Ubuntu).
Copy/Clone this repo by importing into your GitHub or whatever Git platform you had use and make some changes. Don't forget to add credits from original repo and always check your own cloned repo. |
Everything works fine until |
I had changed this in the chroot_build.sh file to fix that issue. I changed it to systemd-resolved and that fixes that. |
I see, but how did you manage |
Well, why just change "resolvconf" into "systemd-resolvd" instead ? So, you type
|
Well, I figured it out at last, just left out the |
I found I don't have internet still, I tried remarking the line out, can I get clarification on what finally worked as no one says change, line 149 to such and such to make this work. Please, PLEASE if anyone has the answer to getting this to build with network working share it as I've been stuck for 3 days and found this script last night only to have it still not work, keeping in mind I am building ubuntu-cinnamon, I am about to do a stock Ubuntu to see if that behaves, but I really don't want Gnome. ----------------Another issue with cinnamon that should be checked for and excluded in the script so it doesn't abort ------- so I did the following changes to make that work for me:
|
Also is there a way to make the script pick defaults instead of having to wait around to pick locales etc, I'd like to automate it with the defaults and be able to come back to a ISO not a prompt for languages. |
The GID 999 isn't an issue, I just built ubuntu 24.04 fine and the network works with the line sorry about messing up the thread, but I am on a mission today with very little sleep. -EDIT- YES that worked, it's 400mb bigger, but to have internet again is a BIG plus, thanks for this script; Edit your config.sh;
I'd still love to have it automate defaults for locale's etc, I was thinking of trying: Edit: chroot_build.sh:-
That will stop the chroot from asking questions, worked perfect to make a silent build with no interaction. -EDIT- I am also going to make it cache the apt archives, so you can build multiple versions to test improvements/changes and it doesn't have to hammer the server, can just grab the updated ones, it's as simple as copying a folder in after debootstrap and copying it out before squishfs cleans it up. -EDIT- I added the cache, but as I can not copy lock file it causes an error and the script aborts unless I remark out the set options at the top, I could possible change it to rsync, but as it is I am happy with, I'll start to make my respin on this base now as using Penguins Eggs on Ubuntu 24.04 or Linux Mint v22 is still problematic (for now), Calamares isn't able to partition the installation drive then rsync fails as output isn't ready to write to. -EDIT- In the past I used to use Xephyr to setup a remote display to edit the chroot via the GUI, but modern OS's don't work well like that. |
And it's still in the process of being updated; at the moment, I'm working on All help (issues and PR) is very welcome. |
I'm working on Secure Boot and the new noble LTS. |
I could help you for pull request for new `noble`.
I'm also working for my own guide which inspired from your guide.
…On Sat, Sep 7, 2024, 05:55 Marcos Tischer Vallim ***@***.***> wrote:
Hi, first, thanks a lot for this guide, I just have one simple question,
anyone know if this still works on noble desktop? I've been using cubic for
my images so far, but unfortunately it works less than optimal for noble.
This tutorial also last updates two years ago, but it still works. Even
little complicated, you just need change it into Noble. I'd using this
tutorial and change the value from Jammy into Noble.
@Runa-Chin <https://github.com/Runa-Chin>,
And it's still in the process of being updated; at the moment, I'm working
on Secure Boot and the new noble LTS.
All help (issues and PR) is very welcome.
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZA5HSL7KRH75RDIEUBFDRTZVIXFRAVCNFSM6AAAAABGX2PX7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUHEYTIOJWGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@Runa-Chin and @tertitten74, Launched: https://mvallim.github.io/live-custom-ubuntu-from-scratch/ |
I keep failing at this step after moving the image folder Compress the chroot After everything has been installed and preconfigured in the chrooted environment, we need to generate an image of everything that was done by following the next steps in the build environment. I follow the guide to the letter, but still it fails. For me as I continue after those steps it fails when I'm supposed to do this step |
Hi,
I have just updated all the steps and scripts.
It is very important to follow all the steps if you are doing it
step-by-step.
Since you didn't send any error logs, I believe you may have skipped a
step, which is why you are encountering an error.
Best regards,
…On Tue, Sep 10, 2024 at 1:24 PM FocusPoint Linux ***@***.***> wrote:
I keep failing at this step after moving the image folder
Compress the chroot
After everything has been installed and preconfigured in the chrooted
environment, we need to generate an image of everything that was done by
following the next steps in the build environment.
I follow the guide to the letter, but still it fails. For me as I continue
after those steps it fails when I'm supposed to do this step
sudo mksquashfs chroot image/casper/filesystem.squashfs
-noappend -no-duplicates -no-recovery
-wildcards
-comp xz -b 1M -Xdict-size 100%
-e "var/cache/apt/archives/
*" -e "root/*"
-e "root/.
*" -e "tmp/*"
-e "tmp/.*"
-e "swapfile"
It simply gives me an error that the image folder does not exist, or file
does not exist, it's not entirely clear from the error, but it complains
about something that does not exist.
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AETF3MJBJ7DAO3IMOYUE6QLZV4MLBAVCNFSM6AAAAABGX2PX7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGQYTSNJUG4>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***
com>
|
Hi, first, thanks a lot for this guide, I just have one simple question, anyone know if this still works on noble desktop?
I've been using cubic for my images so far, but unfortunately it works less than optimal for noble.
The text was updated successfully, but these errors were encountered: